Hi Rephael,
Kindly elaborate on the issue you are trying to solve?
Are you thriving to achieve a better architecture or want to minimize the number of used TMF APIs?
Generally your fulfilment / integration architecture defines how the systems should interact.
And based on the architecture you design the service and its lifecycle.
If the agent is eligible to interact with federated inventory directly it should use TMF-638 API for resources inquiry / reservation.
If the federated inventory is abstracted from an agent and it interracts only with COM/SOM/Orchestration it can be subscribed to service notifications (e.g. state change notification) in order to get updates asynchronously.
Even federated inventory can be organized in multiple ways. It can either replicate the resources from domains and used in RO mode for reporting, planning, etc or can paly a role of a master inventory across all resources.
So there is not right or wrong approach and the solution always depends on various factors.
------------------------------
Mikhail Mamaev
Netcracker Technology
------------------------------