[
Lists Home |
Date Index |
Thread Index
]
You can't declare the type of the element to be conditional on one of its
attributes, unless the attribute has the magic name xsi:type. Your only
options are (a) to define a type that's sufficiently permissive to allow all
the options, and then do extra validation using some other technology, or
(b) to use different element names for the two cases. Alternatively, in this
case you could use the magic xsi:nil attribute to mean status="deleted".
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From: Joe Fawcett [mailto:joefawcett@hotmail.com]
> Sent: 02 May 2006 14:48
> To: xml-dev@lists.xml.org
> Subject: [xml-dev] Schema definition of element with optional children
>
> Dear All
>
> I'm struggling to find the best way to restrict an element
> that holds address data.
> If the address is to be deleted it will look like this:
> <address recordStatus="deleted"/>
>
> if it's new or an update it will be along the lines of:
>
> <address recordStatus="inserted">
> <addressLine1></addressLine1>
> <addressLine2></addressLine2>
> <city></city>
> <postCode></postCode>
> <country></country>
> </address>
>
> with various fields being optional, these are UK addresses only.
>
> What's the most efficient way to declare this using XSD only
> as I believe I can't say, "if recordStatus = 'deleted' then..." etc?
>
> I believe I have to give a choice of two types but this seems tedious?
>
> Thanks
>
> Joe
>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an initiative of OASIS
> <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
|
