Skip to content

Procurement and enterprise appendix

Single entry point for security, platform, and legal questionnaires. Start with the adoption trio before reading this appendix:

  1. What ships today — capability matrix (latest tagged release)
  2. Known limitations — honest gaps
  3. Protégé vs OntoCode — fit decision

Summary for evaluators

Question Answer
Production-ready Protégé replacement? No until 1.0 — pilot/coexistence workflows today
Latest tagged release v0.26.2 — pin installs; see Versions & channels for Marketplace lag
Commercial support Not offered — community via GitHub issues
Editable formats Turtle, OBO, RDF/XML, OWL/XML write-back; XML is semantic re-serialize (not Protégé byte-identical); JSON-LD / TriG / N-Triples read-only
CLI prebuilds Linux x64 only; macOS/Windows use cargo install or bundled VSIX LSP

Non-claims (procurement)

Topic Answer
Commercial support / SLA Not offered
SOC 2 / ISO 27001 No
Code-signed binaries Not yet (SHA256 only) — signing is post-1.0 candidate, not committed
HIPAA BAA No

Details: Production readiness § Support and compliance.

Detailed guides (by topic)

Topic Document
Security policy & threat model Security · SECURITY.md on GitHub
Release integrity (SHA256) Release integrity
CI / automation stability CI integration · Automation and stability
Platform compatibility Platform compatibility
Performance and sizing Performance and sizing (provisional — not benchmark-certified)
LGPL / third-party licenses LGPL compliance · LICENSES
Production readiness tiers Production readiness
Evidence protocol (pilots) Production evidence
Governance & release cadence Governance · Release timeline
Air-gapped / offline Enterprise deployment
API stability (pre-1.0) API stability

Enterprise evaluation checklist

  1. Confirm required capabilities in SHIPPED (VS Code and CLI columns).
  2. Read Known limitations — especially format write-back and SQL subset.
  3. Pin cargo install ontocore-cli --locked --version 0.26.2 (or current TAGGED_RELEASE) in CI.
  4. Verify release artifacts with SHA256SUMS.
  5. Run a pilot using First success + your corpus.