Specification
The schemas say what an ODS document holds. These documents say how to exchange one and how to write one: how a package is built, how its files are hashed, what a reader must check before it trusts them, and the conventions and words the schemas follow.
Package format
draftHow an ODS package holds a document, the inputs of each run and a manifest that lets anyone check the files are unchanged.
Canonical JSON
readyThe one byte form ODS hashes: RFC 8785, with shared test vectors every implementation must pass.
Conventions
draftThe rules every ODS schema, module and vocabulary follows: kinds, names, descriptions and structure.
Glossary
draftOne meaning for each ODS word, with the words ODS does not use for it.
Places and shapes
draftHow ODS carries spatial data: GeoJSON, the coordinate reference system in full, the accuracy and origin of a position, other ways to state a place, and the original dataset.
Validation
draftWhat makes a document valid: the schemas, and the rules they cannot state, each with the code of its finding.
Regulator profiles
draftA framework written so that a program can run it: what a profile holds, the rules it meets, how a flow runs and how a trace is checked.
Versioning and deprecation
pendingHow releases are numbered, and how a field is deprecated and removed.