Great detective work Steve and all.
Not just is it OK to have local ID in array sub-elements, but in fact it is strongly recommended, to allow direct access (e.g. via JSON Patch) to array elements.
------------------------------
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 20, 2024 14:25
From: Steve Harrop
Subject: TMF651 - Agreement - TermOrCondition id reference
Hi,
With the help of Rohit/Abhi, we discussed this in TMF API Governance today. We concluded that the TMF651-Agreement API has an unmanaged entity (AgreementTermOrCondition) which has an id and (incorrectly) a href:
While it is ok to have a localised "id" (same as the Characteristic to the left of it) - which could just have localised numbers (1, 2, 3...) for differentiation, the presence of a "href" implies that it is fully "managed" ie: It has an independent TMF API - which it does not.
This is probably the result of allOf-ing the Addressable schema, but needs to be redone as just including an optional "id" instead. I have raised a TMF-JIRA for this (AP-5004).
------------------------------
Steve Harrop
Principal API/Integration Architect
Vodafone Group
------------------------------