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

[Tim Bray <[e-mail]>]

Easily solved: “In all instances when JSON is transmitted over a network,
it MUST be encoded in UTF-8; a charset argument on the Content-type MAY be
provided, but its value MUST be utf-8.”

 -T


On Mon, Feb 18, 2013 at 4:26 PM, Bjoern Hoehrmann <[e-mail]> wrote:

> * Joe Hildebrand (jhildebr) wrote:
> >As a start, we know there are a couple of things we'd like to fix about
> >RFC 4627:
> >
> >- move to standards track
> >- an ABNF indentation typo in section 2.2
> >- change SHOULD to MUST for the uniqueness of names in an object
> >
> >A *very* important goal would be to minimize change, and to ensure strict
> >backward-compatibility.
>
> 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).
> --
> 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/
> _______________________________________________
> json mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/json
>