- From: Nico Williams <nico@cryptonector.com>
- Date: Tue, 26 Nov 2013 18:39:49 -0600
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: JSON WG <json@ietf.org>, www-tag <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
On Wed, Nov 27, 2013 at 01:14:00AM +0100, Bjoern Hoehrmann wrote: > HTTP/1.1 200 OK > Content-Type: application/json > ... > > ABCD... > > There would be at least two specifications that apply here, the HTTP > and the application/json specification. Would you like them to say > that you are on your own, "ABCD..." could mean anything? [...] Absolutely not, and I didn't say that either. The application/json media type absolutely has to be in a UTF, and preferably UTF-8. > I cannot build robust software based on "well, maybe it's EBCDIC? > Have you tried GB 18030? UTF-7 might be worth a try otherwise. Are > you sure this matters at all?" That is not even remotely what I want. Either you misunderstood me or I wasn't specific or clear enough. Either way, I think it should be clear as of my last message (though you might find things there to disagree with). Nico --
Received on Wednesday, 27 November 2013 00:40:12 UTC