Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8641163
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T11:27:20+00:00 2026-06-12T11:27:20+00:00

The identity template looks like this: <xsl:template match=@*|node()> <xsl:copy> <xsl:apply-templates select=@*|node() /> </xsl:copy> </xsl:template>

  • 0

The identity template looks like this:

<xsl:template match="@*|node()">
    <xsl:copy>
        <xsl:apply-templates select="@*|node()" />
    </xsl:copy>
</xsl:template>

Does <xsl:apply-templates select="@*|node()" /> select more than <xsl:apply-templates />, or could the identity template have been like this?

<xsl:template match="@*|node()">
    <xsl:copy>
        <xsl:apply-templates />
    </xsl:copy>
</xsl:template>

What exactly is selected when I do the following?

<xsl:apply-templates />
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T11:27:21+00:00Added an answer on June 12, 2026 at 11:27 am

    Does <xsl:apply-templates select="@*|node()" /> select more than
    <xsl:apply-templates />, or could the identity template have been
    like this?

    <xsl:apply-templates/> 
    

    is equivalent to:

    <xsl:apply-templates select="node()"/>
    

    and this is a shorter former of:

    <xsl:apply-templates select="child::node()"/>
    

    and this is a equivalent to:

    <xsl:apply-templates select="* | text() | comment() | processing-instruction()"/>
    

    As we see from the last instruction, the xsl:apply-templates instruction you are asking about, doesn’t select any attributes, therefore it cannot be used as a shorthand for:

    <xsl:apply-templates select="@*|node()"/>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

So I'm using the identity design pattern for XSLT: <xsl:template match=@*|node()> <xsl:copy> <xsl:apply-templates select=@*|node()[not(@visible='false')]/>
I'm trying to add a processing instruction after each <xi:include> element. <xsl:template match=@*|node() name=identity>
in mako template, i use this ${request.environ['repoze.who.identity']['user']} and the render in controller: render('file.html') can
I'm using: <xsl:template match=material_id | location_code></xsl:template> To get rid of elements in the source
I have an XML document that looks like this: <?xml version=1.0 encoding=utf-8?> <Schema Namespace=EDIManagement.Models.Store
I'm looking for a workaround on passing parameters to a template-match. I'm aware this
I would like to have a nice template for doing this in development. How
Given the following document: <foo> <object> <property name=value> <!-- MATCH THIS NODE --> <string>alpha</string>
*****Code Sign error: The identity 'iPhone Developer: XXXXXXXXXX' doesn't match any valid certificate/private key
Is there an IDENTITY like column type that generates alphanumeric values? Like 023904F?

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.