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.
------------------------------