I observe that both the FFOS manifest 
(https://developer.mozilla.org/en-US/Apps/Developing/Manifest?redirectlocale=en-US&redirectslug=Web%2FApps%2FManifest#csp)
 and the Chrome Extension apps manifest 
(http://developer.chrome.com/extensions/manifest.html) include CSP definition 
possibilities.

I say +1 to Wonsuk's use cases.

Claes

> -----Original Message-----
> From: Wonsuk Lee [mailto:wonsuk11....@samsung.com]
> Sent: den 1 november 2013 07:25
> To: 'Marcos Caceres'
> Cc: 'public-webapps'; public-sysa...@w3.org
> Subject: RE: [coord] Is there still a need for WebApps + SysApps
> meeting at TPAC?
> 
> Hi. Marcos.
> 
> > -----Original Message-----
> > From: Marcos Caceres [mailto:w...@marcosc.com]
> > Sent: Friday, November 01, 2013 12:24 AM
> > To: Nilsson, Claes1
> > Cc: Arthur Barstow; public-webapps; public-sysa...@w3.org
> > Subject: Re: [coord] Is there still a need for WebApps + SysApps
> > meeting at TPAC?
> >
> >
> >
> > On Thursday, October 31, 2013 at 3:04 PM, Nilsson, Claes1 wrote:
> >
> > > I want to say that we are interested in implementing the JSON
> > > manifest
> > and also to discuss additions to the manifest. Content security
> > policies have already been mentioned and we are looking at something
> > similar to
> > http://developer.chrome.com/extensions/contentSecurityPolicy.html,
> > which allows inclusion of content security policies to support secure
> > hosted apps by defining schemes (https:) that are allowed to use for
> whitelisting secure origins from which scripts should be accepted.
> >
> > This is orthogonal to the manifest, as web apps can already do this.
> > Adding this to the manifest would only be sugar to allow developers
> to
> > tighten the CSP.
> > > I would also like to better understand what a meta tag solution
> > > would
> > mean.
> >
> >
> > See:
> >
> https://developer.apple.com/library/safari/documentation/AppleApplicat
> > ions /Reference/SafariHTMLRef/Articles/MetaTags.html
> >
> > And:
> > https://developers.google.com/chrome/mobile/docs/installtohomescreen
> >
> > So, some standardized thing of the above (without the proprietary
> > prefixes, of course).
> >
> > > However, as the manifest specification editor Marcos unfortunately
> > > is
> > not able to participate in TPAC I am not sure on the most efficient
> > way to discuss the manifest, a joint SysApps-WebApps session with
> > Marcos calling in or a mailing list discussion.
> >
> > I’m happy to dial in, but would like to know specially what people
> > want to discuss about it.
> >
> > > My main point is to stress our interest in the manifest
> > > specification
> > and additions to it.
> > >
> >
> > I think it’s more important to understand the use cases, and then we
> > can evaluate if the manifest is the appropriate place to address
> those.
> >
> 
> I think one of big benefit with manifest format is we can use hyperlink
> for that. User can install a web app with manifest format, no need to
> visit a site.  So manifest can provide more smooth way of installation
> to user. They can install apps via links in blogs, twitter, facebook,
> extra. What do you think?
> 
> Kr, Wonsuk.
> 

Reply via email to