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


Help: OASIS Mailing Lists Help | MarkMail Help

codelist message

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

Subject: Re: [codelist] code list validation

On 8 Sep 2006, at 08:29, G. Ken Holman wrote:

>> In other words, instead of saying:
>> <xsd:restriction base="xsd:string">
>> <xsd:enumeration value="1"/>
>> <xsd:enumeration value="2"/>
>> <xsd:enumeration value="3"/>
>> <xsd:enumeration value="4"/>
>> <xsd:enumeration value="5"/>
>> <xsd:enumeration value="6"/>
>> <xsd:enumeration value="7"/>
>> </xsd:restriction>
>> You could say:
>> <xsd:restriction base="xsd:string" codelist="http://....."/>
>> There is no such syntax yet (that I'm aware of), most likely  
>> because there
>> is no standard codelist format yet. But it might be as simple as  
>> above --
>> defining a 'codelist' attribute on the restriction element within  
>> the schema
>> language. Of course it would need to be accepted into the language  
>> by the W3C.\

XML Schema allows you to have attributes in an xsd:restriction - from  
a non-schema namespace.

So this is possible:

  <xsd:element name="country-codes">
		<xsd:restriction base="xsd:string" codeList:externalList="http:// 

Cheers...  Renato Iannella
National ICT Australia (NICTA)

This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.

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