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

Re: maxoccurs='unbounded' under xsd:all group.

• To: roxenne_2001@y...
• Subject: Re: maxoccurs='unbounded' under xsd:all group.
• From: David Carlisle <davidc@n...>
• Date: Tue, 17 Jan 2006 22:59:23 GMT
• Cc: xml-dev@l...
• In-reply-to: <20060117192118.81458.qmail@w...> (messagefrom Roxette Lurge on Tue, 17 Jan 2006 11:21:18 -0800 (PST))
• References: <20060117192118.81458.qmail@w...>

> I don't see any other way other than to change xml
> structure to get rid of this issue.

do you _have_ to express this constraint at the schema level?
There are always some things a schema (even a relax ng one) can't catch
and have to be caught in the application. If changing the xml format is
inconvenient just schema type it as
(A|B|C|D|E)*
so at least the schema checks that the set of child elements is
plausible, and defer the cardinality checks to whatever application is
handling the schema validated input.


David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

• Follow-Ups:
  • Re: maxoccurs='unbounded' under xsd:all group.
    • From: Roxette Lurge <roxenne_2001@y...>

• References:
  • Re: maxoccurs='unbounded' under xsd:all group.
    • From: Roxette Lurge <roxenne_2001@y...>

• Prev by Date: Re: maxoccurs='unbounded' under xsd:all group.
• Next by Date: Possible Problem Messages
• Previous by thread: Re: maxoccurs='unbounded' under xsd:all group.
• Next by thread: Re: maxoccurs='unbounded' under xsd:all group.
• Index(es):
  • Date
  • Thread