Open APIs

TMF 664 Resource Function Activation and Configuration Sample Jsons

  • 1.  TMF 664 Resource Function Activation and Configuration Sample Jsons

    TM Forum Member
    Posted 7 days ago

    Hi All,

    I want to implement TMF 664 for Resource Function Activation and Configuration. I am referring the User Guide and GitHub JSON for a Resource Function resource ID for  PATCH request.  For a PATCH request for a resource, will the JSON tags be present which are applicable at "ResourceRefOrValue" or the tags of "ResourceFunction" ? Currently I see the JSON in PATCH request has all possible tags from both "ResourceRefOrValue" and "ResourceFunction"  which is not clear to me. For e.g. Can the JSON possibly contain both the tags at same level of hierarchy,  "endOperatingDate" as well as "functionType" where "endOperatingDate" is a parameter of "ResourceRefOrValue" and "functionType"  is a parameter of "ResourceFunction"  ? As well as having the "name", "description" and "category" which belong to both "ResourceRefOrValue" and "ResourceFunction" which again creates doubt about the correct class.

    Is my understanding correct, if I say that using @ type, we can specify the type of object being passed as parameter (Id) in URL  PATH ? And the JSON will contain tags only applicable to the type of object being passed. So as a given time, the JSON attributes will contain the tags of either "ResourceRefOrValue"  or of "ResourceFunction" ?

    Similarily, the JSON keys "activationFeature" and "connectivity" that appear at the same level of hierarchy together in a PATCH request for a resource, is hard to interpret if the @type is "ResourceFunction". Any help to clear my understanding will be appreciated.

    I would like to get some sample JSONs with sample values which anyone of you might have used for any of PUT/PATCH/POST request for RF Resource Function.


    Thanks & Regards,



    ------------------------------
    Sangita Agarwal
    Tech Mahindra Limited
    ------------------------------