A lot of things happened in AppCache land since this group was revived late last summer.
scope the precise nature of the 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.
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).
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) and during the offline panel at Edgeconf 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.
Note that I’ve archived the minutes of all three meetings in the wiki for future reference.
UPDATE February 15, 2013: As there were no objections the chairs pronounce this group closed. See in you in WebApps WG to build the next version of AppCache.