With xs:all and three possible elements, it's not too hard to enumerate the possible sequences and spell the whole thing out as a choice of sequences, but it becomes increasingly difficult when the group size gets larger. Really you've got two choices: change the design, or do the validation using a different technology. (You'll never be able to do complete validation against all possible constraints using XML Schema anyway). Michael Kay http://www.saxonica.com/ > -----Original Message----- > From: xmlschema-dev-request@w3.org > [mailto:xmlschema-dev-request@w3.org] On Behalf Of Petetsky, Alexander > Sent: 05 March 2007 19:11 > To: xmlschema-dev@w3.org > Subject: XML Schema question > > > Hi all, > I have a problem I am trying to find a solution/work around for. > One of the elements in my schema by design must consist of > either one child elements or a group of elements with > absolutely no restriction on the order within this group. So, > ideally it would look something like the following (though I > understand it is invalid): > <xs:complexType name="Parent"> > <xs:choice> > <xs:element name="E0" type="xs:int" > minOccurs="1" maxOccurs="unbounded"/> > <xs:all minOccurs="0"> > <xs:element name="E1" type="xs:string" /> > <xs:element name="E2" type="xs:string" /> > <xs:element name="E3" type="xs:string" /> > </xs:all> > </xs:choice> > </xs:complexType> > > Any ideas? > Thanks > --Alex > > > > > >Received on Monday, 5 March 2007 23:46:43 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:56 GMT