> >  From what I understood you want something like this :
> > 
> > 
> >     <xsd:element name="elementA">
> >         <xsd:complexType>
> >             <xsd:choice>
> > 
> >                 <xsd:element name="elementB">
> >                     <xsd:complexType>
> >                         <xsd:sequence>
> >                             <xsd:element name="elementC" 
> type="xsd:string"/>
> >                             <xsd:element name="elementD" 
> type="xsd:string"/>
> >                         </xsd:sequence>
> >                     </xsd:complexType>
> >                 </xsd:element>
> > 
> >                 <xsd:element ref="elementB" />
> > 
> >             </xsd:choice>
> >         </xsd:complexType>

You can't have two elementB particles in the same content model with
different types. When the validator sees an element named elementB in the
input, it has to be able to go to the schema and discover what its expected
type is.

In Schema 1.1 you can do this with assertions. Define a type with mixed
content and two optional child elements, and then define an assertion to
make the elements and the text mutually exclusive.

But I still think it's not a very good document design.

Michael Kay


From arshad.noor@s... Tue Jun 24 00:14:10 2008
Received: from [128.30.