Re: Call for Consensus: Publish HTML 5.2 FPWD?

[Chaals McCathie Nevile]

On Tue, 05 Jul 2016 16:15:32 +0200, Chaals McCathie Nevile  
 wrote:



This is a call for consensus on the proposition:

Publish the current editors' draft of HTML 5.2 -  
https://w3c.github.io/html/ - as a First Public Working Draft.


With a positive response and no objections, the call for consensus passes.  
We will prepare a draft and Transition request, and hope to make the  
publication next week.



You can provide a response in this email thread.

You can provide a comment or thumbs-up in the issue in the HTML repo -  
https://github.com/w3c/html/issues/515


Most responses were in fact on the HTML repo.

You can provide a comment or thumbs-up in the issue in the WebPlatformWG  
repo - https://github.com/w3c/WebPlatformWG/issues/43


Thanks all

Chaals for the chairs and editors

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
 cha...@yandex-team.ru - - - Find more at http://yandex.com

RE: Call for Consensus: Publish HTML 5.2 FPWD?

[Katie Haritos-Shea GMAIL]

+1 to publish

​



* katie *
 
Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
 
Cell: 703-371-5545 | ryla...@gmail.com | Oakton, VA | LinkedIn Profile | 
Office: 703-371-5545 | @ryladog


-Original Message-
From: Léonie Watson [mailto:t...@tink.uk] 
Sent: Monday, July 11, 2016 6:15 AM
To: Chaals McCathie Nevile <cha...@yandex-team.ru>; public-webapps WG 
<public-webapps@w3.org>
Subject: Re: Call for Consensus: Publish HTML 5.2 FPWD?

Reminder that this CFC closes on Thursday 14th July (end of day). If you can 
take a few minutes to respond through one of the three proposed channels, it 
will help us identify the work mode that suits the WG best. 
Thanks.

Léonie.

On 05/07/2016 15:15, Chaals McCathie Nevile wrote:
> This is a call for consensus on the proposition:
>
> Publish the current editors' draft of HTML 5.2 - 
> https://w3c.github.io/html/ - as a First Public Working Draft.
>
> Silence will be considered assent, but positive responses are preferred.
> In an effort to find a smoother way to assess consensus, there are 
> three possible mechanisms for feedback, and you should pick the one 
> you find most convenient:
>
> You can provide a response in this email thread.
>
> You can provide a comment or thumbs-up in the issue in the HTML repo -
> https://github.com/w3c/html/issues/515
>
> You can provide a comment or thumbs-up in the issue in the 
> WebPlatformWG repo - https://github.com/w3c/WebPlatformWG/issues/43
>
> There is no need to use more than one of these mechanisms, as the 
> chairs will collate the results.
>
> If many people use the issues instead of email, we will likely propose 
> a change to the work mode for assessing consensus.
>
> There will be a separate thread on the merits of any procedural change 
> - please *only* reply to this thread to support or oppose the FPWD 
> publication.
>
> cheers
>
> Chaals, for the chairs
>

Re: Call for Consensus: Publish HTML 5.2 FPWD?

[Dylan Barrell]

+1 to publish

On Mon, Jul 11, 2016 at 6:14 AM, Léonie Watson  wrote:

> Reminder that this CFC closes on Thursday 14th July (end of day). If you
> can take a few minutes to respond through one of the three proposed
> channels, it will help us identify the work mode that suits the WG best.
> Thanks.
>
> Léonie.
>
>
> On 05/07/2016 15:15, Chaals McCathie Nevile wrote:
>
>> This is a call for consensus on the proposition:
>>
>> Publish the current editors' draft of HTML 5.2 -
>> https://w3c.github.io/html/ - as a First Public Working Draft.
>>
>> Silence will be considered assent, but positive responses are preferred.
>> In an effort to find a smoother way to assess consensus, there are three
>> possible mechanisms for feedback, and you should pick the one you find
>> most convenient:
>>
>> You can provide a response in this email thread.
>>
>> You can provide a comment or thumbs-up in the issue in the HTML repo -
>> https://github.com/w3c/html/issues/515
>>
>> You can provide a comment or thumbs-up in the issue in the WebPlatformWG
>> repo - https://github.com/w3c/WebPlatformWG/issues/43
>>
>> There is no need to use more than one of these mechanisms, as the chairs
>> will collate the results.
>>
>> If many people use the issues instead of email, we will likely propose a
>> change to the work mode for assessing consensus.
>>
>> There will be a separate thread on the merits of any procedural change -
>> please *only* reply to this thread to support or oppose the FPWD
>> publication.
>>
>> cheers
>>
>> Chaals, for the chairs
>>
>>
>


-- 
Download the aXe browser extension for free:

Firefox: https://addons.mozilla.org/en-US/firefox/addon/axe-devtools
Chrome:
https://chrome.google.com/webstore/detail/axe/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US

Life is ten percent what happens to you and ninety percent how you respond
to it. - Lou Holtz

Re: Call for Consensus: Publish HTML 5.2 FPWD?

[Léonie Watson]

Reminder that this CFC closes on Thursday 14th July (end of day). If you 
can take a few minutes to respond through one of the three proposed 
channels, it will help us identify the work mode that suits the WG best. 
Thanks.


Léonie.

On 05/07/2016 15:15, Chaals McCathie Nevile wrote:

This is a call for consensus on the proposition:

Publish the current editors' draft of HTML 5.2 -
https://w3c.github.io/html/ - as a First Public Working Draft.

Silence will be considered assent, but positive responses are preferred.
In an effort to find a smoother way to assess consensus, there are three
possible mechanisms for feedback, and you should pick the one you find
most convenient:

You can provide a response in this email thread.

You can provide a comment or thumbs-up in the issue in the HTML repo -
https://github.com/w3c/html/issues/515

You can provide a comment or thumbs-up in the issue in the WebPlatformWG
repo - https://github.com/w3c/WebPlatformWG/issues/43

There is no need to use more than one of these mechanisms, as the chairs
will collate the results.

If many people use the issues instead of email, we will likely propose a
change to the work mode for assessing consensus.

There will be a separate thread on the merits of any procedural change -
please *only* reply to this thread to support or oppose the FPWD
publication.

cheers

Chaals, for the chairs

Re: Call for Consensus: Publish HTML 5.2 FPWD?

[Richard Schwerdtfeger]

Hi Charles, 

I see this is designed to provide semantic-level scripting and markup for 
accessibility: "This specification is limited to providing a semantic-level 
markup language and associated semantic-level scripting APIs for authoring 
accessible pages on the Web ranging from static documents to dynamic 
applications.”

Can you point to sections on this in the FPWD?

Thanks,

Rich

> On Jul 5, 2016, at 9:15 AM, Chaals McCathie Nevile  
> wrote:
> 
> This is a call for consensus on the proposition:
> 
> Publish the current editors' draft of HTML 5.2 - https://w3c.github.io/html/ 
> - as a First Public Working Draft.
> 
> Silence will be considered assent, but positive responses are preferred. In 
> an effort to find a smoother way to assess consensus, there are three 
> possible mechanisms for feedback, and you should pick the one you find most 
> convenient:
> 
> You can provide a response in this email thread.
> 
> You can provide a comment or thumbs-up in the issue in the HTML repo - 
> https://github.com/w3c/html/issues/515
> 
> You can provide a comment or thumbs-up in the issue in the WebPlatformWG repo 
> - https://github.com/w3c/WebPlatformWG/issues/43
> 
> There is no need to use more than one of these mechanisms, as the chairs will 
> collate the results.
> 
> If many people use the issues instead of email, we will likely propose a 
> change to the work mode for assessing consensus.
> 
> There will be a separate thread on the merits of any procedural change - 
> please *only* reply to this thread to support or oppose the FPWD publication.
> 
> cheers
> 
> Chaals, for the chairs
> 
> -- 
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> cha...@yandex-team.ru - - - Find more at http://yandex.com
>