Multiple definition of element in xs:choice element

[pawel.pabich]

Hajo,

I know only one way of forcing element to have one or more childes:

<xs:element name="saleOrSupplyMethod"> <BR/>
<xs:complexType>
<xs:choice>
<xs:sequence>
<xs:element name="generalSale" type="emptyTagType" />
<xs:element name="prescription" type="emptyTagType"/>
<xs:element name="retailSale" type="emptyTagType" />
</xs:sequence>
<xs:sequence>
<xs:element name="generalSale" type="emptyTagType" />
<xs:element name="retailSale" type="emptyTagType" />
</xs:sequence>
etc.....
</xs:choice>
</xs:complexType>
</xs:element>

But going this way I get following error:

Multiple definition of element 'generalSale' causes the content model
to become ambiguous. A content model must be formed such that during
validation of an element information item sequence, the particle
contained directly, indirectly or implicitly therein with which to
attempt to validate each item in the sequence in turn can be uniquely
determined without examining the content or attributes of that item,
and without any information about the items in the remainder of the
sequence.

thnaks in advance for any info

Pawel Pabich

[Stan Kitsis [MSFT]]

<xs:element name="saleOrSupplyMethod"> <BR/>
<xs:complexType>
<xs:sequence>
<xs:element name="generalSale" type="emptyTagType" />
<xs:element name="prescription" type="emptyTagType"
minOccurs="0" />
<xs:element name="retailSale" type="emptyTagType" />
</xs:sequence>
</xs:complexType>
</xs:element>

--
Stan Kitsis
Program Manager, XML Technologies
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

<pa**********@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

Hajo,

I know only one way of forcing element to have one or more childes:

<xs:element name="saleOrSupplyMethod"> <BR/>
<xs:complexType>
<xs:choice>
<xs:sequence>
<xs:element name="generalSale" type="emptyTagType" />
<xs:element name="prescription" type="emptyTagType"/>
<xs:element name="retailSale" type="emptyTagType" />
</xs:sequence>
<xs:sequence>
<xs:element name="generalSale" type="emptyTagType" />
<xs:element name="retailSale" type="emptyTagType" />
</xs:sequence>
etc.....
</xs:choice>
</xs:complexType>
</xs:element>

But going this way I get following error:

Multiple definition of element 'generalSale' causes the content model
to become ambiguous. A content model must be formed such that during
validation of an element information item sequence, the particle
contained directly, indirectly or implicitly therein with which to
attempt to validate each item in the sequence in turn can be uniquely
determined without examining the content or attributes of that item,
and without any information about the items in the remainder of the
sequence.

thnaks in advance for any info

Pawel Pabich

[pawel.pabich]

Thanks for replay. But I think I wasn't precise enough. I have to
ensure that all possible combinations are allowed. And your solution
does not allow me to have only one element, lets say generalSale. Here
I have prepared one more example. In short I have to ensure that at
least one elemnet is chosen and I have a set of 2 elements.

<xs:element name="tempElement">
<xs:complexType>
<xs:choice>
<xs:sequence>
<xs:element name="elem1" type="xs:string" />
<xs:element name="elem2" type="xs:string" />
</xs:sequence>
<xs:sequence>
<xs:element name="elem1" type="xs:string" />
</xs:sequence>
<xs:sequence>
<xs:element name="elem2" type="xs:string" />
</xs:sequence>
</xs:choice>
</xs:complexType>
</xs:element>