Re: Call for Consensus: Publish HTML 5.2 FPWD?

2016-07-05 Thread 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 

Can you point to sections on this in the FPWD?



> 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 - 
> - 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 - 
> You can provide a comment or thumbs-up in the issue in the WebPlatformWG repo 
> -
> 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
> - - - Find more at

RE: User Intentions Explainer (was: List of Intentions)

2014-09-22 Thread Richard Schwerdtfeger

Rich Schwerdtfeger

Ben Peters wrote on 09/19/2014 03:55:46 PM:

 From: Ben Peters
 To: Piotr Koszuliński, Frederico
 Cc: Johannes Wilm, public-editing-, Julie Parent, public-indie-, public-webapps
 Date: 09/19/2014 03:56 PM
 Subject: RE: User Intentions Explainer (was: List of Intentions)

 I agree that we can divide this work, but so far I think we should
 do 2 first. Being able to remove browser functionality with a
 simple API is going to be far quicker to implement (in browsers) and
 provides immediate benefit. Solving Intentions will be a longer
 process, but is also important to really enable performance and
 extensible-web scenarios.

 On Tue, Sep 9, 2014 at 4:28 AM, Piotr Koszuliński wrote:
  I'm not sure if I remember correctly, but I believe that after long
  discussions we left the question what should contenteditable=minimal
  unanswered. First the intention events lists should be created, so we
  see what needs to be handled. And this is what Ben Peters is working
  Still we may also take in consideration that there are limited
  available for working on the specs. Therefore the whole work could be
  separated into two *independent* topics:
   1. Intention events + execCommand.
   2. contenteditable=“minimal”
So, you want to modify contenteditable to minimum. What will that do to
existing apps. that are built on it? We have a number of IBM web
applications that use contenteditable as do many other companies. CKSource
(Piotrek is the lead developer) has an open source product called ckeditor
that IBM contributed accessibility support to and so it is now used by many
large enterprises including Oracle.
A migration strategy is needed for existing consumers of contenteditable.

  That's what I was proposing as well - to have the base (which consists
  mainly of fixed selection API and intention events) ready as soon as
  possible, so hopefully browser makers can start implementing it and
then we,
  editor makers, can start using it. This part will already improve the
  current situation a lot, but it's itself pretty hard as we can see.
Then, if
  anyone will be still interested, a specification for default browser's
  actions can be created. It's a huge task and there are a lot of
  controversial topics like the famous delete/backspace behaviour when
  blocks and that's why I would not recommend starting these discussions
  On Tue, Sep 9, 2014 at 12:59 PM, Frederico Knabben
  On Tuesday, 9 September 2014 at 11:13, Frederico Knabben wrote:
  I don’t think that browsers having time/will for it today is a good
  argumentation for not doing it. The specs have a critical and noble
  of serving as reference for the future of the web. We’re talking about
  future after all.
  Still we may also take in consideration that there are limited
  available for working on the specs. Therefore the whole work could be
  separated into two *independent* topics:
   1. Intention events + execCommand.
   2. contenteditable=“minimal”
  “1” should be concluded asap, because it is the foundation for the
  of “2”. It is also compatible with the current
 contenteditable=“true”, so it
  should enable sites/frameworks to fix the current status of things.
I have to agree with Piotrek, 1 is more important to get done first. It is
very important for mobile and we have real problems with device specific
support across devices. We could refine 1 after 2 is attempted.

  “2” is the ideal world. Something that would require much more energy
  get done right. Still in the beginning, there should be an agreement
  what’s in and what’s out. Following that, several specs can get
  each one defining the default behavior we want for each of the
features we
  want “minimal” to have. The first ofc, would be “Selection” (and

  Piotrek Koszuliński
  CKEditor JavaScript Lead Developer
  CKSource -
  Follow CKEditor on: Twitter | Facebook | Google+ | LinkedIn

Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60 minutes

2014-09-03 Thread Richard Schwerdtfeger

regrets for tonight.

Rich Schwerdtfeger

From:   Janina Sajka
Date:   09/03/2014 01:59 PM
Subject:Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60

My probable regrets as well due to a one-time scheduling conflict.

Michael, given that James and Jason are also both unavailable, I leave
it to your discretion whether to cancell today's call.


Janina Sajka writes:
 As before I'm cross-posting this IndieUI agenda As part of IndieUI's
 continuing open invitation continuing our conversation about working
 jointly.  Allow me to invite you to the next Indie-UI teleconference as
 detailed below.  Please feel free to join us on this call, or any
 following call.

 What:  IndieUI Task Force Teleconference
 When:  Wednesday 3 September
 2:00 PMSan Francisco -- U.S. Pacific (Daylight) Time
(PDT: UTC -7)
 4:00 PMAustin -- U.S. Central (Daylight) Time   (CDT:
UTC -5)
 5:00 PMBoston -- U.S. Eastern (Daylight) Time
(EDT: UTC -4)
10:00 PMLondon -- British (Summer) Time
(BST: UTC +1)
11:00 PMParis -- Central European Time  (CET:
UTC +2)
 5:00 AMBeijing -- China Standard Time
(Thursday, 4 September CST: UTC +8)
 6:00 AMTokyo -- Japan Standard Time
(Thursday, 4 September JST: UTC +9)
 7:00 AMMelbourne -- Australian Eastern (Standard)
Time  (Thursday 4 September AEST: UTC +10)
 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:

 ** Preliminary Agenda for IndieUI Task Force Teleconference 3 September

 Meeting: IndieUI Task Force Teleconference
 Chair: Michael_Cooper
 agenda+ preview agenda with items from two minutes
 agenda+ Editor's Report
 agenda+Checkin with Web Apps' Editing TF [See below]
 agenda+Testing Conversation; Polyfills
 agenda+Requirements  Use Cases Progress
 agenda+ TPAC Planning
 agenda+ User Context Issues  Actions
 agenda+ Events Issues  Actions
 agenda+ Other Business
 agenda+Be Done

 Resource: IndieUI Minutes

 Resource: Web Apps Editing TF

 Resource: For Reference
 Home Page:
 Email Archive:

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

 Alternatively, bypass the Zakim prompts and SIP directly into our

 Instructions for connecting using SIP:
 Place for users to contribute additional VoIP tips.

 IRC: server:, 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
 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,
 The port number is 6665 (Note this is not the normal default) and
 The channel is #indie-ui.

 * Some helpful Scribing and Participation Tips

 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:

 - For Zakim, the IRC interface to the bridge manager, that will
 maintain speaker and agenda queues:

 - For a Web gateway to IRC you can use if your network administrators
 forbid IRC, see:

 - For more on W3C use of IRC see: