[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: question about restrictions

• To: Brent Worden <brent@w...>
• Subject: Re: question about restrictions
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Mon, 21 Jun 2004 22:14:05 -0400
• Cc: xml-dev@l...
• Organization: Booz Allen Hamilton
• References: <cb7mo8$n4m$1@s...>

I believe you found the cause in your explanation below - the
restriction is not actually a restriction. You would have to - for
example - change one of the maxOccurs facets from "unbounded" to "5" (or
anything other than "unbounded").

Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
Strategy and Technology Consultants to the World

Brent Worden wrote:
> 
> I have a question regarding the following schema:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <xsd:schema targetNamespace="urn:example" xmlns="urn:example"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
> attributeFormDefault="unqualified">
> 
>   <xsd:element name="Root" type="RestrictedType"/>
> 
>   <xsd:complexType name="RestrictedType">
>     <xsd:complexContent>
>       <xsd:restriction base="BaseType">
>         <xsd:sequence>
>           <xsd:element name="FirstElement">
>             <xsd:complexType>
>               <xsd:choice>
>                 <xsd:element name="FirstChoice" type="xsd:string"
> maxOccurs="unbounded"/>
>                 <xsd:element name="SecondChoice" type="xsd:string"
> maxOccurs="unbounded"/>
>               </xsd:choice>
>             </xsd:complexType>
>           </xsd:element>
>           <xsd:element name="SecondElement" type="xsd:string" minOccurs="0"
> maxOccurs="unbounded"/>
>         </xsd:sequence>
>       </xsd:restriction>
>     </xsd:complexContent>
>   </xsd:complexType>
> 
>   <xsd:complexType name="BaseType">
>     <xsd:sequence>
>       <xsd:element name="FirstElement">
>         <xsd:complexType>
>           <xsd:choice>
>             <xsd:element name="FirstChoice" type="xsd:string"
> maxOccurs="unbounded"/>
>             <xsd:element name="SecondChoice" type="xsd:string"
> maxOccurs="unbounded"/>
>           </xsd:choice>
>         </xsd:complexType>
>       </xsd:element>
>       <xsd:element name="SecondElement" type="xsd:string" minOccurs="0"
> maxOccurs="unbounded"/>
>     </xsd:sequence>
>   </xsd:complexType>
> 
> </xsd:schema>
> 
> When I try validating a simple XML document using Xerces with full schema
> checking enabled, I get the following error message:
> Error for type 'RestrictedType'.  The particle of the type is not a valid
> restriction of the particle of the base.
> 
> Through the process of elimination, I've determined the trouble lies in
> FirstElement found in the two types.  I've looked at the schema contraints
> at http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction that I
> believe govern this issue.  With reading those and since, FirstElement is a
> verbatium copy from BaseType to RestrictedType I've been unable to determine
> the cause for the invalid restriction message.
> 
> Can someone give me some insight into the cause of the violation?
> 
> Thanks,
> 
> Brent Worden
> 
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>

-- 
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton

• Follow-Ups:
  • Re: question about restrictions
    • From: ht@i... (Henry S. Thompson)

• References:
  • question about restrictions
    • From: "Brent Worden" <brent@w...>

• Prev by Date: Re: XML ... simple building blocks, simple assembly mechanisms, endless complexity
• Next by Date: RE: OFFTOPIC: Go SpaceShipOne
• Previous by thread: question about restrictions
• Next by thread: Re: question about restrictions
• Index(es):
  • Date
  • Thread