Open APIs

 View Only
  • 1.  Open API Table - ODA Domains

    Posted Apr 03, 2023 04:43

    Hi,

    I could see the ODA domains mentioned in the Open API Table, whereas ODA specifies ODA Components.

    where can I find the reference document mentioning the different sets of ODA domains? or ODA Domains the same as SID entities?

    Thanks & Regards,
    Garla.



    ------------------------------
    Garla Lakshman Kumar
    Telstra Corporation
    ------------------------------


  • 2.  RE: Open API Table - ODA Domains

    Posted Apr 03, 2023 05:02

    Hi Garla,

    In Open API Poster https://www.tmforum.org/resources/standard/tmf432-open-api-poster-v22-5/ you can see the different Open APIs grouped by domains.

    These domains are referenced in ODA Domain column in OpenAPI table.

    But my doubt is about the relation of these "Open API ODA Domains" with ODA Component Domains.

    Regards,



    ------------------------------
    Vítor Fernández
    Optare Solutions
    ------------------------------



  • 3.  RE: Open API Table - ODA Domains

    Posted Apr 04, 2023 04:45

    Hi Garla,

    Regarding the mapping of APIs to domains...

    The Open API poster mentioned by Vitor is a good place to see the whole landscape in one place. (https://www.tmforum.org/resources/standard/tmf432-open-api-poster-v22-5/)
    In addition, GB992 The Open API Map has an explanation of the domains and the mapping of the APIs to the domains. (https://www.tmforum.org/resources/specification/gb992-open-api-map-r18-0-0/)
    Be aware GB992 has not been updated for a while so the concepts are correct, but some of the specific APIs may have changed. For the most accurate mapping of any specifc API always refer to the API table (https://projects.tmforum.org/wiki/display/API/Open+API+Table). 

    Regarding ODA domains in general, there is a bit of history behind these which will hopefully make things clearer.
    Several years ago when the main TM Forum assets were eTOM, SID and TAM, we referred to these collectively as Frameworx. And all the assets from each area were mapped to domains (and additionally, in the case of eTOM, vertical contexts).
    When the OpenAPI project was added the APIs were also mapped to the same domains.
    Since we no longer use the collective term "Frameworx", the domains are now referred to as the "ODA Domains"
    Each project maintains the mapping to the domains, (for example, in GB992 mentioned above for Open APIs.) However this means that differences sometimes emerge between the domains used by different projects. We are aware of this issue and are currently working on better master data management to ensure the domains are managed centrally and are consistent. 

    I hope that gives you what you need.

    Thanks,
    Ian



    ------------------------------
    Ian Turkington
    TM Forum
    ------------------------------



  • 4.  RE: Open API Table - ODA Domains

    Posted Apr 05, 2023 01:08

    Thanks, Ian, for the clarification and for providing the history of ODA Domain Naming.

    I have a follow-up question same as Victor about the relation of these "Open API ODA Domains" with ODA Component Domains.

    any clarification would be apricated!!



    ------------------------------
    Garla Lakshman Kumar
    Telstra Corporation
    ------------------------------



  • 5.  RE: Open API Table - ODA Domains

    Posted Apr 05, 2023 04:04

    Hi Garla,

    Regarding "Open API ODA Domains with ODA Component Domains".

    There is one set of domains, the ODA Domains. These are the domains which evolved from Frameworx (eTOM, SID and TAM), but are now used across most of ODA. 

    The ODA Domains are...
       Market/Sales
       Customer
       Product
       Service
       Resource
       Business Partner
       Enterprise
       Common

    The ODA Domains are used by eTOM, SID, FF, OpenAPIs and OpenAPI Data Model. (As I mentioned before there are some differences, but we are continually working on these.) You will see these used on the posters for these assets.

    In addition the ODA Functional Architecture has created a concept of ODA Function Blocks.

    The ODA Function Blocks are...
       Engagement Management
       Party Management
       Core Commerce Management
       Production
       Intelligence Management
       Decoupling and Integration

    The ODA Function Blocks are used by the ODA Components. You will see these used on the Component poster.

    And the ODA Function Blocks are sometimes (incorrectly) referred to as Component Domains, and this often causes confusion. If you stick to the terms ODA Domains and ODA Function Blocks, then things should be clear.

    I'm aware this is not ideal and there is a need for a mapping between the two (as a minimum  in the short term), or ideally a realignment (but that will take longer.)

    Thanks,
    Ian







    ------------------------------
    Ian Turkington
    TM Forum
    ------------------------------



  • 6.  RE: Open API Table - ODA Domains

    Posted Apr 21, 2023 00:09

    Dear @Ian Taylor , @Jonathan Goldberg 

    I am also trying to work independently on mapping the ODA Domains to the ODA Function Blocks, its good to work in a team.
    If there is an already group already formed to work on defining it, it would be great if you can include me in the forum.

    If not, we can create a group to work on it. any thoughts on it? Open for suggestions.

    Best Regards,
    Garla.



    ------------------------------
    Garla Lakshman Kumar
    Telstra Corporation
    ------------------------------