-
Notifications
You must be signed in to change notification settings - Fork 8
Triplestores
Jim Balhoff edited this page Aug 22, 2016
·
14 revisions
We are considering using a triplestore as the storage backend for Minerva. This page collects some feature comparisons relevant to Minerva. Some of these features are relevant to using the triplestore as an object property reasoning engine, whether or not it is used for storage.
| Blazegraph | RDFox | |
|---|---|---|
| URL | https://www.blazegraph.com | http://www.cs.ox.ac.uk/isg/tools/RDFox/ |
| License | gplv2/commercial | academic |
| Named graphs | Excellent support. | No support currently (triples only). |
| Aggregates (SPARQL 1.1) e.g. COUNT | yes | no |
| Property paths (SPARQL 1.1) | yes | no |
| Reasoning approach | Reasoning not supported by default in quads mode. Reasoning rules operate on all triples in graph; results materialized ahead of time. Query using SPARQL. | Import ontology separately from data. Can also separately add rules. Results materialized ahead of time. Query using SPARQL. |
| Object property assertion reasoning | "RDFS+", no property chains by default (but can implement rules) | OWL 2 RL; can add datalog-based rules |
| Logical definition type inference | no | yes |
| Detect inconsistency | no? | yes (individual inferred type owl:Nothing) |
| Import and materialize go-plus.owl on 13" Macbook Pro | < 1 minute | |
| Import and materialize go-lego.owl on 13" Macbook Pro | < 1 minute |