Hi all,
I understand there will be a new version of these APIs fairly soon. A couple of points that could be considered (if not already captured):
- TMF634 ResourceSpecification has an array of ResourceSpecRelationship, which has name, type and role relationships. I understand that "name" uniquely identifies the relationship, while "type" describes its behaviour. It would therefore be possible to have relationships with different names but the same type. However in TMF639 the ResourceRelationship is qualified by "type" and does not have a "name" field. I believe the ResourceRelationship should have a "name" to match the "name" in the specification.
- TMF639 ResourceRelationship has an array of ResourceRelationshipCharacteristic, allow attributes of the relationship to be captured, e.g. sequence. However, TMF634 does not provide modeling to define these characteristics.
- I see the inconsistencies between the various artefacts has already been noted and is planned to be addressed.
Is there a work-in-progress JSON available, to understand which areas of the model are changing in the next version?
Thanks,
Simon.
------------------------------
Simon Durrant
Amdocs Management Limited
------------------------------