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 850237
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T07:13:57+00:00 2026-05-15T07:13:57+00:00

Why does <xsl:if test=<XPATH to boolean value here>> … </xsl:if> ALWAYS return true? Since

  • 0

Why does

<xsl:if test="<XPATH to boolean value here>">
...
</xsl:if>

ALWAYS return true?

Since boolean can be 0,1,”false” and “true” by definition, the ONLY way to test for a boolean value is to do string comparison against these. This can’t be right.

  • 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-05-15T07:13:58+00:00Added an answer on May 15, 2026 at 7:13 am

    The test specified in <xsl:if> works as if it called the boolean function. This function doesn’t work the way you might think. If its argument evaluates to a node-set (which it will be if you use a path as its argument) it will return true if the node-set is not empty, and false otherwise. So effectively, you’re testing for the existence of an element, not its value. If foo contains false,

    <xsl:if test="/path/to/foo">
    

    will always evaluate to true, since what you’re really asking in that test is “does this element exist?” and not “is element’s value true?” And the element exists.

    The rule that boolean values must be true, false, 1, or 0 is a part of XML Schema (which see) and not XPath, which doesn’t know anything about this rule. (XPath 1.0, that is. XPath 2.0/XQuery 1.0 has the fn:boolean function, which does smart, i.e. XML Schema aware, evaluation of boolean values.) To determine if a value is true in XSLT, you have to explicitly check it:

    <xsl:if test="/path/to/foo = 'true' or /path/to/foo = '1'">
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 436k
  • Answers 436k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer That's a list. Try >>> a = [1,1,2,3,5,8,13,21] >>> import… May 15, 2026 at 3:55 pm
  • Editorial Team
    Editorial Team added an answer Try changing the names of the parameters myCommand.Parameters.Add(new OleDbParameter("@startRowIndex",startRowIndex)); myCommand.Parameters.Add(new… May 15, 2026 at 3:55 pm
  • Editorial Team
    Editorial Team added an answer It wouldn't harm replacing Bind with Eval in your Item… May 15, 2026 at 3:55 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.