Hi Eswar
The Open APIs are interrelated in the sense that we use a common data schema to generate the swaggers and user guides. So (for example) entities in the Quote Management API may well have references to entities (Customer, Product Offering, etc.) that are managed by other APIs.
However the swagger for each API is self-contained, there are no unresolved references to other swagger files.
You could migrate your inhouse API for quotes to the TMF648 API using the published swagger, your challenge would be how to fill the entity references for the other entities - so you would need to at least understand how these entities map into your other systems and use (for example) the primary key as the id in the ref structures. You would presumably not be able to populate the hrefs (e.g. for customer) with an actionable uri since you are not implementing the other APIs. Similarly you would not be able to support the depth query string directive to expand other entities.
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.
------------------------------
Original Message:
Sent: Nov 30, 2020 01:23
From: Eswar Babu Kutuva Naraynamoorthy
Subject: Migrating to TMF648 - Quote Management
Hello Members!
Is it possible to migrate our existing inhouse APIs to TMF648 Specs without considering other TMF specs like catalog, productOfferingQualification, serviceOfferingQualification, agreementManagement, etc,.
Basically we are looking at migrating our Quote systems alone to TMF specs and not to disturb the other systems for time being (Atleast now!)
PS: I referred the TMF648 specs and found other systems like catalog, product & service offering, agreement, billing management APIs are interconnected with the Quote requests & so I came up with this question.
------------------------------
Eswar Babu
Verizon Communications
------------------------------