Copyright © 2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, and document use rules apply.
Bindings
This page describes W3C SPARQL Working Group's SPARQL 1.1 test suite.
The test manifests and entries are built automatically from manifest.ttl using a Rake task. Tests may be contributed via pull request to https://github.com/w3c/rdf-tests with suitable changes to the manifest.ttl and referenced files.
Distributed under both the W3C Test Suite License and the W3C 3-clause BSD License. To contribute to a W3C Test Suite, see the policies and contribution forms.
UNDER BOTH MUTUALLY EXCLUSIVE LICENSES, THIS DOCUMENT AND ALL DOCUMENTS, TESTS AND SOFTWARE THAT LINK THIS STATEMENT ARE PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
| data01.ttl |
| data02.ttl |
Each VALUES row is joined with every named graph
| data01.ttl |
| data02.ttl |
Only graphs named by FROM NAMED are iterated; rows binding the graph variable to a graph excluded by FROM NAMED (ex:g2) or to an IRI that is no graph name at all (ex:unknown) are removed
GRAPH ?g does not produce solutions for graph names outside the dataset, even if they are bound by a joined pattern and the inner pattern contains no triple patterns
GRAPH
ORDER BY sorts by a variable that only the trailing VALUES clause binds
OFFSET and LIMIT apply after the join with the trailing VALUES clause
DISTINCT applies after the join with the trailing VALUES clause, which duplicates each solution
The trailing VALUES clause is joined after grouping, so ORDER BY can use an expression over a variable that only the trailing VALUES clause binds
SELECT * includes the variables of the trailing VALUES clause
A trailing VALUES clause without rows makes the result empty
A trailing VALUES clause with two empty rows duplicates each solution
OFFSET and LIMIT of the subquery apply after the join with its trailing VALUES clause
The trailing VALUES clause removes all solutions, so the answer is false
The template uses a variable that only the trailing VALUES clause binds
The trailing VALUES clause is joined after grouping, so the template can use a variable that only the trailing VALUES clause binds
The trailing VALUES clause is joined before LIMIT. The template has a single triple, so LIMIT gives the same result whether it applies to the solutions or to the constructed triples
The trailing VALUES clause is joined after grouping, so the projection can use a variable that only the trailing VALUES clause binds
The trailing VALUES clause is joined after grouping, so a SELECT expression can use a variable that only the trailing VALUES clause binds
The trailing VALUES clause is joined with the grouped solutions on the grouping variable