Ontology Quality Suite
Python tools for checking that an OWL2 ontology stays internally consistent across versions, and that TARQL/oxi-gen CONSTRUCT-query transformation files stay aligned with the ontology(ies) they triplify against -- namespaces, class/property usage -- with suggested diffs for automated repair, either against local files or a live Fuseki (SPARQL 1.1 Protocol) triplestore.
This package carries forward the full ontology_suite pipeline from the
sibling consolidated_ontology_suite checkout (OntoQA/OQuaRE metrics,
SHACL+SPARQL registry checks, OWL2 profile/reasoner-backed consistency,
docgen -- the same logic is also ported to TypeScript in
consolidated_ontology_suite_webapp, the VS Code extension) and adds three
things that didn't exist in Python before:
- Ontology-version consistency + rename detection
(
ontology_suite.versioning.rename_detection) -- pairs up a version diff's removed/added classes and properties into probable renames, using either an explicitowl:equivalentClass/dcterms:isReplacedBymigration annotation (high confidence) or local-name similarity (fallback). - Automated repair suggestions (
ontology_suite.repair,ontology_suite.checks.repair) -- turns a TARQL/ontology misalignment or a registry-check finding into a concrete unified diff: aPREFIXline fix, an IRI-rename substitution across a query file, an ontology declaration stub, or a real SPARQL 1.1 Update -- reviewable as a.patchfile, or applied directly. - Live triplestore support (
ontology_suite.remote) -- runs the same checks against a Fuseki (or any SPARQL 1.1 Protocol) dataset, named-graph aware: diff two ontology versions held as separate named graphs, run the existing registry.rqchecks scoped to exactly the graphs they should see, or three-way check a live triplified named graph against its ontology graph and its local TARQL source file.
Every --ontology/--data/query-source argument throughout accepts a
local file, an http(s) URL, or either gzip-compressed, transparently (see
ontology_suite/io_utils.py and docs/ARCHITECTURE.md's "Loading files"
section).
New here? Start with docs/PRIMER.md -- a task-oriented guide to which
command answers which question, worked examples for every major use case
(auditing an ontology, validating a CSV-to-RDF pipeline, releasing a new
version, auto-repairing drift, taxonomy governance, live-triplestore
checks, CI wiring), and a suggested adoption path. New to RDF/OWL? It opens
with a short, plain-language glossary. Prefer running things over reading
them? docs/primer.ipynb is a Jupyter notebook covering most of the same
ground with live, executable cells against this repo's own examples/
fixtures (validated on every push by .github/workflows/notebook.yml).
See docs/CONSISTENCY_AND_REPAIR.md for the local-file workflow,
docs/FUSEKI.md for the live-triplestore one, docs/ARCHITECTURE.md for
the inherited pipeline this all sits on top of, and
docs/UPSTREAM_README.md for that pipeline's own original README.
Want one continuous, realistic worked example instead of task-by-task
fixtures? docs/ACME_ROBOTICS_WALKTHROUGH.md runs nearly every stage above
against a single small org chart built on two real external vocabularies
(W3C Organization Ontology, FOAF) -- with two companion notebooks,
docs/acme_robotics_lifecycle.ipynb and
docs/acme_robotics_data_pipeline.ipynb (also validated on every push).
Quick start
uv sync
uv run ontology-quality-suite consistency --new domain-v2.ttl --old domain-v1.ttl --queries queries/
from ontology_suite import consistency
report = consistency.check_consistency(
"domain-v2.ttl", old_ontology="domain-v1.ttl", tarql_sources=["queries/"],
)
print(consistency.format_consistency_report(report))
consistency.apply_repairs(report.repairs, min_confidence=0.7)
CLI
ontology-quality-suite ontology --ontology domain.ttl
ontology-quality-suite checks --ontology domain.ttl [--data data.ttl]
ontology-quality-suite sketch --queries queries/ [--ontology domain.ttl]
ontology-quality-suite triplify --csv-dir csv/ --queries queries/
ontology-quality-suite data data.ttl [more.ttl ...] [--ontology domain.ttl]
ontology-quality-suite docgen --ontology domain.ttl
ontology-quality-suite run whichever of --ontology/--queries/--csv-dir/--data apply
ontology-quality-suite version-diff old.ttl new.ttl
ontology-quality-suite consistency --new domain.ttl [--old domain-v1.ttl] [--queries queries/] [--apply-repairs]
ontology-quality-suite consistency-remote --query-endpoint URL --manifest graphs.json
Tests
uv run pytest
Release files for ontology-quality-suite 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ontology_quality_suite-0.6.0.tar.gz | 663.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ontology_quality_suite-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 910.9 kB
Release files / ontology_quality_suite-0.6.0.tar.gz
| Download URL | ontology_quality_suite-0.6.0.tar.gz |
|---|---|
| Size | 663.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9aec80429a8c499c1f72055d2af08ef77026c0f9112d664886d45cc691b89e91
|
|
BLAKE2b-256 checksum How to use checksums |
76d7b7914ab435a6412ec27360415bd21e88dcdfae7c3540cc07b8de3ad6c0c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / ontology_quality_suite-0.6.0-py3-none-any.whl
| Download URL | ontology_quality_suite-0.6.0-py3-none-any.whl |
|---|---|
| Size | 247.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25636cf986f5e567eca7c2e15cd6eac265d9ddd171b3dcc6e18984949f9ea2e4
|
|
BLAKE2b-256 checksum How to use checksums |
fd44edcae7008d9275aceb9ac4a788e7ab00186680cad2243bbd8b91c81a2011
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency log