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 ; public-webapps WG 

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: Request to move HTML5.1 to Candidate Recommendation (CR)

[Katie Haritos-Shea GMAIL]

+1 to publish WD

​



* 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


-Original Message-
From: Léonie Watson [mailto:t...@tink.uk] 
Sent: Thursday, June 2, 2016 8:53 AM
To: public-h...@w3.org
Subject: FW: Request to move HTML5.1 to Candidate Recommendation (CR)

Please respond on public-webapps@w3.org as the official email for the WP WG.
Thanks.


-Original Message-
From: Léonie Watson [mailto:t...@tink.uk]
Sent: 02 June 2016 13:48
To: 'public-webapps WG' 
Subject: CFC: Request to move HTML5.1 to Candidate Recommendation (CR)

Hello WP,

This is a call for consensus to request that W3C publish the current HTML 
Working Draft (WD) as a Candidate Recommendation (CR). It has been posted to 
public-webapps@w3.org as the official email for this WG.

Please reply to this thread on public-webapps@w3.org  no later than end of day 
on 10 June. Positive responses are preferred and encouraged, silence will be 
considered as assent.

The current HTML5.1 WD [1] improves upon HTML5. It includes updates that make 
it more reliable, more readable and understandable, and a better match for 
reality. Substantial changes between HTML5 and HTML5.1 can be found in the spec 
[2].

When a specification moves to CR it triggers a Call For Exclusions, per section 
4 of the W3C Patent Policy [3]. No substantive additions can be made to a 
specification in CR without starting a new Call for Exclusions, so we will put 
HTML5.1 into "feature freeze". It is possible to make editorial updates as 
necessary, and features marked "At Risk" may be removed if found not to be 
interoperable.

The following features are considered "at risk". If we cannot identify at least 
two shipping implementations, they will be marked "at risk" in the CR and may 
be removed from the Proposed Recommendation.

keygen element. [issue 43]
label as a reassociatable element [issue 109] Fixing requestAnimationFrame to 
60Hz, not implementation-defined [issues 159/375/422] registerContentHandler 
[Issue 233] inputmode attribute of the input element [issue 269] autofill of 
form elements [issue 372] menu, menuitem and context menus. [issue 373] dialog 
element [issue 427] Text tracks exposing in-band metadata best practices [Issue 
461] datetime and datatime-local states of the input element [Issue 462]

Please share implementation details for any of these features on Github. To 
mark other features "at risk", please identify them by 10th June (ideally by 
filing an issue and providing a test case).

At the same time we move HTML5.1 into CR, we plan to continue updating the 
Editor's Draft, and in the next few weeks we expect to post a Call for 
Consensus to publish it as the First Public Working Draft of HTML5.2, so 
improving HTML will continue without a pause. It also means that changes that 
didn't make it into
HTML5.1 will not have long to wait before being incorporated into the 
specification.

Léonie on behalf of the WP chairs and team, and HTML editors.
[1] https://www.w3.org/TR/html51/
[2] https://www.w3.org/TR/html51/changes.html#changes
[3] https://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Exclusion 

[issue 43] https://github.com/w3c/html/issues/43
[issue 109] https://github.com/w3c/html/issues/109
[issues 159/375/422] https://github.com/w3c/html/issues/159 and links [issue 
233] https://github.com/w3c/html/issues/233
[issue 269] https://github.com/w3c/html/issues/269
[issue 372] https://github.com/w3c/html/issues/372
[issue 373] https://github.com/w3c/html/issues/373
[issue 427] https://github.com/w3c/html/issues/427
[Issue 461] https://github.com/w3c/html/issues/461
[Issue 462] https://github.com/w3c/html/issues/462 


--
@LeonieWatson tink.uk Carpe diem

RE: IndieUI Teleconference Agenda; 18 March at 21:00Z

[Katie Haritos-Shea GMAIL]

Andy,

It is the 18th. Janina did reply to you because I got it, but maybe that
missed you.:-)



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

-Original Message-
From: Andy Heath [mailto:andyhe...@axelafa.com] 
Sent: Tuesday, March 10, 2015 4:43 PM
To: Janina Sajka; public-indie...@w3.org
Cc: public-editing...@w3.org; public-webapps@w3.org
Subject: Re: IndieUI Teleconference Agenda; 18 March at 21:00Z

Hi, Janina can you clarify whether this is for the 11th or the 18th please.
The last couple of weeks or so it has been 18th in conversations (and what
I put in my diary at the time of the conversations).  The subject here says
18th but the body says 11th.

?

My hope is its 18th because that's easier for me than 11th.

Best

andy

On 10/03/2015 13:36, Janina Sajka wrote:
 Cross-posting as is now usual ...

 IMPORTANT: The U.S. is now on Daylight Time. Please carefully confirm 
 the time of this teleconference in your time zone using the resources 
 enumerated below.

 What:IndieUI Task Force Teleconference
 When:Wednesday 11 March
  2:00 PMSan Francisco -- U.S. Pacific  Time(PDT: UTC -7)
  4:00 PMAustin -- U.S. Central  Time(CDT: UTC -5)
  5:00 PMBoston -- U.S. Eastern  Time(EDT: UTC -4)
  9:00 PMLondon -- British  Time(BST: UTC +0)
 10:00 PMParis -- Central European Time(CET: UTC +1)
  5:00 AMBeijing -- China Standard Time(Thursday, 12 
 March CST: UTC +8)
  6:00 AMTokyo -- Japan Standard Time(Thursday, 12 
 March JST: UTC +9)
 Where:W3C Teleconference--See Below

 * Time of day conversions

 Please verify the correct time of this meeting in your time zone using 
 the Fixed Time Clock at:

 http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconfe
 renceiso=20150311T1700p1=43ah=1


 ** Preliminary Agenda for IndieUI Task Force Teleconference 11 March 
 2015

 Meeting: IndieUI Task Force Teleconference
 Chair:Janina_Sajka
 agenda+ preview agenda with items from two minutes
 agenda+Future of the IndieUI WG  TF -- Janina
 agenda+Schema.org Mappings -- Rich  Andy [See Below]
 agenda+Checkin with Web Apps' Editing TF [See below] Editors' 
 agenda+ Reports User Context Issues  Actions
 https://www.w3.org/WAI/IndieUI/track/products/3
 agenda+ Events Issues  Actions
 https://www.w3.org/WAI/IndieUI/track/products/2
 agenda+ Other Business
 agenda+Be Done

 Resource: Schema.org meta data mapping to Indie UI User context
 https://docs.google.com/spreadsheets/d/1pb92piOlud5sXQadXYnbmtp9LCut26
 gv8ku-qqZTwec/edit#gid=0


 Resource: Teleconference Minutes
 http://www.w3.org/2015/02/04-indie-ui-minutes.html

 Resource: Web Apps Editing TF
 Editing Explainer:http://w3c.github.io/editing-explainer/
 User Intentions: 
 http://w3c.github.io/editing-explainer/commands-explainer.html

 Resource: For Reference
 Home Page:http://www.w3.org/WAI/IndieUI/
 Email Archive: http://lists.w3.org/Archives/Public/public-indie-ui/

 Resource: Teleconference Logistics
 Dial the Zakim bridge using either SIP or the PSTN.
 PSTN: +1.617.761.6200 (This is a U.S. number).
 SIP: za...@voip.w3.org
 You should be prompted for a pass code, This is 46343#
 (INDIE#)

 Alternatively, bypass the Zakim prompts and SIP directly into our 
 teleconference.
 SIP: 0046...@voip.w3.org

 Instructions for connecting using SIP:
 http://www.w3.org/2006/tools/wiki/Zakim-SIP
 Place for users to contribute additional VoIP tips.
 http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips

 IRC: server: irc.w3.org, channel: #indie-ui.

 During the conference you can manage your participation with Zakim 
 commands as follows:
61# to mute yourself
60# to unMute yourself
41# to raise your hand (enter speaking queue)
40# to lower your hand (exit speaking queue)

 The system acknowledges these commands with a rapid, three-tone 
 confirmation.  Mobile phone users especially should use the mute 
 function if they don't have a mute function in their phone.  But the 
 hand-raising function is a good idea for anyone not using IRC.

 * IRC access

 An IRC channel will be available. The server is irc.w3.org, The port 
 number is 6665 (Note this is not the normal default) and The channel 
 is #indie-ui.

 * Some helpful Scribing and Participation Tips 
 http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet

 For more on the IRC setup and the robots we use for agenda and speaker 
 queuing and for posting the log to the web, see:

 - For RRSAgent, that captures and posts the log with special attention 
 to action items:
 http://www.w3.org/2002/03/RRSAgent

 - For Zakim, the IRC interface to the bridge manager, that will 
 maintain speaker and agenda queues:
 http://www.w3.org/2001/12/zakim-irc-bot

 - For a Web gateway to IRC you can use if your 

RE: IndieUI Teleconference Agenda; 4 February at 22:00Z for 60 minutes

[Katie Haritos-Shea GMAIL]

Possible regrets overseas



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

-Original Message-
From: Janina Sajka [mailto:jan...@rednote.net] 
Sent: Monday, February 2, 2015 11:31 PM
To: public-indie...@w3.org
Cc: public-editing...@w3.org; public-webapps@w3.org
Subject: IndieUI Teleconference Agenda; 4 February at 22:00Z for 60 minutes

Cross-posting as is now usual ...

What:   IndieUI Task Force Teleconference
When:   Wednesday 4 February
 2:00 PMSan Francisco -- U.S. Pacific  Time (PST: UTC
-8)
 4:00 PMAustin -- U.S. Central  Time(CST: UTC
-6)
 5:00 PMBoston -- U.S. Eastern  Time(EST: UTC
-5)
10:00 PMLondon -- British  Time (BST: UTC +0)
11:00 PMParis -- Central European Time  (CET: UTC
+1)
 6:00 AMBeijing -- China Standard Time  (Thursday, 13
November CST: UTC +8)
 7:00 AMTokyo -- Japan Standard Time(Thursday, 13
November JST: UTC +9)
Where:  W3C Teleconference--See Below

* Time of day conversions

Please verify the correct time of this meeting in your time zone using the
Fixed Time Clock at:

http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconference;
iso=20150204T1700p1=43ah=1

** Preliminary Agenda for IndieUI Task Force Teleconference 4 February 2015

Meeting: IndieUI Task Force Teleconference
Chair:  Janina_Sajka
agenda+ preview agenda with items from two minutes
agenda+ Checkin with Web Apps' Editing TF [See below]  Editors' Reports
agenda+ User Context Progress
agenda+ User Context Issues  Actions 
agenda+https://www.w3.org/WAI/IndieUI/track/products/3
agenda+ Events Issues  Actions
https://www.w3.org/WAI/IndieUI/track/products/2
agenda+  Other Business
agenda+ Be Done

Resource: TPAC Minutes
Monday: http://www.w3.org/2014/10/27-indie-ui-minutes.html  
Tuesday:http://www.w3.org/2014/10/28-indie-ui-minutes.html

Resource: Teleconference Minutes
http://www.w3.org/2015/01/21-indie-ui-minutes.html

Resource: Web Apps Editing TF
Editing Explainer:  http://w3c.github.io/editing-explainer/
User Intentions:
http://w3c.github.io/editing-explainer/commands-explainer.html
 
Resource: For Reference
Home Page:  http://www.w3.org/WAI/IndieUI/
Email Archive:  http://lists.w3.org/Archives/Public/public-indie-ui/

Resource: Teleconference Logistics
Dial the Zakim bridge using either SIP or the PSTN.
PSTN: +1.617.761.6200 (This is a U.S. number).
SIP: za...@voip.w3.org
You should be prompted for a pass code,
This is
46343#
(INDIE#)

Alternatively, bypass the Zakim prompts and SIP directly into our
teleconference.
SIP: 0046...@voip.w3.org

Instructions for connecting using SIP:
http://www.w3.org/2006/tools/wiki/Zakim-SIP
Place for users to contribute additional VoIP tips.
http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips

IRC: server: irc.w3.org, channel: #indie-ui.

During the conference you can manage your participation with Zakim commands
as follows:
61# to mute yourself
60# to unMute yourself
41# to raise your hand (enter speaking queue)
40# to lower your hand (exit speaking queue)

The system acknowledges these commands with a rapid, three-tone
confirmation.  Mobile phone users especially should use the mute function if
they don't have a mute function in their phone.  But the hand-raising
function is a good idea for anyone not using IRC.

* IRC access

An IRC channel will be available. The server is irc.w3.org, The port number
is 6665 (Note this is not the normal default) and The channel is #indie-ui.

* Some helpful Scribing and Participation Tips
http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet

For more on the IRC setup and the robots we use for agenda and speaker
queuing and for posting the log to the web, see:

- For RRSAgent, that captures and posts the log with special attention to
action items:
http://www.w3.org/2002/03/RRSAgent

- For Zakim, the IRC interface to the bridge manager, that will maintain
speaker and agenda queues:
http://www.w3.org/2001/12/zakim-irc-bot

- For a Web gateway to IRC you can use if your network administrators forbid
IRC, see:
http://www.w3.org/2001/01/cgi-irc

- For more on W3C use of IRC see:
http://www.w3.org/Project/IRC/

-- 

Janina Sajka,   Phone:  +1.443.300.2200
sip:jan...@asterisk.rednote.net
Email:  jan...@rednote.net

The Linux Foundation
Chair, Open Accessibility:  http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,  Protocols  Formats http://www.w3.org/wai/pf
IndieUI http://www.w3.org/WAI/IndieUI/

RE: [editing] Responsive Input Terminology

[Katie Haritos-Shea GMAIL]

+1 to device-independent events (di-events...hopefully not become die-events
per the time perspective conversation)



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

-Original Message-
From: cha...@yandex-team.ru [mailto:cha...@yandex-team.ru] 
Sent: Friday, December 12, 2014 9:36 AM
To: Simon Pieters; Arthur Barstow; Tobie Langel
Cc: Ben Peters; public-editing-tf; public-webapps@w3.org;
public-indie...@w3.org; public-h...@w3.org
Subject: Re: [editing] Responsive Input Terminology

sounds quite reasonable to me.

12.12.2014, 16:41, Simon Pieters sim...@opera.com:
 On Fri, 12 Dec 2014 13:39:47 +0100, Tobie Langel 
 tobie.lan...@gmail.com
 wrote:
  On Fri, Dec 12, 2014 at 1:00 PM, Arthur Barstow 
 art.bars...@gmail.com
  wrote:
  What is your counter-proposal?
  Heh.

  Fair enough, I guess. :)

  These seem related to what Java calls semantic events [JAVADOC], so 
 I'd
  give that a try to see if it fits the model. If not, would abstract
  events or simply high-level events work? Sorry if these have 
 already
  been discussed and dismissed (haven't had much time to look through 
 the
  archives, tbh).

 How about device-independent events?

 --
 Simon Pieters
 Opera Software

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