Hello,I have a question regarding ProductPrice resource exposed in TMF 637 API in a flatten way, compared with SID model where the ProductPrice can be composed of multiple prices. Flattening a complex structure of composite prices with multiple alterations at different layers can be quite a challenge considering their stacking and sequencing. Having this in mind, we would like to understand how these use cases are handled at API level as we are missing the reasons/concerns for not exposing the hierarchy at API level as well.
Following a similar approach as for Product Offering Prices (considering that a ProductPrice is an instantiation of a ProductOfferingPrice), and trying to add a new attribute bundledProductPricesRelationship (similar with bundlePopRelationship) for exposing the bundled product prices (as references) it's not feasible as long as we don't have APIs to expose the ProductPrice resource only, therefore we are thinking to add a new attribute – bundledProductPrices ( List of ProductPrice) in order to expose the entire product price hierarchy.
We would like to keep the resources as per Open API , so we are keen to receive guidance from your side on this topic.
Thanks in advance,Mihaela