Doxsl uses the metaphor of a stylesheet as an application. Each application consists of one or more modules (individual stylesheet files).
The core Doxsl processor traverses through the
xsl:include declarations and collects each stylesheet
file contents into a
dx:module element. The
element contains several attributes that contain metadata about each stylesheet including
import precedence, and the "parent" stylesheet that imported/included the current stylesheet.
dx:application element is used as a container for the collection
When the collection process is complete, the core Doxsl processor invokes the
OnApplicationCollected named template and passes the
dx:application element as a parameter.
OnApplicationCollected named template acts like
an "abstract" method that must be overridden. For each Doxsl implementation,
there will be a local instance of this named template that overrides the base instance.
This should be the starting point for generating the output. At this point,
processing occurs on the