- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Sat, 22 Sep 2012 08:58:30 +1000
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: Adrian Roselli <Roselli@algonquinstudios.com>, Sam Ruby <rubys@intertwingly.net>, HTML WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On Sat, Sep 22, 2012 at 6:07 AM, Maciej Stachowiak <mjs@apple.com> wrote: > > On Sep 21, 2012, at 11:34 AM, Adrian Roselli <Roselli@algonquinstudios.com> wrote: > >>> >>> http://lists.w3.org/Archives/Public/public-html/2012Aug/0142.html >>> http://lists.w3.org/Archives/Public/public-html/2012Aug/0346.html >>> http://lists.w3.org/Archives/Public/public-html-wg- >>> announce/2012JulSep/0023.html >>> http://lists.w3.org/Archives/Public/public-html/2012Sep/0020.html >> >> I only see that the survey was put off until no sooner than 11 September. I understand "no sooner" can mean "End of Days," but I'm not getting that it's on hold indefinitely, let alone until a new process is put in place, from that correspondence. > > I think the key point there is that we never actually got an all-clear to post the survey. It may be that this would have eventually happened. But before that point, we came up with this plan as an alternative. To summarize the way I look at it (and thereby counter-check my understanding): basically the plan puts a feature-freeze in place such that all open issues that haven't been resolved yet are regarded as "at risk features" since they don't meet the implementation requirement and are thus pushed into extension specifications, that may make it if implementation experience can be brought forward before REC, but otherwise will go into HTML.next. Is that a correct (while simplified) understanding? Cheers, Silvia.
Received on Friday, 21 September 2012 22:59:17 UTC