XSD data types - was Re: [ubl-lcsc] Re: UBL 0.81 CCT draft-9-mod

Thanks for the clarification, Tim.  I see what you mean now.

I took the spirit of the discussion about changing IdentifierType
from xsd:token to xsd:normalizedString to be a facilitation of
layman user-assigned IDs used in businesses, where the IDs
might have inherited legacy position-oriented and/or space-filled
formating.

I looked at the attribute values and thought those IDs, on the
other hand, would have been assigned by (presumably standards and
organizational) agencies who are not (in my opinion)
expected to have likelihood of having inherited such 
formating restrictions with spaces.  Even for privately
held and controlled identifier values, the name of the
list of values, the version, and other metadata of the values
are usually (again, just in my limited opinion) not subject 
to the same spacing-filling restrictions.  Making this supposition,
then, xsd:token could fit the attribute's type requirements
better.

Certainly, this assessment is at most subjective.  So I'm
open to collect more suggestions to change them to other
types.  I've also collected some more feedbacks from Stephen
and can bundle these comments into draft-9-mod-2 perhaps
on Wednesday pending further inputs from other members of list.

Thanks.



Best Regards,
Chin Chee-Kai
SoftML
Tel: +65-6820-2979
Fax: +65-6743-7875
Email: 
http://SoftML.Net/


On Mon, 8 Sep 2003, Tim McGrath wrote: