RE: Recursive Template Application

Subject: RE: Recursive Template Application
From: Matt Sergeant <matt@xxxxxxxxxxxx>
Date: Mon, 19 Jun 2000 11:22:38 +0100 (BST)
On Mon, 19 Jun 2000, Kay Michael wrote:

> > This stylesheet works only half-way in that it correctly 
> > transforms "<toc/>" to "<section .../>" but leaves it at that. The output
> of T1 
> > is not matched by T2. But how can I enforce this, so that "<toc/>" is 
> > finally transformed to "<h2>..."? Should I run the XSL processor twice? Or
> is there a more
> > efficient way to accomplish this?
> > 
> XSLT is a "single-pass" process, all template rules are applied to the input
> document (or tree), there's no standard way within the language of applying
> a second transformation to the result of the first.

Actually there is a standard way, but its outside the realm of XSLT and
inside the realm of XML. Its called "cascading" and is detailed in the
HTML 4.0 spec, and referenced explicitly in

The only processor I'm aware of that directly supports this model is AxKit
(funny that, eh?), although I'm certain there must be others. I've written
a sort of high-level overview of how this works on the axkit web


Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability. | AxKit:

 XSL-List info and archive:

Current Thread