Open APIs

Expand all | Collapse all

TMF 633 Service candidate parent child relationship

  • 1.  TMF 633 Service candidate parent child relationship

    TM Forum Member
    Posted Jul 09, 2019 04:31
    ​Hi All,
    IN  TMF 633 how is parent child relationship represented in case of service candidate.
    Is the relationship Parent Service Candidate -> Child Service candidate invalid?
    How can a Service candidate inherit the characteristics of parent Service Candidate?

    ------------------------------
    Shino Jacob
    Infosys
    ------------------------------


  • 2.  RE: TMF 633 Service candidate parent child relationship

    TM Forum Member
    Posted Nov 12, 2019 11:21
    Even i am having this same concern.. someone please shed light on this..

    ------------------------------
    Thomas Tholath
    Infosys
    ------------------------------



  • 3.  RE: TMF 633 Service candidate parent child relationship

    TM Forum Member
    Posted Nov 13, 2019 01:31
    Hi
    Service Candidate (and Resource Candidate) are effectively placeholder classes, with no significant business meaning. They are simply intended to reflect the exposure of the underlying Service Specification (or Resource Specification) within a particular Catalog instance.
    The parent-child relationship (or any other relationship between Candidates) is expressed by the relationship between the Specifications, by ServiceSpecificationRelationship (or ResourceSpecificationRelationship).

    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: TMF 633 Service candidate parent child relationship

    TM Forum Member
    Posted 10 days ago
    Hello,
    Regarding relationship for service-candidates under TMF633, I'm assuming that a possible use-case is to have service-candidates being associated to a parent product-offering.
    In this sense, from modeling perspective, a product-offering in catalog from vendor-A is indeed offering a service-candidate from a related party vendor-B.
    Is this valid?



    ------------------------------
    Marcos Donato da Silva
    Ericsson Inc.
    ------------------------------



  • 5.  RE: TMF 633 Service candidate parent child relationship

    TM Forum Member
    Posted 8 days ago
    Hi Marcos
    Indeed the product offering has a reference to service and resource candidates, as documented in TMF620 Product Catalog Management.
    I suppose this allows the flexibility that you refer to in your use case. But the real link between the product and service domains is modeled at the specification level, where product specification has a link to the implementing service specification (and resource specification).

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



  • 6.  RE: TMF 633 Service candidate parent child relationship

    TM Forum Member
    Posted 6 days ago
    Hi Jonathan,
    Great, thanks a lot for your answers (you've been answering some of my questions along different posts recently).

    One thing that called my attention is that we have good complementary topics in other specs (e.g.: starting from TMF633,
    I could see referrences to TMF620, TMF630, TMF634, Data Types document, among others).
     After reading these additional specifications, the understanding of TMF633 itself improved a lot.

    My question is:
    Do we have a reference document/matrix that correlates the specifications?

    If we have it, it would be really hand to have a reference to this document added to every TMF spec document.
    If we don't have it, it's a suggestion.

    My feeling is that a link added on every spec to a mandatory reference it would help a lot new TMF users,
    that have as entrance door to the TMF world a given TMF spec itself (e.g.: TMF633 in my case) to gather
    complementary information.

    Thanks and Regards,
    Marcos.

    ------------------------------
    Marcos Donato da Silva
    Ericsson Inc.
    ------------------------------