The p:for-each will apply that subpipeline to each document in the sequence in turn.
The phrasing "in turn" might suggest, that p:for-each has to be implemented iterative, so that its guaranted, that the subpipeline with document 1 is excecuted before document 2's subpipeline.
The specification for xsl:for-each does not suggest this restriction:
The xsl:for-each instruction processes each item in a sequence of items, evaluating the sequence constructor within the xsl:for-each instruction once for each item in that sequence.
I wonder whether it would be better to align with XSLT's concept.
The current specification says:
The phrasing "in turn" might suggest, that
p:for-each
has to be implemented iterative, so that its guaranted, that the subpipeline with document 1 is excecuted before document 2's subpipeline. The specification for xsl:for-each does not suggest this restriction:I wonder whether it would be better to align with XSLT's concept.