> On Jul 11, 2020, at 00:50, Anders Rundgren <[email protected]>
> wrote:
>> On 2020-07-10 22:21, Mike Jones wrote:
>> There are things I would have commented on in JCS if I'd seen intermediate
>> drafts before it became an RFC. (For instance, I would have asked for
>> explicit serialization instructions for the one ASCII control character not
>> in the range 0x00-0x1F - 0x7F (DEL).)
>
> Serialization of JSON tokens follows ECMAScript to 100% so the string
> serialization algorithm is essentially just a copy.
Neither IETF nor ECMA variants of JSON actually define required escaping for
the high control points (0x7F-0x9F). So this is likely fairly consistent, if
arguably bad behavior.
In the node REPL (which is the same JSON code as Chrome):
> console.log(JSON.stringify({"a":"\u007f"}))
{"a":""}
Printing the code points, that is an inline DEL character in the JSON
stringified output.
-DW_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
