We have APIs (primarily in the catalog P/S/R/E domains) where the definitions (specifications) are in separate APIs from the instances (inventory).
But we also have APIs that combine the definitions and instances in the same API, e.g. usage, party role (in progress), and process flow.
Apart from technical considerations (shared swagger file, shared end-point), I'm not sure what the practical functional difference is between the two approaches. But happy to hear discussion comments.
------------------------------
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: Jun 23, 2022 03:53
From: Ludovic Robert
Subject: TMF701: inventory and catalog functions
Hello Opher,
This is a fair observation. As we slightly modified the ProcessFlow & TaskFlow resource to add links (respectively) to ProcessFLowSpecification & TaskFlowSpecification we opted to add the 2 new resources in 701. Up to my knowledge we plan to let them together in the same API.
Hope it helps
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
Original Message:
Sent: Jun 17, 2022 03:44
From: Opher Yaron
Subject: TMF701: inventory and catalog functions
Hello,
The recent release of TMF701 (Version 4.1.0) adds catalog-type functionality (management of ProcessFlowSpecification and TaskFlowSpecification resources) to the original inventory-type functionality (management of ProcessFlow and TaskFlow resources.) It is quite unusual, as in all other cases I am familiar with these two types of functionality are divided to separate APIs.
I wonder if this is a temporary solution, with an intention to split them in a future release; or they are expected to remain together under a single API.
Thank you,
Opher
------------------------------
Opher Yaron
Proximus SA
------------------------------