- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 11 Mar 2009 15:25:51 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6686 Summary: xsl:xpath-default-namespace should apply to expressions, not only patterns Product: XPath / XQuery / XSLT Version: Recommendation Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSLT 2.0 AssignedTo: mike@saxonica.com ReportedBy: frans.englich@telia.com QAContact: public-qt-comments@w3.org Section 5.2 Unprefixed QNames in Expressions and Patterns says that xpath-default-namespace applies to, among other things, "any unprefixed element name or type name used in a pattern". However, I think it also should apply to any XPath expession, such as found in xsl:sequence/@select. For instance, I think this: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:template match="/"> <xsl:sequence xpath-default-namespace="TEST" select="e"/> </xsl:template> </xsl:stylesheet> should match on the input document <e xmlns="TEST"/>. I think that would be inline with what the spec intended(e.g, consider the name of the attribute), and how people expect it to function. Maybe I have missed something, but perhaps an editorial change in the direction of turning "any unprefixed element name or type name used in a pattern" into "any unprefixed element name or type name used in a pattern or expression", would be useful. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 11 March 2009 15:26:06 UTC