Open APIs

Expand all | Collapse all

TMF633 - nested catalog

  • 1.  TMF633 - nested catalog

    TM Forum Member
    Posted Sep 11, 2020 03:16
    Hi

    Can we have/support multiple nested catalog (TMF633) in a single parent service catalog?
    is it recommended? Or how else it can be achieved?


    thanks
    vikas

    ------------------------------
    Vikas Kumar
    Ciena Corporation
    ------------------------------


  • 2.  RE: TMF633 - nested catalog

    TM Forum Member
    Posted Sep 13, 2020 03:24
    Hi Vikas
    I'm not sure I understand the use case for nested catalogs.
    The Information Framework (SID) allows relationships between catalogs (and since catalog is a base class you could have relation between a product catalog and service catalog), and I suppose you could represent nesting with this.
    But in the Open API (TMF620, 633, 634) there is no such relationship.
    Be aware that the catalog is simply a window to the underlying entities (product offerings, p/s/r specifications, etc.). The same underlying entities can appear in multiple catalogs.

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



  • 3.  RE: TMF633 - nested catalog

    TM Forum Member
    Posted Sep 13, 2020 21:23
    Hi Jonathan

    Thanks for your response.

    Requirement is to have 3 CFS definitions - which are published as catalogs
    And one of that CFS is a master or Main Service definitions. Remaining 2 are the supporting catalog definition to the master

    I assume - this is not as per the standard to have parent-child relationship within catalogs - if you could please confirm?

    Secondly - if the standards doesnot support such kind of relationship for catalogs - is it possible in serviceCandidates? Or it's not recommended in that also?


    thanks
    vikas

    ------------------------------
    Vikas Kumar
    Ciena Corporation
    ------------------------------



  • 4.  RE: TMF633 - nested catalog

    TM Forum Member
    Posted Sep 14, 2020 03:01
    Hi Vikas
    Still not sure I understand. Your CFS definitions would be published as ServiceSpecification . Depending on the exact business, your master/main CFS could be a parent ServiceSpecification and the two supporting ones would be children. Or, if they are potentially independent, you could relate them with a different relationship type. Both use ServiceSpecificationRelationship to express this.
    You surely don't need multiple catalogs (ServiceCatalog) to express this.
    Unless I misunderstood what you are trying to achieve.

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



  • 5.  RE: TMF633 - nested catalog

    TM Forum Member
    Posted Sep 15, 2020 05:29
    If you join the ODA project at  https://www.tmforum.org/collaboration/current-projects/  but if you are registered on the API project you will be already a member of teh core team

    Under ODA     IG1222 ODA Technical Architecture - Snapshot
    We are developing a series of ODA Patterns / Integration Patterns  which includes drafts on ODA catalog federation and catalog /data synchronisation ODA integration patterns
    ODA Service and Integration Pattern: Catalog Federation
    ODA Pattern: Data Synchronization Pattern

    Work is embryonic but pretty useful for understanding how to tackle these types of needs and are based on member  implementation experiences.
    be.
    Comments and feedback  on the working pages welcome.

    ------------------------------
    Dave Milham
    TM Forum CHIEF ArchItect
    ------------------------------