I wish to add something important.. There is something
called "document order" - which is order of nodes in
the original document(and it is fixed). In
xsl:for-each the select attribute evaluates to a
node-set. The XSLT 1.0 spec says (about select
attribute of xsl:for-each).. "the nodes are processed
in document order, unless a sorting specification is
present"..
This statement is actually rather confusing, especially when quoted in this
particular context. It gives the impression that the specification requires
the processor to process the first node first, then the second node, and so
on. In fact this is not the intent. What it is really describing is a
mapping of an input sequence to an output sequence: the nodes obtained by
processing the first node in the input sequence come first in the output
sequence, followed by the nodes obtained by processing the second node in
the output sequence, and so on. So long as the order of the output sequence
corresponds in this way to the order of the input sequence, the nodes can
actually be processed in any order or in parallel. For example, you could
start by processing the last input node to generate the final output nodes,
then the second-last input node, and so on.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--