W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2015

[Bug 29150] New: [XSLT30] Editorialities / typos

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Sep 2015 09:16:00 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29150-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29150

            Bug ID: 29150
           Summary: [XSLT30] Editorialities / typos
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

A small list of some (ir)relevant nitpicks:

1) In section 12, first Note, first para, it ends with:

the format-numberFO30 function may be more suitable: see Section 4.7.2
fn:format-number FO30.

which is essentially a double reference, the format-number function is already
hyperlinked and then we point to it again.

2) 18.1.2 Streamability examples, we write:

4. The argument to count is a RelativePathExpr that takes the form of a
motionless pattern[...]

We don't have the "if an expression can be rewritten as a motionless pattern"
rule anymore. We now have rules on Axis Steps and Path Expressions. It is still
streamable, but for other reasons.

3) In section 21 Maps, we write:

TODO: replace the error codes defined in this section by the error codes used
in XPath 3.1.

I think this has meanwhile been done (?), I don't see error codes other than
the ones that apply to XSLT only.

4) In section Abstract, we write:

TODO: describe the relationship to XPath 3.1 and related specs.

I think this was done meanwhile, I see the relevant sections.

5) In section L Changes Since LCWD

Under first item, also a "TODO": "TODO: add the streamability rules for new
expressions and functions", but I think this one is still open (I scanned for
fn:transform, but didn't find it).

6) In section B.1 Schema for the XML Representation of JSON, we write:

    <xs:simpleType name="numberType">
        <xs:restriction base="xs:double">
            <!-- exclude positive and negative infinity, and NaN -->
            <xs:minExclusive value="-INF"/>
            <xs:maxExclusive value="INF"/>
        </xs:restriction>
    </xs:simpleType>

In the comment we say we exclude NaN, but we don't do so in the schema. Was
this intended to be excluded?

7) In section 2.3.3 Apply-Templates Invocation, we write:

The initial match selection. An API that chooses to maintain compatibility with
previous versions of this specification should allow a singleton node to be
provided, which is then used in two ways: the node itself acts as the initial
match selection, and the document node of the containing document acts as the
global context item.

However, a singleton node does not need to be rooted at a document node. Should
we be a bit more precise here (even though it is merely a suggestion to
implementors)?

8) In section 24.1 Creating Final Result Trees, we write in the fourth bullet:

The corresponding serialization parameter is not set (is "absent"). it is not
possible [...]

typo: it --> It

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 24 September 2015 09:16:12 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 24 September 2015 09:16:12 UTC