Any idea if this will change in xslt 2.0? Couldn't really find it in the
  rec (http://www.w3.org/TR/xslt20/) but it seems like a change which is
  plausible enough.


No, chance: it would completely break the xslt processing model, you
can't evaluate any expressions unless you know all functions. variables
templates etc that are defined, and you can't know that until _after_ the
stylesheet has been assembled by following the xsl:import.

as I wrote in the xsl-list thread:


Date: 6 Aug 2004 14:18:22 +0100
From: David Carlisle <davidc@n...>
To: xsl-list@l...
In-reply-to: <411381A6.1090205@f...> (message from Ralph Holz
	on Fri, 06 Aug 2004 15:03:34 +0200)
Subject: Re: [xsl] Parametrized includes -work-around?


> Correct?

yes

> Now, of course, that would be exactly the feature we want (typical, eh). :-)

why?

You want to have

main.xsl
...
<xsl:param name="x"/>
<xsl:include href="$foo"/>
...

and go

saxon input.xml main.xsl x=custom-a.xsl

you can't do that, but you can do this which is simpler and usually
equivalent:


custom-a.xsl
<xsl:include href="main.xsl"/>


saxon input.xml custom-a.xsl


That is instead of having your runtime choice pass a parameter to the
main stylesheet choose your top level stylesheet at run time, and have
all those top level stylesheets include the common code.


If you really do need to generate a stylesheet then what you described
is what Mike meant.

David





________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________