Which artifact do I need?¶
OntoCode is a product family. You usually need one primary artifact — not all of them.
Decision table¶
| I want to… | Install | Docs |
|---|---|---|
| Browse and edit ontologies in VS Code | OntoCode extension (Marketplace or Open VSX) | First success (~10 min) |
| Validate, query, or classify ontologies in CI | cargo install ontocore-cli --locked --version 0.13.0 |
Getting started · CI integration |
| Embed indexing/query in a Rust application | ontocore = "0.13" in Cargo.toml |
Rust library guide |
| Build a custom editor on the language server | Bundle or spawn ontocore-lsp |
LSP API |
| Run OWL reasoning (classification, explanations) | Included via OntoCore — no separate install | Reasoner guide |
Product names (30 seconds)¶
| Name | What it is |
|---|---|
| OntoCode | VS Code / Cursor extension (IDE) |
| OntoCore | Rust engine — ontocore CLI, ontocore-lsp, and ontocore-* crates |
| Ontologos | External reasoner library used by OntoCore (not installed separately for normal use) |
The extension bundles ontocore-lsp. You do not need Rust to use the IDE.
Common combinations¶
Solo ontology author: OntoCode extension only.
Team with Git + CI: OntoCode extension locally + ontocore validate (and optional classify / diff) in CI.
Rust service or pipeline: ontocore crate or ontocore-cli — no VS Code required.
Air-gapped enterprise: VSIX + optional CLI tarball from GitHub Releases — Enterprise deployment.
What ships today¶
Canonical capability matrix: What ships today.
Next step¶
- IDE path → First success (~10 min core path)
- CLI / Rust path → Rust & CLI guide