Hello Supraja
Your point is valid and we probably need to fix the examples and/or the attribute description.
From my perspective, we should use serviceType to differentiate CFS/RFS (but implementation are free to specifiy additionnal value --> this is not defined as an enum in the API) and serviceCategory to classify service based on specific requirement (like Mobile, Internet, Mobile Access, etc...). Indeed there is a serviceCategory resource and we should leverage it to structure service specification.
Hope it helps,
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------
Original Message:
Sent: Oct 08, 2020 06:52
From: supraja chaduvula
Subject: ServiceRestriction serviceType in TMF641 specification R18.5.1
In ServiceRestriction(Service) sub-resource in TMF641 specification R18.5.1
category : description given as - A string. Is it a customer facing or resource facing service.
and
serviceType - description given as - A string. Business type of the service.
Below is the example provided in the specification in which serviceType is given as "CFS" and category is not mentioned.
But as per the category description is should be either CFS or RFS.
"service":
{
"@type": "vCPE",
"@schemaLocation": "http//my.schemas/vCpe.schema.json",
"state": "active",
"serviceType": "CFS",
}
Can we provide both the category and serviceType values or only one attribute(category/serviceType) needs to be mentioned.
please provide the significance of these attributes with examples.
#General
------------------------------
supraja chaduvula
Tata Consultancy Services
------------------------------