[Home] [By Thread] [By Date] [Recent Entries]


Ah yes, xs:sequence in my example was redundant. I guess I'm used in 
ovecomplicating things when using XSD ;-)

Eric van der Vlist wrote:

> Manos said:
> 
>>Just nest a choice in a sequence like:
>>
>>
>><xs:element name="lala">
>>        <xs:complexType>
>>            <xs:sequence minOccurs="0" maxOccurs="unbounded">
>>                <xs:choice>
>>                    <xs:element name="foo"/>
>>                    <xs:element name="bar"/>
>>                </xs:choice>
>>            </xs:sequence>
>>        </xs:complexType>
>>    </xs:element>
> 
> 
> Note that you can also just replace the sequence by a choice:
> 
>  <xs:element name="lala">
>   <xs:complexType>
>    <xs:choice minOccurs="0" maxOccurs="unbounded">
>     <xs:element name="foo"/>
>     <xs:element name="bar"/>
>    </xs:choice>
>   </xs:complexType>
>  </xs:element>
> 
> Eric

-- 
Manos Batsis

Netsmart S.A.

Snail mail:
Panepistimiou 58,
10678, Athens, Hellas

URL:    http://www.netsmart.gr
Email:  mbatsis at netsmart dot gr
Tel:    (+30) 210 33 02 608
Fax:    (+30) 210 33 02 658
FOAF:   http://forte.netsmart.gr/foaf/manos_foaf.rdf





Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member