27848 2015-01-18 10:29:11 +0000 UseCaseJSON-002, UseCaseJSON-007 2015-01-19 16:14:30 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Working drafts PC Windows NT RESOLVED FIXED P2 normal --- 1 christian.gruen oneil mike public-qt-comments oldest_to_newest 117295 0 christian.gruen 2015-01-18 10:29:11 +0000 The query results should contain all possible permutations, because maps do not necessarily return key/value pairs in the order in which they had been inserted. See UseCaseJSON-007 as example: <result> <assert-deep-eq>map { "visible" : [ "AJISAI (EGS)", "AKARI (ASTRO-F)" ], "invisible" : [ "AAU CUBESAT" ] }</assert-deep-eq> </result> <result> <any-of> <assert-deep-eq>map { "visible" : [ "AJISAI (EGS)", "AKARI (ASTRO-F)" ], "invisible" : [ "AAU CUBESAT" ] }</assert-deep-eq> <assert-deep-eq>map { "visible" : [ "AKARI (ASTRO-F)" , "AJISAI (EGS)"], "invisible" : [ "AAU CUBESAT" ] }</assert-deep-eq> </any-of> </result> 117299 1 mike 2015-01-18 18:58:45 +0000 Surely this is unnecessary because deep-equal() on maps considers two maps as deep-equal regardless of the order of entries? 117300 2 christian.gruen 2015-01-18 20:29:31 +0000 The order of map entries does not matter indeed. But the results have nodes (UseCaseJSON-002) and arrays (UseCaseJSON-007) that have been generated from map contents; that's why I believe that all possible permutations need to be checked as possible outcomes. 117321 3 mike 2015-01-19 16:08:51 +0000 Sorry, yes, I see your point. 117322 4 mike 2015-01-19 16:14:30 +0000 Fixed as suggested.