[Json] A possible summary of the discussion so far on code points and characters

[Paul Hoffman <[e-mail]>]

No hat at all, just trying to get some focus on the current facts before trying to reach conclusions.

1) Some people have read the following statement from the RFC to mean "only Unicode characters are allowed in strings":
   A string is a sequence of zero or more Unicode characters [UNICODE].

2) The ABNF is more liberal about what can be in a string than that statement:
      char = unescaped /
          escape ( ...
              %x75 4HEXDIG )  ; uXXXX                U+XXXX
      ...
      unescaped = %x20-21 / %x23-5B / %x5D-10FFFF

3) Some JSON parsers enforce (1), rejecting JSON texts that have strings that have some unallowed code points.

4) Some JSON parsers accept strings with all code points.

5) The definition of "Unicode character" has been surprising to some people on this list, and thus might be surprising to some developers and users of JSON.

6) Some people on the list consider some code points that are Unicode non-characters to be more objectionable than other code points.

--Paul Hoffman