Re: [xsl] XSLT 1.0 support in browsers, as of June 2008

[Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>]

At 11:01 AM 6/18/2008, it was written:
> > and
> > <xsl:if test="not(ancestor::ed:del) and not(//xref[@target=$anchor])">
> > ...very much :0)
>
> The only way to avoid the "//" above would be to use xsl:key

Is that they case? Binding //xref or //xref[@target] to a variable 
might do nearly as well as a key.

Not that using a key wouldn't give an even finer edge.

Semantically, keys are entirely redundant. If performance were never 
an issue, one could always write an absolute location path from the 
root that would work as well as a key. Keys are useful only because 
they allow for optimization using information that cannot always be 
deduced reliably from a stylesheet by itself. (Without an input 
document or schema it can't always be known if a particular path will 
be traversed many times, or only once.)

Cheers,
Wendell



======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================