Open APIs

We want to use the Categories for ProductSpecifications.
Our Reference is the TMF620 Open API Specification in v5: Product Catalog Management API TMF620-v5.0.0

The ProductSpecification has the attribute category, which makes it possible to refer categories from the ProductSpecification.
But the Category Object itself, only has a reference to ProductOfferings and not ProductSpecifications.
This means we can only express ProductSpecification Categories in one direction, from ProductSpecification to Category and not from Category to ProductSpecification.

Is this correct or do I miss something?

Hi Florian

I believe that when the category hierarchy is used within the scope of the product catalog, it is meant to be a product offering catalog.

However, a category hierarchy may still be used for product specifications as well, hence the category (ref) pattern from the product spec.

Note that service/resource layers already have the specs added to the category pattern, so it is reasonable (perhaps for the product design process) to have a catalog of the product specs too (for consistency).

------------------------------
Dan d'Albuquerque
Individual
------------------------------

When you look at the product offerings and product specifications ressources, they have the exact same CategoryRef sub-resource definition.

Also, Category is a sub-resource for the Catalog resource. Catalog resource is not exclusive to product offerings. the API polymorphism allows entities in collections to inherit properties from a base entity. For example, a Product Catalog, a Ressource Catalog, a ProductSpec Catalog inherit properties from the base Catalog entity.

In the TMF620 user guide, page 28 says "catalogType = Type of this Catalog, like Product, Service, Resource, etc.)

It's a small defect in TMF620. The Category Resource should have a ProductSpecificationRef sub-resource.
You can just fix it yourself by adding a new sub-ressource.