Re: Call for Consensus: Publish HTML 5.2 FPWD?
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 >
RE: User Intentions Explainer (was: List of Intentions)
Rich Schwerdtfeger Ben Peters ben.pet...@microsoft.com wrote on 09/19/2014 03:55:46 PM: From: Ben Peters ben.pet...@microsoft.com To: Piotr Koszuliński p.koszulin...@cksource.com, Frederico Knabben f.knab...@cksource.com Cc: Johannes Wilm johan...@fiduswriter.org, public-editing- t...@w3.org public-editing...@w3.org, Julie Parent jpar...@gmail.com, public-indie...@w3.org public-indie- u...@w3.org, public-webapps public-webapps@w3.org 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 p.koszulin...@cksource.com wrote: I'm not sure if I remember correctly, but I believe that after long discussions we left the question what should contenteditable=minimal be? unanswered. First the intention events lists should be created, so we can see what needs to be handled. And this is what Ben Peters is working on. Still we may also take in consideration that there are limited resources 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 merging blocks and that's why I would not recommend starting these discussions right now. On Tue, Sep 9, 2014 at 12:59 PM, Frederico Knabben f.knab...@cksource.com wrote: 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 scope, of serving as reference for the future of the web. We’re talking about the future after all. Still we may also take in consideration that there are limited resources 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 success 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 to get done right. Still in the beginning, there should be an agreement on what’s in and what’s out. Following that, several specs can get started, 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 “Focus”!). Rich -- Piotrek Koszuliński CKEditor JavaScript Lead Developer -- CKSource - http://cksource.com -- Follow CKEditor on: Twitter | Facebook | Google+ | LinkedIn
Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60 minutes
regrets for tonight. Rich Schwerdtfeger From: Janina Sajka jan...@rednote.net To: public-indie...@w3.org Cc: public-editing...@w3.org public-editing...@w3.org, public-webapps@w3.org public-webapps@w3.org Date: 09/03/2014 01:59 PM Subject:Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60 minutes 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 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: http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI +Teleconferenceiso=20140903T1700p1=43ah=1 ** Preliminary Agenda for IndieUI Task Force Teleconference 3 September 2014 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 http://www.w3.org/2014/11/TPAC/ agenda+ 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: IndieUI Minutes http://www.w3.org/2014/08/20-indie-ui-minutes.html Resource: Web Apps Editing TF Explainer: 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: