[
Lists Home |
Date Index |
Thread Index
]
Exactly! We have an XML source that uses an app to generate xml which by
default places the tags in alphabetical order. So, we were hoping to say
"no problem!", but at present I think we are going to have to enforce
it. We really don't want to have to use 2 forms of validation (XML
Schema and Schematron). We wanted to be able to simply put the XSD
online and have everyone prevalidate from it.
Brian
On Tue, 2003-01-21 at 00:26, Bryce K. Nielsen wrote:
> > It's not, although by default it is. To declare child elements as
> > unordered, place them in an <interleave> element.
> >
>
> Heh, about an hour after I posted my original post, I came across the
> <interleave> node. Bravo to RelaxNG for allowing flexible node ordering.
>
> > a) if order doesn't matter, choose one (because it doesn't matter!)
> > b) if order does matter, declare the correct order
> >
>
> I suppose the main reason for wanting/needing unordered (or any-ordered)
> elements is if you're receiving XML documents from different sources, be it
> applications or users/vendors. It seems to be a serious pain to report back
> to them that the document failed validation just because element "B" was
> listed before element "A"...
>
> -BKN
>
>
> -----------------------------------------------------------------
> 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://lists.xml.org/ob/adm.pl>
|
