Comments from Monica Martin. These comments are referencing the HTML Query QA UBL Naming Definitions.html document.
Original comments from Monica, in black.
Suggestions and comments in Red from Lisa Seaburg, 1 July 2002.
BIE |
Question |
Comments or Suggestion (if applicable) |
Ship ToLocation UBL000295 and UBL000296 |
No-space names |
To allow for processing and lower chance of errors FIX: fix spreadsheet to take out spaces??? |
CurrencyIdentificationCode UBL000133 |
May not be at header level account. Could be transactional or by release of a purchase order for example |
Consider lower level association |
TypeCode UBL000168 Contract type code UBL000222 (Tax) type code UBL000145 Reference type code UBL000070 Size type code UBL000139 Type ID
|
There are many type codes besides contract |
Revise to generic TypeCode or multiple types of "TypeCode"
This needs to be looked at. But I think each type is unique, we could maybe model it differently to be more neutral and reuseable. |
CurrencyCode UBL000133 CurrencyIdentificationCode UBL000179 UBL000180
|
Need for to and from currency to accommodate the transitions of the transaction itself (particularly for accounting audit mechanism as may infer agreement/contractual responsibility) |
ToCurrencyCode FromCurrencyCode
Doesnt ExchangeRateDetails take care of this? Yes, it could although this brings up two items: The currency for the account (like a default) not sure if to or from and the transaction where UBL000179 and 180 accommodate. |
SizeTypeCode UBL000070 See comments above |
How to handle aggregated or embedded types Size and type |
Suggest a type of "TypeCode" and a SizeCode that are aggregated to SizeTypeCode if desired by the business context |
CreditCard UBL000123 is CardInfo UBL000150 156 |
Duplicates with 123 and 150 two credit cards entities |
Delete duplicate.
I think CardInfo should be inside of Card Details. |
PriceQuantityRange to Quantity UBL000098 |
How to decompose these aggregates? |
Quantity Price PriceQuantityPrice Many types of Quantity
As it is, this should show depth of elements, PriceQuantityRange has two elements or attributes (?) Show these better. MinimumValue and MaximumValue. |