Open APIs

Hi Members/experts,

Within my company we have decided to make extensive use of TMF-669 (Party Role Management) with a number of sub-classes to suit our needs. When we try to refer to these Party Roles via the relatedParty lines across the various other TMFs we provide the "id" and "@referredType" required/mandatory attributes as you would expect to be needed. These two  "required" attributes for relatedParty seems to be common to all the TMFs we're using except for TMF-641 which for some reason additionally wants @type. Is this deliberate or a mistake? We have no intention to sub-class the relatedParty array itself so why does TMF-641 seem to want you to define "@type" : "relatedParty" ?

https://tmf-open-api-table-documents.s3.eu-west-1.amazonaws.com/OpenApiTable/4.1.0/swagger/TMF641-ServiceOrdering-v4.1.0.swagger.json

Thanks,

Jonathan

Hi Members/experts,

Within my company we have decided to make extensive use of TMF-669 (Party Role Management) with a number of sub-classes to suit our needs. When we try to refer to these Party Roles via the relatedParty lines across the various other TMFs we provide the "id" and "@referredType" required/mandatory attributes as you would expect to be needed. These two  "required" attributes for relatedParty seems to be common to all the TMFs we're using except for TMF-641 which for some reason additionally wants @type. Is this deliberate or a mistake? We have no intention to sub-class the relatedParty array itself so why does TMF-641 seem to want you to define "@type" : "relatedParty" ?

https://tmf-open-api-table-documents.s3.eu-west-1.amazonaws.com/OpenApiTable/4.1.0/swagger/TMF641-ServiceOrdering-v4.1.0.swagger.json

Thanks,

Jonathan

Hi Jonathan

I looked into this, it does seem to be an anomaly. The rules file that we use to generate swaggers for APIs has @type mandatory in relatedParty for TMF641, but not in other APIs.
I can open a defect report, but I'm not sure that there is priority for republishing v4 APIs.

Please note that in v5 APIs @type is mandatory in entities since it is used as a discriminator.

Hope it helps

Hi Members/experts,

Within my company we have decided to make extensive use of TMF-669 (Party Role Management) with a number of sub-classes to suit our needs. When we try to refer to these Party Roles via the relatedParty lines across the various other TMFs we provide the "id" and "@referredType" required/mandatory attributes as you would expect to be needed. These two  "required" attributes for relatedParty seems to be common to all the TMFs we're using except for TMF-641 which for some reason additionally wants @type. Is this deliberate or a mistake? We have no intention to sub-class the relatedParty array itself so why does TMF-641 seem to want you to define "@type" : "relatedParty" ?

https://tmf-open-api-table-documents.s3.eu-west-1.amazonaws.com/OpenApiTable/4.1.0/swagger/TMF641-ServiceOrdering-v4.1.0.swagger.json

Thanks,

Jonathan