This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: How is this part of the XSLT specification to be interpreted?
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: How is this part of the XSLT specification to be interpreted?
- From: Thorbjørn Ravn Andersen <TRA at stibo dot dk>
- Date: Tue, 20 Jun 2000 16:26:51 +0200
- Reply-To: xsl-list at mulberrytech dot com
> <xsl:template match="p[list]" linda:someattribute="">
> <xsl:apply-templates/>
> </xsl:template>
Ah! That makes sense.
Since this is a part of a "how can we document our style sheets internally" project, an attribute is still a bit limited since it is a scalar instead of a node set.
Is there a similar way to have non-XSLT elements inside an XSLT-element (like a template) without having it copied verbosely to the output. I basically just want the element and everything therein ignored.
Basically, so
<xsl:template match="TOC">
<doc:test>Hallo</doc:test>
<rowset>
<xsl:apply-templates/>
</rowset>
</xsl:template>
is treated identically to
<xsl:template match="TOC">
<rowset>
<xsl:apply-templates/>
</rowset>
</xsl:template>
Currently the following line is output (buh is the namespace URI I used)
<doc:test xmlns:doc="buh">Hallo</doc:test>
From my glancing at the other parts of the spec, it appears that I must make the doc:* namespace "active" in order to get the behaviour I desire, which in Saxon means I must create a Java class for the purpose, which is rather inconvenient since it looses portability.
My goal is documentation on a higher level than <!-- comment --> and JavaDoc. Can it be done as a valid XSLT-file?
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list