On 2/19/14 2:15 PM, LeVan,Ralph wrote:
>> I don't think there's any standard about "+json".
> There seems to be application/ld+json to get JSONLD responses.
Okay, you can register any MIME type you want that uses legal
characters. So they registered "application/ld+json" that's fine.
You can certainly register "application/sru+json" if you want too.
But, there is a standard requiring that any content type ending in
"+xml" be valid XML -- so allowing consumers to assume that any content
type ending in "+xml" is XML.
As far as I know there is no similar standard for "+json".
You certainly still can register a content type "application/sru+json"
if you want. And it seems perfectly reasonable to use "+json" for things
that are json. It is perhaps an emerging information convention, on the
basis of being parallel to "+xml".
But there's no standard requiring that all content types representing
json end in "+json"; or that all content types ending in "+json" be json
(although i suspect nobody's going to do that anyway); or that there is
any neccesary relation between "something" and "something+json".
Regardless, if you want "application/sru+json" you have to register it,
the previous existence of either "application/sru" or
"application/sru+xml" doesn't get you anything.