Specification
The canonical OpenBody standard is SPEC.md — a single normative document. This site
renders it verbatim (synced from the canonical repository at build time); it never holds a
hand-edited fork.
DRAFT · v0.6.0 · pre-v1.0
What is normative
- §§3–10 are the normative standard — the model and the mapping rules.
- §§1–2 are introductory — problem framing and the prior-art survey; their only normative force is the forward-referenced design commitments.
- §11 (reference implementation) is non-normative and deferred.
The conformance keywords MUST / MUST NOT / SHOULD / SHOULD NOT / MAY carry RFC 2119 /
RFC 8174 meaning only when capitalized. Parenthetical provenance tags like (R1), (D3),
(F7) are non-normative design-history markers — ignore them when implementing.
Serialization
The normative model is defined independently of any serialization (field names, types, cardinality, semantics). JSON, with a published JSON Schema, is the primary, first-class binding and the form used by every worked example and conformance vector. Protocol Buffers, FlatBuffers, and other encodings are valid non-normative alternate bindings for high-throughput implementations — they must preserve the normative field semantics and round-trip losslessly to JSON.