W3C home > Mailing lists > Public > public-fixing-appcache@w3.org > February 2013

Re: Moving further spec development to WebApps and closing the CG.

From: Tobie Langel <tobie@fb.com>
Date: Mon, 11 Feb 2013 15:03:40 +0000
To: "public-fixing-appcache@w3.org" <public-fixing-appcache@w3.org>
Message-ID: <F9981AFB970564408FEB7DFCF62D44084711E9B2@PRN-MBX01-4.TheFacebook.com>
And here's the mailing-list friendly version:

---

Hi,

A lot of things happened in AppCache land since this group was revived
late last summer.

The meetings organized in London at FT Labs ([minutes][1]) and at
Mozilla's HA in Mountain View ([minutes][2]) helped with two things:

1. scope the precise nature of problem with the current AppCache spec. It
turned out that this had much more to do with serious API flaws (mainly,
the conflation of routing and caching APIs) than unclear or unmet use
cases and requirements.

2. get consensus among browser vendors that this was a problem worth
solving.

In November 2012, during TPAC, the WebApps WG agreed to take on authoring
of a new version of the spec ([minutes][3]).

Since then, Mozilla and Google have been actively working on two different
propositions which they started socializing during an informal meeting
last week in Google's London office ([minutes][4]) and during the [offline
panel][5] at [Edgeconf][6] this saturday. Unfortunately, neither
proposition is public at the moment, but I'm hopeful this will be
addressed shortly.

Formalizing the case studies and use cases collected through our previous
meetings by publishing a document seems rather moot now that we've
identified the problem as being related to API design. Also, it would
require work no one seems to have the bandwidth for at the moment.

This CG not being chartered to work on the actual API (that's for the
WebApps WG to do), CG participants who wish to have a say in how the API
is designed should do so within the WebApps WG directly. The API changes
considered are such that use cases fulfilled will probably be much broader
than what we're currently looking at. Because of that, I also feel they'd
be best discussed within WebApps.

Keeping this CG alive seems artificial at this point and I suggest we kill
it.

Best,

--tobie

Note that I've [archived the minutes][7] of all three meetings in the wiki
for future reference.

---
[1]: https://etherpad.mozilla.org/appcache-london
[2]: https://etherpad.mozilla.org/appcache
[3]: http://www.w3.org/2012/10/30-webapps-minutes.html#item06
[4]: 
https://docs.google.com/document/d/15xIoWnXT3Vpo-QZv_vspAj2bf55nhwRqXahPh0C
X3Z8/edit
[5]: http://www.youtube.com/watch?v=Oic22dQMRXQ
[6]: http://edgeconf.com/
[7]: http://www.w3.org/community/fixing-appcache/wiki/Main_Page
Received on Monday, 11 February 2013 15:04:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:41:26 UTC