Generated reference
Safe DOCX conformance explorer
Trace the product’s stated OOXML scope from an ECMA-376 clause to its schema declaration, implementation rationale, and bounded source, test, or formal evidence. This is a generated projection of pinned upstream registries—not an independent conformance assessment.
Browse ECMA sections
Start from a cited clause and inspect Safe DOCX’s bounded posture, related schema declarations, capability identities, and evidence.
Browse schema declarations
Start from a complete declaration identity—including schema, kind, name, and context—rather than a potentially ambiguous QName.
Browse capabilities
Start from a user-observable feature and compare Safe DOCX’s per-operation posture with mapped neutral scenarios and their latest measured outcomes.
Claim boundaries: a schema-valid fragment is not automatically supported by the Safe DOCX API and tool surface, and a passing scenario is not proof of complete Microsoft Word interoperability. Each page preserves the narrower upstream claim.
5 explicit non-goals
These OOXML structures are recognized or preserved at the stated boundary, but Safe DOCX does not claim their full document-editing semantics.
- § 17.13.5.1 — Table cell deletion (w:cellDel) Read the stated boundary and related schema context.
- § 17.13.5.2 — Table cell insertion (w:cellIns) Read the stated boundary and related schema context.
- § 17.13.5.3 — Vertically merged or split table cells (w:cellMerge) Read the stated boundary and related schema context.
- § 17.13.5.33 — Table-grid revisions (w:tblGridChange) Read the stated boundary and related schema context.
- § 17.13.5.35 — Table-property-exception revisions (w:tblPrExChange) Read the stated boundary and related schema context.