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

Re: Standards for Web applications on mobile devices: August 2011 updates

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Sat, 3 Sep 2011 22:47:25 +0200
To: Dominique Hazael-Massieux <dom@w3.org>
Cc: public-webapps@w3.org
Message-ID: <B0272117A6E54051920AF228E4804376@gmail.com>
 Hi Dom,  

Thank you for continuing to keep the document up to date. This document is very helpful.  

I have request: can you please ungroup Widgets and HTML's ApplicationCache? They are conceptually different things and have different use cases.

Widgets are a way to zip up a bunch of HTML, CSS, and JS files that constitute an "installable application" (or some such). That is, something someone might want to distribute to keep.  

ApplicationCache is cache control thing: it does not "package" a Web Application; just makes some resources available from the cache (potentially for off-line use). The end user has not control over it and the author can shut it off at any point. The author cannot take the application away "packaged" in some format.  

IMO, keeping them together will lead to confusion. The use cases are different: a widget can embed content that uses ApplicationCache, as well as load in proprietary APIs (e.g., WAC). It can be used for defining other classes of applications and formats (e.g., Opera Extensions). So, it's not really logical, IMO, to lump them together.

If I've convinced you, when you split Widgets and ApplicationCache from the packaging section, can you please add View Mode Media Feature, Widget URI, and the Widget Interface, and Widget updates to the list (as they are a standard part of Widgets and implemented across some user agents… see implementation reports where available).  

Many thanks!  

Marcos  

--  
Marcos Caceres
http://datadriven.com.au

On Friday, 2 September 2011 at 15:56, Dominique Hazael-Massieux wrote:

> Hi all,
>  
> I've just released a new version of “Standards for Web Applications on
> Mobile” that takes into account the latest changes in the open Web
> platform:
> http://www.w3.org/2011/08/mobile-web-app-state.html
>  
> Updates since May 2011 [1] includes:  
> * Addition of a new section on technologies useful for device adaptation
> * Addition of the new W3C Community Groups as a way to start
> standardization work in W3C
> * Four new APIs from the Web Performance Working Group: Performance
> Timeline, User Timing, Efficient Script Yielding and Timing control for
> script-based animations
> * The first editor draft of Web Real-Time Communication
> * A number of other documents made progress on the Recommendation track
> (WOFF, Contacts API, DeviceOrientation Event, Network Information API,
> the family of Widgets specifications)
> * Addition of the proposed work on model-based user interfaces
> * Updates based on the adoption of the new Device APIs Working Group
> charter
>  
> That document is extracted from the equivalent page in the W3C wiki
> where contributions from others are welcomed:
> http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile
>  
> I'm planning to run another update of that document end of November.
> Feedback is as always very welcomed.
>  
> Dom
>  
> 1.
> http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0743.html
Received on Saturday, 3 September 2011 23:55:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT