i've got a sizable template in which this:
   <xsl:value-of select="//core:type[@id='publisher_type']/@id"/>

works correctly when in my main template, but finds no nodes when in
a later template.

with my understanding, any path starting with "//" should produce
the same thing regardless of where it is located, at least as long
as it doesn't use any variables in it, and there is no use of xsl:document
above it. 

if someone could confirm that theory to me, that would be great,
so i can work on finding a minimal test case for the processor
bug, rather than tearing my hair out.

-mda


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list