[Bug 25364] New: Incorrect sweep and posture in the effect of operand on the streamability of path expressions

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

            Bug ID: 25364
           Summary: Incorrect sweep and posture in the effect of operand
                    on the streamability of path expressions
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: All
                OS: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: eugene.fotin@gmail.com
        QA Contact: public-qt-comments@w3.org

In "19.4.1 Examples showing the Effect of Operand Usage"
(http://www.w3.org/TR/xslt-30/#operand-usage-examples) section "Example: The
Effect of Operand Roles on the Streamability of Path Expressions".
Expression ".//chapter" is consuming and crawling.
The example states that expression "count(.//chapter)" and "exists(.//chapter)"
are motionless: "The operand usage (the usage of the argument to count or
exists) is defined as a inspection. The general streamability rules show that
when the posture of an operand is crawling and the operand usage is inspection,
the resulting expression is motionless" (http://marker.to/CZCtMH).
But, according to GSR, operand ".//chapter" is potentially consuming (consuming
and crawling with inspection) and is not a high-order, and step 2.d.ii of GSR
(http://www.w3.org/TR/xslt-30/#general-streamability-rules) is applied, which
produces grounded and consuming (http://marker.to/DaScke).

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

Received on Wednesday, 16 April 2014 11:55:31 UTC