Good catch Denis. Although, having looked at many, many certifications of TMF620, I can tell you that "presence and proper constructs for the entities in data model" is often not enough to use the API (I know a vendor that has certified TMF620 but doesn't support: product offering bundle, recurring or usage prices, which is quite a gap in the telecom world)
Do your own due diligence and check conformance. You can also discuss with your vendor to change the API. We improve a TMF API with our BSS vendor several times a year. It benefits all parties.
Original Message:
Sent: Jan 13, 2025 09:51
From: Denis Kozlov
Subject: Place as Array vs Object in Product Inventory and Product Order API
In addition, i would point to this document https://www.tmforum.org/resources/technical-report/tr250-api-rest-conformance-guidelines-r15-5-1/
Although one may say it is quite old, but i find information there quite relevant and it is marked still as "current production version".
This paper outlines multiple conformance levels, where 1 and 2 are self-administered.
On page 9 there are criteria for the level 1, and among others we have "the support of the core data model of the API (presence and proper constructs for the entities in data model)". So clearly "proper constructs" principle is violated here.
------------------------------
Denis Kozlov
Telefonica Germany GmbH & Co. OHG
Original Message:
Sent: Jan 13, 2025 08:56
From: Aneesh Da
Subject: Place as Array vs Object in Product Inventory and Product Order API
Thank you @Denis Kozlov - I was also of the same opinion that this is not in compliance. But the API Provider claims that their API is already certified and do not accept to change their implementation.
TMForum should make sure that CTK is aligned and make sure to test what conformance profile preaches.
What is the process to report concerns about already certified APIs? How can I get some attention on this?
------------------------------
Aneesh Da
Infosys
Original Message:
Sent: Jan 13, 2025 03:27
From: Denis Kozlov
Subject: Place as Array vs Object in Product Inventory and Product Order API
CTK will not catch this issue as it only checks mandatory attributes as far as I can see, here is an excerpt from underlying postman collection used within CTK:

But conformance guide is very clear about that

So yes, implementation of the API with "place" defined as "object" is not compliant with TMF 622.
------------------------------
Denis Kozlov
Telefonica Germany GmbH & Co. OHG
Original Message:
Sent: Jan 12, 2025 21:31
From: Aneesh Da
Subject: Place as Array vs Object in Product Inventory and Product Order API
As per the API Documentation for TMF-622 and TMF 637, place is represented as an Array.

But as part of implementation the API provider has implemented place as an Object. Snippet of the sample payload is as below:

Is this an accepted implementation? Is the Conformance Test Kit capable of highlighting such deviations?
------------------------------
Aneesh D
Infosys
------------------------------