Addison Phillips

> I assume this means that we still plan to fix this in LDML 47. This means that the WG would like it to be addressed in 47 and will...

A proposal would be very helpful. This can take the form of a [design](https://github.com/unicode-org/message-format-wg/tree/main/exploration) or it can just be a PR against the registry. We are working on regularizing the...

Given deadlines, this won't make v47. The functions in question won't be stable then, so marking for 48

@sffc I did reserve time in a previous call for this, but you were not available that day. Due to the timing of v47, this will not appear in the...

A data model that cannot represent (some) invalid messages seems better than one that can reproduce with fidelity known bugs. It will help prevent, e.g. tools from doing bad things....

> canonical order when serializing is alphabetic by option id. Note that the value space for option names is `identifier`, so probably not "alphabetical". Code point order?

Note: the correct tag for the English used in the UK is `en-GB` I'm not sure your intuition is correct, @domenic? You are very correct that language tag matching isn't...

Note that release LDML45-alpha was created for the CLDR-TC call that resulted in the above. We will have an LDML45 release that corresponds to the 27 March document.

Created LDML45-Tech-Preview branch and tagged it as a release.

I agree with having this issue. I note (as I did in the call) that exact fraction matching is a rare corner case. Plural rules work just fine with non-integer...