Re: [w3c/manifest] Identifier for external interpretation (Issue #1104)

I wanted web app manifests to be useful as standalone resources too (e.g for crawling, remote installation, app stores, all kinds of things), but I'm afraid that ship has long-since sailed.

The parsing algorithm only works if a user agent follows a link from an HTML page, and the parser knows both the manifest URL and the document URL of the page it was linked from. Therefore in practice the user agent doesn't need a `.webmanifest` file extension, `Content-type` HTTP header or a JSON-LD `@context` to know that the file is a manifest. It knows it's a manifest because it was linked to from a web page using a `manifest` link relation. At that point, if it can be parsed as a manifest then it's a manifest.

There's a long history for why this is the case, and at this point I'm afraid I don't think it can be fixed without backwards incompatible changes, especially for Chromium based browsers. Perhaps in a version 2!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1104#issuecomment-1810455959
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1104/1810455959@github.com>