|
@@ -1,14 +1,12 @@
|
|
# `lsup_rdf`
|
|
# `lsup_rdf`
|
|
|
|
|
|
-**This project is work in progress.**
|
|
|
|
-
|
|
|
|
Embedded RDF (and maybe later, generic graph) store and manipulation library.
|
|
Embedded RDF (and maybe later, generic graph) store and manipulation library.
|
|
|
|
|
|
## Purpose
|
|
## Purpose
|
|
|
|
|
|
The goal of this library is to provide efficient and compact handling of RDF
|
|
The goal of this library is to provide efficient and compact handling of RDF
|
|
data. At least a complete C API and Lua bindings (in a separate project) are
|
|
data. At least a complete C API and Lua bindings (in a separate project) are
|
|
-bering built.
|
|
|
|
|
|
+being built.
|
|
|
|
|
|
This library can be embedded directly in a program and store persistent data
|
|
This library can be embedded directly in a program and store persistent data
|
|
without the need of running a server. In addition, `lsup_rdf` can perform
|
|
without the need of running a server. In addition, `lsup_rdf` can perform
|
|
@@ -29,10 +27,9 @@ minimal changes to the core. More documentation on the topic will follow.
|
|
|
|
|
|
## Development Status
|
|
## Development Status
|
|
|
|
|
|
-**Alpha.** Considered feature-complete from an MVP standpoint. The API may
|
|
|
|
-still change significantly. The code may not compile, or throw a fit when run;
|
|
|
|
-however, most commits (not prefixed with "WIP") should be pushed after tests
|
|
|
|
-pass with a clean `make memcheck` output.
|
|
|
|
|
|
+**Beta.** Considered feature-complete from an MVP standpoint. The API may
|
|
|
|
+change significantly. Most commits (not prefixed with "WIP") and merges to the
|
|
|
|
+master branch are pushed after tests pass with a clean `make memcheck` output.
|
|
|
|
|
|
Test coverage is not sufficient. Documentation is fairly extensive but needs
|
|
Test coverage is not sufficient. Documentation is fairly extensive but needs
|
|
reformatting. This code is being integrated in higher-level projects and is
|
|
reformatting. This code is being integrated in higher-level projects and is
|
|
@@ -83,9 +80,10 @@ of features as a standalone library:
|
|
- JSON-LD: overwhelmingly bloated and complicated to understand and implement.
|
|
- JSON-LD: overwhelmingly bloated and complicated to understand and implement.
|
|
- SPARQL, SPARUL, GraphQL, etc: they might make sense as separate plug-ins, but
|
|
- SPARQL, SPARUL, GraphQL, etc: they might make sense as separate plug-ins, but
|
|
this project has a minimalist query approach based on combinations of set
|
|
this project has a minimalist query approach based on combinations of set
|
|
- operations supported by a scripting language.
|
|
|
|
|
|
+ operations supported by an external scripting language.
|
|
- Python bindings: an initial implementation has been built and then shelved in
|
|
- Python bindings: an initial implementation has been built and then shelved in
|
|
- favor of Lua, due to the complexity and slowness of the Python C API.
|
|
|
|
|
|
+ favor of Lua, due to the complexity and slowness of the Python C API, as well
|
|
|
|
+ as my recent personal gripes with Python.
|
|
|
|
|
|
## Building
|
|
## Building
|
|
|
|
|