Subject: Re: searching for occurrences of unique string-value and replacing with string value of another node
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Wed, 11 Jun 2008 11:52:26 -0400
|
Julie,
At 10:40 AM 6/11/2008, you wrote:
>Assuming the context node is an element, that means all attributes of
>the element. Otherwise it means zero nodes (as only elements have
>attributes).
Okay, so in this case I don't think I understand the purpose of this
template. The context is matching all nodes on the attribute access OR
all child nodes of the context node, right? It is then applying
templates and selecting the exact same thing. Doesn't that mean there
*is* no context? Wouldn't the same thing be achieved by just calling a
match to the root?
<xsl:template match="/">
I tried removing this template from the stylesheet and I do still get
the same beautiful result (thanks Michael!).
As it happens, the template
<xsl:template match="@*|node()">
<xsl:apply-templates select="@*|node()"/>
</xsl:template>
does almost the same thing as XSLT's built-in templates, which are
used whenever a node is matched for which you have not provided a
template. (It doesn't do exactly the same thing, but it has the same
result. The built-in templates do not select attributes for
processing, but if they are selected, their values get written. With
this template, they are selected and matched, but their values never
get written.)
So generally speaking, you can remove this template and get the same output.
Cheers,
Wendell
======================================================================
Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
|
Cart
