This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In 19.8.5.4, in the example for streamability="filter", we say: 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. There are several inaccuracies here: (a) the argument is called $input, not $nodes (b) its value must be a singleton (c) it is not values, but expressions, that have posture and sweep (d) the effect is not that the function call is "guaranteed streamable" but rather than it has the same posture and sweep as the argument supplied to the function. Proposed rewrite: The effect of the rules is that the posture and sweep of a function call f:large-regions(EXPR) are the same as the posture and sweep of EXPR.
The rules for constraints on the function body in the entries for the function streamability categories also use some imprecise terminology. For example: Rules for the function body: For the function to be guaranteed-streamable, the posture of the function result must be striding, and the sweep of the function result must be motionless. This should say: Rules for the function body: For the function to be guaranteed-streamable, the type-adjusted posture of the function body with respect to the declared return type must be striding, and the type-adjusted sweep of the function body with respect to the declared return type must be motionless. (and even this assumes that we know what's meant by "the function body").
The changes were agreed and have been applied.