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: Tue, 03 Jun 2008 01:42:33 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1K3LXl-0001fB-L7@wiggum.w3.org>

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





------- Comment #3 from jmdyck@ibiblio.org  2008-06-03 01:42 -------
(In reply to comment #2)
> by keyword we mean any token having the lexical form of an NCName.

I'm not disagreeing with the meat of what you're saying, just with that
particular meaning for "keyword".

Although the spec doesn't define "keyword", it generally uses it in the sense
of a token that matches a quoted word (/"[a-z-]+"/) in the A.1 EBNF. So, e.g.
  for
and
  union
are keywords, but
  foo
and
  Union
aren't (though they are NCNames).

Where this section talks about (a slash followed by) a keyword, I think it
means a token whose spelling matches that of some keyword (but the parser
doesn't yet know [before applying this constraint] whether it's actually a
keyword or an NCName). That is, the constraint is talking about a smaller set
of cases than you think it is. (If a slash is followed by a word-like token
that *doesn't* have the spelling of any keyword, then presumably it must be an
NCName, and there isn't a parsing conflict.)
Received on Tuesday, 3 June 2008 01:43:08 GMT

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