Open APIs

Hello, 

I appreciate if somebody could clarify for me the current approach for PATCH of multi-value attribute modification.

I am looking into a TMF630_REST_API_Design_Guidelines_Part_1_R14.5.1 specification and I see that multi-value attribute modification is achieved by specification of 2 additional attributes in a request payload, op and path e.g: 
 
However,  when I look into  TMF632 API swagger there are no such attributes like "op", "path": TMF632_PartyManagement/TMF632-Party-v4.0.0.swagger.json at master · tmforum-apis/TMF632_PartyManagement

and there is no such information in TMF632 specification v4.0.1 either.

What is the current approach for multi-value attribute modification for me it is a wider topic how to add, remove items in arrays?

Could I ask for help in this area, please ?

Best Regards,

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Hi Marcin
The tooling that we used to generate PATCH in swaggers creates contracts for PATCH merge, not for JSON patch (the one with op, path and value) :(
This is rather unfortunate, and has been fixed for the version 5 tooling. There is an open CR for fixing also in v4 but I don't know when this will be addressed.
You can of course extend the swagger for your own implementation.
Hope it helps.

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Thank you Jonathan for the clarification. I got what I wanted know.

Best Regards,
Marcin

------------------------------
Marcin Gizka
TO BE VERIFIED
------------------------------

Original Message:
Sent: Mar 18, 2022 09:23
From: Jonathan Goldberg
Subject: PATCH modify multi-value attribute

Hi Marcin
The tooling that we used to generate PATCH in swaggers creates contracts for PATCH merge, not for JSON patch (the one with op, path and value) :(
This is rather unfortunate, and has been fixed for the version 5 tooling. There is an open CR for fixing also in v4 but I don't know when this will be addressed.
You can of course extend the swagger for your own implementation.
Hope it helps.

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------