Dan thanks for raising this. Strictly speaking, your observation applies to the embedded Service entity, so we should raise it against TMF638 Service Inventory.
I personally am not happy with this category String field. In catalog APIs, we have a full Category model with trees of categories and subcategories. Having a category property that doesn't relate to the Category model can be confusing.
Also the serviceType property is not well-defined, and the example does not shed much light on this.
I'm opening a JIRA for discussion within the Open API team.
------------------------------
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: Sep 12, 2023 00:24
From: Dan d'Albuquerque
Subject: Discrepancy in TMF641 Service Order category/serviceType fields
Hi All
The TMF641 SOM API seems to suggest that the category field is used to determine whether the Service Order is for a CFS or RFS, yet the example Service resource representation has this value stored in the serviceType field as below. Is the example incorrect? Thanks in advance!
#General
------------------------------
Dan d'Albuquerque
Individual
------------------------------