[no subject]

(It would've been good if there was a default initial template name
(like #default) which would indicate the template to start at if no
initial template was supplied - this would allow XSLT files to be
executed in the simplest way by say just double clicking them rather
than needing to supply an input or initial template... but thats
another story.)

The point worth mentioning is that with custom extensions you are
tying yourself to a particular processor anyway - and sometimes to a
particular version.  Given that version you have a fair understanding
of the order of execution, so I think you could expect certain
behaviour happy in the knowledge that your code isn't portable and
even it was might not behave the same on a different processor.

-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/