This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Implementing XPointer Resolution Withsaxon:evaluate()


Hi Eliot,

> The use of generate-id() is simply a test that this is happening:
> generate-id() lets me test node (object) identity in the context of
> XSLT processing.

The generated IDs would also let you get to the node you were after,
if you defined a key that indexed nodes by their generated ID:

<xsl:key name="generated-id" match="node()|@*" use="generate-id()" />

If you had your resolve-xpointer template returning a result tree
fragment of 'node' elements for the value of the $members variable,
you could use:

  key('generated-id', exsl:node-set($members)/node)

to get your list of the actual nodes themselves.

It's quite a large key table, though (!) which is why using an
extension function to return the nodes themselves is possibly a
cleaner way to do it.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]