W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2017

[Bug 30123] New: [xslt30]Example in https://www.w3.org/TR/xslt-30/#streamable-stylesheet-functions defines parameter named "input", explaining text talks about "$nodes" argument

From: <bugzilla@jessica.w3.org>
Date: Fri, 09 Jun 2017 08:20:41 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30123-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 30123
           Summary: [xslt30]Example in
                    unctions defines parameter named "input", explaining
                    text talks about "$nodes" argument
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: editorial
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: martin.honnen@gmx.de
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

While exploring streamable stylesheet functions with Saxon 9.8 I found that the
example "An absorbing stylesheet function" in
https://www.w3.org/TR/xslt-30/#streamable-stylesheet-functions has the code

<xsl:function name="f:count-descendants" as="xs:integer"
  <xsl:param name="input" as="node()*"/>
  <xsl:sequence select="count($input//*)"/>

so it defines the argument of the function with the name "input", however the
explaining text then says "The effect of the rules is that a call to this
function is guaranteed-streamable provided that the sequence supplied as the
value of the $nodes argument is motionless or consuming, and is either grounded
or striding.", that is, it uses the name "nodes" and not the name "input".

So the text and the code are inconsistent as far as the argument name is

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 9 June 2017 08:20:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 9 June 2017 08:20:49 UTC