Subject: RE: process order (still...) From: "Pawson, David" <DPawson@xxxxxxxxxxx> Date: Thu, 13 Apr 2000 08:41:10 +0100 |
Mike Brown >So, count(@*) should never vary, but generate-id(@*[1]) in one >implementation might be equal to generate-id(@*[5]) in some other >implementation. I would hope that would fail Mike. An id on an attribute? <q>The generate-id function returns a string that uniquely identifies the node in the argument node-set that is first in document order. </q> I see the param is node-set, so perhaps you are right! I'd love to see that tested :-) >Also, it seems to be complicated by the fact that element >nodes do have a >natural order. Take for example the node-set returned by this XPath >expression for an imaginary XHTML document: "//img/@*" ... Could I be >assured that //img[1]'s attribute nodes would come before //img[2]'s? Suggest yes because then you are dealing with the in-memory model which should be consistant. Regards, DaveP XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: Printing out variables with esc, Kay Michael | Thread | Re: process order (still...), David Carlisle |
Re: process order (still...), Mike Brown | Date | RE: Generating Tab delimited lists, Pawson, David |
Month |