Open APIs

Hello, 
I'm part of development team that maintain existing telecom subsystem and we are completely new to TMForum, and we are interested in implementing TMF632 Party Management Api V5.0.0 in the system. But we are facing a case where the telecom vendor is forced by legal authorities in its country to hold a specific data for each party that we found in TMF632 schema attributes but its marked as optional (for example: Individual Party model should have at least one Individual Identification of any type).

To pass this we made a validation that will make Apis fail unless these fields are provided which practically make the fields from "optional" to "required". Now we are fearing that doing such thing will make our implementation break TMF conformance.

By quick research I found that CTK contains a CHANGEME.json file that allow us to modify payloads thus, assumed that we can add the attributes we made as required when we are trying to get the certification. I hope to validate this assumption.
Thanks,

------------------------------
Hussein Anabtawi
Software Engineer @ Leading Point
------------------------------

you can read the the conformance requirement guide in the API table.

Many countries/regions have local requirements, if you wish to add new attributes and make them required, that's entirely up to you and how you define your API contract.

------------------------------
Kind regards,

Matthieu Hattab
Lyse Platform
------------------------------

Original Message:
Sent: Oct 01, 2024 07:48
From: Hussein Anabtawi
Subject: Making TMF Optional OpenApi attribute required

Hello, 
I'm part of development team that maintain existing telecom subsystem and we are completely new to TMForum, and we are interested in implementing TMF632 Party Management Api V5.0.0 in the system. But we are facing a case where the telecom vendor is forced by legal authorities in its country to hold a specific data for each party that we found in TMF632 schema attributes but its marked as optional (for example: Individual Party model should have at least one Individual Identification of any type).

To pass this we made a validation that will make Apis fail unless these fields are provided which practically make the fields from "optional" to "required". Now we are fearing that doing such thing will make our implementation break TMF conformance.

By quick research I found that CTK contains a CHANGEME.json file that allow us to modify payloads thus, assumed that we can add the attributes we made as required when we are trying to get the certification. I hope to validate this assumption.
Thanks,

------------------------------
Hussein Anabtawi
Software Engineer @ Leading Point
------------------------------