Re: [xsl] xinclude, temp trees, and keys

[Bruce D'Arcus <bdarcus@xxxxxxxxxxxxx>]

On Nov 20, 2004, at 12:37 PM, Michael Kay wrote:

> <xsl:for-each-group select="//db:biblioref/@linkend" group-by=".">
>            <xsl:if test="position() &gt; 1">,%20</xsl:if>
>            <xsl:text>&apos;</xsl:text>
>            <xsl:value-of select="."/>
>            <xsl:text>&apos;</xsl:text>
>          </xsl:for-each-group>
>
> One reason is that for-each-group gives you more control over ordering 
> in
> the result than distinct-values (the order of the result of 
> distinct-values
> is implementation-defined).

So if in other contexts I need to be able to know the first occurrence 
of a unique value, then I want to be using the above approach?

> Incidentally, the &apos; could just as well be written '.
>
> However, I don't understand the problem well enough to know which 
> document
> you are trying to search at this point.

The concrete case is to account for two different scenarios:

1)  an article
2) a book, which may have xincluded chapters (as mine does)

So, I need to scan the complete document (including the outside 
chapters which I suck into a temporary tree) for citation references, 
then use the unique values from that to construct a query that I send 
via the doc() function to eXist, taking the returned results an adding 
it to the temporary tree.

As I thought about this more, then, it's starting to seem like I need 
another pass:

1)   xinclude content
2)  resolve citation references and include them
3)  work with temporary tree enhancing data where necessary
4)  pass off to main stylesheets for final rendering

Does that seem right?

Bruce