Μετάβαση στο κύριο περιεχόμενο

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.

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​

ModelDraft versionStudio evidenceReview phasePinned evidence examples
OMI-SPEC-000 — Core Principles0.2.0architectural1README.md
OMI-SPEC-100 — Document Model0.2.0partial1src/types/omi.ts; src/app/useStudioStore.ts
OMI-SPEC-110 — Anchor Model0.1.0partial2src/model/namedAnchors.ts; tests/named-anchors.test.ts
OMI-SPEC-120 — Scholarly Object Model0.3.0partial1src/types/omi.ts; src/services/manuscriptValidation.ts
OMI-SPEC-130 — Annotation Model0.2.0partial2src/model/notes.ts; tests/notes-model.test.ts
OMI-SPEC-140 — Metadata Model0.2.0partial1src/model/scholarlyMetadata.ts; src/app/scholarlyMetadataActions.ts
OMI-SPEC-150 — Identity and Contributor Model0.1.0partial2src/model/identity.ts; tests/identity-model.test.ts
OMI-SPEC-160 — Versioning and Change Model0.1.0partial3src/model/versioning.ts; src/model/workingState.ts
OMI-SPEC-170 — Translation Model0.1.0partial6src/model/translation.ts; tests/translation-model.test.ts
OMI-SPEC-180 — Validation Model0.1.0partial3src/services/manuscriptValidation.ts; src/model/validation.ts
OMI-SPEC-190 — Collaboration and Permission Model0.1.0partial6server/src/services/collaborationInvitationService.ts; server/src/services/collaborationTicketService.ts
OMI-SPEC-200 — Review Model0.1.0partial6src/model/peerReview.ts; tests/peer-review-model.test.ts
OMI-SPEC-210 — Citation Model0.2.0partial4src/model/citations.ts; tests/citation-model.test.ts
OMI-SPEC-220 — Bibliographic Record Model0.1.0partial4src/types/omi.ts; tests/bibliographic-lookup.test.ts
OMI-SPEC-221 — Reference Library and Registry Architecture0.1.0partial4src/services/referenceManagerApi.ts; tests/reference-manager-integrations.test.ts
OMI-SPEC-225 — Source and Derivation Model0.2.0partial4src/model/sourceAttributionExport.ts; tests/source-attribution-lifecycle.test.ts
OMI-SPEC-230 — Publishing Model0.1.0partial7src/model/publicationBuild.ts; tests/publication-build.test.ts
OMI-SPEC-240 — Rendering and Publication Profile Model0.1.0partial7src/model/publicationProfile.ts; tests/publication-profile.test.ts
OMI-SPEC-300 — Plugin Architecture0.1.0partial9src/modules/registry.ts; tests/studio-module-framework.test.ts
OMI-SPEC-310 — Platform API0.1.0partial9src/services/authApi.ts; tests/studio-api-transport.test.ts
OMI-SPEC-320 — File Format0.3.0partial5src/model/omiFormatConstants.ts; src/services/omiPortableFormat.ts
OMI-SPEC-330 — Container Architecture0.1.0partial5src/services/omiContainer.ts; tests/asset-container.test.ts
OMI-SPEC-340 — Import and Export Model0.1.0partial8src/services/docxImportStrategy.ts; src/components/ExportFormatsPanel.tsx
OMI-SPEC-350 — Capability and Conformance Model0.1.0partial9src/model/jatsConformance.ts; tests/jats-conformance.test.ts

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​

VersionDateChange
0.16.02026-11-11Added 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.02026-11-05Added 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.02026-11-05Added 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.02026-11-05Added 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.02026-11-05Added 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.02026-11-04Added 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.02026-11-04Added 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.02026-11-04Added 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.02026-11-04Added 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.02026-11-04Added 12 requirement-mapped validation behavior cases; current core coverage is 25 partial / 41 untested. Retained dated Studio evidence; no lifecycle promotion.
0.6.02026-10-31Rebuilt 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.