Governance processes

Sections marked as "Note" or "Example" are non-normative. Everything else is normative.

As well as sections marked non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Normative sections use the terms MUST, SHOULD, and MAY as described in RFC 2119.

This chapter documents the change-control workflow and registry stewardship obligations for the specification.

Change control process

Proposals for new features or $type identifiers MUST be filed as GitHub issues. The specification editor reviews proposals and records decisions. Deprecated features remain supported for at least two revision cycles.

Registries

The specification editor maintains registries for $type values and extension namespaces. Each entry records the owner, contact information, and specification reference.

Backward compatibility

Breaking changes increment the major version. Implementations SHOULD support the previous major version for a grace period of twelve months.