Hello Ludovic,
Thanks for your reply.
From your feedback, it seems to be valid that we can create a supportingService together with the head service from TMF640.
Looking in the resource model from the TMF640 spec document (v18), I see only "ServiceRef" on the supportingService relationship.
Wouldn't it make sense to define it there with a different name (ref or service itself)?
Just a suggestion so that we can have a better understanding on the valid use-cases.
Another question, when performing a GET with TMF640, would it be possible to expose the supportingResource characteristics or, also in this case, only the reference ID?
------------------------------
Carlos Portela
Proximus SA
------------------------------
Original Message:
Sent: Apr 02, 2020 11:28
From: Ludovic Robert
Subject: TMF640 - Understanding the use of 'supportingService'
Hello Carlos,
This is still on the to-do list for the examples. This is always the trickest part to deliver good examples ;)
Regarding your questions
1) Yes. Supporting resource will be present...but ....only as a reference and not by value. So you can indicate resource id (from inventory) to used for supporting the service but no request resource creation.
2) Yes. It should be in TMF641 v4.0 release.
Hope it helps
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
Original Message:
Sent: Mar 29, 2020 18:22
From: Carlos Portela
Subject: TMF640 - Understanding the use of 'supportingService'
Hello Ludovic,
Do you have any feedback on your CR for adding this example? I've had a look on the new version of the TMF640 Spec (18.5.1) but I couldn't find it.
I have two additional questions on this point:
1) Would it make sense to follow this same approach for the supportingResource? I mean, could it be possible to create resources behind the service directly on the same request?
2) Could we apply it (creating supportingService/supportingResource) also for TMF641?
Regards
------------------------------
Carlos Portela
Solution Architect
Proximus SA
Original Message:
Sent: Aug 29, 2018 09:03
From: Ludovic Robert
Subject: TMF640 - Understanding the use of 'supportingService'
Yes, I think the better is to add an example.
But in order to do this, my recommendation is to log a CR in Jira for this API (suggesting to add an example based on 'embedded service description). It will allow to get feedback from the API team, and will be in the backlog for this API next release.
Ludovic
------------------------------
Ludovic Robert
Orange
Original Message:
Sent: Aug 29, 2018 03:31
From: Abdul Majid Hussain
Subject: TMF640 - Understanding the use of 'supportingService'
Thanks Ludovic.
How do we document these understanding around 'supportingService' so that whoever implements TMF640, does that in consistent manner rather than leaving it for open interpretation?
Can we update the API document with different examples?
------------------------------
Abdul Majid Hussain
Telstra Corporation
Original Message:
Sent: Aug 29, 2018 03:05
From: Ludovic Robert
Subject: TMF640 - Understanding the use of 'supportingService'
Hello Abdul,
My feedback: I share the same interpretation than you for the use of supportingService so related to you question I will assume you can do this way. It means than it allows through one service creation request in fact to create a service hierarchy with a compositeService and an array of atomicService.
Best regards
Ludovic
------------------------------
Ludovic Robert
Orange
Original Message:
Sent: Aug 28, 2018 03:37
From: Abdul Majid Hussain
Subject: TMF640 - Understanding the use of 'supportingService'
TMF640 API Document (Release 15.5.1) describes the usage of supportingService as
"supportingService":[
{
"id": "59",
"href":" http://server:port/inventoryApi/service/59"
…. May contain the fully embedded service or only an hyperlink
}],
Our interpretation of the documentation of supportingService is as given below,
- I can provide the hyperlink of another service instance which act as a supporting service.
- I can embed the full details of another service instance (retrieved using GET operation) which act as a supporting service.
- Since there is no relationship type attribute in the supportingService block, the supportingService only represents the parent child relationship (vertical relationship).
Question: Can we use the supportingService block in the TMF640 API to create a supporting service along with the primary service in the same TMF640 request? i.e Can I embed the service create request of the supporting serivce by providing the request details under the supportingservice block.
Example:
{"name": "Mobile",
"state": "active",
"serviceSpecification": {
"href": ".../serviceSpecification/Mobile/11"
},
"supportingService": [
{
"name": "Data",
"state": "active",
"serviceSpecification": {
"href": ".../serviceSpecification/Data/12"
},
"serviceCharacteristic": [
{
"name": "Limit",
"value": "1 GB"
}
]
}
],
"serviceCharacteristic": [
{
"name": "MSISDN",
"value": "0123456789"
}
]
}
------------------------------
Abdul Majid Hussain
Telstra Corporation
------------------------------