Andrew Welch wrote:
Then in specific.xslt you can override $pathToConfig with whatever you
want, eg:
Thanks to you all for the many contributions! I've resolved my issue by
both de-generalizing a bit, requiring that the specific XSLT files (they
obey to a certain predefined structure) must include a global param with
value as follows:
<xsl:param name="resource-location-url" as="xs:string"
select="resolve-uri('')" />
This, as a matter of fact, resolves my problems, even though I cannot
place this line outside the specialized documents into the generalized
ones. In the imported files, I do basically the same, but luckily, the
import precedence takes over and chooses the highest parameter.
Still, I wonder pretty much how I could utilize xml:base with, for
instance, saxon, or any other xslt 2.0 aware processor. As I understand
now, and from Michael's books, this should indeed be utilized by the
processor.
Thanks again all of you,
Cheers,
-- Abel Braaksma
http://www.nuntia.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>
--~--