|
RFC 7454 conformance
John Cowan
(18 Jan 2020 21:58 UTC)
|
|
Re: RFC 7454 conformance
Amirouche Boubekki
(19 Jan 2020 03:20 UTC)
|
|
Re: RFC 7454 conformance
John Cowan
(19 Jan 2020 03:21 UTC)
|
|
Re: RFC 7454 conformance
Amirouche Boubekki
(21 Jan 2020 10:50 UTC)
|
|
Re: RFC 7454 conformance
John Cowan
(21 Jan 2020 17:08 UTC)
|
|
Re: RFC 7454 conformance Amirouche Boubekki (21 Jan 2020 17:14 UTC)
|
|
Re: RFC 7464 conformance
Lassi Kortela
(21 Jan 2020 22:42 UTC)
|
|
Re: RFC 7464 conformance
John Cowan
(21 Jan 2020 23:02 UTC)
|
Re: RFC 7454 conformance Amirouche Boubekki 21 Jan 2020 17:14 UTC
Le mar. 21 janv. 2020 à 18:07, John Cowan <xxxxxx@ccil.org> a écrit : > > No, it doesn't. In JSON Sequence, you are guaranteed that every JSON value has a specific start (U+001E) and end (LF) character, and it is guaranteed that the start character can't appear in the JSON representation, because control characters in JSON strings have to be \U-encoded. > > In JSON Lines, it is guaranteed that the end character doesn't appear within the JSON representation either, so no start character is needed. > > Both are robust against incomplete JSON representations. They are also robust against accidentally adjacent values (just writing 3 and then 4 will be reread as 34 otherwise). Unfortunately a single doc can't conform to both because a Json Lines processor will break on reading the U+001E. > JSON Sequence is https://tools.ietf.org/html/rfc7464