- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Tue, 10 Jul 2012 13:36:09 +0100
- To: public-rdf-dawg@w3.org
On 10/07/12 12:48, Polleres, Axel wrote: > >> ARQ passes 05 because ARQ only does graph isomorphism >> compare, not dataset isomorphism compare - it ought to fail >> but ARQ only has graph isomorphism checking code which is >> enough for all other tests. > > > But isn't this exactly what we ask for in the tests-README? > Cf. > >> http://www.w3.org/2009/sparql/docs/tests/README.html#updateevaltests >>>>>> we write: >>>>>> >>>>>> "A SPARQL implementation passes a update evaluation >> test if the >>>>>> graphs in the graph store are equivalent [RDF-CONCEPTS] to >>>> the graphs >>>>>> denoted in the mf:action property (and mf:result property, >>>>>> respectively) prior to the update execution (after update >>>> execution, >>>>>> respectively). Equivalence can be tested as described >>>> above for query >>>>>> evaluation tests." > > > We ask here exactly for equivalence in the sense of http://www.w3.org/TR/rdf-concepts/#section-graph-equality (i.e. modulo bnode labels)... So if 05a works for an implementation, then 05 should work as well, shouldn't it? If you define works as "passes our specific definition of a test that, in fact, does not actually test the right thing" then yes. 05 is not possible using the defn. 05a avoids the problem. 05 is confusing and adds nothing. Andy > > Axel >
Received on Tuesday, 10 July 2012 12:36:41 UTC