This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: 2.1 Must Allow Matching on Default Namespace Without Explicit Prefix
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] 2.1 Must Allow Matching on Default Namespace Without Explicit Prefix
- From: "Steve Muench" <Steve dot Muench at oracle dot com>
- Date: Wed, 21 Feb 2001 11:29:19 -0800
- References: <BNEMICIEADHDDOIKLHNCCEKKDIAA.elenz@xyzfind.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
| http://www.w3.org/TR/2001/WD-xslt20req-20010214
|
| 2.1 Must Allow Matching on Default Namespace Without Explicit Prefix
Evan,
This requirement comes from scores and scores of XSL-List
questions about users who start with a document like:
<foo xmlns="urn:something">
<bar>baz</baz>
</foo>
and then try to do:
<xsl:stylesheet xmlns:xsl="..." xmlns="urn:something">
<!--
| A naive XSLT user expects this to match
| their <foo>/<bar> combination from the doc above
+-->
<xsl:template match="/foo/bar">
:
<!-- OOPS. But it doesn't match -->
:
</xsl:template>
</xsl:stylesheet>
To someone like yourself who is an XSL veteran, it may
never be a mistake that you make, or the workaround is
so burnt into your brain that you don't think twice about it,
but the WG perceived this issue as a major "learnability" hurdle.
______________________________________________________________
Steve Muench, Lead XML Evangelist & Consulting Product Manager
BC4J & XSQL Servlet Development Teams, Oracle Rep to XSL WG
Author "Building Oracle XML Applications", O'Reilly
http://www.oreilly.com/catalog/orxmlapp/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list