Service Execution Failure

\n\n

The execution of a SERVICE pattern may fail due to several reasons: the remote service may be down, the service IRI may not be dereferenceable, or the endpoint may return an error to the query. Normally, under such circumstances the invoked query containing a SERVICE pattern fails as a whole. Queries may explicitly allow failed SERVICE requests with the use of the SILENT keyword. The SILENT keyword indicates that errors encountered while accessing a remote SPARQL endpoint should be ignored while processing the query. The failed SERVICE clause is treated as if it had a result of a single solution with no bindings.

In the following query the SILENT keyword is present. If the remote SPARQL endpoint is not available because the SPARQL endpoint does not exist, it is down or it is not accessible the query will return a solution sequence of one empty solution mapping. If the SILENT keyword is not present, the query will stop and return the error.

Data in <http://people.example.org/sparql> endpoint:

  <http://example.org/people15>  <http://xmlns.com/foaf/0.1/name>     \"Charles\" .\n

Query:

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nSELECT ?name\nWHERE\n{\n  SERVICE SILENT <http://people.example.org/sparql> { \n    <http://example.org/people15> foaf:name ?name . }\n}\n

Query result if an error occurs while querying the remote SPARQL endpoint:

\n\n \n \n \n \n \n \n

name

"^^ ; ; "Service Execution Failure" . a ; "

Simple query to a remote SPARQL endpoint

\n\n

This example shows how to query a remote SPARQL endpoint and join the returned data with the data from the local RDF Dataset. Consider a query to find the names of the people we know. Data about the names of various people is available at the http://people.example.org/sparql endpoint:

  @prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n  @prefix : <http://example.org/> .\n\n  :people15  foaf:name     \"Alice\" .\n  :people16  foaf:name     \"Bob\" .\n  :people17  foaf:name     \"Charles\" .\n  :people18  foaf:name     \"Daisy\" .\n

and one wants to combine with a local FOAF file

http://example.org/myfoaf.rdf that contains the single triple:

<http://example.org/myfoaf/I> <http://xmlns.com/foaf/0.1/knows>  <http://example.org/people15> . \n

Query:

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nSELECT ?name\nFROM <http://example.org/myfoaf.rdf>\nWHERE\n{\n  <http://example.org/myfoaf/I> foaf:knows ?person .\n  SERVICE <http://people.example.org/sparql> { \n    ?person foaf:name ?name . } \n}\n

This query, on the data above, has one solution:

Query Result:

\n\n \n \n \n \n \n \n

name
\"Alice\"

"^^ ; ; "Simple query to a remote SPARQL endpoint" . a ; "

SPARQL query with OPTIONAL to two remote SPARQL endpoints

\n\n

Imagine we want to query people and optionally obtain their interests and the names of people they know. Imagine for instance, two endpoints containing data about people:

Data in the default graph at remote SPARQL endpoint: http://people.example.org/sparql

\n  @prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n  @prefix : <http://example.org/> .\n\n  :people15  foaf:name     \"Alice\" .\n  :people16  foaf:name     \"Bob\" .\n  :people17  foaf:name     \"Charles\" .\n  :people17  foaf:interest     <http://www.w3.org/2001/sw/rdb2rdf/> .\n\n

and data in the default graph the remote SPARQL endpoint: http://people2.example.org/sparql

\n  @prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n  @prefix : <http://example.org/> .\n\n  :people15  foaf:knows    :people18 . \n  :people18  foaf:name     \"Mike\" .\n  :people17  foaf:knows    :people19 . \n  :people19  foaf:name     \"Daisy\" .\n\n

Query:

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nSELECT ?person ?interest ?known\nWHERE\n{\n  SERVICE <http://people.example.org/sparql> { \n    ?person foaf:name ?name .  \n    OPTIONAL { \n      ?person foaf:interest ?interest .\n      SERVICE <http://people2.example.org/sparql> { \n        ?person foaf:knows ?known . } }\n  }    \n}\n

This query, on the data above, has three solutions:

Query Result:

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

person	interest	known
\"Alice\"
\"Bob\"
\"Charles\"	<http://www.w3.org/2001/sw/rdb2rdf/>	<http://example.org/people19>

\n\n

Notice that in the query above there is a nested SERVICE in the OPTIONAL clause. This query requires the SPARQL query service at http://people.example.org/sparql to support basic federated query.

"^^ ; ; "SPARQL query with OPTIONAL to two remote SPARQL endpoints" . a , ; "

SPARQL 1.1 Federated Query Extension

\n\n

The SERVICE keyword instructs a federated query processor to invoke a portion of a SPARQL query against a remote SPARQL endpoint. This section presents examples of how to use the SERVICE keyword. The following sections define the syntax and semantics of this extension.

"^^ ; ; "SPARQL 1.1 Federated Query Extension" . a ; "

Interplay of SERVICE and VALUES (Informative)

\n\n

SPARQL 1.1 Query includes the VALUES clause (VALUES), which can be used to provide an unordered solution sequence that is joined with the results of the query evaluation. Implementers of SPARQL 1.1 Federated Query may use the VALUES clause to constrain the results received from a remote endpoint based on solution bindings from evaluating other parts of the query.

The following example shows how SERVICE and VALUES can work together. Suppose a query that asks for all instances of foaf:Person in the default graph and also their known people in the remote endpoint http://example.org/sparql:

Data in the default graph:

\n  @prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n  @prefix : <http://example.org/> .\n\n  :a a foaf:Person  ;\n     foaf:name     \"Alan\" ;\n     foaf:mbox;     \"alan@example.org\" .\n  :b a foaf:Person  ;\n     foaf:name     \"Bob\" ;\n     foaf:mbox     \"bob@example.org\" .\n\n

and data in the default graph the remote SPARQL endpoint http://example.org/sparql:

\n  @prefix foaf:  <http://xmlns.com/foaf/0.1/> .\n  @prefix : <http://example.org/> .\n\n  :a  foaf:knows     :b . \n  :b  foaf:knows     :c .\n  :c  foaf:knows     :a .\n  :a  foaf:interest  \"SPARQL 1.1 Basic Federated Query\" . \n  :b  foaf:interest  \"SPARQL 1.1 Query\" .\n  :c  foaf:interest  \"RDB2RDF Direct mapping\" .\n\n

Query:

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nSELECT ?s\n{\n  ?s a foaf:Person .\n  SERVICE <http://example.org/sparql> {?s foaf:knows ?o }\n}\n

When the original query is executed naively, with an unconstrained service call the endpoint may return more results than necessary. It may also happen that the SPARQL endpoint will not return all of them. Many existing SPARQL endpoints have restrictions in the number of results they return and may miss the ones matching subjects ?s from the local default graph. Thus, an implementation of a query planner for federated queries may decide to decompose the query into two queries instead, where first the bindings from the local default graph are evaluated:

Query:

PREFIX : <http://example.org/>\nPREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nSELECT ?s\n{\n  ?s a foaf:Person\n} \n

This query, on the data above, has two solutions:

Query Result:

\n\n \n \n \n \n \n \n \n \n \n

s
<http://example.org/a>
<http://example.org/b>

\n\n

Next, dispatch to the remote endpoint <http://example.org/sparql> a constrained query with the solutions for ?s:

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nPREFIX : <http://example.org/>\nSELECT * {?s foaf:knows ?o } VALUES (?s) { (:a) (:b) }\n

The query process involving SERVICE limits the data returned to the data it needs for the overall query:

Query:

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>\nSELECT ?s ?o\n{\n  ?s a foaf:Person\n  SERVICE <http://example.org/sparql> {?s foaf:knows ?o }\n} \n

This query, on the data above using VALUES, has the expected two solutions to the overall query:

Query Result:

\n\n \n \n \n \n \n \n \n \n \n \n \n \n

s	o
<http://example.org/a>	<http://example.org/b>
<http://example.org/b>	<http://example.org/c>

"^^ ; ; ; "Interplay of SERVICE and VALUES (Informative)" .