Open APIs

Dear Community,

which PATCH syntaxes must definitely be implemented?

1. JSON Merge Patch as per RFC7396 and application/merge-patch+json
2. JSON PATCH as per RFC6902 and application/json-patch+json
3. JSON PATCH query as per TMF REST Guidelines Part 5 and application/json-patch-query+json

In other words: Would it be compliant to support only one syntax, e.g. only RFC7396?

Thank you and best regards,
Roland

Good question.

My understanding is that the conformance scripts use `application/json` as the header. In PATCH context is has been mentioned that this should be treated as like `application/merge-patch+json`.

So, I guess,

• You are required to support PATCH for partial updates.
• You can choose one of the standard PATCH syntaxes -typically application/merge-patch+json unless you have a specific reason to support others.
• You don't have to support all three.

------------------------------
Manu
------------------------------

Hi Manu,

thank you for sharing your view which matches mine. Even though this cannot be derived from TMF630/763, at least not with confidence.
Nevertheless, it's a practical advice, saving implementation and test effort.

I'll leave this topic open for a couple of days. Maybe others also share their views.

Best regards,
Roland

Note that using application/json is marked as deprecated in the V5 TMF630 (see the pre-production https://www.tmforum.org/resources/specifications/tmf630-rest-api-design-guidelines-5-0-0/) , i.e. it can still be used (and then must be handled as if it was applcation/merge-patch+json, as before), but in the next version (V6) this will be removed completely.