Open APIs

TMF620: Differences between Resource Attribute Conformance specifications

  • 1.  TMF620: Differences between Resource Attribute Conformance specifications

    TM Forum Member
    Posted Nov 30, 2020 16:01
    Edited by Richard Williams Nov 30, 2020 17:05
    Sorry, this is duplicate post because it didn't appear on the discussion board for several hours. Please respond to my other post instead!

    TMF620B_Product_Catalog_Management_Conformance _Profile_R19.0.0 document section 3 includes tables for mandatory & optional attributes for each resource.
    But these don't always seem to match the rules.yaml, which I thought was the master definition of rules.
    For example, for the Category resource, rules.yaml defines:
    mandatory in post:
    - name
    But the Conformance Profile document (section 3.7) defines:
    id M (in response messages)
    href M (in response messages)
    lastUpdate M (in response messages)
    name M
    lifecycleStatus M (in response messages)

    it seems the Conformance Profile implies that Category.name is mandatory in all operations, whereas the rules.yaml only makes it mandatory in post operation.
    Also, where does the rule definition "mandatory in response messages" for id, href, lastUpdate and lifecycleStatus come from, since these aren't described in the rules.yaml?

    Sorry, this is duplicate post because it didn't appear on the discussion board for several hours. Please respond to my other post instead!

    Many thanks,

    Richard

    ------------------------------
    Richard Williams
    Oracle Corporation
    ------------------------------