Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Would application/json-seq be a suitable mime type for jsonl? #36

Closed
andre-c-andersen opened this issue Jan 27, 2020 · 4 comments
Closed

Comments

@andre-c-andersen
Copy link

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.

@wardi
Copy link
Owner

wardi commented Jan 27, 2020

sounds good to me, mind making the change?

@andre-c-andersen
Copy link
Author

andre-c-andersen commented Feb 14, 2020

@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.

@glensc
Copy link

glensc commented Mar 3, 2021

There's also: application/json-l and extension .jsonl:

@sp4ce
Copy link
Collaborator

sp4ce commented Dec 19, 2022

I suggest closing this issue and keeping only #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.

@sp4ce sp4ce closed this as completed Apr 3, 2023
@sp4ce sp4ce closed this as not planned Won't fix, can't repro, duplicate, stale Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants