W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2009

[Bug 6131] [XPath 2.1] Requirement: context-free paths

From: <bugzilla@wiggum.w3.org>
Date: Wed, 26 Aug 2009 09:23:06 +0000
To: public-qt-comments@w3.org
Message-Id: <E1MgEig-0006iW-QQ@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6131





--- Comment #24 from Michael Kay <mike@saxonica.com>  2009-08-26 09:23:06 ---
>> EQname: QName | UriLiteral ':' NCName   /* ws:explicit */

In many ways this suggestion is attractive. However, there is one context where
it wouldn't work well:

<xsl:value-of select="key('my:key', 1234)"/>

<xsl:value-of select="system-property('my:operating-system', 1234)"/>

<xsl:if test="function-available('my:function')"/>

Replacing the lexical QNames here by an EQName as proposed here would require
use of escaped quotation marks (&quot;), which is unappealing.

So perhaps we should adopt this, but also introduce backtick as a third kind of
quotation mark for use in all contexts where we currently allow paired
double-quotes or single-quotes? Or perhaps just as a third option for a
UriLiteral?

An alternative would be to use a different format (such as {uri}local) for
run-time QNames, but that's not nice either.


-- 
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, 26 August 2009 09:23:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:40 UTC