- From: Doug Schepers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2015 17:42:14 +0000
- To: public-annotation@w3.org
> :-1: to multiple media types. I wasn't proposing multiple media types, I was proposing a single media type that isn't `application/ld+json`. > All of the pros listed are possible with a profile, and we can have an annotation > file type associated with the profile (Verified with IETF already, following on from TPAC). > > The proposals miss the actual current proposal of using a profile: the media type > would be application/ld+json;profile="http://www.w3.org/ns/anno.jsonld" Interesting. That's pretty clumsy, but maybe it will work. How well are MIME Type profiles understood by the average developer (this is the first I've heard of them)? What's the rationale to use a profile rather than a dedicated MIME type? > Proposal 3 is an illegal media type, as there MUST NOT be more than one + according to the RFC. Okay, thanks. That suggestion was by Manu in a hallway conversation, but I should have researched it better. -- GitHub Notification of comment by shepazu Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/125#issuecomment-165188971 using your GitHub account
Received on Wednesday, 16 December 2015 17:42:20 UTC