Re: [Json] Encoding Schemes

[Paul Hoffman <[e-mail]>]

<no hat>

On Jun 18, 2013, at 12:20 PM, Carsten Bormann <[e-mail]> wrote:

> JSON the interchange format, which specifies a sequence of characters, certainly can be encoded in any character encoding scheme that is able to represent the characters that are needed in a specific case.

...as long as the receiver can determine the encoding scheme. Otherwise, there is no chance for meaningful interop.

> JSON the media type (application/json) is specifically limited to UTF-8 (and theoretically the two or possibly four other character encoding schemes listed in RFC 4627; the RFC isn't quite consistent here).

Can you point to the text in the draft that supports that statement? I see the opposite:
   Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32

     JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON
     is written in UTF-8, JSON is 8bit compatible.  When JSON is
     written in UTF-16 or UTF-32, the binary content-transfer-encoding
     must be used.

> There is no way to use another encoding in that media type as there is no charset parameter in the media type.
> (This is intentional and certainly is not a candidate for change.)

It would certainly be my preference to not add a charset parameter in the -bis document; that would seem like a major change.

--Paul Hoffman