Hi Frederic
As you correctly point out, in v5 Characteristic (and corresponding CharacteristicSpecificationValue) do not have the value property, since this is strongly-typed (using JSON basic types) in the various subclasses.
The API designers need to ensure that the subclasses are included into the published API Swagger/OAS yaml file, and to best of my knowledge this is being done. It's possible that early beta version yaml files were published without the subclasses, but I hope that as we near the publication deadline for the first batch of APIs that this will be done correctly.
------------------------------
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: Jul 26, 2023 03:48
From: Frederic Thise
Subject: Characteristic value for v5 APIs
Hi Guys,
I had a look at multiple v5 APIs (TMF 638, TMF 641 and TMF 701) and can't find the value property on the Characteristic types. I know that v5 changes value from the standard Any type to subTypes for boolean, Integer, String, Object, etc. but those are nowhere to be found in the yamls. I even generated the stubs from these 3 yamls to be sure and found nothing to hold a characteristic value.
Is there something still missing in those v5 APIs?
Best regards,
------------------------------
Frederic Thise
Proximus SA
------------------------------