-
-
Notifications
You must be signed in to change notification settings - Fork 34
Things That Need Doing
This page is to keep track of all of the items that are needed in order to ship MF2.0
-[ ] 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
-[x] Create a stability policy section
-[ ] Review stability policies
-[ ] Incorporate changes as needed
-[x] Resolve mutability of external values. External values can be annotated or masked, but are otherwise immutable.
-[x] Resolve mutability of local variables. Variables are immutable
-[ ] Resolve name pattern and questions about the semi-adoption of Nmtoken
-[x] Address #299 (when do we evaluate declarations)
-[ ] Expression attributes
-[ ] 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
-[ ] 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
-[ ] Create complete tests for syntax -[ ] Create complete tests for formatting -[ ] Create complete tests for selection -[ ] Create complete tests for each default registry entry
This includes:
- format to parts
- data model
-[ ] Identify (at least) two implementations -[ ] (#1): name here -[ ] (#2): name here
- ... -[ ] Demonstrate two implementations passing the tests
-[ ] 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
-[ ] Develop a user guide