Altova Mailing List Archives

Re: [xml-dev] Errors in Kendall Clark's article on QNames

From: Eric van der Vlist <vdv@--------.--->
To: xml-dev@-----.---.---
Date: 2/13/2002 5:07:00 PM
Henry S. Thompson wrote:
> Eric van der Vlist <vdv@d...> writes:
> <snip/>
>>(just remember the mess it has been to transform a version of W3C
>>XML Schema into the next one before it went rec).
> Um, I'm confused -- I posted stylesheets to do this to this list, and
> put tools up to do the transformation, both times we revved the Schema
> syntax in any significant way (see for example xsu online [1]).  What
> mess were you referring to?

"Mess" was too strong a word, sorry for this.

Even though you have answered that these were "marginal cases", I 
remember that those stylesheets could not handle the cases where 
namespaces were redefined locally in a schema:

Not taking these marginal cases into account might be acceptable for 
convertions sheets, but they show nevertheless the complexity involved 
by handling QNames in attributes with XSLT/XPath 1.0 and this looks like 
a design flaw.


Rendez-vous a Paris pour mes formations XML/XSLT.
Eric van der Vlist   


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.