W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2008

[Bug 5727] [XQuery] Syntax ambiguities with leading "/"

From: <bugzilla@wiggum.w3.org>
Date: Mon, 02 Jun 2008 08:27:45 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1K35OL-0004zb-9e@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5727


mike@saxonica.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Syntax ambiguities with     |[XQuery] Syntax ambiguities
                   |leading "/"                 |with leading "/"




------- Comment #2 from mike@saxonica.com  2008-06-02 08:27 -------
In the existing rule:

To reduce the need for lookahead, therefore, if the token immediately following
a slash is "*" or a keyword, then the slash must be the beginning, but not the
entirety, of a PathExpr (and the following token must be a NameTest, not an
operator).

I suspect the first consequence is correct: "the slash must be the beginning,
but not the entirety, of a PathExpr"

but the second is wrong: "the following token must be a NameTest, not an
operator". The following construct might also be an axis name (/child::x), a
function name (/base-uri()), a node test (/element(x)), an ordered|unordered
expression (/unordered{node()}, a computed node constructor (/text{"a"}), etc.
We should delete the phrase in brackets, and explain that by keyword we mean
any token having the lexical form of an NCName.
Received on Monday, 2 June 2008 08:28:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:52 GMT