Open APIs

 View Only

  • 1.  TMF633 and JSON patch

    Posted May 31, 2022 09:05
    Hi

    Why does the TMF633 specification not follow the standard document structure for JSON PATCH?

    For example, the PATCH endpoint for service specification is found here. It uses just the JSON structure of the service specification instead the standard structure of JSON PATCH found here.

    Thanks a lot,
    Marco

    ------------------------------
    Marco Creola
    Swisscom (Schweiz) AG
    ------------------------------


  • 2.  RE: TMF633 and JSON patch
    Best Answer

    Posted May 31, 2022 09:12
    Hi Marco
    The Open APIs, at least in principle, should support PATCH Merge and JSON PATCH - of course it is a matter of implementation.
    Currently, the tooling that we use to generate swagger and user guides creates PATCH Merge signatures, rather than JSON PATCH.
    I believe that in the tooling being developed for V5 API versions this is taken care of, so that JSON PATCH is explicitly expressed in the API swagger file.

    ------------------------------
    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.
    ------------------------------



  • 3.  RE: TMF633 and JSON patch

    Posted May 31, 2022 09:21
    Hi Jonathan

    Thanks a lot for your reply.

    Yes, you are right. I missed the support for PATCH merge.

    Good to see that this will be taken care of in V5 API.

    Regards,
    Marco

    ------------------------------
    Marco Creola
    Swisscom (Schweiz) AG
    ------------------------------

    Original Message


  • 4.  RE: TMF633 and JSON patch

    Posted Jan 24, 2026 05:39

    Hi Marco / Jonathan,

    We're hitting the same gap while still on TMF v4 (Swagger / OAS 2.0).

    We understand APIs can support both Merge Patch and JSON Patch (and JSON Patch Query per TMF630 Part 5), but in v4 the swagger typically models PATCH only as a merge-style "partial resource" schema. In OAS2, even if we list multiple consumes,  it effectively supports only one request body schema for that operation 

    For teams staying on v4, what's the recommended compliant approach to support JSON Patch as well



    ------------------------------
    Qasim Shah
    Vodafone Group
    ------------------------------

    Original Message


Related Content