How decisions are made
A framework decision changes what the specification says, or when it says it. This page states what counts as one, who decides it, and what the public gets to see before and after.
Read with Methodology · Versions · Contribute
Who decides what, and what consultation is required
| Decision | Decided by | Consultation |
|---|---|---|
| New statements | Editorial group proposes; board adopts at release | REQUIRED |
| Amendments to a published statement | Editorial group, with board adoption where the meaning changes | REQUIRED |
| Deprecations | Board, on editorial group recommendation | REQUIRED |
| Extensions | Board, on the recommendation of the extension's editorial group | REQUIRED |
| Level and verb list changes | Board, on editorial group recommendation | REQUIRED |
| Releases and release dates | Board | NOTICE ONLY |
| Editorial corrections | Editorial group | NOT USED |
Rejected proposals are published with the reason
A consultation whose rejections are invisible is not a consultation. Every submission is acknowledged, considered, answered and published — including those that are not accepted.
Acknowledged
Within 10 working days, with a reference the proposer can cite.
Considered
By the editorial group for the domain or extension concerned.
Answered
With a published outcome and the reasons for it. Rejections carry their reason.
Published
On the open proposals register, with author and date, and kept there permanently.
What must go to consultation, and what may not
Where the ordinary process does not apply
Available only where a published statement creates a safety, legal or security risk. It requires a board resolution, published as a notice on the day the change is made.
A proposer may appeal an outcome once, within 20 working days, on the ground that the process was not followed. Appeals are decided by 3 directors who did not take the original decision.