Structure to make changes to the specification

Have a look at the versioning system to understand what Conflictive/Additive/`Bugfixes' means in relation to versions.

Minor Changes

Changes that are minor like fixing typos, fixing the ABNF (due to a bug in it) or similar cases can be done without having to open an issue and discuss the proper solution. To fix these problems simply opening a PR is enough.

Syntax Changes

Syntax changes refer to any changes that are well syntactic i.e. addition of arrays through the [x, y, z] value, the addition of date times... Or perhaps allowing _ in numbers or allowing you to perform constructors with arguments.

Additive Changes

If any syntax changes are additive (that is they don't require the changing of any previous code) then it can be done in an Additive update (exact times are under the versioning system page). This requires a PR to discuss the best way to achieve this syntax change (i.e. use of [...] or {...} for arrays or have them implicit...) and whether or not it requires any new opcodes if it does then a discussion on the opcodes also has to be had (information on that later on below).

Conflictive Changes

These changes during the pre v1.0 period can occur just as if they were additive changes but after that these changes will be rare, and will often take months upon months (as each conflictive change post v1.0 is aimed to cover around a year).

Opcode Changes

These can exist in the same PR as syntax changes as long as they are relevant. The discussion of whether or not current functionality can be done without adding opcodes is necessary and important.