Re: [manifest] Define identity of a web app. (#272)

>Either we do think that the concept of "app" is useful, or even might be useful in the future, and we want the "app" metadata to live as a separate resource.

I think a fair expectation is to assume the metadata will grow over time (both standard, as well as proprietary extensions), so planning ahead to keep metadata off the critical path likely pays off. An example of what one is required to do today to cater for iDevices only: https://gist.github.com/tfausak/2222823

>In that case the only sensible solution that I can see is to require that the metadata lives on the same origin, and that we enforce a mimetype.

This is close to what is spec'd:

* Obtaining a manifest (http://w3c.github.io/manifest/#obtaining) requires the manifest to be same-origin with its owner Document.
* MIME type is currently not enforced, but RECOMMENDED (http://w3c.github.io/manifest/#media-type-registration). A MUST will be problematic for people who are unable to configure the web server. For example, GitHub Pages currently does not recognize `application/manifest+json` and does not allow people to add new MIME types. Not sure about shared web hosting providers at large though.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/272#issuecomment-87618067