For various reasons, a Candidate Recommendation of Widget Updates was
never published, although the CfC to do so passed and the ED is prepared
as such [widget-updates].
Since no one has raised this as an issue, I would like feedback on what
we should do with this spec. The main options are: 1) to stop work (and
publish a WG Note); 2) to move forward with the CR.
I don'tthink it makes much sense to move the spec to CR if we do not
have commitments for at least two independent implementations of the
CR. Therefore, Implementors should please speak up if they willcommit to
implementing this CR.
-Thanks, AB
[widget-updates] <http://dev.w3.org/2006/waf/widgets-updates/>
-------- Original Message --------
Subject: CfC: publish Candidate Recommendation of Widget Updates;
deadline May 2
Resent-Date: Thu, 26 Apr 2012 16:42:00 +0000
Resent-From: <public-native-web-a...@w3.org>
Date: Thu, 26 Apr 2012 12:41:34 -0400
From: ext Arthur Barstow <art.bars...@nokia.com>
To: public-webapps <public-webapps@w3.org>
CC: <public-native-web-a...@w3.org>
The comment deadline for the Widget Updates LCWD ended April 19. No
comments were submitted for that document so this is a Call for
Consensus to publish a Candidate Recommendation of the spec using the LC
as the basis <http://www.w3.org/TR/2012/WD-widgets-updates-20120322/>.
The Exit Criteria for the CR will be the same as that used for the other
widget specs, namely that two or more implementations must pass each
test case.
This CfC satisfies: a) the group's requirement to "record the group's
decision to request advancement" to CR; and b) "General Requirements for
Advancement on the Recommendation Track" as defined in the Process Document:
http://www.w3.org/2005/10/Process-20051014/tr.html#transition-reqs
Positive response is preferred and encouraged and silence will be
considered as agreeing with the proposal. The deadline for comments is
May 2 and all comments should be sent to public-webapps at w3.org.
-Thanks, AB