W3C home > Mailing lists > Public > public-webappsec@w3.org > January 2017

Allow for multiple scopes (w3c/manifest #449)

From: Rob Dolin <robdolin@microsoft.com>
Date: Wed, 4 Jan 2017 00:50:32 +0000
To: "public-webappsec@w3.org" <public-webappsec@w3.org>
CC: Marcos Caceres <mcaceres@mozilla.com>, "kenneth.r.christiansen@intel.com" <kenneth.r.christiansen@intel.com>
Message-ID: <BN3PR03MB144558C946DC6320B41020AADE610@BN3PR03MB1445.namprd03.prod.outlook.com>
Dear Web App Security WG members,
I'm writing on behalf of a number of W3C members working on the W3C Web App Manifest spec. (http://www.w3.org/TR/appmanifest/)
We have two use cases where web app developers want to indicate a web app includes multiple domains.

  *   In one case, a web app (scope:Example.com) might have a CDN (scope:ExampleCDN.com), personal data (scope:MyExample.com), etc. that is served from a second domain.
  *   In another case, a web app (scope:Chat.Example.com) might have peer subdomains that are in-scope (scope:Music.Example.com and scope:Video.Example.com) but might also have peer domains that are out-of-scope (scope:Events..Example.com)
We are considering a proposal (#449<https://github.com/w3c/manifest/issues/449>) where the W3C Web App Manifest file (a JSON file residing on the primary domain) be able to indicate other (HTTPS-only) domains that could be rendered within the context of the web app rather than being rendered in the context of web browser chrome.
We would appreciate any questions or suggestions you have as we consider this proposal.
Thanks very much--
--Rob
Received on Wednesday, 4 January 2017 00:55:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:22 UTC