Open APIs

 View Only
Back to discussions
Expand all | Collapse all

TMF620 Product Offering Resource Relationship Cardinality to Service Candidate does not match SID

  • 1.  TMF620 Product Offering Resource Relationship Cardinality to Service Candidate does not match SID

    Posted Jul 20, 2023 21:41

    I have noticed that the TMF620 OpenAPI specification for the product offering resource only allows a maximum of one service candidate (via the ServiceCandidateRef) , whereas the TMF SID defines that there should be many service candidates. There should be a one to many relationship between product offering and service candidate. Can the TMF620 OpenAPI spec be updated to align with the SID?

    Richard Loo

    Telstra



    ------------------------------
    Richard Loo
    Telstra Corporation
    ------------------------------


  • 2.  RE: TMF620 Product Offering Resource Relationship Cardinality to Service Candidate does not match SID

    Posted Jul 21, 2023 10:31

    Hi Richard

    It's a bit late to make such a change, TMF620 is frozen for final review and I'm reluctant to ask for such a change.

    The truth is that I have never understood the meaning of service and resource candidates, and I even agitated for their removal (from both the API model and the SID). My initiative was rejected. The mapping between the BSS and OSS view is done at any rate at the ProductSpecification level, where you have a list of implementing service and resource specs.



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



Related Content