 <p>On a very basic level, you use <code>&lt;xsl:apply-templates&gt;</code> when you want to let the processor handle nodes automatically, and you use <code>&lt;xsl:call-template/&gt;</code> when you want finer control over the processing. So if you have:</p> <pre><code>&lt;foo&gt; &lt;boo&gt;World&lt;/boo&gt; &lt;bar&gt;Hello&lt;/bar&gt; &lt;/foo&gt; </code></pre> <p>And you have the following XSLT:</p> <pre><code>&lt;xsl:template match="foo"&gt; &lt;xsl:apply-templates/&gt; &lt;/xsl:template&gt; &lt;xsl:template match="bar"&gt; &lt;xsl:value-of select="."/&gt; &lt;/xsl:template&gt; &lt;xsl:template match="boo"&gt; &lt;xsl:value-of select="."/&gt; &lt;/xsl:template&gt; </code></pre> <p>You will get the result <code>WorldHello</code>. Essentially, you've said "handle bar and boo this way" and then you've let the XSLT processor handle these nodes as it comes across them. In most cases, this is how you should do things in XSLT.</p> <p>Sometimes, though, you want to do something fancier. In that case, you can create a special template that doesn't match any particular node. For example:</p> <pre><code>&lt;xsl:template name="print-hello-world"&gt; &lt;xsl:value-of select="concat( bar, ' ' , boo )" /&gt; &lt;/xsl:template&gt; </code></pre> <p>And you can then call this template while you're processing <code>&lt;foo&gt;</code> rather than automatically processing <code>foo</code>'s child nodes:</p> <pre><code>&lt;xsl:template match="foo"&gt; &lt;xsl:call-template name="print-hello-world"/&gt; &lt;/xsl:template&gt; </code></pre> <p>In this particular artificial example, you now get "Hello World" because you've overriden the default processing to do your own thing.</p> <p>Hope that helps.</p>