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

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

From: <bugzilla@wiggum.w3.org>
Date: Thu, 09 Jul 2009 11:00:45 +0000
To: public-qt-comments@w3.org
Message-Id: <E1MOrMr-0003GX-3C@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6131





--- Comment #13 from Michael Kay <mike@saxonica.com>  2009-07-09 11:00:44 ---
So, would Clark names work?

They would certainly work in XPath, which does not currently use curlies for
anything else.

In XSLT there would have to be a rule for their use in attribute value
templates: probably simply that if the XPath expression starts with an
open-curly, then it must be preceded by a space. For example, code="{
{uri}local }".

In XQuery there's a risk of clashing with existing uses of curly braces.
EnclosedExpr would need a similar rule to the XSLT rule above. Most other
places that currently use a curly, it's a follow-on to something like text{} or
validate{}, and these cases may be OK. However, there's a major clash with
scripting, which has

Block ::= "{" BlockDecls BlockBody "}"

which is clearly incompatible.


-- 
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 Thursday, 9 July 2009 11:00:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:28 UTC