> You put your finger exactly on the difference in the last paragraph.
> XSLT is not a sequential processing language. It proceeds through
> the templates rather than the document, processing those parts of the
> document that relate to each template, and then putting the whole
> thing together at the end. It is the templates that are "processed" not
> the document.
Thanks, Michael, this was just the info I was looking for. Am I right in
thinking then that the first thing XSLT does it read in the entire XML
instance and store it in memory? And that it then works through the
templates as laid out in the style sheet, picking elements off the
memory-resident document tree as needed? In other words, no matter which
template is being processed, the transformation has access to the entire XML
instance at all times?
This is pretty slick.