[Bug 29700] New: [XP31] ws: explicit wording on comments is a tad unfortunate

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29700

            Bug ID: 29700
           Summary: [XP31] ws:explicit wording on comments is a tad
                    unfortunate
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XPath 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The current test on ws:explicit in production rules states:

<quote>

ws: explicit

   /* ws: explicit */ means that the EBNF notation explicitly notates, with S 
   or otherwise, where whitespace characters are allowed. In productions with
the
   /* ws: explicit */ annotation, A.2.4.1 Default Whitespace Handling does not 
   apply. Comments are also not allowed in these productions.
</quote>

The word "Comments" is underlined and points to the production rule for
comments. This suggests that for instance the following is disallowed:

Q{http://(:comment:)/test}

But I think that's not true, in fact, I think the above EQName is valid and the
whole string including the comment is part of it. That is, the URI is equal to
"http://(:comment:)/test", not "http:///test", and it should not throw a syntax
error. 

Essentially, such comment is not a comment. Perhaps a better wording would be
to say:

<proposal>
   Comments are not recognized as comments in these productions and the
   characters "(", ":" and ")" may or may not be allowed by the production
rule.
</proposal>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 21 June 2016 11:33:14 UTC