Open APIs

 View Only
Expand all | Collapse all

OpenAPI Specification 3.0

  • 1.  OpenAPI Specification 3.0

    TM Forum Member
    Posted Apr 15, 2020 02:38
    Hi, Is any plan when TMF Open API will support openapi spec 3.0?
    As I know open api spec 3.0 was released at middle of 2017, so I think that 2020 it is right time to support it.

    ------------------------------
    Sergey N Lukin
    Deutsche Telekom (Tel-IT)
    ------------------------------


  • 2.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Apr 20, 2020 01:46
    Hi Sergey
    Preparation work continues within the Open API team in order to support OAS 3.0 - we definitely want to be there.
    Perhaps @Pierre Gauthier or @Joel Burgess​​ can give additional insights into progress.
    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: OpenAPI Specification 3.0

    Posted May 04, 2021 09:34
    Hello there. I am co-chair of the OpenAPI Initiative (OAI), as well as the Chief Evangelist at Postman -- I'd love to talk more about your migration from Swagger 2.0 to OpenAPI 3.0, as well as the role Postman collections are playing -- I notice you use both.  i have been playing with the APIs, and establishing a sandbox for using them without an actual implementation, via a public workspace.

    ------------------------------
    Kin Lane
    TO BE VERIFIED
    ------------------------------



  • 4.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted May 07, 2021 07:47
    Hi Kin,

    Thanks for your interest, the TMForum does extensively use Postman scripts as a "Conformance Test Kit" (CTK) for each TMF-API. We have a tool which generates this from the swagger + example payloads + a "conformance profile" (additional rules which cannot be reflected in swagger).

    Vendors who want to be "TMF API Certified" run the CTK against their own product. The CTK will exercise all swagger-defined mandatory operations, and assert any mandatory attributes or relationships are present in the associated responses. If your product survives these tests without a fail, it can be deemed to be compliant with that release of that API.

    Given that TMF APIs are quite lenient on mandatory operations/attributes/relationships - it can be debated whether this is a high or low "bar" - but it is at least an indication that the vendor/product are "on the same page".

    ------------------------------
    Stephen Harrop
    ------------------------------



  • 5.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted May 07, 2021 07:59
    Just a further point on the Swagger and OASv3 files. The TMF maintains a schema repository (distinct JSON files in GitHub) that act as masters to all entities used across the API catalog (think: ProductOffering, TroubleTicket, ShoppingCart...). With the aid of a high-level DSL to describe each API, the swagger file is then constructed by a tool that draws on this DSL and the repository. This ensures consistent design patterns and terminology are used across the catalog.

    As Jonathan mentioned above @Joel Burgess is working on a clean-room refresh of this tool that constructs the same in OASv3 - taking the opportunity to exploit some of the new features available. This is a large-scale exercise that is being tested on a small set of TMF (and MEF) APIs for evaluation before embarking on the catalog-wide rollout during this year.

    @Pierre Gauthier is the TMF Chief API Architect​​​ overseeing this.

    ------------------------------
    Stephen Harrop
    ------------------------------



  • 6.  RE: OpenAPI Specification 3.0

    Posted May 19, 2021 18:58
    Hello Stephen,

    Thanks for info on your process -- great to hear.

    Also great to hear on the OASv3 refresh -- please let us know if we can help. Maybe when ready, we can do a blog post on that OAI / OAS blog about your standard? Feel free to stay in touch -- happy to support.

    ------------------------------
    Kin Lane
    TO BE VERIFIED
    ------------------------------



  • 7.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Dec 23, 2022 20:55
    Hi Steve,

    Can you please share the github repository for schema of Open APIv3. Also where can I find any WIP artifacts for OASv3 work. Can you please share the team details that is working on this. Would like to explore if I could contribute to this effort.

    Regards
    Srinivas


    ------------------------------
    Srinivasa Vellanki
    Jio Platforms Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of my employer or TM Forum.
    ------------------------------



  • 8.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Aug 23, 2022 13:07
    Stephen if CTK is generated based on swagger why is that tmf 629 has discrepancy between swagger api specificatio vs what CTK fires?
    ex: There is no definition of /customer?name={} in swagger but CTK expects it to return successful response

    ------------------------------
    Vasanth Varma
    Verizon Communications
    ------------------------------



  • 9.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Aug 25, 2022 02:33
    It looks as if this was posted in error as a reply to an unrelated thread.
    Please continue the discussion on the new thread here: https://engage.tmforum.org/discussion/swagger-contract-not-matching-ctk-evaluation-ex-tmf-629-customer-management

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 10.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Mar 29, 2022 13:34
    Hi Jonathan,
    is there a roadmap with dates, when to expect OAS 3.x format beside the swagger 2.0 format?

    PS: Could not find any information on tmforum.org for this migration project. Is there a URL / page I missed?
    Thanks in advance

    ------------------------------
    Ludwig Ronny Eckardt
    T-Systems International Services GmbH
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 11.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Mar 30, 2022 02:24
    Hi Ludwig
    I'm afraid that it's still in progress, so we'll have to wait patiently.
    Sorry

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 12.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Dec 23, 2022 20:49
    Hi Jonathan,

    Any progress on any of the Open APIs complying with OAS3.x?

    Regards
    Srinivas

    ------------------------------
    Srinivasa Vellanki
    Jio Platforms Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of my employer or TM Forum.
    ------------------------------



  • 13.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Dec 25, 2022 02:49
    Answering both of your questions, Srinivas - happy holiday period:

    1. Regarding TMF Open APIs for OAS 3.x:  some API assets have already been published at v5, including OAS3.x support, here: https://projects.tmforum.org/wiki/pages/viewpage.action?pageId=128855518
    2. Regarding your question to Steve about Open API schemas, you first need to be a member of the Open API project. After you have joined the project, you'll need to ask @Henrique Rodrigues to give you access to the private GitHub repository holding the v5 work. If you want to contribute you'll also need to get up-to-speed with the new tooling, again Henrique might be able to assist here.

    Hope it helps



    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 14.  RE: OpenAPI Specification 3.0

    TM Forum Member
    Posted Dec 25, 2022 21:12
    Thank you Jonathan,  appreciate all the help.

    Will follow the next steps.

    Happy Holidays!!

    Regards
    Srinivas

    ------------------------------
    Srinivasa Vellanki
    Jio Platforms Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of my employer or TM Forum.
    ------------------------------