UseJunior Book a Demo

ECMA-376 edition 5, Part 1 § 17.10.5

w:headerReference binding

Product posture and evidence for this normative section. The ECMA publication is the authority; this page reports only the pinned Safe DOCX projection.

ECMA publication ↗

Safe DOCX posture

targeted

w:headerReference binding

Each declared header slot (first/default/even) becomes its own part bound through a typed w:headerReference whose r:id (written namespace-aware via setAttributeNS) resolves in the document's relationships. References lead the w:sectPr child sequence; the structural validator rejects dangling or missing ids. The package audit follows each reference through document.xml.rels, checks the header relationship type, resolves its target part, and requires a w:hdr root. Duplicate roles within one section, duplicate relationship ids, targets that escape the package root, and fragment-bearing targets are rejected. Relative and package-absolute targets are normalized before lookup; URI-fragment semantics are outside this audit's supported OPC target model. Relationship reuse across sections is accepted. Pagination, role inheritance when a reference is absent, and reader rendering are not evaluated. Comparison uses this same audit to select only valid direct section bindings; target normalization and package containment are additional SafeDocX safety policies rather than claims made by this clause.

Registry identity: ECMA-PART1-17-10-5

Schema declarations

Bounded evidence