Hi Markus, Igor, and all
Please note that all the TMF Open APIs assets continue to be published as Swagger 2.0. The Open API team is working on an upgrade path to Swagger (OAS) 3.0, not sure when this will come to fruition in published APIs.
Both TMF641 Service Order and TMF652 Resource Order have been published recently as beta, on the API beta page
here. Suggest you take a look and see if they meet your needs (I'm afraid I did not look at the schemas).
But yes you are correct that the JIRA is still open, I imagine it will take time for the updated external ID pattern to become adopted across the full list of APIs.
------------------------------
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: Jun 06, 2019 10:49
From: Markus Schmalzried
Subject: Resource Order Management API - Swagger / API Spec Difference
Hi Jonathan
I currently have the same problem with tmf652 and the outdated swagger-file. We are considering to use tmf652 in the near future for ordering gigabit lines and therefore I updated the swagger-file to the current pdf specification.
Perhaps you can take a look at the attached swagger-file (I added an openApi v3 version as well) and replace the current version. I really cannot imagine that anybody can work with the current public version of the swagger-file :)
Thanks in advance
------------------------------
Markus Schmalzried
Compax Software Development
Original Message:
Sent: Apr 29, 2019 10:56
From: Andrew Lamb
Subject: Resource Order Management API - Swagger / API Spec Difference
Throughout the API Spec the attribute "ExternalID" is used, however when implementing the API with the Swagger definition it is named "CorelatioID".
Please, can anyone advise which is the correct attribute name?
------------------------------
Andrew Lamb
KCOM Group PLC
------------------------------