RE: import/include and apply-imports

What the spec actually says is that "xsl:apply-imports processes the current
node using only template rules that were imported into the stylesheet
element containing the current template rule".

The term "current template rule" is well-defined, but "stylesheet element"
and "imported into" are not. I interpret "stylesheet element" to mean "an
xsl:stylesheet element", or what in my book I call a stylesheet module. I
interpret "imported into" to mean that the template rule must be in a
stylesheet module that was either imported directly into this module using
an <xsl:import> element in this module, or that was "imported into" a
stylesheet module that was "directly imported" or "directly included" into
this module.

In this situation, on my reading of the spec, the template rule in
"third.xsl" is not "imported into" the stylesheet module containing the
template rule in "second.xsl".

Mike Kay

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of
> Janning Vygen
> Sent: 09 May 2001 18:19
> To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  import/include and apply-imports
>
>
> strange behaviour using apply-imports
>
> following example:
>
> first.xsl:
> ------
> <xsl:import href="third.xsl">
> <xsl:include href="second.xsl">
>
> second.xsl
> --------
> <template match="book">
>   <xsl:apply-imports/>
> </template>
>
> third.xsl
> ------
> <template match="book">
>   AM I EVER EVER MATCHED?
> </template>
>
>
> the template in the third.xsl is NEVER matched!!
> Why? I thought, that include means, the stylesheet is
> included like it was
> always in this file??
>
> Is this correct behaviour? i am using Saxon and i dont think
> that saxon is
> making any mistakes, but including means to me just splitting
> a huge document.
>
> Janning
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list