Thanks Jonanthan, Yes, i can see not other way either.
Unfortunate, be cause staying true to the version, means we have an agreed contract with either clients or suppliers.
I suppose what we'd need to do, is try as best to use the KeyValue pairs for dot releases 4.1, 4.2 etc, and then fold those into the next major release. e.g. 4.0, 5.0
so only the major releases would fully align to the TMF spec.
Thanks again
Marty
------------------------------
marty oliver
BT Group plc
------------------------------
Original Message:
Sent: Sep 18, 2021 14:22
From: Jonathan Goldberg
Subject: General Management of API's
Hi Marty
Welcome to the club.
Indeed, it does take time for change requests to be implemented in the TMF Open API, and there is no guarantee that every change request will actually be implemented.
I don't think there's any magic here - you need to decide that your implementation will be based on (say) v4.0 of a specific API, and then decide if and how to extend to meet your local requirements.
------------------------------
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: Sep 17, 2021 07:07
From: marty oliver
Subject: General Management of API's
If I was to adopt and implement an API, how do the incremental changes get adopted?
Does the party requesting the change have to submit for review and wait for adoption?
I'm concerned that if trying to get change to a core API take time, consumers will just branch the code for their local implementation
regard
Marty
------------------------------
marty oliver
BT Group plc
------------------------------