It doesn't seem to be explicitly mentioned in the TMF633 spec 18.5, whether a ServiceCategoryRef is a
reference to actual ServiceCategory.
If Yes, then ServiceCategoryRef can be treated as transient representation of actual ServiceCategory Persistent entity, whenever needed. e.g. In RDBMS representation, ServiceCategory can have a FK(or mapping as needed by UC) to ServiceCatalog entity. However when the ServiceCatalog is fetched, the response would contain the <servicecategoryref> fields and omit the other ServiceCategory fields, which can be a on-the-fly transformation. </servicecategoryref>
Or
ServiceCategoryRef and ServiceCategory are 2 independent persistent entities? In that case we need to keep both the entities at-sync all the time; in other words their lifecycle is same?
The `href` attribute sample values suggest they both belong to different namespace as mentioned below :
- Servicecatalog.category is a ServiceCategoryRef[] and each ServiceCategoryRef is available at
/tmf-api/serviceCatalogManagement/v4/category
- ServiceCategory is available at
/tmf-api/serviceCatalogManagement/v4/serviceCategory
If they both represent the same entity, can we include `@referredType` in the sample representation(s)?
If they don't, which API describes the `category` namespace? Does it relate to ServiceCategory?
It'd be really helpful to be advised on the above.
------------------------------
Thanks,
D Basu
Architect
India
------------------------------