W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2013

Re: FileSystem API

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 19 Aug 2013 16:59:30 -0700
Message-ID: <CA+c2ei8vN2pnMZmnUPZ861LUNBa_97L+jaRK_7o+wg9+7YD6Ag@mail.gmail.com>
To: Eric U <ericu@google.com>
Cc: Arun Ranganathan <arun@mozilla.com>, Web Applications Working Group WG <public-webapps@w3.org>, Arthur Barstow <art.barstow@nokia.com>
On Mon, Aug 19, 2013 at 4:44 PM, Eric U <ericu@google.com> wrote:
> OK, I just finished making my way through the public-script-coord
> thread [I'm not on that list, but someone pointed me to it].  I have
> no official objections to you editing a spec based on Jonas's
> proposal, but I do have a couple of questions:
>
> 1) Why is this on public-script-coord instead of public-webapps?

I started on public-webapps, but once discussion died out here I also
wanted to get input from TC39. Generally we're trying to improve
coordination between W3C and TC39 so public-script-coord was set up as
an attempt to help that. I'm hoping that we'll run all major API
designs past them going forward. Not just file-related things, but any
API that we design here and in other WGs.

There were so far many more changes based on discussions on this list
than discussions on public-script-coord.

However public-webapps is still the main list for discussing this API.
If any major changes are coming out of the discussion with TC39 the
intent is to bring those proposed changes back here.

> 2) Is any vendor other than Mozilla actually interested in this
> proposal?  When it was brought up on public-webapps, and at the
> WebApps F2F, it dropped with a resounding thud.

I'll let others speak up, but yes, I've heard positive signals from
other vendors. If we hadn't I wouldn't have let the discussions go as
far as they have.

/ Jonas

> On Mon, Aug 19, 2013 at 3:11 PM, Arun Ranganathan <arun@mozilla.com> wrote:
>> Greetings Eric and WG,
>>
>> The Chair and I were discussing setting up repositories for the specifications discussed here (http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0307.html), notably the FileSystem API and File API v2.  Before creating a repository to edit the FileSystem API, we thought we'd check with you about the first proposal, which Chrome implements, and get the Google perspective.
>>
>> You've edited the first FileSystem API proposal, which currently lives here (http://www.w3.org/TR/file-system-api/).  Can I create a repository and edit the other proposal for FileSystem API, which currently exists as an email thread (http://lists.w3.org/Archives/Public/public-script-coord/2013JulSep/0379.html) ?
>>
>> Just checking to see if there are any objections or concerns that would stop a draft or future WG activity.  Of course, technical nits should be heard as well, and can proceed concurrently with a draft :)
>>
>> -- A*
>
Received on Tuesday, 20 August 2013 00:00:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:12 UTC