On some of the top level EMIX objects, there is an Extended Price, which is defined as being of type EmixPrice. This makes no sense.
There are cogent arguments for and against even having the Extended Price - it is quite possible it should be eliminated. That would answer this issue.
If it stays, thought, it should not be of type EMixPrice. EmicPrice is a compound object in which there is a choice of:
- A price, say, in [$], whthe this is per unit or absolute is not specified.
- A Multiplier and a URI, say 1.25 * the base price, findable at uri
- An Adder and a uri, say $2 more than the base price, findable at uri
For extedned price to make any kind of sense, it clealry can only be one of these. Somehow, as we added multiplier and adder, we muddled the overall price model in the schema.