|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Implementing XPointer Resolution Withsaxon:evaluat
Hi Eliot,
At 06:21 PM 8/13/2002, you wrote: > Yet if they contain all the same information, using a node-set extension > couldn't you query into them and find the further information you need to > continue along your chain? Yes, this makes sense. Maybe I wasn't clear or complete enough in my question. Cutting through, for example, if you had <xsl:key match="*" use="generate-id()"/> you could at any time get a node back given its generated ID as a key value. Admittedly this isn't much use if you don't have the node and therefore can't get its generated ID to look for it. (I guess in effect this is the knot you're trying to cut. The application of keys for node referencing assumes you know what values associated with a node, such as an attribute or whatever, will be referenced elsewhere and thus be useful as a key.) But if you did have that value in a node, it wouldn't matter if you called the key function with that node or a copy of it. I guess I'm spinning around the same circle you are. :-) Cheers, Wendell
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








