If you store bandwidth values in UoM. I understand you would have a problem with TMF663. UoM has a dependency on priceType.
in your example, a specChar should represent the bandwidth and the charValue represent the 28 Mbps speed value.
But I agree with you that consistencies between entities, attributes etc are important.
@Jonathan Goldberg, in the next version of the APIs, could you add some relevant examples?
there's been a few recent discussions from members who need clarification on UoM in TMF620 and/or other commerce APIs.
especially examples that illustrate how UoM relate to priceType
------------------------------
Kind regards,
Matthieu Hattab
Lyse Platform
------------------------------
Original Message:
Sent: Aug 29, 2023 00:21
From: Santosh M K
Subject: TMF663 Shopping Cart - Inconsistency in "unitOfMeasure" attribute definition
I am comparing the unitOfMeasure attribute defined by Quantity object, usually under ProductOfferingPrice with the CartPrice in Shopping Cart (TMF 663)
"unitOfMeasure": { "amount": 28, "units": "mbps" }
Regards,
------------------------------
Santosh M K
Comviva
Original Message:
Sent: Aug 28, 2023 10:51
From: Matthieu Hattab
Subject: TMF663 Shopping Cart - Inconsistency in "unitOfMeasure" attribute definition
There are several unitOfMeasure in TMF620. Which one are you trying to compare with the shopping Cart API?
------------------------------
Kind regards,
Matthieu Hattab
Lyse Platform
Original Message:
Sent: Aug 25, 2023 06:41
From: Santosh M K
Subject: TMF663 Shopping Cart - Inconsistency in "unitOfMeasure" attribute definition
The unitOfMeasure attribute defined in the CartPrice entity is a String (as shown below).
Whereas the same unitOfMeasure attribute in TMF620 Product Catalog is defined as an object (as shown below)
This inconsistency needs to be removed, since the client application needs to do some juggulery to consume both the APIs.
------------------------------
Santosh M K
Comviva
------------------------------