This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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>
Surely this is unnecessary because deep-equal() on maps considers two maps as deep-equal regardless of the order of entries?
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.
Sorry, yes, I see your point.
Fixed as suggested.