An RDF toolchain for the Odin programming language, written from scratch in Odin. LMDB — the storage engine under the store — is the single external dependency, and odin-rdf-record carries none at all.
Five independent libraries — a strict stack from the parser up to the query and validation engines, plus a second store beside it. Each depends only downward, and each is usable on its own.
odin-rdf-parser formats, data model, and parser
|
+-- odin-rdf-store storage and the match interface
| |
| +-- odin-rdf-sparql query engine
| |
| +-- odin-rdf-shacl shape validation
|
+-- odin-rdf-record tamper-evident system of record
| Project | What it does | Status |
|---|---|---|
| odin-rdf-parser | Streaming parsers and emitters for N-Triples, N-Quads, Turtle, and TriG, plus the shared term/triple/quad model | All 1045 W3C conformance tests pass, RDF 1.2 / RDF-star included |
| odin-rdf-store | LMDB-backed quad store and the match() interface engines query through — transactional, with transaction time: every commit is dated and attributed, and the past is readable as-of |
One shared conformance suite, run at both Term_ID widths |
| odin-rdf-sparql | SPARQL 1.1 Query with the 1.2 surface: text → algebra → solutions over the store's match interface, plus SPARQL results JSON and XML writers | 352 syntax and 483 evaluation tests, run at both Term_ID widths |
| odin-rdf-shacl | SHACL Core validation of data graphs against shapes graphs | All 98 entries of the W3C core/ suite pass, run at both Term_ID widths — SHACL-SPARQL is a later phase |
| odin-rdf-record | Tamper-evident system of record: an append-only, hash-chained log is the only durable form, replayed into a memory-resident projection — a second store beside odin-rdf-store, third-party verifiable from the format spec alone | The log of record is complete (format v1), cross-checked verdict for verdict against an independent Python verifier on every test run — the resident projection is next |
Libraries, not applications. Each layer supplies primitives and leaves policy to its consumers — there are no servers or protocol layers anywhere in the stack, by design.
Correctness is defined by executable suites: the official W3C test suites, vendored into each repository so runs are hermetic and reproducible offline — and in odin-rdf-record, where the format is its own rather than a W3C one, an independent verifier written from the format specification alone that must agree with the Odin implementation on every test run. Everything is idiomatic Odin: explicit memory management, allocator awareness, streaming over materialization, and zero-copy parsing that leaves the document in a caller-owned buffer.
Start with odin-rdf-parser — it carries the quick-start examples and the data model the rest of the family speaks.
