That's great, thanks Matthieu.
Original Message:
Sent: Oct 09, 2024 03:35
From: Matthieu Hattab
Subject: Making TMF Optional OpenApi attribute required
The conformance requirement guide tells what is mandatory at resource or attribute level. That's the only requirement to pass the conformance.
any element that is optional will not be tested, so if you make one element mandatory, it does't concern conformance.
also, if you add resource/attributes, they will not be tested.
------------------------------
Kind regards,
Matthieu Hattab
Lyse Platform
------------------------------
Original Message:
Sent: Oct 08, 2024 10:22
From: Mohammad Obeidat
Subject: Making TMF Optional OpenApi attribute required
Thanks Matthieu Hattab,
Let me provide a use case: in Party Management API (TMF 632), "POST /individual" which used to creates an Individual; the mandatory fields are "givenName" and "familyName" only, but in some countries, you cannot create a party without identity (individualIdentification.identificationType and individualIdentification.identificationId)
So in this case you have to make the individualIdentification.identificationType and individualIdentification.identificationId mandatory attributes!
The concern is: if this change of making optional fields as mandatory will cause a CTK failure or not?
------------------------------
Mohammad Obeidat
Leading Point
Original Message:
Sent: Oct 07, 2024 10:32
From: Matthieu Hattab
Subject: Making TMF Optional OpenApi attribute required
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