RFC 7464 defines a "JSON text sequence" MIME type that consists of a sequence (naturally) of JSON texts where each text starts with an ASCII RS (record separator, 0x1E) and ends with an ASCII LF (newline, 0x0A). There is no requirement that the JSON texts be "compact" (no interstitial newlines) but generally that would be the case, and we could always add a new MIME type that is like this but with compactness required.

Compare to the commonly used compact JSON text sequences with newlines after each JSON text (as emitted by jq -c, and also various HTTP JSON APIs).

Might the use of unambiguous record separators make it easier to parse incrementally with SIMD?

See also #188.