Things That Need Doing

This page is to keep track of all of the items that are needed in order to ship MF2.0

Answer the TechPreview list

• How best to define value resolution https://github.com/unicode-org/message-format-wg/issues/678
• How to perform non-integer exact number selection https://github.com/unicode-org/message-format-wg/issues/675
• Whether markup should support additional spaces https://github.com/unicode-org/message-format-wg/issues/650
• Whether "attribute-like" behavior is needed and what form it should take https://github.com/unicode-org/message-format-wg/issues/642
• Whether to relax constraints on complex message start https://github.com/unicode-org/message-format-wg/issues/610
• Whether omitting the * variant key should be permitted https://github.com/unicode-org/message-format-wg/issues/603

Address all Preview-Feedback issues

• Close all of these: https://github.com/unicode-org/message-format-wg/issues?q=is%3Aissue+is%3Aopen+label%3APreview-Feedback

Function Interaction and Resolved Values

• Specify the handling of "resolved values"
• Specify the interaction of declarations, selectors, and variable references.
• Create tests

Error handling

• Ensure that a complete enumeration and error types is in place
• Fix requirements for error handling (ECH)
• Update tests to match

Bidi and whitespace handling

• Finish design of bidi isolation support in the message syntax (APP)
• Address the handling of pattern-exterior whitespace (PEWS) with regard to UAX31 (APP)

Interchange Data Model

• Specify the Interchange Data Model
  • Are namespaces separated from the name or all-one-field?
• Ensure that there are implementations
• Update tests

Function Registry (EAO)

• Specify the Registry Data Model
• Establish registry maintenance procedures
• Address default registry options not included in Tech Preview
• Update tests

Markup

Expression Attributes

Tests

• Create complete tests for syntax
• Create complete tests for formatting
• Create complete tests for selection
• Create complete tests for each default registry entry

Informative Annexes

This includes:

• format to parts (EAO) (on 2024-06-24 the WG discussed not including this)

Publication

• Review and approve the details of the stability policy as a WG
• Convert specification parts into a single HTML document (plus ancillary files as appropriate)
• Linkfy terms to definitions
• Publish to unicode.org

Later?

• Develop a user guide

Chair Resources

Nudge the CLA server:

• http://cla-assistant.io/check/unicode-org/message-format-wg?pullRequest=###