OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ubl-ndrsc] NDR Review - Section 7.7


Greetings,

The Address ABIE contains a sequence including Region and District optional elements. Both of these indicate a BusinessTerm of 'LocalityName'. I would think that it is at least possible that a customizer may want to allow one or the other to appear, but not both.

This also brings up the issue I raised at the last call concerning UBL conformant Schemas vs. UBL conformant instances. If a customizer decides to use the Choice construct (as in the example above) in their Schema, and it is the only customization in their Schema, every instance of that Schema *will* validate against the normative UBL Schema. What do we gain from referring to that Schema as 'Nonconformant'? What should we call schemas that only 'produce' UBL conformant instances, even if the schema itself is not?

Mike Grimley


-----Original Message-----
From: CRAWFORD, Mark [mailto:MCRAWFORD@lmi.org]
Sent: Monday, 12 January 2004 09 59
To: UBL-NDRSC (E-mail)
Subject: RE: [ubl-ndrsc] NDR Review - Section 7.7


I have yet to see a use case for the inclusion of choice.  In the cases where I have seen arguments for the use of choice, the data is really more properly part of either a code list or identification scheme.  


Mark 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]