This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25364 - Incorrect sweep and posture in the path expressions sample for the effect of operand on the streamability
Summary: Incorrect sweep and posture in the path expressions sample for the effect of ...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-16 11:55 UTC by Eugene Fotin
Modified: 2014-08-05 10:34 UTC (History)
1 user (show)

See Also:

Attachments

Description Eugene Fotin 2014-04-16 11:55:23 UTC 
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).
Comment 1 Michael Kay 2014-05-15 14:31:57 UTC 
Thank you for reporting this. I have fixed the explanation of the example editorially.