Skip to content

Fix stability policy #480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 25, 2023
Merged

Fix stability policy #480

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bea3f27
Use "will not", use semantic line breaks
eemeli Sep 19, 2023
b58659c
Re-add making invalid valid
eemeli Sep 19, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions spec/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,34 +70,34 @@ A reference to a _term_ looks like this.

### Stability Policy

Updates to this specification MUST NOT change
Updates to this specification will not change
the syntactical meaning, the runtime output, or other behaviour
of valid messages written for earlier versions of this specification
that only use functions and expression attributes defined in this specification.
Updates to this specification will not remove any syntax provided
in this version. Future versions MAY add additional structure or meaning
to existing syntax.
Updates to this specification will not remove any syntax provided in this version.
Future versions MAY add additional structure or meaning to existing syntax.

Updates to this specification will not remove any reserved keywords
or sigils.
Updates to this specification will not remove any reserved keywords or sigils.

> Note: future versions may defined new keywords
> Note: future versions may define new keywords.

Updates to this specification will not reserve or assign meaning to any
character "sigils" except for those in the `reserved` production.
Updates to this specification will not reserve or assign meaning to
any character "sigils" except for those in the `reserved` production.

Updates to this specification will not remove any functions
defined in the default registry nor will they remove any options
or option values. Additional options or option values MAY be
defined.
Updates to this specification
will not remove any functions defined in the default registry nor
will they remove any options or option values.
Additional options or option values MAY be defined.

> [!NOTE]
> This does not guarantee that the results of formatting will never change.
> Even when the specification doesn't change,
> the functions for date formatting, number formatting and so on
> will change their results over time.

Updates to this specification MUST NOT introduce message syntax that,
Later specification versions MAY make previously invalid messages valid.

Updates to this specification will not introduce message syntax that,
when parsed according to earlier versions of this specification,
would produce syntax or data model errors.
Such messages MAY produce errors when formatted
Expand Down