open-ontologies: A single-binary ontology engine for planning production changes, reasoning over RDF and OWL, and producing independently checkable certificates.
What problem it solves
Production ontology changes can introduce consequences that are not visible in a text diff, making it difficult to assess their impact before deployment. Reviewers also need evidence they can verify later without trusting the engine or the person who applied the change.
Key features
Plan and control ontology changes — The lifecycle workflow plans changes, reports their blast radius and risk, tracks drift, and supports applying and rolling back modifications to a production ontology.
Source: README, src
Reason with checkable certificates — Reasoning over OWL and RDFS produces materialized inferences together with derivation certificates that can be checked by a proved Lean 4 checker.
Source: README, lean
Validate, query, and prove ontology properties — The engine supports SHACL validation, satisfiability and inconsistency checks, SPARQL, RAG slice checks, and export to several prover formats.
Source: README, Cargo.toml
Load and transform real-world data — Data can be imported from common tabular, structured, and database formats into RDF for ontology workflows.
Source: README
Operate through a CLI or assistant — The project ships as one Rust binary and exposes an MCP server so supported assistants can operate its workflows in conversation.
Source: README, .mcp.json
Quick start
Copied verbatim from the project's README.
mkdir /tmp/oo-demo && cd /tmp/oo-demo
cat > coffee.ttl <<'EOF'
@prefix ex: <http://example.org/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
ex:Espresso rdfs:subClassOf ex:Coffee .
ex:Coffee rdfs:subClassOf ex:Drink .
ex:myCup a ex:Espresso .
EOF
export OPEN_ONTOLOGIES_STORAGE_MODE=persistent # in-memory by default, see below
open-ontologies --data-dir /tmp/oo-demo/store load coffee.ttl
open-ontologies --data-dir /tmp/oo-demo/store reason --profile rdfs --certificate ./certWho it may suit
Inference: may suit ontology maintainers, data-governance teams, auditors, and developers who need to evaluate or deploy RDF and OWL changes with independently reproducible evidence.
Topics to discuss
Which production ontology changes should require a blast-radius review before deployment?
How should independent certificates be integrated into existing review and audit workflows?
Which OWL and RDFS inference workflows need clearer distinctions between proved results and tool opinions?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/fabio-rovai/open-ontologies#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…