Skip to content

Limit spec-defined option values #929

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 5 commits into from
Nov 15, 2024
Merged

Limit spec-defined option values #929

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0a80d6d
Limit spec-defined option values
eemeli Nov 10, 2024
ce0fe2a
Apply changes adopted during the 2024-11-11 call
eemeli Nov 14, 2024
a58c6e5
Update spec/README.md
aphillips Nov 14, 2024
9386a23
Reserve single-character uppercase namespaces
eemeli Nov 14, 2024
1a979a3
Be explicit about reserved characters
eemeli Nov 14, 2024
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
22 changes: 16 additions & 6 deletions spec/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,10 +84,10 @@ Updates to this specification will not make any valid _message_ invalid.

Updates to this specification will not remove any syntax provided in this version.

Updates to this specification MUST NOT specify an error for any message
Updates to this specification will not specify an error for any message
that previously did not specify an error.

Updates to this specification MUST NOT specify the use of a fallback value for any message
Updates to this specification will not specify the use of a fallback value for any message
that previously did not specify a fallback value.

Updates to this specification will not change the syntactical meaning
Expand All @@ -107,12 +107,22 @@ defined in the default registry.
> (such as due to the release of new CLDR versions).

Updates to this specification will only reserve, define, or require
function names or function option names
consisting of characters in the ranges a-z, A-Z, and 0-9.
All other names in these categories are reserved for the use of implementations or users.
function identifiers and function option identifiers
which satisfy either of the following two requirements:
- Includes no namespace,
and has a name consisting of characters in the ranges a-z, A-Z, and 0-9.
- Uses the `u:` namespace.

All other identifiers in these categories are reserved for the use of implementations or users.

Updates to this specification will only reserve, define, or require
function option values
consisting of characters in the ranges a-z, A-Z, and 0-9,
and the characters U+002D HYPHEN-MINUS `-` and U+002E FULL STOP `.`.
All other option values are reserved for the use of implementations or users.

> [!NOTE]
> Users defining custom names SHOULD include at least one character outside these ranges
> Users defining custom identifiers and values SHOULD include at least one character outside these ranges
> to ensure that they will be compatible with future versions of this specification.
> They SHOULD also use the namespace feature to avoid collisions with other implementations.

Expand Down