- From: Marcos Caceres <w3c@marcosc.com>
- Date: Fri, 4 Oct 2013 16:54:22 +0200
- To: Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com>
- Cc: Kostiainen, Anssi <anssi.kostiainen@intel.com>, Dave Raggett <dsr@w3.org>, "public-sysapps@w3.org" <public-sysapps@w3.org>, Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>, Isberg, Anders <Anders.Isberg@sonymobile.com>
On Friday, October 4, 2013 at 1:19 PM, Nilsson, Claes1 wrote: > [Claes]: I am not sure that I interpret Marcos correctly, but it seems as you argue that "hosted web sysapps" and webpages running in the normal browser context are the same. Yes. > However, I think that what Ansi says is an argument for "hosted web sysapps". So installing a manifest on the device and having the web application content on servers instead of on the device in an installed package has several advantages. For example, users will always get the latest version of an application without having to be bothered with application updates, Furthermore, Dave just referred to the SysApps charter in another mail and stated, "SysApps is responsible for aspects specific to the needs for system applications, i.e. security contexts other than the regular browser context". So SysApps should define standards, in addition to what we already have, that make it possible to provide more sensitive APIs to system web applications than is possible in a browser context. Our view is that this also includes web system applications for which the content resides on web servers. As I said in previous emails, I see value in standardizing APIs that are remarkably better than what is available on any one of our platform. -- Marcos Caceres
Received on Friday, 4 October 2013 14:54:53 UTC