OMI Implementation Status Matrix
Evidence baseline
Version 0.16.0, core validation, identity/reference, export/privacy, metadata, localized conversion, extension, local authoring, authority-boundary and semantic-relationship and remaining-core evidence updated 2026-11-11. The 24-model source/Studio inventory below retains its 2026-10-31 baseline; the separate Studio suites pin newer candidate commits and do not re-audit the deployed release. Informative evidence report; no lifecycle promotion. The registry and exact versioned normative text remain authoritative.
-
Specification baseline:
b4e12ef, plus the proposed core Draft revisions in this change. -
Studio baseline:
5a69669. -
2026-11-04 core validation supplement, with current manifest/validator digests and bounded behavioral coverage.
-
Combined core evidence index and archived Studio identity/reference report. Studio candidate b9c80c1, proposed in PR #856, supplies bounded editor/serializer observations rather than deployed-release or independent conformance evidence.
-
Third-bundle combined index and archived Studio export/privacy report. Candidate da5b530, proposed in PR #857, adds credential, supported audience-filtering and source-preservation observations. Its deployment and independent conformance are not established here.
-
Fourth-bundle combined index and archived Studio metadata report. PR #858 adds 12 assertion-state, provenance, visibility, audit-event and portable-preservation scenarios, bound to the source commit in the archive. Synthetic claim fixtures do not establish real-world identity or membership.
-
Fifth-bundle combined index and archived localized conversion run. PR #859 adds 12 locale-preservation, collision-rejection, editor, portable and office projection/loss scenarios. The archive pins the tested candidate; full metadata mapping and deployment are not established.
-
Sixth-bundle combined index and archived extension run. PR #860 adds 12 opaque metadata/vocabulary preservation, known-profile boundary, explicit metadata review-profile and office omission scenarios. Foreign semantic interpretation, full cardinalities and independent conformance remain outside scope.
-
Seventh-bundle combined index and archived local authoring run. PR #861 adds 12 cases for initialized local-model operations under denied network entry points, editable source metadata/notices, attributed-content deletion/restoration and nested-tree editing. Offline app bootstrap, device recovery and hosted authorization remain outside scope.
-
Eighth-bundle combined index and archived authority-boundary run. PR #862 adds 12 cases for identity/rights versus actual collaboration service decisions, missing-fact preservation and federated-admin prerequisites. The real server sources run with an isolated persistence double; live route/database and complete SSO enforcement remain outside scope.
-
Current combined index and archived relationship/fallback run. PR #863 adds 12 cases for explicit semantic relationships, native note roles and non-equivalent export disclosures. Full adapter mappings, external-editor roundtrips and independent conformance remain open.
-
Studio PR #785 was open with successful executed checks at review time. Its new 190/340/350 profiles are proposed, not merged baseline evidence. This snapshot is historical, not a live PR-status widget.
-
Remaining-core supplement and archived 22-case Studio run, pinned to 3a85ebf in PR #900. All eleven previously untested IDs now have bounded partial observations. This does not certify an integrated deployment or independent conformance.
Interpretation
A listed file demonstrates related code or tests, not full requirement coverage. Partial means identifiable product behavior with open normative/interoperability gaps. Architectural means principles guide design rather than define a standalone executable feature. No model is labelled conformant. No independent implementation is verified here. The vendored shared validator is not independent evidence.
All-model inventory
Core review evidence
The 000/120/100/140 rewrites provide 66 requirement IDs, 22 versioned fixtures, a minimal structural schema and a bounded pure validator. The first 2026-11-04 supplement adds 12 validator behavioral cases, giving validator-only coverage of 25 partial / 41 untested. The second bundle adds 12 Studio identity/reference scenarios mapped to seven more requirements; the third adds 12 export/privacy scenarios and three more newly evidenced requirements. The fourth adds 12 metadata scenarios and five newly evidenced requirements. The fifth adds 12 localized metadata/conversion scenarios and three newly evidenced requirements. The sixth adds 12 extension/vocabulary scenarios and two newly evidenced requirements. The seventh adds 12 local authoring/source editability scenarios and three newly evidenced requirements. The eighth adds 12 identity/rights authorization-boundary scenarios and four newly evidenced requirements. The ninth adds 12 semantic-relationship/fallback scenarios and three newly evidenced requirements. The tenth bundle adds 22 remaining-core scenarios for all eleven IDs previously lacking observations. Combined role-scoped coverage is 66 partial / 0 untested / 0 complete. Every requirement still has incomplete normative evidence; this is not a completion percentage for the specifications or product. This supersedes earlier aggregate counts while preserving the separate dated reports and validator-only manifest. No requirement is promoted to complete evidence merely because a case passes. Detailed scope and exclusions.
The Studio companion panel runs this separate experimental profile without changing existing validation-report versions or manuscript producer declarations. It is proposed support until merged and deployed.
Corrections and current gates
The runtime file-format constants already identify OMI-SPEC-320@0.3.0 and the 0.3 schema; the former claim that Studio still uses 0.2.0 was stale. Source and Derivation is 0.2.0; the registry version and missing dependency row are corrected. The new core Draft versions are not silently substituted into existing producer envelopes.
The citation/library dependency cycle OMI-SPEC-210 → OMI-SPEC-221 → OMI-SPEC-210 must be reviewed as a coordinated group; no strict independent promotion order is implied for those two models. This Draft cycle remains recorded, not silently removed.
Every stronger status still requires exact normative applicability, code/test mapping, versioned positive and negative fixtures, compatible behavior, public review, meaningful independent evidence and a recorded approval. A successful Studio build is one implementation observation.
Change history
| Version | Date | Change |
|---|---|---|
| 0.16.0 | 2026-11-11 | Added 22 bounded observations for the eleven remaining core IDs, including paragraph identity-map repairs; combined coverage 66 partial / 0 untested / 0 complete. Nine Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.15.0 | 2026-11-05 | Added semantic-relationship and non-equivalent export disclosure observations; combined coverage 55 partial / 11 untested. Eight Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.14.0 | 2026-11-05 | Added bounded identity/rights authorization observations against real server services with isolated persistence; combined coverage 52 partial / 14 untested. Seven Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.13.0 | 2026-11-05 | Added bounded local authoring and source editability evidence, including nested-tree regression fixes; combined coverage 48 partial / 18 untested. Six Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.12.0 | 2026-11-05 | Added opaque extension/vocabulary preservation and explicit profile-boundary observations; combined coverage 45 partial / 21 untested. Five Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.11.0 | 2026-11-04 | Added localized metadata preservation and explicit DOCX/ODT conversion-loss observations; combined coverage 43 partial / 23 untested. Four Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.10.0 | 2026-11-04 | Added metadata assertion-state, provenance, visibility and audit-event observations; combined coverage 40 partial / 26 untested. Three Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.9.0 | 2026-11-04 | Added export/privacy observations and credential-alias regression checks; combined coverage 35 partial / 31 untested. Two Studio suites remain one reference implementation. No lifecycle promotion. |
| 0.8.0 | 2026-11-04 | Added commit-pinned Studio identity/reference observations for seven more requirements; combined coverage 32 partial / 34 untested, with archived versus local execution explicit. No lifecycle promotion. |
| 0.7.0 | 2026-11-04 | Added 12 requirement-mapped validation behavior cases; current core coverage is 25 partial / 41 untested. Retained dated Studio evidence; no lifecycle promotion. |
| 0.6.0 | 2026-10-31 | Rebuilt all-model source/code inventory, corrected 0.3.0 runtime and version drift, added 66-requirement core review evidence and explicit open gates. No lifecycle promotion. |
Earlier evidence baselines remain available in repository history; their old counts are not current completion percentages.