Addison Phillips

I agree. A syntax error can occur in a simple message: ``` This has a {$syntax :error ``` ... so we should clarify that the quoted paragraph applies to all...

... or we could just get rid of "MAY be" (or convert to SHOULD). Some syntax errors are recoverable (at least to the point of not requiring the logo be...

Sorry I wasn't clear. The proposal is that syntax/data model errors fail the message outright. I agree that expression-internal syntax errors are sometimes recoverable and that we can allow these...

I think this would be a mistake. I agree that there is no specific `bad-option` error. I think we should fix registry.md for some of the cases you point out....

Note: I made #741 to (try to) address part of the gap. It doesn't mess with the `bad-option` problem.

I'm marking this for Monday's agenda. I used `resolve-candidate` because at least two of us feel that this shouldn't go in, but that doesn't mean the WG won't feel differently.

In the 2024-03-25 call we agreed not to merge this.

Numeric literals are not numbers. They are a sub-production of literal that makes it convenient to use numeric values in the syntax. We have `number-literal` instead of mutating `name` a...

@mihnita I think options are the same thing. Functions need to specify what string serialization they accept. For an expression like `{$count :number minimumFractionDigits=1}`, the `1` has to be a...

@macchiati "The" data model in our discussions refers to the data model defined in the specification. It is intended as an interchange format and thus can be formalized. Implementations are...