W3C home > Mailing lists > Public > public-html@w3.org > October 2009

Re: Canvas 2D API specification update - defining the element or not

From: Philip Taylor <pjt47@cam.ac.uk>
Date: Fri, 23 Oct 2009 14:18:39 +0100
Message-ID: <4AE1AD2F.50109@cam.ac.uk>
To: Paul Cotton <Paul.Cotton@microsoft.com>
CC: "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-html@w3.org" <public-html@w3.org>
Paul Cotton wrote:
>> * Even if the LC->WD->LC thing didn't happen, the W3C Process seems
>> to allow for the first HTML5 LC to say the canvas feature is "at
>> risk" and then it could be removed (and added to a separate spec)
>> before moving to PR. That would give time to develop accessibility
>> solutions, before deciding if/how to best split canvas out of the
>> HTML5 spec.
> 
> The W3C Process step that permits a WG to declare features as being
> "at risk" is the Call for Implementation (aka Candidate
> Recommendation) stage.  See: 
> http://www.w3.org/2004/02/Process-20040205/tr.html#cfi

Oops, I need to read these things more carefully - thanks for the 
correction!

-- 
Philip Taylor
pjt47@cam.ac.uk
Received on Friday, 23 October 2009 13:19:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:50 GMT