- From: kael <notifications@github.com>
- Date: Fri, 05 Oct 2018 01:11:05 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 5 October 2018 08:11:27 UTC
Currently a WebApp manifest is discoverable using the HTML `<link>` header: ```html <link rel="manifest"/> ``` I've come across the [Readium Web Publication Manifest](https://github.com/readium/webpub-manifest) which _« is an attempt to standardize a JSON based manifest format »_ for collections discovery, in the context of [WebPublications](https://www.w3.org/TR/wpub/) - noting that currently _« [The precise format of how such a manifest is stored is not considered in this document. ](https://w3c.github.io/dpub-pwp-ucr/#terminology) »_ To make such collections discoverable, Readium proposes the following HTML `<link>` header: ```html <link href="manifest.json" rel="manifest" type="application/webpub+json"> ``` While writing a parser for HTML `<meta>` and `<link>` tags, I'm now wondering how I should handle those cases. Which brings me to asking, shouldn't the MIME type `application/manifest+json` be explicitly added in the HTML `<link>` element to make it clearly distinguishable, unequivocal ? ```html <link type="application/manifest+json" rel="manifest"> ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/721
Received on Friday, 5 October 2018 08:11:27 UTC