[Bug 29814] New: [xslt30] Use of XPath comments

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

            Bug ID: 29814
           Summary: [xslt30] Use of XPath comments
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

There are a number of places where the value space of an XSLT attribute is
defined by reference to XPath constructs such as ItemType, SequenceType,
IntegerLiteral, NCName, or EQName.

We make it fairly clear that whitespace is generally allowed around such
values, but we say nothing about comments. Can I write

<xsl:function name="f:goForIt (:quickly:)">

It's pretty clear that comments are allowed in multi-token constructs -
expressions and patterns - and that surely must include ItemType and
SequenceType unless we say anything to the contrary - but for EQName it seems
much less clear.

Incidentally, for package-version I think the rules are ambiguous about
whitespace (as well as comments). We say

Here IntegerLiteralXP30 and NCName are as defined in the XPath 3.0 grammar
productions of the same name (including rules on limits). Leading and trailing
whitespace is ignored; no other whitespace is allowed.

That doesn't make it clear whether leading and trailing whitespace is allowed
around each IntegerLiteral/NCName, or only at the start and end of the
PackageVersion as a whole (the latter is intended).

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

Received on Friday, 9 September 2016 07:24:39 UTC