Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

["HANSEN, TONY L" <[e-mail]>]

I would still like to see Julian’s small table on differentiating between UTF variants added as an appendix.

	Tony Hansen

On 3/23/17, 10:40 AM, "json on behalf of Matthew A. Miller" <[e-mail] on behalf of [e-mail]> wrote:

    Hello JSONbis,
    
    It looks like we have consensus for the following text for all of
    Section 8.1:
    
    """
    JSON text MUST be encoded in UTF-8, UTF-16, or UTF-32 Section 3 of
    [UNICODE].  The default encoding is UTF-8, and JSON texts that are
    encoded in UTF-8 are interoperable in the sense that they will be
    read successfully by the maximum number of implementations; there are
    many implementations that cannot successfully read texts encoded in
    UTF-16 or UTF-32. Text encoded in character encodings other than UTF-8,
    UTF-16, or UTF-32 cannot be used with the media type "application/json".
    
    Implementations MUST NOT add a byte order mark (U+FEFF) to the
    beginning of a JSON text.  In the interests of interoperability,
    implementations that parse JSON texts MAY ignore the presence of a
    byte order mark rather than treating it as an error.
    
    Recipients that wish to support Unicode encodings other than UTF-8
    can do this using a detection mechanism that is based on the fact
    that the first character will always have a Unicode code point
    greater than 0 and less than 128, thus the UTF-16/32 variants can
    be detected by inspecting the first octets for nulls.
    """
    
    Please speak now if you have any objections.
    
    Thank you all,
    
    --
    - m&m
    
    Matthew A. Miller
    JSONbis Chair