Re: A suggestion re <xsl:import>

Not got my eye on what is in the pipeline but I frequently run into
scenarios where I would like to but cannot use xsl:import.

It would be nice to have a facility that replicated the semantics of
xsl:import without the requirement for the imported code to be in a
separate file - the intended use case is as above ( although it will
probably get abused).

In principle the code doesn't _have_ to be in a separate file, it
depends on the abilities of your URI resolver, for example you could use

But there are rather few cases where you can not replace a xsl:import by
just directly including the templates in the current file, adjusting
priorities and using xsl:next-match instead of xsl:apply-imports

Actually converting from one form to another is a bit tiresome but if
you know that you want to keep things in ome file it is usually possible
to write in a style using xsl;next-match more and xsl:apply-imports less.

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.