RE: CR Features ar Risk

Hi Paul,

will the canvas features that are at risk also be discussed there?

We are worried that the path and hit region features will have to be removed since there are no implementations.
There have been some discussions on public mailing lists where people have expressed unease with the path syntax. There are also some concern over implementation details of the hit regions.

Rik
________________________________________
From: Paul Cotton [Paul.Cotton@microsoft.com]
Sent: Monday, October 22, 2012 2:06 PM
To: public-html@w3.org
Subject: CR Features ar Risk

The W3C Process defines “features at risk” [1]:

In the Call for Implementations, the Working Group MAY identify specific features of the technical report as being "features at risk." General statements such as "We plan to remove any unimplemented feature" are not acceptable; the Working Group MUST precisely identify any features at risk. Thus, in response to a Call for Implementations, reviewers can indicate whether they would register a Formal Objection<http://www.w3.org/2005/10/Process-20051014/policies.html#FormalObjection> to the decision to remove the identified features.

After gathering implementation experience, the Working Group MAY remove features from the technical report that were identified as being "at risk" and request that the Director Call for Review of a Proposed Recommendation<http://www.w3.org/2005/10/Process-20051014/tr.html#cfr>. If the Working Group makes other substantive changes<http://www.w3.org/2005/10/Process-20051014/tr.html#substantive-change> to the technical report, the Director MUST return it to the Working Group for further work<http://www.w3.org/2005/10/Process-20051014/tr.html#return-to-wg>.
The HTML WG is currently working on a draft list of “features at risk” at:
http://www.w3.org/html/wg/wiki/index.php?title=HTML5.0AtRiskFeatures

The Chairs intend to have the HTML WG F2F discuss the above list of candidate “features at risk” at the TPAC F2F meeting next week in order that we can do a CfC on Candidate Recommendation as soon after the TPAC meeting as possible.

Therefore the Chairs would like to encourage email discussion of the draft list of “features at risk” before TPAC so that we can get as wide as possible input on the draft list before we do the discussion at TPAC and before we start any CR CfC.  HTML WG members are asked to reply to this thread if they wish to support the current draft list or have concerns about individual items on the list.

/paulc
HTML WG co-chair

[1] http://www.w3.org/2005/10/Process-20051014/tr.html#cfi

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

Received on Monday, 22 October 2012 22:40:51 UTC