Introduction
Release 4.11 of AllegroGraph provides numerous enhancements and bug fixes for the SPARQL 1.1 query engine.
Supported features
AllegroGraph provides support for
- SPARQL 1.1 Query,
- SPARQL 1.1 Update,
- SPARQL 1.1 Federated Query,
- SPARQL 1.1 Query Results JSON Format,
- SPARQL 1.1 Query Results CSV and TSV Formats,
- SPARQL Query Results XML Format (Second Edition)
It does not directly support entailment regimes but AllegroGraph's RDFS++ reasoner or OWL Materializer can be used to support inference.
We also do not support some of the changes between 1.0 and 1.1 in the SPARQL Protocol. Lastly, we do not support the Graph Store HTTP Protocol (note that all of the functionality in this protocol can be found using SPARQL Update).
SPARQL functions
Aside from the following caveats, AllegroGraph's sparql-1.1 engine supports all of the functions in the specification.
we do not yet support the
timezone
ortz
datetime functionswe do not yet support the
SHA384
hash functionthe
BNODE
function only works correctly in the no argument case
DAWG test failures
the query parser does not correctly parse some legal but unusual forms like
:c:d
,:c\~z`, or a triple like
:: z:: :12.3`.AllegroGraph encodes numbers and dates directly rather than storing them as strings. This means that the following literals will all encode the same way:
"+1"^^xsd:integer
,"1"^^xsd:integer
, and"0001"^^xsd:integer
. DAWG tests that rely on non-canonical values being able to round-trip will fail.the
(pp37) Nested (*)*
DAWG test fails.
If you find any other problems (with conformance or performance) please let us know by e-mailing support.