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

What is the appropriate mime-type? #9

Closed
goloroden opened this issue Apr 23, 2015 · 10 comments
Closed

What is the appropriate mime-type? #9

goloroden opened this issue Apr 23, 2015 · 10 comments

Comments

@goloroden
Copy link

@goloroden goloroden commented Apr 23, 2015

What is the appropriate mime-type for jsonlines? Is it application/json, too, or should I use something different?

@webwurst
Copy link

@webwurst webwurst commented Jul 12, 2015

I would also like to see a suggestion :)

@kmike
Copy link

@kmike kmike commented Sep 26, 2015

At ScrapingHub we're using application/x-jsonlines.

@wardi
Copy link
Owner

@wardi wardi commented Sep 27, 2015

ndjson is now essentially the same format, why not use theirs "application/x-ndjson" https://github.com/ndjson/ndjson-spec

@giorgiosironi
Copy link

@giorgiosironi giorgiosironi commented Nov 12, 2018

FWIW application/json is incorrect, because multiple lines of JSON values are not valid JSON.

@goloroden
Copy link
Author

@goloroden goloroden commented Apr 24, 2019

Today, almost four years later, I found my own question via Google 😂

I am going to use application/x-ndjson, as @wardi suggested 😊

@AndreCAndersen
Copy link

@AndreCAndersen AndreCAndersen commented Jan 27, 2020

I found this issue after giving a suggestion elsewhere: #36

https://tools.ietf.org/html/rfc7464 seems to suggest using application/json-seq as the mime type.

@dimaqq
Copy link

@dimaqq dimaqq commented Jan 31, 2020

json-seq has slightly different format than jsonl Orz

@whlavina
Copy link

@whlavina whlavina commented Dec 30, 2020

The lack of a definitive IANA Media Type for JSON Lines causes some difficulty for those of us using the format. In the interest of pushing the issue, I took the liberty of starting a conversation:
https://mailarchive.ietf.org/arch/msg/json/dWMWD0JDa2HiUYjWjLjrQExeIx4/

Perhaps someone here would like to join that thread?

Disclaimer: I am in no way affiliated with the IANA/IETF. I am merely interested in using the format, correctly.

@sthagen
Copy link

@sthagen sthagen commented Dec 30, 2020

ndjson is now essentially the same format, why not use theirs "application/x-ndjson" https://github.com/ndjson/ndjson-spec

@whlavina - I joined that so called IETF discussion thread (and was present during the JSON sequences RFC shaping) and I still think application/x-ndjson is a sensitive way to go.

@dimaqq
Copy link

@dimaqq dimaqq commented Jan 7, 2021

I've also subscribed to the IETF mailing list, but I'm not sure how to respond to a past thread...

Meanwhile, on my end, we support application/jsonl and application/json-lines MIME types.

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

9 participants