25335 2014-04-13 08:56:54 +0000 [xslt 3.0] Streamed merging 2014-05-15 14:00:46 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 1 mike mike abel.braaksma public-qt-comments oldest_to_newest 103799 0 mike 2014-04-13 08:56:54 +0000 There are two specific problems with section 15.4 on streamable merging: (a) We say the xsl:merge-source/@select attribute must be striding, but in several of the examples it is grounded (b) We place no constraints on the use of the current-merge-group() function within the xsl:merge-action (or within the merge keys). I think these problems are not superficial. The concepts of sweep and posture have been developed with the idea in mind that there is only one streamable document and that it is the document containing the context item. Generalizing this to multiple input documents is non-trivial. I currently feel that the right answer is to insist that xsl:merge-source/@select is grounded (e.g. by using copy-of() or snapshot()), in which case we do not need to place any constraints on xsl:merge-action or the use of current-merge-group(). 103949 1 mike 2014-04-16 08:28:16 +0000 *** Bug 24343 has been marked as a duplicate of this bug. *** 104326 2 mike 2014-04-24 10:37:28 +0000 The working group discussed this on 2014-04-17 and agreed with this direction. When streaming is requested and xsl:merge-source/@for-each-stream is used, the nodes selected using the @select attribute will be subjected to an implicit call on snapshot().