Skip to content
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

Define "option resolution" and require order to be insignificant #920

Merged
merged 1 commit into from
Oct 28, 2024
Merged

Define "option resolution" and require order to be insignificant #920

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 9 additions & 1 deletion spec/formatting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -333,7 +333,15 @@ Implementation-defined _functions_ SHOULD use an implementation-defined _namespa

#### Option Resolution

The result of resolving _option_ values is an unordered mapping of string identifiers to values.
**_<dfn>Option resolution</dfn>_** is the process of computing the _options_
for a given _expression_.
_Option resolution_ results in a mapping of string _identifiers_ to _values_.
The order of _options_ MUST NOT be significant.

> For example, the following _message_ treats both both placeholders identically:
> ```
> {$x :function option1=foo option2=bar} {$x :function option2=bar option1=foo}
> ```

For each _option_:

Expand Down