Re: [Json] Allow any JSON value at the top level

["Markus Lanthaler" <[e-mail]>]

On Sent: Monday, June 10, 2013 9:33 PM, Jacob Davies wrote:
> Lots of people do this, in my experience, including me pretty often.

I was hoping for something more concrete. Something like "Facebook's,
Google's and Bing's APIs are doing that. Here are the links."


> The big problem with the current requirement is that arbitrary
> sub-values of a JSON value cannot be sent as application/json.

Of course not. How would you path a JSON object or array by just sending a
number? How should that number be interpreted?


> So for
> instance, if you wish to implement a form of PATCH on a JSON document,
> you must demand that clients wrap their new value in a JSON object or
> array instead of sending raw primitive values.

Are you really talking about PATCH? Looks more like a PUT to me.. PATCH
requires a different media type anyway.


> If you implement a
> service returning an inherently primitive value (e.g. a plain-text
> document server) you must wrap your responses in a JSON object or
> array even though there is nothing else that could reasonably be
> added.

... or you just return text/plain. That would even enable browsers to render
the responses.


Cheers,
Markus


--
Markus Lanthaler
@markuslanthaler