RDF · OWL · SHACL
An editor for
what your data means.
Write a triple, watch it become a node. Declare a class, watch it become a constraint. Semantic Editor is a desktop-grade editor for ontologies and knowledge graphs — Turtle in one pane, the resolved graph in the other, always in sync.
Turtle, TriG, JSON-LD, RDF/XML in — SHACL validation on every keystroke.
How it's organized
Three tiers, one editor.
Most tools flatten a graph into one undifferentiated pile of triples. Semantic Editor keeps the tiers you actually reason in separate — and lets you move between them without switching tools.
Classes & properties
Model your ontology visually or in OWL functional syntax — hierarchies, restrictions, property chains — with inline consistency checks as you edit.
Instance data
Browse and edit the assertions themselves: entities, facts, provenance. Filter by graph, by source, by the point in time a fact was true.
SHACL constraints
Write shapes next to the data they govern. Violations surface inline, on the exact node and property path that caused them — not in a separate report.
Under the hood
Built for people who read Turtle for fun.
Bidirectional graph ↔ text
Drag a node, the Turtle updates. Edit a triple, the graph re-lays itself out. Neither view is the "real" one — they're the same document.
Reasoning, not just storage
Materialize OWL 2 RL or RDFS entailments on demand, and see inferred triples rendered distinctly from asserted ones — with a click-through to the rule that produced them.
SPARQL that writes itself
Select a node or a subgraph and get a working SPARQL query for it. Or write the query first and watch the match highlight live in the graph pane.
Store-agnostic
Point it at a file, a triple store, or a virtualized SQL-to-RDF mapping. The editor doesn't care where the triples actually live.
Diff-friendly by design
Canonical Turtle serialization means your ontology changes produce clean, reviewable git diffs — no more noisy re-orderings on every save.
Provenance-aware
Attach PROV-O metadata to any assertion as you make it — who, when, from what source — without leaving the triple you're editing.
Live validation, not a build step
Early access
Your graph, legible again.
We're onboarding a small number of ontology engineers and data teams before general release.