At TMForum Action Week I promised to have a look at the Resource Pool API.
I would like to post my initial view on the topic here to get some feedback whether my thoughts go in the right direction.
I also put them to the resource inventory API page as well since it is closely related and I think at least part of it also relates to discussions in this thread:
Does this sound understandable and reasonable? If so, I would consider whether and how we could support an adaptation and schemification of these APIs in this direction, collaborating with their owner.
P.S. The second aspect for me hints at a general question regarding APIs that is unclear: How do we describe which APIs are intended for which use cases (why cannot some frontend simply go ahead and modify the product inventory)? This topic came up in Frameworx and is very valid: A mapping between APIs and TAM Domains would be desirable, and actually I suspect an extension of these mappings to the ODA would lead to another level of (fruitful) discussion: Which APIs expose functionality of TAM blocks, which APIs expose the interface of ODA domain areas? To standardize this would really mean to define an architecture which standardizes functional placement