Re: [xsl] key declarations (using a sequence constructor)

Subject: Re: [xsl] key declarations (using a sequence constructor)
From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 06 Oct 2009 13:52:22 -0400
At 2009-10-06 18:22 +0100, Andy Chambers wrote:
I'm playing around with the added features available in key
declarations but I think I must be misunderstanding
something.  Here's my key declaration (I realize that this particular
example would be better as a simple
@use but I want to understand how it works to see if it might make
some of my other keys look a little

  <xsl:key name="keyNames"
                   match="name | mdv">
        <lookup oid="{@oid}"/>

According to the value of the key is atomized. Your key is an element node. The typed value of the element node is the string value (untypedAtomic) of the text content, in your case an empty string, according to:


I thought that to use this key to lookup the @name associated with
@oid="AA.AA" for example, I'd do

        <xsl:variable name="lookup">
          <lookup oid="AA.AA"/>
        <xsl:sequence select="key('keyNames', $lookup)/@name"/>

According to the lookup value is an atomic value. Your key being passed is a document node and the atomized value is the string value of that tree, which in your example is the empty string.

But this actually returns a sequence containing all the @names.

I seek enlightenment as to why this is so :-)

Every member in your key table has the empty string as the associated key value, and you are looking up the key value using an empty string. Thus, every member of the key table is being returned to you, so you are getting every attribute.

I hope this helps.

. . . . . . . . . . Ken

-- Upcoming: hands-on code list, UBL, XSLT, XQuery and XSL-FO classes in Copenhagen Denmark and Washington DC USA, October/November 2009 Interested in other classes? Crane Softwrights Ltd. Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video Video lesson: Video overview: G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Male Cancer Awareness Nov'07 Legal business disclaimers:

Current Thread