Hi Artyom
In previous releases of this API, ProductOfferingPrice was a contained entity within ProductOffering, so that there was no way to directly address a POP. In the 17.5 release,
@Kamal Maghsoudlou has made a significant enhancement, making POP an independently managed entity. This allows re-use of the same POP in multiple offerings, making it easier for catalog implementers and reducing duplication.
Per Open API guidelines, if a managed entity refers to another manged entity, the Ref pattern is used, so ProductOffering would contain POPRef, that has a minimum set of fields (id, href, perhaps name). When doing a GET on a managed entity, you should be able to specify the level of expansion required for Refs, consult the published guidelines for more details.
https://projects.tmforum.org/wiki/display/API/API+Design+GuidelinesHope this is clear enough.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: May 11, 2018 04:40
From: Artyom Valeev
Subject: ProductOfferingPrices in ProductOffering
I want to get a ProductOfferingPrice via a ProductOffering request. According to TMF620 realese 17.5.0 a ProductOfferingPrice in a ProductOffering is a full object with name, description, priceType, price etc attributes, this sample on the page 30. But in the same document on the page 85, we can see that the ProductOffering response has a short variant of a ProductOfferingPrice: only "id", "href", "name" and "@type" attributes. What is the right variant of a ProductOffering response?
------------------------------
Artyom Valeev
Mobile TeleSystems OJSC
------------------------------