A Service Characteristic has a name value pair, and a list of them can very well describe the service schema. Then what does ServiceSpecification do?
"service": {
"@type": "Service",
"state": "active",
"serviceType": "CFS",
"serviceCharacteristic": [
{
"id": "452-gh6",
"name": "vCPE",
"valueType": "object",
"value": {
"@type": "vCPE",
"@schemaLocation": "http://nbi/api/v4/serviceSpecification/ONAPvCPE_Spec/specificationInputSchema",
"vCPE_IP": "193.218.236.21",
"MaxTxRate": 300,
"TransmitPower": "11 dBm",
"maxTream": "OFF"
}
}
],
"serviceSpecification": {
"@type": "ONAPServiceSpecificationRef",
"@schemaLocation": "http://my.schema/ONAPServiceSpecificationRef.json",
"id": "ONAPvCPE_Spec",
"href": "http://../serviceSpecification/ONAPvCPE_Spec",
"name": "vCPE",
"version": "1",
"invariantUUID": "456-852-357",
"toscaModelURL": "http//..."
}
In the above example from the TM Forum 641 document, what would the schema specified in the serviceSpecification look like? It is complicated by the fact that the schema url
http://nbi/api/v4/serviceSpecification/ONAPvCPE_Spec/specificationInputSchema is a non-existant url, is there somewhere I can find a real world example of how the service specification looks like?
------------------------------
Kannan Jayaprakasam
TO BE VERIFIED
------------------------------