Open APIs

Hello,
I was checking TAX element associated to POPs and, I have some questions/comments on it.

1) As TAXes are usually reusable elements, why isn't this a reference element in the specification rather than an embed element?
2) The examples are showing populated values for Tax Amount and for taxRate at same time. Shouldn't they be mutually exclusive?

Thanks and Regards

------------------------------
Marcos Donato da Silva
Ericsson Inc.
------------------------------

Hi Marcos

1) You are correct. A long while back, I contributed an update to the Information Framework (the SID) that defined how taxes and tax exemptions should be represented across the entire model. In the Open API this adoption has been limited to the area of tax exemption for parties and account. We really do need to extend this to the catalog and inventory.

2) Why would the amount and rate be mutually exclusive? True, for a simple tax definition the rate defines the amount, but why should we be miserly and expect the consumer to calculate. For a complex tax definition, it is possible that the amount is calculated by an external tax engine and the rate is a reflection of that calculation.

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.
------------------------------