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

[Bug 3606] [XPath] delimiting tokens

From: <bugzilla@wiggum.w3.org>
Date: Fri, 25 Aug 2006 15:38:02 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1GGdkw-0004Wg-Rr@wiggum.w3.org>

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


scott_boag@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from scott_boag@us.ibm.com  2006-08-25 15:38 -------
> Is there any good reason why StringLiteral is classified as a non-delimiting
> symbol?

Not that I can see. In fact, I think it's contradicts """ and "'" being
delimiting characters.  So, yes, I think this is a bug and should be fixed.

> Am I correct in saying that as the spec stands, the above line should be a
> syntax error?

I would let it pass, given my statement above that there is a contradiction.

>> There are other oddities in the list of non-delimiting symbols as well. For
>> example, it includes Char. This suggests that in the production rule
>> 
>> [159]           CommentContents            ::=          (Char+ - (Char* ('(:' >|
>> ':)') Char*))
>> 
>> the Char tokens must be separated by whitespace, whereas of course the >>opposite
>> is true. I think that symbols that are used only in ws:explicit rules have no
>> place in this list.

I agree.

>> "." also requires a separator if it precedes or follows a
>> numeric literal.

I agree.
Received on Friday, 25 August 2006 15:38:23 GMT

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