Type correction Re: New editors for Clipboard API spec

[Chaals McCathie Nevile]

On Sun, 31 Jul 2016 02:16:17 +0200, Chaals McCathie Nevile  
 wrote:



Hi,

I'm happy to announce


Grisha *Lyukshin*. Sorry Grisha

and Gary Kačmarčik as the new editors of the Clipboard API  
specification, and to thank them for

volunteering,


cheers


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

Fwd: Minutes / results of editing meeting

[Chaals McCathie Nevile]

FYI

--- Forwarded message ---
From: "Chaals McCathie Nevile" 
To: "public-editing...@w3.org" 
Cc:
Subject: Minutes / results of meeting
Date: Sat, 30 Jul 2016 23:51:18 +0200

Hi folks,

Detailed minutes are at http://www.w3.org/2016/07/29-editing-minutes.html

Gary produced a summary of what we said and decided at
https://docs.google.com/document/d/1XxIEF0So-kMF5mcJ03Yj0zsYMFRHEgXw1fV1K5FOwuQ

And Grisha filed issues, and what we decided on them, in the issue tracker
https://github.com/w3c/editing

Thanks to Ojan and Google for hosting.

cheers


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

New editors for Clipboard API spec

[Chaals McCathie Nevile]

Hi,

I'm happy to announce Grisha Lyushkin and Gary Kačmarčik as the new editors
of the Clipboard API specification, and to thank them for volunteering, as
well as Hallvord for the work he put into it until now.

cheers

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

Re: Draft recharter proposal

[Chaals McCathie Nevile]

On Fri, 29 Jul 2016 18:29:44 +0200, Olli Pettay  wrote:


On 07/29/2016 06:13 PM, Chaals McCathie Nevile wrote:

Hi folks,

our charter expires at the end of September. I've produced a draft  
version of a new charter, for people to comment on:

http://w3c.github.io/charter-html/group-charter.html

Feel free to raise comments as issues:  
https://github.com/w3c/charter-html/issues/new


As per the change section:

New deliverables:
Microdata

Removed as deliverables:
Streams; URL; XHR1

Marked as deliverables to be taken up if incubation suggests likely  
success:
Background Synchronisation; Filesystem API; FindText API; HTML Import;  
Input Methods; Packaging; Quota API



Given what has been happening with directory upload stuff recently,  
Filesystem stuff is a bit controversial.
(Gecko and Edge implementing https://wicg.github.io/entries-api/, or  
something quite similar. The draft doesn't quite follow browsers.

  Entries API is a subset of what Blink has been shipping.)
But I think some way better API than the old Chrome-only API should be  
implemented for Filesystem in general, and at that point also

better stuff for directory upload, *and* for directory download.
I'd consider the callback based, awkward to use Blink API a legacy thing.


Filesystem is a bit controversial - there have been a number of proposals  
over most of a decade now. The idea is that if we have one that matches  
something browsers do and want to continue with, and we maintain it, that  
would be a helpful thing to do.


I thought it is pretty much agreed that HTML Import is deprecated, or  
something to not to do now.


At any rate, I believe there is not enough apparent interest to rate it as  
a definite work item.


Both of those are in a section of things the group *may* do, if there is  
reason to expect success, but I think that could be made much clearer in  
the document.


Microdata has very wide ongoing usage, and it would be helpful to have  
something clearer than the current W3C Note - which includes things  
that don't
work - for people to refer to. So I'm proposing to do the editing,  
along with Dan Brickley from Google, and to work roughly on the basis  
we use in
HTML of specifying what actually works, rather than adding in what we  
would like.



So the only implementation of HTML Microdata API in browsers was removed  
recently
https://bugzilla.mozilla.org/show_bug.cgi?id=909633 because exposing the  
API caused web pages to break.


Yes, removing the API from the spec is one of the things we expect to do.  
Browsers generally do nothing with microdata as far as I know, which is  
fine. It's not particularly directed at them anyway. It's used by search  
engines, and put into massive numbers of web sites for that purpose.


cheers, and thanks for the comments.

Chaals

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