W3C home > Mailing lists > Public > xsl-editors@w3.org > April to June 1999

evaluation context of parameters:

From: Jon Seymour <Jon.Seymour@cwo.com.au>
Date: Thu, 10 Jun 1999 22:56:59 +1000
Message-ID: <55383C05310FD211A99F0000F87C0B4B01C0666F@milnte01.optus.com.au>
To: "'xsl-editors@w3.org'" <xsl-editors@w3.org>
First let me say, I think XSLT is an excellent piece of work! We have been
using Lotus XSL for the past month now, primarily to do java code
generation. It has saved us absolutely heaps of time!

I posted this to the LotusXSL discussion group, but since I think it
highlights a deficiency in the specification, you guys might be interested

The stylesheet below contains a complete test case for the issue at hand.

jon seymour

Working at Optus Communications Ltd (jon.seymour@yes.optus.com.au)
Employed by IBM Global Services Australia (jseymour@au1.ibm.com)


<?xml version="1.0" encoding="ISO-8859-1"?>

   Consider the XML below, the expected output and the actual output (with
Lotus XSL 0.17.1)

   I say, expected output, because I think it would be reasonable for @id to
be evaluated in the
   context of the node which is invoking apply-templates, rather than the
context of the node
   which matches the selection criteria of apply-templates. I read the
specification for clarification
   on this matter, but it appears to be mute on this point.

      <A id="a">
         <B id="b">

   Expected Output:

   Actual Output:



<xsl:template match="A">
   <xsl:apply-templates select="B">
       <xsl:param name="p1" expr="@id"/>

<xsl:template match="B">
   <xsl:param-variable name="p1"/>
   <xsl:value-of select="string($p1)"/>
Received on Thursday, 10 June 1999 08:54:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:16 UTC