Capability claims and evidence index
Translation notice: this page is an English translation of the authoritative Traditional Chinese (Taiwan) document. Claim identifiers and machine-readable values are not translated.
This index separates capability into three dimensions that do not imply one another. The
machine-readable source is claims.json;
CI validates claim IDs, evidence paths, and limitation descriptions.
| Claim | Format | Dimension | Level | Limitation summary |
|---|---|---|---|---|
ODS-PACKAGE-001 |
ODS | PackageFidelity | round-trip-verified | Package round trips do not imply formula recalculation or complete spreadsheet semantics. |
ODS-SEMANTIC-001 |
ODS | SemanticApiDepth | semantic-contract-verified | Reads stored values and formulas but does not recalculate formulas. |
ODT-SEMANTIC-001 |
ODT | SemanticApiDepth | semantic-contract-verified | No page-layout or rendering engine is provided. |
ODP-SEMANTIC-001 |
ODP | SemanticApiDepth | semantic-contract-verified | ODP is a DOM/package workload; no streaming slide API is claimed. |
ODG-SEMANTIC-001 |
ODG | SemanticApiDepth | semantic-contract-verified | SmartArt layout and pixel-level rendering are not implemented. |
ODF-INTEROP-001 |
ODF | InteropEvidence | interop-tested | Tests against a specific LibreOffice version do not guarantee pixel-identical output in every suite. |
PackageFidelity addresses safe package handling; SemanticApiDepth addresses how much document
meaning an API can understand and change; InteropEvidence records external applications and versions
that were tested. The highest level in one dimension cannot replace either of the other dimensions.
The single source of truth for semantic families, CRUD operations, specification sections,
implementation, tests, interoperability evidence, and limitations is
semantic-coverage.json. CI
enforces it through eng/Test-SemanticCoverage.ps1. See
provenance/semantic-api-clean-room.md
for clean-room source boundaries.
Semantic coverage schema v4 additionally requires every topic to have evidence for Create, Get,
Find, Set, Update, Remove, Clear, RoundTrip, and Interop, linked to specifications,
implementation, tests, limitations, and clean-room provenance. Every family must also have
machine-verified evidence for existing documents, unknown-content preservation, ODF 1.1–1.3,
downgrade diagnostics, and invalid input. See the migration guide
and the four-format semantic facade reference.