This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There are quite some rules that do not mention the posture of a construct. Perhaps this is on purpose (if so, how do we determine the posture, just take the context posture?). Some examples: 19.8.4.24 Streamability of xsl:merge 19.8.4.36 Streamability of xsl:try 19.8.5 Classifying Attribute Sets (mentioned in the non-normative Note though) 19.8.7.10 Streamability of Variable References (only the last Otherwise) 19.8.7.12 Streamability of Function Calls 19.8.7.13 Streamability of Named Function References 19.8.7.14 Streamability of Inline Function Declarations Not sure this list is complete, as different wordings have been used and I may have missed a few when reading over the rules.
The WG discussed this during the ftf meeting in Prague and agreed that the editor needs to check to make sure the rewrite is complete. If the answer is obvious, the editor will make it; if not, the editor will come back to the WG for further discussion.
Done. In all these cases it's essentially a question of changing "free-ranging" to "roaming and free-ranging", and "motionless" to "grounded and motionless". Fixed xsl:merge (straightforward). xsl:try is handled under bug #24495 attribute sets - reworded slightly. variable references - handled under bug #24342. function calls - for partial function calls of focus-dependent functions, changed "free-ranging" to "roaming and free-ranging". named function references - done, interacts with bug #22936
for reference and historical accuracy: It doesn't say so in the prev. comment, but the section on inline function declarations was also fixed by adding roaming and grounded respectively.