- From: kael <notifications@github.com>
- Date: Fri, 05 Oct 2018 01:52:47 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 5 October 2018 08:53:09 UTC
Indeed, I've missed the `<link rel="publication">` proposal, but it's still unclear. Regarding the use of a specific MIME type for webapps manifests, it'd make sense as: - it'd be aligned with the way web servers can [optionally add a `Link`header](https://w3c.github.io/manifest/#media-type-registration) with a type `application/manifest+json` ; - it'd let free the `<link rel='manifest'>` as generic manifests class, similarly to `<link rel="alternate" type="application/[atom|rdf|rss]+xml">`, and would hence make it unequivocal for webapps ; - but it'd partially break compatibility. Seems to me there could be some clarification between the groups about the definition and use of `<link rel="manifest">`. Anyway, that was my 2 cents. Regarding parsing, for now I'll filter `<link rel='manifest'>` based on the lack of the `type` attribute to distinguish webapps manifests from potential others. -- 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#issuecomment-427292949
Received on Friday, 5 October 2018 08:53:09 UTC