Hi Igor
The Open API model is a deliberate simplification of the SID, using patterns such as collapsing class hierarchies, consolidating entities, omitting attributes and relationships, and more.
In addition, the Open API model is just that, a model of the API payload. It does not necessarily represent the underlying persisted data model, for example.
Specifically for the characteristic model (used in catalogs of Product, Service, Resource, and elsewhere), it was decided not to make Characteristic a separately managed resource. This does not mean that in your persistence model and your API implementation you would repeat Characteristic - you can certainly re-use the same Characteristic in multiple specs, perhaps by ensuring that the Characteristic.name is globally unique.
The ValueUse entity is intended to allow restriction of the characteristic values in context. For example, suppose we have a Characteristic named
downstreamBandwidth, used in a Product Spec for
ADSL. This Characteristic might have a set of CharacteristicValues such as
10Mbps,
100Mbps,
200Mbps. Now when the
ADSL spec is offered for sale in a general Product Offering, all these values might be valid and selectable at ordering time (with corresponding impact on price). But when offered for sale in (say) a
Student Broadband offering, we might allow only
10Mbps - the ValueUse entity on Offering would have only one entry in this case, for 10Mbps.
Hope this helps, feel free to get back to me if you need additional clarification.
Hope it helps
------------------------------
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: Oct 07, 2019 11:26
From: Igor Veliev
Subject: Product Characteristics: TMF 620 vs GB922 Product
------------------------------
Igor Veliev
Netcracker Technology
------------------------------