Addison Phillips

I think what we should do is: merge #911 and #922 and then do a cleanup edit on registry.md in a new PR

This was discussed in the 2024-11-18 call. We resolved to use valid in most cases, but with careful phrasing in the boilerplate. I believe this is now addressed?

I see your elaboration. One callout: "implementation" has to be used carefully. In most cases in our spec it refers to the MessageFormat framework/executable/host environment itself, e.g. in ICU4J the...

@macchiati asked for Agenda+ on this item via email.

In the 2025-02-03 call we agreed that this feature depends on developing machine-readable function definitions, a deliverable that is not in v47 scope. I am removing Agenda+ and moving to...

Note that `timeZone` is an option, not a function. > However, LDML and TZDB define two different standards for time zone identifiers: a BCP-47 ID and a longer form string...

I'm not a big fan of the short ids for general interchange. I would be okay with ICU supporting them using an `icu:` prefix or with `timeZone` having two value...

We don't have a teleconference for two weeks, so this is likely to be the first change committed after issuing the tech preview. While this marks a normative change, I...

Looking closely this morning, I see that data model errors are tricky. - _Variant Key Mismatch_ has specific handling in the pattern selection section. I put some error handling text...

@eemeli I think the challenge for me is: Syntax errors relate solely to the ABNF and parsing errors generated from that. Data model errors are aspects of MF2 that cannot...