Altova Mailing List Archives

Re: [xml-dev] RELAX NG Marketing

From: "Thomas B. Passin" <tpassin@-------.--->
To: "Xml-Dev (E-mail)" <xml-dev@-----.---.--->
Date: 3/26/2002 10:55:00 PM
[Jeff Lowery]

> But in order to know how to reorder the schema, you'd have to read the
> instance document. Oh, and continually reorder the schema depending on the
> element content currently being read.

Exactly.  But to get a schema to allow certain children in any order, you
have to check it every time, nes'pa?

> Perhaps there's more elegance there than is apparent?
I suppose they really meant that they wanted to __read__ the schema and
discover that any order would be allowed, rather than to __validate__ each
time.  But the question posed was for validation each time.  You have to
read the instance document for that.  I bet you could use it to set up a
stylesheet - maybe run a fast SAX pass first to just observe the order and
give the information to the stylesheet.

Maybe I better get my tongue out of my cheek before I bite it...


Tom P

> > Aha, payback time, eh, Jeff?
> Credit where credit is due, Tom.
> > The smallest performance hit
> > would be to use
> > an xslt stylesheet to reorder the __schema__, not the data
> > (after all, they
> > want to allow any order, right?)!
> >


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.