[FEEDBACK] Limits of Digit Size Options

[sffc]

The Digit Size Options in registry.md say they use the following EBNF:

digit-size-option = "0" / (("1"-"9") [DIGIT])

This appears to accept 0, 1, 2, ..., 9, 10, 11, ..., 98, 99.

However, ECMA-402 restricts the range of some of these integers to be less. For example, minimum and maximum significant digits and minimum integer digits are restricted to the range 1-21:

https://tc39.es/ecma402/#sec-setnfdigitoptions

[eemeli]

Given that the spec also includes

message-format-wg/spec/registry.md

Lines 690 to 693 in 849db9c

	A "digit size option" is an _option_ value that the _function_ interprets
	as a small integer value greater than or equal to zero.
	Implementations MAY define an upper limit on the _resolved value_
	of a digit size option option consistent with that implementation's practical limits.

it's not clear to me what this feedback is about?

[sffc]

I feel limits on these options should be more strict in general because it is a dereliction of duty for MF2 to allow a message that is supported in one implementation but rejected in another (without using implementation-specific namespaced options), but I'll leave it up to the WG to decide if this text, permitting engines to differ in the limits they impose, is acceptable to MF2.