Open Ontologies

Open Ontologies

Plan a change to a production ontology. See every consequence before you apply it. Then give the reviewer a proof that they can check without trust in you. Open Ontologies is written in Rust. It ships as one binary.

tesseractsemantics.com

English · 简体中文

Put in one spreadsheet. Get one ontology, with the evidence for each line. Then change one cell, and see the shape find the error. The page runs the released binary.

Look for enterprise support? tesseractsemantics.com The engine is MIT, and it stays MIT. The platform is the hosted version of the engine.

---

426 asserted, 259 certified, 1 rejected. The engine derived the green edges. A Lean 4 checker then proved them. One certificate holds all 259, and one run of the checker accepts it. The red edge is a forged line. The same checker refused that line, gave exit 1, and named the rule. The run supplies each count. Nobody writes a count into the caption.

The same machinery, on a file from a different group, two times. HQDM ships as two files. hqdmTop/hqdmFramework publishes an RDFS file. MagmaCore keeps a copy of that file, byte for byte. gchq/HQDM publishes an OWL file. The two files fail different checks. The RDFS file has no owl: term and no disjointness axiom. Thus no named class in that file can be unsatisfiable. But the file has 23 terms that it uses as a class and never declares. It has 12 rdfs:range declarations that name a relation and not a class. It also has 13 pairs of names that differ by one final underscore. Three of those pairs have the same domain and the same range. The OWL file passes all three checks, and the OWL file is not coherent. The tableaux of this engine finds 190 of its named classes satisfiable. The tableaux finds 39 unsatisfiable. HermiT calls the same 39 unsatisfiable, and HermiT is an opinion in the vocabulary of this repository. This figure proves nothing, and the figure does not claim a proof. A test computes each count again, and the test also computes that intersection. For the source and the method, read docs/assets/hqdm/PROVENANCE.md.

One triple. Nothing added, nothing removed, blast radius zero. 901 consequences that were not there before.

$ printf 'load base.ttl\nplan proposed.ttl\n' | open-ontologies batch -
#   the whole change:  ex:hasParent rdfs:domain ex:Person

added_classes         0
removed_classes       0
blast_radius          0 triples affected
risk_score            low
                      ────────────────────────────────────────────
conservativity        not_conservative_under_rule_table
new consequences      901          rule table owl-rl, in 0.04s

Each number from a shape diff tells you that this change is safe. But the change gave a new type to each individual that the property already had. The tool closes this gap. A text diff cannot show you the gap. The change is one correct line, and the text diff is one line long.