Hello Uma,
For 1 & 2 please consider swagger and conformance profile. The UML is informative and we have some isuue regarding cardinality. I checked for you the root yaml used for generation and in both case mentionned attributes are mandatory.
For 3 &4 we need to raise a Jira - Looking in other Service API seem that we have some divergence in feature mandatory representation. Globally service.feature has name and featureCharacteristic mandatory ; service.feature.featureCharacteristic has name and value.... But Service Inventory conformance profile mention also service.feature id as mandatory. We need probably an alignement there.
Not sure to understand point 5. - can you elaborate the issue (or directly raise a jira if you identified a doc issue).
Thanks
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------
Original Message:
Sent: Feb 10, 2021 20:22
From: Uma Lakshman
Subject: TM 645 V4- Documentation
Hi ,
Would like to understand your view on the below discrepancies noticed in TMF- 645 V4 documentation .
#
|
Description
|
Task
|
1
|
checkServiceQualification to checkServiceQualificationItem association in resource model is marked as 0 to * . As per conformance profile and swagger, this association is M
|
checkServiceQualification
|
2
|
queryServiceQualification to searchCriteria association in resource model is marked as 0 to * . As per conformance profile and swagger, this association is M
|
queryServiceQualification
|
3
|
Service.feature.name is mandatory as per swagger . Conformance profile doesn't have it marked as M
|
checkServiceQualification, queryServiceQualification
|
4
|
Conformance profile has name repeated as mandatory for featureRelationshsip .
As per the schema, only name and relationshipType are mandatory. Is there any additional attribute expected to be mandatory ?
|
checkServiceQualification, queryServiceQualification
|
5
|
Below sub resources are named in correctly in documentation . Not sure if this is a tooling issue
ConstraintRef relationship
ResourceRef relationship
ServiceCategoryRef relationship
ServiceSpecificationRef relationship
|
checkServiceQualification, queryServiceQualification
|
------------------------------
Thanks & Regards,
Uma Lakshman
Telstra Corporation
------------------------------