On 29.12.2021 20:06, Dimitre Novatchev dnovatchev(_at_)gmail(_dot_)com wrote:
On Wed, Dec 29, 2021 at 10:27 AM Martin Honnen
martin(_dot_)honnen(_at_)gmx(_dot_)de
<mailto:martin(_dot_)honnen(_at_)gmx(_dot_)de>
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com
<mailto:xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>> wrote:
> I don't have to know one, I just pointed out that the spec doesn't
> guarantee the order. Thus I don't see why, given the spec, one should
> expect any implementation to preserve the order.
I am happy to state that the provided solution produces the correct
result on all currently-existing XPath engines :)
As if you had or could verify that. As I said, eXist-db is struggling
with generate-id based approaches, at least if nodes from different
document (fragments?) are involved.
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--