News for hackers. Stuff that matters.
Re:REST is over by icebraining on Sunday February 26, 2012 @06:03AM (#3635342)
Having to define a Content-Type like "application/vnd.my-service+json" and submit it to a standards body and then approved like described in Amundsen's book is hardly practical or desirable.

Yeah, but that's why I chose media types in the Vendor Tree (application/vnd.) as examples - as far as I can tell, they do not need to be registered with IANA. And I'm sure they don't have to be reviewed, even if you do register them:

    public exposure and review of media types to be 
    registered in the vendor tree is not required
For example, Github uses application/vnd.github and I don't think they've ever registered that.

The way I see it, defining types in a JSON format to help with type-marshalling until that format is successful and thus merits standardization is far more effective at promoting innovation than starting with submission to a standards body so that everyone can comment on (i.e. bikeshed) about a format until it gains acceptance.

Sure, but it doesn't have to be a standard to have its own mimetype. Just put it after your company's name (application/vnd.COMPANY.FORMAT) and forget about registration, imho.

Sure, a standard would be better, but this is still way better than having to use an hack like that.

Re:REST is over by malandrew on Monday February 27, 2012 @08:20PM (#3641381)
Cool beans. I'm still learning more about custom media types at the moment and this is useful info. Thanks.