«

I have a current xsd that allows the xml to have 0..1 chassisid element
and 0..1 terminalid element. But now I want to restrict these elements
in a way that either both chassisid and terminalid are supplied or
neither are supplies never just one of the elements is ever supplied.
I believe this can be done but the restriction I have is that I cannot
change the structure of the xml file, i.e. by nesting a new section for
chassisid/terminalid.

e.g.

xsd:
....
<xs:element name="chassisid" type="xs:string" minOccurs="0"
maxOccurs="1"/>
<xs:element name="terminalid" type="xs:string" minOccurs="0"
maxOccurs="1"/>
....

xml:
....
<chassisid>A123456789</chassisid>
<terminalid>A2345678</terminalid>
....

If you can help then many thanks.

Regards

Billy

How about:

<xs:sequence minOccurs="0" maxOccurs="1">
<xs:element name="chassisid" type="xs:string"/>
<xs:element name="terminalid" type="xs:string"/>
</xs:sequence>

Hope that helps,
Priscilla

----------------------------------
Priscilla Walmsley
Author, Definitive XML Schema
http://www.datypic.com
----------------------------------

*** Sent via Developersdex http://www.developersdex.com ***

Billy wrote:
> I have a current xsd that allows the xml to have 0..1 chassisid element
> and 0..1 terminalid element. But now I want to restrict these elements
> in a way that either both chassisid and terminalid are supplied or
> neither are supplies never just one of the elements is ever supplied.

<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="1">
<xs:element ref="chassisid"/>
<xs:element ref="terminalid"/>
</xs:sequence>
</xs:complexType>

--
Klaus Johannes Rusch

http://www.atmedia.net/KlausRusch/

Thanks for your time,

It looks pretty simple and unsure why I haven't tried that already. I
will try it Monday when I get back to work.

Once again, thanks

Billy



*** Sent via Developersdex http://www.developersdex.com ***

It works a treat, many thanks Priscilla & Klaus.

Billy