[Json] On characters and code points

[Paul Hoffman <[e-mail]>]

<no hat>

This may be a part of the spec where some people have to hold their noses. The Unicode definition of "character" does not include non-characters, and the code points for some of those non-characters make sense in JSON strings when those strings. Bjoern has pointed out a good one: strings used for test cases of other code. The issue not just unpaired surrogates. Do we *really* want to prohibit:
   { "End of data marker": "\uFFFF" }

Proposal:

Remove the word "character" from the spec except in an explanatory paragraph in Section 2.5 that says:
   All code points, even those that represent non-characters in the Unicode specification [UNICODE], are allowed in JSON strings.

--Paul Hoffman