JSON schema reference¶
owlcompare diff --format json emits a versioned, machine-readable contract,
formalized as a JSON Schema 2020-12 document. If you
build automation on top of owlcompare — a dashboard, a custom gate, a language
server — this is the surface to target. The schema is bundled with the package
and published in the repository.
This page is being expanded
The full field-by-field reference is coming. The pointers below are enough to integrate against the contract today.
The bundled schema¶
The canonical schema file lives at
docs/schema/diff-result.schema.json
and ships inside the installed package. External consumers can pin the raw URL:
Validate your own captured output against it during development with
owlcompare diff ... --format json --validate-schema.
What this page will cover¶
- The top-level shape —
schema_version,summary,changes, andmetadata. - The
Changeobject —kind,severity,details,subsumes, and the per-kinddetailsvariants. - The
summaryblock — the counts CI reads (total,breaking, …). - The
metadatablock — the subsumption registry and severity-refinement audit trail. - The versioning policy — what's forward-compatible (new optional fields, new
kindvalues) versus what bumps the majorschema_version.