Hi Dan
Regarding the ID, I think that the guideline text needs to be fixed, I have submitted a JIRA issue for this.
Regarding POST of versioned entity, this is indeed an unfortunate defect in our generated swaggers, also for this I have submitted a JIRA issue.
Thanks for your alertness
------------------------------
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: Nov 09, 2020 07:59
From: Kalpana HV
Subject: Business Identifier (mapping between OpenAPI and Frameworx)
I am also trying to understand this. Could some one please help.
@Adrienne Walcott, @Jonathan Goldberg could you please throw some light.
Best Regards,
------------------------------
Kalpana HV
Colt Technology Services
Original Message:
Sent: Nov 04, 2020 04:29
From: Dan d'Albuquerque
Subject: Business Identifier (mapping between OpenAPI and Frameworx)
Hi All
Does anyone know whether a CR has already been submitted for this?
Thanks
------------------------------
Dan d'Albuquerque
TO BE VERIFIED
Original Message:
Sent: Oct 29, 2020 05:24
From: Dan d'Albuquerque
Subject: Business Identifier (mapping between OpenAPI and Frameworx)
Hi All
I am trying to understand the mapping between the 'id' field within the OpenAPIs for the concrete entities and the 'ID' (business identifier) attribute within the SID model and physical data model. According to the OpenAPI design guidelines part 1 there is no mapping between the two. Hence how do you determine the business identifier?
The TMF630_REST_API_Design_Guidelines_Part_1_v4.0 states that the resource identifier (id) is not the Business Identifier (ID from SID) as follows:
Would it be possible to correct this specification to state that the resource identifier IS the business identifier?
Also, in the various OAS for Product/Service/Resource catalogs, a version field has been added to the OpenAPI to indicate entity version management for the lifecycle management. However, the POST operation definition does not allow the 'id' field to be supplied when creating new entity versions of the resources. Is this a mistake?
Thanks
Dan.
------------------------------
Dan d'Albuquerque
TO BE VERIFIED
------------------------------