Tpt
dedbfbafa0
|
4 years ago | |
---|---|---|
.github | 4 years ago | |
bench | 4 years ago | |
lib | 4 years ago | |
python | 4 years ago | |
server | 4 years ago | |
spargebra | 4 years ago | |
testsuite | 4 years ago | |
wikibase | 4 years ago | |
.dockerignore | 4 years ago | |
.gitignore | 4 years ago | |
.gitmodules | 4 years ago | |
CHANGELOG.md | 4 years ago | |
Cargo.toml | 4 years ago | |
LICENSE-APACHE | 7 years ago | |
LICENSE-MIT | 5 years ago | |
README.md | 4 years ago | |
clippy.toml | 5 years ago | |
logo.svg | 4 years ago |
README.md
Oxigraph
Oxigraph is a graph database implementing the SPARQL standard.
Its goal is to provide a compliant, safe, and fast graph database based on the Sled key-value store. It is written in Rust. It also provides a set of utility functions for reading, writing, and processing RDF files.
Oxigraph is in heavy development and SPARQL query evaluation has not been optimized yet.
It is split into multiple parts:
- The database written as a Rust library. Its source code is in the
lib
directory. pyoxigraph
that exposes Oxigraph to the Python world. Its source code is in thepython
directory.- Oxigraph server that provides a standalone binary of a web server implementing the SPARQL 1.1 Protocol and the SPARQL 1.1 Graph Store Protocol. Its source code is in the
server
directory. - Oxigraph Wikibase, a web server able to synchronize with a Wikibase instance. Its source code is in the
wikibase
directory.
Oxigraph implements the following specifications:
- SPARQL 1.1 Query, SPARQL 1.1 Update, and SPARQL 1.1 Federated Query.
- Turtle, TriG, N-Triples, N-Quads, and RDF XML RDF serialization formats for both data ingestion and retrieval using the Rio library.
- SPARQL Query Results XML Format, SPARQL 1.1 Query Results JSON Format and SPARQL 1.1 Query Results CSV and TSV Formats.
A preliminary benchmark is provided.
License
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Futures by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.