- From: Marcos Caceres <notifications@github.com>
- Date: Tue, 13 Jan 2015 22:04:37 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/272/69873167@github.com>
On January 13, 2015 at 11:11:45 PM, Janusz Majnert (notifications@github.com) wrote: > I just don't think that the manifest spec in its current form (with all the requirements > and restrictions documented in this repo) is fit for defining identity. Probably. It's why I left it out in the first place... however, it doesn't hurt to throw around a bunch of ideas to see what sticks. Clearly, it's possible to isolate and identify apps in OSs (even if problematic, as you pointed out). > Please consider the requirement for multiple apps per manifest or the fact that `start_url` > is not a mandatory member of the manifest. To be clear, it doesn't matter that there is no mandatory start_url field, as the start URL is always derived from either the manifest or at the time when the user adds the app to the home screen. > It seems that the manifest is just a collection > of additional info about app(s). Correct. > > Counter-counter-proposal: identity is managed by OS > > So: define identity in the spec but leave its interpretation entirely to the user's OS+UA > combination? How interoperable will that be? "How interoperable will it NOT be?" is the interesting question. I'll have a shot a scaling this identity thing back. Then we can put it out for wider discussion. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/272#issuecomment-69873167
Received on Wednesday, 14 January 2015 06:05:04 UTC