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

Re: <xsd:all> problem

• To: PeterHowells@h...
• Subject: Re: <xsd:all> problem
• From: John Cowan <jcowan@r...>
• Date: Wed, 12 Jun 2002 12:52:51 -0400 (EDT)
• Cc: xml-dev@l...
• In-reply-to: <1119A6F01289-01@M..._> from "PeterHowells@h..." at Jun 12, 2002 05:40:26 PM

PeterHowells@h... scripsit:

> <?xml version="1.0" encoding="UTF-8"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="person">
>   <xsd:complexType  >
>     <xsd:all minOccurs="0" maxOccurs="1">
>       <xsd:element name="firstname" type="xsd:string"/>
>       <xsd:element name="lastname" type="xsd:string"/>
>     </xsd:all>
>   </xsd:complexType>
> </xsd:element>
> </xsd:schema>

What you've said here is that there must be either 0 or 1 instances
of the combination firstname-lastname in either order.  This can be
satisified by nothing, or by firstname-lastname, or by lastname-firstname.
A firstname by itself doesn't work, because it can't substitute for the
required combination.

-- 
John Cowan <jcowan@r...>     http://www.reutershealth.com
I amar prestar aen, han mathon ne nen,    http://www.ccil.org/~cowan
han mathon ne chae, a han noston ne 'wilith.  --Galadriel, _LOTR:FOTR_

• References:
  • <xsd:all> problem
    • From: PeterHowells@h...

• Prev by Date: SOAP, XSD, and HTTP
• Next by Date: RE: <xsd:all> problem
• Previous by thread: <xsd:all> problem
• Next by thread: RE: <xsd:all> problem
• Index(es):
  • Date
  • Thread