From 46ac922b3cd7a90faa48a9757ab6d90c6f116a72 Mon Sep 17 00:00:00 2001 From: Ruben Taelman Date: Mon, 20 May 2019 08:52:44 +0200 Subject: [PATCH] Clarify comparison of literals in SPARQL test suite Closes #58 --- sparql11/index.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/sparql11/index.html b/sparql11/index.html index 7973cef8..1b6774e2 100644 --- a/sparql11/index.html +++ b/sparql11/index.html @@ -281,8 +281,7 @@

Query Evaluation Tests

equivalent [RDF-CONCEPTS] to the graph named in the result (after encoding in the DAWG result set vocabulary, if necessary). Note that, solution order only is considered relevant, if the result is expressed in the test suite in the DAWG result set vocabulary, with explicit rs:index triples; otherwise solution order is considered irrelevant for passing. Equivalence can be tested by -checking that the graphs are isomorphic and have identical IRI and -literal nodes. Note that testing whether two result sets are isomorphic is simpler than full graph isomorphism. Iterating over rows in one set, finding a match with the other set, removing this pair, then making sure all rows are accounted for, achieves the same effect.

+checking that the graphs are isomorphic with identical IRI nodes, and equal literal nodes that are compared by value (test runners may convert lexical form to canonical form to compare character by character). Note that testing whether two result sets are isomorphic is simpler than full graph isomorphism. Iterating over rows in one set, finding a match with the other set, removing this pair, then making sure all rows are accounted for, achieves the same effect.

Query evaluation tests that involve the REDUCED keyword have slightly different passing criteria. These tests are indicated in the manifest files with the mf:resultCardinality predicate with an object of mf:LaxCardinality. To pass such a test, the result set produced by a SPARQL implementation must contain each solution in the expected result set at least once and no more than the number of times that the solution occurs in the expected result set. (That is, the expected result set contains the solutions with cardinalities as they would be if the query did not contain REDUCED; to pass the test, an implementation must produce the correct results with cardinalities between one and the cardinlity in the expected result set.)