Saxon is correct. In terms of the XSLT 1.0 specification, $w is a result tree fragment, so the rules are given in 11.1
 
http://www.w3.org/TR/xslt#section-Result-Tree-Fragments
 
A result tree fragment is treated equivalently to a node-set that contains just a single root node. However, the operations permitted on a result tree fragment are a subset of those permitted on a node-set. An operation is permitted on a result tree fragment only if that operation would be permitted on a string (the operation on the string may involve first converting the string to a number or boolean). In particular, it is not permitted to use the /, //, and [] operators on result tree fragments. When a permitted operation is performed on a result tree fragment, it is performed exactly as it would be on the equivalent node-set.
 
When a node-set is converted to a boolean, the result is true if the node-set contains at least one node. So the boolean value of a result tree fragment is always true. It is *not* correct to convert the node-set to a string and then convert the string to a boolean.
 
The 2.0 spec is couched in different language but the effect is the same.
 
As it happens, I read a couple of days ago that Xalan "optimizes" <xsl:variable name="x"><xsl:value-of select="abc"/></xsl:variable> to <xsl:variable name="x" select="abc"/>. This "optimization" is incorrect, because the boolean value is different in the two cases.
 
In practice it's nearly always better to use the form <xsl:variable name="x" select="abc"/> - creating a result tree fragment rather than a string is very inefficient. Saxon tries to optimize it too, because (for reasons I have never understood) users will insist on writing the more verbose and less efficient construct: but it optimizes it to something that retains the semantics.
 
Michael Kay
http://www.saxonica.com/


From: saxon-help-admin@lists.sourceforge.net [mailto:saxon-help-admin@lists.sourceforge.net] On Behalf Of Wolf, Phillips
Sent: 12 April 2006 22:21
To: saxon-help@lists.sourceforge.net
Subject: [saxon] Unexpected xsl:when test result

Saxon and Xalan execute this XSL differently. 
Saxon finds the "xsl:when" test true; Xalan finds it false.
Isn't false correct?

Xalan-J 2.7 (Interpreted) displays Puffins
Saxon 8.7J                displays Penguins

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match='/'>
  <xsl:variable name='v'/>
  <xsl:variable name='w'><xsl:value-of select='$v'/></xsl:variable>
  <xsl:message>
    <xsl:choose>
      <xsl:when test='$w'>Penguins</xsl:when>
      <xsl:otherwise>Puffins</xsl:otherwise>
    </xsl:choose>
  </xsl:message>
</xsl:template>
</xsl:stylesheet>