-
Notifications
You must be signed in to change notification settings - Fork 25
SPARQL 1.1 Status
kasei edited this page Sep 12, 2010
·
44 revisions
Based on Lee Feigenbaum’s breakdown of SPARQL 1.1 features, these are best guesses as to the status of those features in RDF::Query and RDF::Endpoint checked into github as of 2010.06.30.
Everything needs more testing as we don’t have a 1.1 test suite yet…
Projected Expressions | 100% | |
Subqueries | 100% | |
Negation | 100% | |
Aggregates | 100% | |
Service Description | 100% | |
Update Language | 95% | See issues list below. |
Update Protocol | 0% | Updates can be submitted to an RDF::Endpoint with POST using the query operation (SPARQL Protocol 1.0), but there’s no response body on success. Protocol 1.1 has not been implemented yet. |
HTTP RDF Update | 80% | KjetilK is working on this in RDF::Query::HTTPBindings. |
Property Paths | 100% | Will track the evolving semantics of negated property classes and result cardinality. |
Basic Federated Query | 100% | |
Common Functions | 100% | COALESCE, IRI, URI, STRLANG, STRDT, IF, BNODE, IN and NOT IN. Will track new functions as the working group agrees on them. |
Entailment Regimes | N/A | No current plans to implement entailment. |
Known issues:
- Blank nodes in DELETE {} WHERE {} and DELETE WHERE {} don’t follow the semantics of SPARQL 1.1 Update.
There is a sample SPARQL 1.1 Endpoint at myrdf.us, but it’s not guaranteed to stay up.