OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] How to design XML to have broad utility and yet also enable efficient application processing?

> "we're so used to people not getting namespaces right that we hardly even notice any more"
> Some simple examples would be much appreciated, for my education.

Cases of beginners getting namespaces wrong are too legion to be interesting. But perhaps a more interesting case is that XSLT, despite herculean efforts to do the right thing, still struggles with some simple cases. For example given this XML fragment (actually an XSD fragment)

<xs:schema xmlns="http://something"; xmlns:xs="theUsual" xmlns:t="http://t";>
<xs:complexType name="T">
  <xs:restriction base="t:base">
    <xs:group ref="agroup" xmlns=""/>

an xsl:copy-of instruction applied to the xs:complexType element will lose the namespace undeclaration xmlns="", and thus invalidate the QName-valued attribute ref="agroup".

We've spent untold hours of WG time trying to find a solution to this bug, without success. If we can't get it right, how can mere mortals with more important things in their lives to worry about?

Sorry, I just noticed you asked for simple examples. If only namespaces were simple.

Michael Kay

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS