Things That Need Doing

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

Global

• Resolve the open/close/standalone design
• #298: are implementations allowed to override default registry functions?
  • are implementations allowed to extend default registry functions? Example: providing date skeletons
• #272: decide on formatting to something other than text
  • this is proposed for close by @eemeli's design document #463, in which format-to-parts is non-normative

ABNF

• Incorporate changes as needed

Syntax

• Resolve mutability of external values
• Resolve mutability of local variables
• Resolve name pattern and questions about the semi-adoption of Nmtoken
• Address #299 (when do we evaluate declarations)

Formatting

Registry Spec

• Decide if format and selector functions are distinct
• Resolve list of required functions
• Resolve options for each function
• Resolve if we provide "optional" options, such as skeletons

Default Registry

• Set criteria for inclusion in the default registry "ever"
  • is there a registration process?
• Set criteria for inclusion in the 2.0 registry
• Create complete registry

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
• data model

Implementations

• Identify (at least) two implementations
  • (#1): name here
  • (#2): name here
  • ...
• Demonstrate two implementations passing the tests

Publication

• 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