W3C home > Mailing lists > Public > public-html-admin@w3.org > January 2013

Re: CfC: handle ISSUE-207 responsive-images consistently with Plan 2014

From: Wayne Carr <wayne.carr@linux.intel.com>
Date: Wed, 16 Jan 2013 16:04:43 -0800
Message-ID: <50F7401B.7000002@linux.intel.com>
To: public-html-admin@w3.org
We support the Chairs proposal to handle the the usual way in an 
extension spec.  Especially, given the ability to reintegrate if it 
meets the HTML5 exit criteria.

On 1/16/2013 1:04 AM, Maciej Stachowiak wrote:
> Based on a tracker request in <https://www.w3.org/Bugs/Public/show_bug.cgi?id=18384>, we have an issue raised regarding responsive images, and a request to incorporate a responsive image solution into HTML5 as soon as possible, rather than proceeding via extension specs: https://www.w3.org/html/wg/tracker/issues/207>.
>
> It seems that many in the Working Group have been satisfied to handle responsive images consistently with Plan 2014, by proceeding via extension specifications for possible later reintegration. Previously, the Working Group decided to handle many existing open issues in this way: <http://lists.w3.org/Archives/Public/public-html/2012Oct/0026.html>
>
> At this time, the Chairs propose to decide by consensus to address the new ISSUE-207 responsive-images in the same way: by allowing extension specifications to proceed (as they already are) and by allowing an opportunity for future reintegration if the extensions can meet the HTML5 exit criteria.
>
> If you have any comments or concerns about this CfC, please respond by Wednesday, January 23rd, 2013. Positive response is preferred and encouraged and silence will be considered as agreement with the proposal.
>
> If your comment is an objection, please clearly state that. In accordance with the W3C Process, objections SHOULD cite substantive arguments and propose changes that would remove the objection.
>
> Regards,
> Maciej
> (on behalf of the HTML WG chairs)
>
>
>
Received on Thursday, 17 January 2013 00:05:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 17 January 2013 00:05:30 GMT