Open APIs

 View Only
  • 1.  633 - Service Candidate and Service Specification Association

    TM Forum Member
    Posted Oct 27, 2020 21:44
    Hi,

    As per the 633 v4.0 documentation , a service candidate can be associated to 0 or 1 specification as in below UML.



    But as per V4 conformance profile , the specification is marked as mandatory for a candidate . 

    Please let us know which one reflects the correct cardinality.

     cc: @Rati Mehrotra​​

    ------------------------------
    Uma Lakshman
    Telstra Corporation
    ------------------------------


  • 2.  RE: 633 - Service Candidate and Service Specification Association

    Posted Oct 28, 2020 01:01
    I guess the conformance profile is right and the diagram needs an update. Looking forward to read the answers from the experts/authors.

    ------------------------------
    Daniel Lauxtermann
    Glasfaser NordWest GmbH & Co .KG
    ------------------------------



  • 3.  RE: 633 - Service Candidate and Service Specification Association

    TM Forum Member
    Posted Oct 28, 2020 01:27
    Hi
    From a business perspective (according to my understanding anyway) it doesn't make sense to have a service candidate that does not point to a specification. Take for example this description from the SID model:

    A ServiceCandidate is an entity that makes a ServiceSpecification available to a catalog. A ServiceCandidate and its associated ServiceSpecification may be "published" (made visible) in any number of ServiceCatalogs, or in none. One ServiceSpecification can be composed of other ServiceSpecifications. These ServiceSpecifications may also be published.

    Having said that, also in the SID the association cardinality is actually 0..1.

    So it probably needs more thought and discussion within the API team, and perhaps with the SID leads, to clarify what is correct. @Cecile Ludwichowski and @Kamal Maghsoudlou might have what to say here.

    Hope it helps
    ​​

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



  • 4.  RE: 633 - Service Candidate and Service Specification Association

    TM Forum Member
    Posted Oct 29, 2020 19:02
    Thanks @Jonathan Goldberg, @Daniel Lauxtermann.

    I can see that ​​​​​the  API documentation recently checked into RAD has the updated diagram with a 1 to 1 relationship between candidate and specification which is in alignment with conformance profile. Will wait for the final release.


    ------------------------------
    Uma Lakshman
    Telstra Corporation
    ------------------------------