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

RE: mixing orderer and unordered elements

From: Mark Feblowitz <mfeblowitz@frictionless.com>
Date: Wed, 12 Jun 2002 09:52:11 -0400
Message-ID: <4DBDB4044ABED31183C000508BA0E97F040ABC68@fcpostal.frictionless.com>
To: "'Torsten Curdt'" <tcurdt@dff.st>, xmlschema-dev@w3.org

Ah - I wondered about that. Then you'd have to go with something more like

<xs:element name="Root">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="Seq1"/>
				<xs:element name="Seq2"/>
				<xs:choice>
					<xs:sequence>
						<xs:element
name="Unordered1" minOccurs="0" maxOccurs="unbounded"/>
						<xs:element
name="Unordered2" minOccurs="0" maxOccurs="unbounded"/>
					</xs:sequence>
					<xs:sequence>
						<xs:element
name="Unordered2" minOccurs="0" maxOccurs="unbounded"/>
						<xs:element
name="Unordered1" minOccurs="0" maxOccurs="unbounded"/>
					</xs:sequence>
				</xs:choice>
			</xs:sequence>
		</xs:complexType>
	</xs:element>

Any number of Unordered1's followed by any number of Unordered2's, or
Any number of Unordered2's followed by any number of Unordered1's

Does that sound more like it?

Mark Feblowitz                                   	
XML Architect
       [t]   617.715.7231                                     	
       [f]   617.495.0188
Frictionless Commerce Incorporated 	
       [e]  mfeblowitz@frictionless.com
       [w] http://www.frictionless.com
       [m] 400 Technology Square, 9th Floor
             Cambridge, MA 02139 
Open Applications Group Incorporated
       [e]  mfeblowitz@openapplications.org
       [w] http://www.openapplications.org 

 -----Original Message-----
From: 	Torsten Curdt [mailto:tcurdt@dff.st] 
Sent:	Wednesday, June 12, 2002 3:58 AM
To:	Mark Feblowitz; xmlschema-dev@w3.org
Subject:	Re: mixing orderer and unordered elements

Hi, Mark,

thanks for the suggestion but

On Tuesday 11 June 2002 17:14, Mark Feblowitz wrote:
> How about:
>
> 	<xs:element name="Root">
> 		<xs:complexType>
> 			<xs:sequence>
> 				<xs:element name="Seq1"/>
> 				<xs:element name="Seq2"/>
> 				<xs:sequence>
> 					<xs:choice maxOccurs="unbounded">
> 						<xs:element
> name="Unordered1"/>
> 						<xs:element
> name="Unordered2"/>
> 					</xs:choice>
> 				</xs:sequence>
> 			</xs:sequence>
> 		</xs:complexType>
> 	</xs:element>

wouldn't that also allow:

  <Root>
     <Seq1/>
     <Seq2/>
     <Unordered2/>
     <Unordered1/>
     <Unordered2/>
  </Root>

which is not what I want...
--
Torsten
Received on Wednesday, 12 June 2002 09:52:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:31 GMT