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

Re: json-string for HTTP header field parameter values

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 31 Oct 2011 13:47:18 +0100
Message-ID: <4EAE98D6.2090207@gmx.de>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
CC: httpbis Group <ietf-http-wg@w3.org>
On 2011-10-30 14:07, Manger, James H wrote:
 > ...

Here's a list of problems I see with this proposal:

- Scope - the proposed syntax overloads quoted-string, potentially 
changing the interpretation of existing content, thus I don't think we 
*can* do this as part of HTTPbis.

- Adding a different type of quoted-string might make things more 
confusing; for the RFC5987 encoding it's at least easy to understand 
when it's in use.

- the JSON \u format doesn't really use Unicode but UCS-2 code points; 
which means that senders and receivers will need to understand surrogate 
pairs; see also <https://tools.ietf.org/html/rfc5137#section-5.1> for 
context (that proposal adds additional delimiters to avoid the variable 
length issue)

Best regards, Julian
Received on Monday, 31 October 2011 12:48:07 GMT

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