Hi Nick
The purpose of a catalog is to expose catalog elements (this is true for Product Catalog TMF620, and also for Service and Resource catalogs).
Specifically for product catalog, one can imagine having multiple catalogs, perhaps for different sub-markets.
The catalog elements themselves can be exposed in multiple catalogs, so I would decide at authoring time whether or not (for example) to expose a Gaming Data offering in my Corporate Services catalog (perhaps not). It is optional to have multiple catalogs.
The point is that the catalog elements themselves, including categories, are thus independent of a particular catalog. Categories are a means for structured browsing/navigation through catalog elements, and this applies independently of which catalogs expose the elements.
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: Jul 07, 2020 11:49
From: Mykola Nilga
Subject: TMF 620 - What categories does List Categories operation list?
Hello,
Recently I was analyzing TMF 620 and figured out that the List Categories operation does not require catalog. First I thought that the operation list all categories in all catalogs, however, in the JSON example I see only root categories as standalone array elements. I also do see nested sub-categories in the categories elements, but I don't see them as standalone array elements.
With above in mind, am I right assuming that the operation lists only root categories from all catalogs? What's the purpose of such operation?
------------------------------
Nick Nilga
.NET Solutions Architect
Telenor Denmark
------------------------------