Yes, Ravi, it should probably say Swagger/OAS, or have an explicit distinction between v4 (Swagger) and v5 (OAS).
------------------------------
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.
------------------------------
Original Message:
Sent: Mar 08, 2024 07:05
From: Ravi Pendurty
Subject: 641 and OpenAPI
Thank you Olivier. I could see that the v5 are in OAS format, though the name is a bit misleading. Ex:
Regards,
Ravi
------------------------------
Ravi Pendurty
TO BE VERIFIED
Original Message:
Sent: Mar 08, 2024 05:30
From: olivier arnaud
Subject: 641 and OpenAPI
Hi Ravi
The latest status is on the Open API Table 60+ Open APIs tried, tested and de-risked - TM Forum.
All TMF API in v5 are generated with Open API Specification format v3 (so no more with swagger v2). To my knowledge, the existing v4 TMF API will stay with swagger v2 format.
------------------------------
olivier arnaud
Orange
Original Message:
Sent: Mar 07, 2024 00:46
From: Ravi Pendurty
Subject: 641 and OpenAPI
Hi, What is the status with availability of OpenAPI files for the different TMF specifications? Is there a plan to provide Openapi files along with the swagger files for the respective TMF specs or we just use the swagger editor and convert the available JSON files to Openapi format?
Regards,
Ravi
------------------------------
Ravi Pendurty
TO BE VERIFIED
Original Message:
Sent: Dec 04, 2022 08:48
From: Jonathan Goldberg
Subject: 641 and OpenAPI
The update to OAS 3 (Open API v5) is an ongoing effort. In fact we have a dedicated spec-jam this week as a result of which we hope additional APIs will be published.
I'm not sure if TMF641 is one of these, I don't have the full list. I'll be the wiser in the next few days if I get to see the plan.
Watch this space (and send me a reminder if you don't hear from me).
------------------------------
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.
Original Message:
Sent: Dec 02, 2022 12:40
From: Lynn Dueck
Subject: 641 and OpenAPI
Looking at version 4.0.1 of the TMF641 Service Ordering specification, it is still swagger 2.0 and has not yet been converted to openAPI 3.0.1.
Are there plans to update this to an openapi spec and if so is there a timeline when this will be completed?
thanks
Lynn
------------------------------
Lynn Dueck
Oracle Corporation
------------------------------