VS Code extension (OntoCode)¶
OntoCode is the VS Code extension: explorer sidebar, Entity Inspector, Query Workbench, Manchester editor, reasoner panels, and inline diagnostics. It talks to the bundled ontoindex-lsp language server — you do not need Rust installed for normal use.
Looking for the CLI or Rust crates? See the Rust & CLI path.
Quick start¶
- Install OntoCode from the Marketplace.
- Open a folder with
.ttl,.owl, or other ontology files and Trust the workspace. - Open the OntoCode activity bar → Classes → click an entity.
First success in 10 minutes — full walkthrough with sample ontologies.
Install and setup¶
| Topic | Guide |
|---|---|
| Install, trust, bundled LSP | Install VS Code |
| Supported formats, activation | Install VS Code · FAQ |
| Problems after install | Troubleshooting |
Using the extension¶
| Feature | Guide |
|---|---|
| Browse classes, properties, individuals | First success |
| Edit Turtle (labels, parents, create/delete) | Authoring |
| Workspace refactoring (rename, migrate, move, extract) | Refactoring |
| SQL and SPARQL in VS Code | Query Workbench |
| Complex axioms (Manchester) | Manchester editor |
| EL / RL / RDFS classification | Reasoner |
| Working alongside Protégé | Protégé coexistence · Protégé decision matrix |
| Team evaluation | Enterprise evaluation |
Reference¶
| Topic | Link |
|---|---|
| What ships today | What ships today |
| Patch JSON (inspector / LSP) | Patch reference |
| LSP methods (advanced) | LSP API |
| Workspace limits | Workspace limits |
| Errors | Errors reference |
Help¶
- FAQ — multi-root workspaces, trust mode, editing limits
- Troubleshooting — LSP failed to start, empty explorer
- Best practices — repo layout, when to use SQL vs SPARQL vs reasoner
Related¶
- Rust & CLI path —
ontoindexbinary,cargo install, embedding crates - Documentation home