RE: [xsl] XSLT 2.0 question

["Michael Kay" <michael.h.kay@xxxxxxxxxxxx>]

It's perfectly possible (even in XSLT 1.0) for a document to contain an
embedded stylesheet, which itself contains xsl:import declarations to import
additional stylesheet modules from elsewhere. The template rules in the
embedded stylesheet module would have the highest precedence, and therefore
override any template rules in the external stylesheet modules.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Bryan
> Rasmussen
> Sent: 18 March 2002 09:15
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] XSLT 2.0 question
>
>
> I'm thinking the answer to the following will be no, along
> with some choice
> witticisms regarding my ancestry, but I had a weird freaking
> idea a couple
> nights ago about using inline xslt as sort of a scripting
> language for an
> app I'm working on, obviously this is me thinking of future
> extensions to
> said app.
>
> am wondering if it would be possible to set up solutions that do the
> following in xslt 2.0, let us say you run your xslt against
> an xml document
> that contains inline xslt code, perhaps just a single
> xsl:template, would
> there be any way, hopefully incredibly involved and complex
> :) to declare
> that inline templates should be run and take precedence over
> templates in
> the xslt.
> so if I have in the xslt
> <xsl:template match="person">
> do something
> </xsl:template>
>
> and in the xml document I'm transforming
> <person>...</person>
> <code><xsl:template match="person">do something
> else</xsl:template></code>
>
>
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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