Closed AndreCAndersen closed 1 year ago
sounds good to me, mind making the change?
@wardi Unfortunately I discovered it is likely not the "correct" mime-type. I asked over at SO, and was made aware that json-seq
includes a <RS>
(ref) character. While jsonl
, from what I understand, relies on just line separators. Some suggestions which showed up where:
application/json-lines
application/jsonl
applicaiton/x-...
I suggest we somehow figure out which is used most, and support it as preferred (as well as listing other alternatives).
To start:
Google returns 9 results for "application/json-lines"
and 52 for "application/jsonl"
. Just for reference "application/json-seq"
gets 1340 results.
There's also: application/json-l
and extension .jsonl
:
I suggest closing this issue and keeping only https://github.com/wardi/jsonlines/issues/19 open to avoid confusion application/json-seq
does not work (because jsonl is not the same), so we would probably need another type. I suggest closing this issue because the title of the issue is about json-seq and nothing else.
I came accross this RFC: https://tools.ietf.org/html/rfc7464
It suggests using
application/json-seq
as the mimetype for json objects delimited by new lines. It is also cited on wikipedia . For completeness sake, I also created a stackoverflow question/answer here .If this is the correct mime type for
jsonl
, then I suggest adding it to jsonlines.org since it was the first hit on google, when researching this.