why not? It appears to do exactly what you want. Did you try it?
Well, I did, but probably I am doing it wrong... In your earlier message, you
wrote:
just have
<xsl:apply-templates select="abcd:Gathering"/>
together with a template
<xsl:template match="LongitudeDecimal"/>
that does nothing on thse elements.
then when you do want to process the elements do (according to taste)
<xsl:apply-templates
abcd:Gathering/GatheringSite/SiteCoordinates/LongitudeDecimal"
mode="somemode"/>
together with some templates in somemode to do whatever needs doing or
if you don't want a new mode do
<xsl:apply-templates
abcd:Gathering/GatheringSite/SiteCoordinates/LongitudeDecimal/node()"
/>
so you process the children of LongitudeDecimal.
So I do have something very simple like
<xsl:template match="/">
(...)
<xsl:apply-templates select="abcd:Gathering"/>
(...)
<xsl:template>
<xsl:template match="LongitudeDecimal">
<!-- do nothing -->
</xsl:template>
There are no children to LongitudeDecimal, so I would not have to process them.
But what I still don't understand is the rest of it: how do I apply the
LongitudeDecimal-template to Gathering, so that the "empty" template rule
overrules the output I get from just calling the Gathering node?
-----Original Message-----
From: David Carlisle [mailto:davidc(_at_)nag(_dot_)co(_dot_)uk]
Sent: Dienstag, 2. September 2003 13:43
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] XPath: excluding a descendant
(...)
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list