Re: [Json] [apps-discuss] JSON mailing list and BoF

[Bjoern Hoehrmann <[e-mail]>]

* Joe Hildebrand (jhildebr) wrote:
>On 2/18/13 5:26 PM, "Bjoern Hoehrmann" <[e-mail]> wrote:
>>A Working Group will also likely have to look at revising the rules to
>>detect the character encoding in application/json resources (there is a
>>lack of consensus whether to auto-detect UTF-32 and whether to honour a
>>Unicode signature, whether to support UTF-32 when it is detected, and so
>>on, partly due to how people load JSON resources; a generic "load text"
>>API for instance might detect and remove a Unicode signature before the
>>data is passed to a JSON parser; this used to be true for XMLHttpRequest
>>for instance, I haven't checked the current situation there though).
>
>(individual)
>
>Yeah, that probably needs to be dealt with.  If 4627 had been written as
>"JSON SHALL always be encoded as UTF-8 when transmitted or stored", then
>this would not be a problem.

A practical problem is that some people include a Unicode Signature in
their JSON documents, and their code works in some environments either
by accident or because someone made a deliberate choice to support the
Unicode Signature even though the RFC does not permit one, but it would
break in more strict implementations. I would expect the Working Group
to investigate whether the "UTF-8 BOM" should be allowed and how JSON
documents with one should be handled, even if it decides to limit JSON
to UTF-8.
-- 
Björn Höhrmann · mailto:[e-mail] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: [phone] · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/