[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Schema definition of element with optional children

• To: xml-dev@l...
• Subject: Schema definition of element with optional children
• From: "Joe Fawcett" <joefawcett@h...>
• Date: Tue, 02 May 2006 14:48:20 +0100
• Bcc:
• Reply-to: joe@r...

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

• Follow-Ups:
  • Re: Schema definition of element with optional children
    • From: George Cristian Bina <george@o...>
  • RE: Schema definition of element with optional children
    • From: "Michael Kay" <mike@s...>

• Prev by Date: Re: Choosing a target name for a processing instruction
• Next by Date: RE: Schema definition of element with optional children
• Previous by thread: RE: Handling of PIs (was RE: Choosing a target name...)
• Next by thread: RE: Schema definition of element with optional children
• Index(es):
  • Date
  • Thread