Start here¶

You can be successful with OntoCode/OntoCore in 5–15 minutes if you follow one path below.

Primary path for most users: First success (~10 min).

Which artifact?¶

Read Known limitations before a large evaluation.

When not to use OntoCode (today)¶

• You need OWL/XML or RDF/XML in-place write-back — edit as Turtle/OBO or use Protégé.
• You need full SQL (JOINs, ORDER BY, LIKE) — use catalog SQL (subset) or SPARQL instead.
• You need a stable, semver-guaranteed plugin API or production owlmake integration without subprocess scaffolding — plugin host MVP shipped in v0.14 (Plugin authoring); ecosystem hardening is v1.0.

Canonical matrix: What ships today · Known limitations.

Path A — VS Code IDE (recommended for most users)¶

1. Complete the tutorial: First success (~10 min)
2. Confirm your formats: Supported formats
3. Learn the core workflows:
4. Editing: Authoring guide
5. Query: Query Workbench
6. Reasoning: Reasoner guide
7. Imports: Manage Imports

Then (optional): Feature tour · Install options · Manchester editor · Refactoring

If something doesn’t work:

• Troubleshooting
• FAQ
• Support and contact

Path B — CI / CLI (recommended for automation and evaluation)¶

1. Install + run your first command: Getting started
2. Run a CI gate locally:
3. ontocore validate /path/to/ontologies
4. Optional: ontocore classify /path/to/ontologies --profile el --format json
5. Wire into CI: CI integration
6. Know your limits: Workspace limits and Performance and sizing
7. Decide what’s safe to automate: Automation and stability

If you plan to embed OntoCore or integrate via LSP:

• Rust: Rust library guide
• LSP: LSP API (and schema)

If you’re evaluating adoption¶

Read these in order:

1. What ships today
2. Known limitations
3. Enterprise evaluation
4. Production readiness
5. Security policy

Supported since v0.10+¶

• Multi-root workspaces: All workspace folders are indexed on open. Manual Index Workspace may prompt you to pick a folder when multiple roots are open.