- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Fri, 6 Sep 2013 21:01:29 +0000
- To: "public-sysapps@w3.org" <public-sysapps@w3.org>
- CC: Marcos Caceres <w3c@marcosc.com>, "jungkee.song@samsung.com" <jungkee.song@samsung.com>
Hi All, I've updated the "Application Lifecycle and Events" draft [1] that we reviewed at the F2F last week as per the F2F feedback by you recorded at [2]. The draft is now annotated with many NOTEs (non-normative) and ISSUEs (normative implications) that map directly to your feedback. All the comments in the Etherpad document [2] marked as [CLOSED] should have a corresponding commit at [3]. The comments marked as [OPEN] require more information or clarification. The most significant changes were (for a detailed changelog see [3]): * Added NOTEs and ISSUEs as per your review comments. * Clearer split between non-normative sections (use cases etc.) and normative sections. All the sections that are non-normative now start with the usual "This section is non-normative" for clarity. Also RFC 2119 terms are only used in normative sections of the document now. [Special thanks to Marcos for the most entertaining conformance class comment :-)] * Added a strawman proposal for "a dualistic main document" that can be of type document or worker. I think we may want to try to pick one type for v1 to allow us move faster. All - if you have a preference for either a document or worker-derived main document/event page we'd like to hear from you now. Lastly, I think we may want to merge this draft into sysapps runtime repo soon to make it easier for people to start contributing, including our new co-editors Marcos and Jungkee ;-) Thank You All for the most productive F2F session, feedback and comments. -Anssi [1] http://anssiko.github.io/runtime/app-lifecycle.html [2] https://etherpad.mozilla.org/event-pages [3] https://github.com/anssiko/runtime/commits/lifecycle
Received on Friday, 6 September 2013 21:02:03 UTC