MHonArc v2.5.0b2 -->

















ubl-ndrsc message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [ubl-ndrsc] range of valid values for cc types




From: "Stephen Green" <stephen_green@seventhproject.co.uk>
To: <ubl-ndrsc@lists.oasis-open.org>
Date: Tue, 3 Feb 2004 07:31:10 -0000






Hi

Please may I add to Anne's question the matter of:

Would there be any need to specify *how* (leading
sign, trailing sign, etc) a negative amount is
specified as a separate BIE to ensure correct
interpretation of the negative aspect? Is the
expression of negativity controlled enough so as to
be clear and unambiguous?

This is similar to
another issue - Do we need precision BIE(s) to
allow unambiguous expression of a) decimals
(separator = . or , or ...etc) b) 1000s etc separators
- either adding separate BIE(s) for decimal places
(might have to instead find a way to associate this
kind of data with each amount or currency), etc.

(Behind this is the wide range of uses worldwide of
different ways to express decimals, thousands or
tens of thousands and positive/negative sign.)

Perhaps this value metadata should be attributes of an
amount (particularly decimal places and/or separator
and pre-decimal number of digits and/or thousand (etc)
separator and ,as my original question asks, whether
negative or positive and/or leading or trailing sign (etc))

then

Is it catered for by either
a) something in the CCT Spec
to limit how the above are expressed or indicated and/or
b) something in the CCT supplementary components or
xsd base type?

If not, can we add supplementary components for these of
our own?
Or should we be thinking of adding BIEs?
Or should we just leave it for implementers? (???)

I guess it applies too to cct:Quantity and cct:Measure as
well as to cct:Amount.

Thanks

Steve