W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

RE: json-string for HTTP header field parameter values

From: Thomson, Martin <Martin.Thomson@commscope.com>
Date: Mon, 31 Oct 2011 13:55:48 +0800
To: httpbis Group <ietf-http-wg@w3.org>
Message-ID: <27AFD040F6F8AA4193E0614E2E3AF9C910D7C1EFC9@SISPE7MB1.commscope.com>
On 2011-10-31 at 15:33:35, David Morris wrote:
> 
> Using the JSON string syntax w/o designing in support for JSON objects 
> doesn't make sense to me. I suspect it would be quite confusing and 
> many would assume that JSON objects were supported.

I wouldn't have made that conclusion.  You wouldn't even have to mention JSON in any specification, just to add the syntactical constructs so that the string syntax becomes identical.

But Mark said it best.  The encoding in 5987 is sufficient.  I tend to think that it loses a lot in the human-readable area, which is still important to me, but it is hard to justify adding another mechanism where an adequate one already exists.

Sadly, the aesthetic concern only has any sway once all the other concerns are addressed.

--Martin
Received on Monday, 31 October 2011 05:56:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:49 GMT