Hi Andrew
Thanks for your alertness in pointing out this inconsistency.
We are now working through a process whereby both spec document and swagger file will be generated from the same common sources, thus eliminating such inconsistencies. For R18.5 this was done for some APIs in Service domain, and we are continuing this for R19.0 with additional APIs in Product and Customer domains - the Resource domain is not in the current scope and will hopefully be addressed in a future release.
I have opened a JIRA issue
https://projects.tmforum.org/jira/browse/AP-1294 that references your specific concern, and suggests to align on a single ExternalID across all the APIs that need this concept.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
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
------------------------------