Each item in the store has its own URI based on its unique identifier:
The Multisparql service does not support specification of the graph using SPARQL protocol parameters (default-graph-uri, named-graph-uri) or specifying of named graphs using FROM NAMED.
The Multisparql service does allow the default (background) graph to be specified using FROM clauses in the query. The graph URIs must correspond to either the URI of the Metabox or any graph in the Private Graphs Collection.
Note: for backwards compatibility, where the text/turtle media type is listed, the deprecated application/x-turtle media type is also supported, though it is given a lower weighting during Content Negotiation
The following table summarizes the content-negotiation logic for obtaining the sparql results as JSONP using the output (or Accept header) and the callback parameter (see here for all the logic). The output parameter, if set, will override the Accept header.
The Multi SPARQL service endpoint enforces a maximum execution time for all SPARQL queries. This is to ensure that long-running queries do not degrade the service for other users. Queries that exceed the maximum allowable time will be terminated and a 500 Internal Server error response returned.
The SPARQL service endpoint includes support for some extensions to the SPARQL query language. The full list of SPARQL Extensions are documented separately.
The official SPARQL protocol specification has additional information on specifying queries, response formats and error conditions.