Re: [xsl] xml:base, resolve-uri and imported xslt files: how to get the importing base url from imported xslt

Subject: Re: [xsl] xml:base, resolve-uri and imported xslt files: how to get the importing base url from imported xslt
From: "Andrew Welch" <andrew.j.welch@xxxxxxxxx>
Date: Mon, 9 Oct 2006 15:46:57 +0100
On 10/9/06, Abel Braaksma <> wrote:
Dear List,

For what I understand from the specs and Michael Kay's books, the
following may very well be impossible: find the base URL of the
importing stylesheet from an imported stylesheet.

The use case:
I have a set of generalized xslt files. These are, naturally, imported
in more specific xslt files. One of these generalized xslt files (let's
call it common.xslt) must take an external document that has some
configuration options and parse these options. I declare it like this in
the root:

<xsl:variable name="configuration" select="document($param-config-url) />

My specific xslt file (let's call it specific.xslt), I use this variable
$configuration exhaustively. But the configuration xml file, referred to
by global parameter $param-config-url, is relative to the root of
specific.xslt. Is there a way to tell my imported xslt file where to look?

I tried the following to no avail:
<xsl:import href="../common/common.xslt" xml:base="." />
<xsl:import href="../common/common.xslt"
xml:base="file://specificpath/specific.xslt" />
<xsl:value-of select="$configuration"
xml:base="file://specificpath/specific.xslt" />

Even if these could work, I still cannot make xml:base dynamic, so only
the first option could be useful. I also tried xml:base on either root
xslt element and I tried if xsl:include had a different way or resolving
the uri.

The specs say (my interpretation):
- the uri is relative to the base uri of the xslt document or the base
uri of the source document, depending the location of the first argument
of document()
- the uri is relative to the current xslt instruction's base-uri
- if an xslt instruction does not have a base uri, it uses the base uri
of the parent, up until the uri of the xslt document.

Unfortunately, my parameters and variables are in global scope, meaning
that there's not context node I can trick to use as base href from.
Furthermore, I cannot use a variable, because a variable in the
importing xslt is not known in the imported xslt.

Only option I see, so far, is setting another global parameter that must
define the base uri for the imported xslt. I hoped that one relative uri
would suffice, but I guess I have to resort to using a specific absolute
location for each importing xslt.

Any better ideas? Did I miss something from the specs? In a way I hoped
that the import precedence would apply here, but apparently, that is not

In common.xslt change the variable

<xsl:variable name="configuration" select="document($param-config-url) />


<xsl:variable name="configuration" select="document($pathToConfig) />
<xsl:variable nam="pathToConfig" select="$param-config-url"/>

Then in specific.xslt you can override $pathToConfig with whatever you want, eg:

<xsl:variable nam="pathToConfig" select="concat('../../', $param-config-url)"/>


Current Thread