24508 2014-02-05 03:48:39 +0000 xsl:fork streamability rule #2 2014-08-02 13:26:46 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC Windows NT CLOSED FIXED P2 normal --- 1 abel.braaksma mike cmsmcq public-qt-comments oldest_to_newest 99740 0 abel.braaksma 2014-02-05 03:48:39 +0000 The second rule of 19.8.4.19 Streamability of xsl:fork (http://www.w3.org/TR/xslt-30/#streamability-xsl-fork) is ambiguous in the part "not grounded and motionless". Does it mean "not grounded and also not motionless", or does it mean "not the both of grounded and motionless". At any rate, I think that part can be removed, because even when grounded and/or motionless, the rule is still applicable: the result of xsl:fork with one xsl:sequence is the result of the streamability analysis of xsl:sequence. 100290 1 cmsmcq 2014-02-11 15:25:20 +0000 We discussed this in Prague. For "that is not grounded and motionless" read "that is not both grounded and motionless" (or some equivalent). We considered dropping the qualification entirely before realizing that we mustn't. The "that" is restrictive; not all readers saw this at once, so if there is a way to make it clearer, it might be helpful. 100733 2 mike 2014-02-17 08:10:11 +0000 I have fixed this by reordering the rules. Since rule 4 requires that all the xsl:sequence instructions are grounded, we can move this rule earlier and simplify the subsequent rules. I also noted (and fixed) that the current rules say that if all the xsl:sequence instructions are motionless, the result is consuming. This is clearly wrong. 101827 3 abel.braaksma 2014-03-04 11:12:28 +0000 The bottom line of streamaiblity of xsl:fork is that xsl:sequences must be grounded, and then the widest sweep counts. Hence, I suggest to simplify this even further, as follows: 1. If the posture of any of the child xsl:sequence instructions is not grounded, then roaming and free-ranging. 2. Otherwise, the posture is grounded and the sweep is the widest sweep of any of the xsl:sequence children (or motionless if there are no children). This then gets more in line with the xsl:map streamability rules, (which is only slightly different because xsl:map-entry has different rules than xsl:sequence). ---- If we decide to stick to the current rules, note: The current rule #4 has a typo: "then the grounded..." => "then grounded...". ---- As a result of the new rules, the last paragraph has become redundant. The rule about "exactly one child", for which I filed this bug, is now gone, which I think is the right thing to do: why allow an exceptional case for which xsl:fork is pointless anyway? The last para, should probably go: "The only case where xsl:fork is permitted to return streamed nodes is in the case where only one of the xsl:sequence instructions is consuming (in which case the xsl:fork instruction is pointless)." (I took the liberty to reopen the bug report, it was closed) 106046 4 mike 2014-05-15 14:57:26 +0000 The suggestions in comment #3 are essentially editorial; they simplify the rules while leading to the same outcome. I have therefore accepted and applied the changes suggested.