• To: "'Mark Seaborne'" <MSeaborne@o...>
• Subject: RE: Problem with restricting a W3C Schema Type
• From: "Priscilla Walmsley" <priscilla@w...>
• Date: Fri, 15 Nov 2002 12:20:51 -0500
• Cc: <xml-dev@l...>
• Importance: Normal
• In-reply-to: <DC65AE678B89004B9CCB202E19482CC704FB67@m...>

Hi Mark,

You can't restrict a type whose elements have anonymous types like yours
do (unless you want to restrict it to be empty).  I would change the
definition of Term to:

 <xsd:complexType name="Term">
 	<xsd:sequence>
 		<xsd:element name="years" minOccurs="0"
type="origo:SmallNumberWithID">
 		<xsd:element name="months" minOccurs="0"
type="origo:SmallNumberWithID">
 	</xsd:sequence>
 	<xsd:attribute name="id" type="xsd:ID"/>
 </xsd:complexType>

 <xsd:complexType name="SmallNumberWithID">
  <xsd:simpleContent>
   <xsd:extension base="origo:SmallNumber">
    <xsd:attribute name="id" type="xsd:ID"/>
   </xsd:extension>
  </xsd:simpleContent>
</xsd:complexType>

Then you can restrict Term as follows:

 <xsd:complexType name="RestrictedTerm">
 	<xsd:sequence>
 		<xsd:element name="years" minOccurs="0"
type="origo:SmallNumberWithID">
 	</xsd:sequence>
 </xsd:complexType>

Hope that helps,
Priscilla

-----------------------------------------------------
Priscilla Walmsley             priscilla@w...
Author, Definitive XML Schema     (Prentice Hall PTR)
----------------------------------------------------- 

• References:
  • Problem with restricting a W3C Schema Type
    • From: "Mark Seaborne" <MSeaborne@o...>

• Prev by Date: Re: RDF and the new releases
• Next by Date: RE: Changing XForms 1.0 Semantics in XPath 1.0?
• Previous by thread: Problem with restricting a W3C Schema Type
• Next by thread: unsubscribtion
• Index(es):
  • Date
  • Thread