W3C home > Mailing lists > Public > xmlschema-dev@w3.org > July 2002

type substitution question

From: Danny Vint <dvint@mindspring.com>
Date: Mon, 29 Jul 2002 14:39:49 -0700
Message-Id: <>
To: xml-dev-help@lists.xml.org, xmlschema-dev@w3.org

I have a schema that defines a standard type (OpenEnum) to be used as the 
basis of all code lists (enumerated lists). In some cases we actually have 
a list of values associated with a specific element and in other cases 
where we don't own the list we just use the base type of OpenEnum as the 
type for the element.

When I validate a stream that has one of these elements of type OpenEnum, 
the tool (XML Spy) comes up with a suggested list of all the code list 
values concatenated together. Is this correct behavior? I thought at least 
I would have to define a substitution group or being using the xsi:type 
attribute to get this flexibility.

Here are the key parts:

***** Schema definitions

	<xsd:complexType name="OpenEnum">
			<xsd:extension base="OpenEnum_NoID">
				<xsd:attribute ref="id"/>
				<xsd:attribute ref="CodeListRef"/>

	<xsd:simpleType name="OpenEnum_NoID">
		<xsd:restriction base="NC_NoID">
			<xsd:maxLength value="80"/>

	<xsd:simpleType name="NC_NoID">
		<xsd:restriction base="xsd:string">
			<xsd:minLength value="1"/>
			<xsd:pattern value="[\p{IsBasicLatin}]*"/>

	<xsd:element name="CurCd" type="OpenEnum"/>

	<xsd:element name="AirBagTypeCd" type="AirBagType"/>
	<xsd:element name="BillingMethodCd" type="BillingMethod"/>
	<xsd:element name="BondTermCd" type="BondTerms"/>

	<xsd:complexType name="AirBagType">
			<xsd:restriction base="OpenEnum">
				<xsd:enumeration value="Driver"/>
				<xsd:enumeration value="FrontBoth"/>
				<xsd:enumeration value="FrontSide"/>
				<xsd:enumeration value="None"/>

	<xsd:complexType name="BillingMethod">
			<xsd:restriction base="OpenEnum">
				<xsd:enumeration value="AB"/>
				<xsd:enumeration value="CAB"/>
				<xsd:enumeration value="CPB"/>
	<xsd:complexType name="BondTerms">
			<xsd:restriction base="OpenEnum">
				<xsd:enumeration value="CON"/>
				<xsd:enumeration value="NRN"/>
				<xsd:enumeration value="REN"/>

******** XML Stream



What XML Spy reports on this element is that "USD" is not allowed, and it 
shows me a list of what is all the other enumerated values without allowing 
just a plain string that would be from 1 to 80 characters restricted to the 
basicLatin character set.

Is this a correct behavior?

If it is correct is there anything else that should be in the stream to 
allow me to have just any old value and still keep these similar types of 
elements defined together?

What if I don't want to allow this to happen at all, is there any way I can 
control this without defining each lists separately?

Danny Vint

Received on Monday, 29 July 2002 17:41:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:57 UTC