Skip to content

Things That Need Doing

Eemeli Aro edited this page Sep 7, 2024 · 33 revisions

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

Address all Preview-Feedback and TechPreview issues

Function Interaction and Resolved Values

  • How best to define value resolution #678
  • Specify the handling of "resolved values"
  • Specify the interaction of declarations, selectors, and variable references. #824
  • Create tests

Error handling

  • Ensure that a complete enumeration and error types is in place
  • Fix requirements for error handling #782 (ECH)
  • Ensure that error requirements are defined in the specification (EAO)
  • Ensure that error fallback format is define for each error state (EAO)
  • Update tests to match

Bidi and whitespace handling

  • Whether to relax constraints on complex message start #610
  • Finish design of bidi isolation support in the message syntax #746 (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
  • A specification for a one-to-one mapping between the data model and XLIFF (this is one of our deliverables)

Function Registry (EAO)

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

Markup

  • Whether markup should support additional spaces #650

Expression Attributes

  • Whether "attribute-like" behavior is needed and what form it should take #642

Tests

  • Create complete tests for syntax (TIM) #843
  • 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?

Chair Resources

Nudge the CLA server:

Clone this wiki locally