Hi Priya
The current published versions of the API TMF620 (v4.2 and beta v5) already include ProductOfferingPriceRefOrValue within ProductOffering.
Just be aware that this is not a standard RefOrValue construct, as explained here
https://engage.tmforum.org/discussion/tmf620-why-productofferingpricereforvalue-is-different-than-productofferingpriceRegarding the response, if the price is by value it should be returned regardless of the depth and expand directives. If the price is by ref then the API implementation should honor depth and expand.
Hope it helps
------------------------------
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: Oct 14, 2022 10:07
From: Priya Prasad
Subject: TMF 620 - ProductOfferingPriceRefOrValue
Hi folks
We are planning to adopt the EntityRefOrValue pattern for productOfferingPrice within a productOffering entity. We intend to implement oneOf between the value class and the ref class to support passing the price by value or by ref during POST.
Question - How should this pattern appear in the productOffering (parent) GET response? Is it fine to just have the productOffering GET response only return the priceRef and have the caller use an expand directive if an inline expand of the price is needed?
Appreciate any thoughts / feedback on this.
Thanks
Priya
------------------------------
Priya Prasad
Oracle Corporation
------------------------------