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

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

From: <bugzilla@wiggum.w3.org>
Date: Mon, 04 Aug 2008 15:01:55 +0000
To: public-qt-comments@w3.org
Message-Id: <E1KQ1ZL-00085C-Ph@wiggum.w3.org>

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





--- Comment #10 from John Snelson <john.snelson@oracle.com>  2008-08-04 15:01:55 ---
(In reply to comment #9)
> (1) The proposal in comment #8 does not address the problem that if these rules
> are adopted,
> 
> / < 5
> 
> now parses in XPath but not in XQuery. Perhaps that's acceptable.

I think that's acceptable. It's not the only case of an XPath expression that
isn't valid in XQuery, although I agree we should keep these occurrences to a
minimum.

> (2) What about
> 
> / instance of document-node(schema-element(x))
> 
> Are we saying this must be reported as a syntax error? I might be reluctant to
> implement that because I don't want to invalidate existing stylesheets - it's a
> perfectly reasonable thing to write, although I agree it's arguably illegal
> already (depends on what you think "keyword" means - I allow it because my
> parser recognizes "instance of" as a single token, which cannot appear at the
> start of a RelativePathExpr).

I believe this expression was already dis-allowed in the intent of the previous
rule. Although "instance of" used to be a combined token in previous versions
of the grammar, it is not in the recommendation.


-- 
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 Monday, 4 August 2008 15:02:30 GMT

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