- From: Kay, Michael <Michael.Kay@softwareag.com>
- Date: Mon, 17 Nov 2003 23:23:54 +0100
- To: David Carlisle <davidc@nag.co.uk>, public-qt-comments@w3.org
- Message-ID: <DFF2AC9E3583D511A21F0008C7E62106073DD2B7@daemsg02.software-ag.de>
I would also think that if eg:union and eg:intersect remove duplicates, then eg:except should do the same. So perhaps putting distinct-values() into this one is the answer. Michael Kay > -----Original Message----- > From: David Carlisle [mailto:davidc@nag.co.uk] > Sent: 17 November 2003 15:57 > To: public-qt-comments@w3.org > Subject: [F&O] C.2.3 eg:value-except > > > > > The description (possibly copied from C.2.1 eg:value-union) says > > " ...in an undefined order." > > However both the xslt and xquery implementations given > preserve the input order. Either the phrase should be dropped > or fn:unordered() should be used in the implementations. > > The equivalent comment in C.2.1 does not have this problem as > there the implementations use fn:distinct-values() so do > return things in an > an implementation dependent (rather than undefined) order. > > David > > ______________________________________________________________ > __________ > This e-mail has been scanned for all viruses by Star > Internet. The service is powered by MessageLabs. For more > information on a proactive anti-virus service working around > the clock, around the globe, visit: http://www.star.net.uk > ______________________________________________________________ > __________ >
Received on Monday, 17 November 2003 17:24:56 UTC