17250 2012-05-30 17:32:09 +0000 fn-filter-012 2012-05-31 09:55:11 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Last Call drafts PC All CLOSED FIXED P2 normal --- 1 mike tim public-qt-comments oldest_to_newest 68312 0 mike 2012-05-30 17:32:09 +0000 This test does fn:filter( fn:string#1, () ) and expects the result (). I think it is legitimate to raise XPTY0004, on the grounds that the supplied function is the wrong type: it returns a string rather than a boolean. Under Errors and Optimization it is also legitimate to return () 68368 1 oneil 2012-05-31 08:20:17 +0000 Hi Tim, this seems right to me, however would you be able to resolve this bug issue. Thanks. 68376 2 tim 2012-05-31 08:47:36 +0000 Agreed. For the record, it is the text "If the result of invoking the new function would necessarily result in a type error, that error may be raised during function coercion. It is implementation dependent whether this happens or not." that permits XPTY0004. 68383 3 tim 2012-05-31 09:19:05 +0000 Fixed in CVS. Please mark the bug as CLOSED if you agree with the resolution. Otherwise, REOPEN.