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

Proper content-type for .jsonl #44

Closed
brianorwhatever opened this issue Apr 12, 2024 · 8 comments
Closed

Proper content-type for .jsonl #44

brianorwhatever opened this issue Apr 12, 2024 · 8 comments
Labels
discuss Let's talk about this at our next meeting

Comments

@brianorwhatever
Copy link
Contributor

Continuing discussions from #41 I think we need to specify something.

When I upload it to a browser it says it's application/octet-stream.

There doesn't appear to be a consensus in wardi/jsonlines#19

The proposal there is application/jsonl which I think looks like a typo..

Another proposal in there (amazon uses) is application/jsonlines which seems pretty good to me other than not being in IANA

@swcurran
Copy link
Collaborator

We could help the JSON Lines folks write a draft spec so that our draft spec would be complete and so that we can make an IANA submission. Turtles all the way down…

I think we go with application/jsonlines, but I’m not the expert in this area. It just feels right...

@swcurran
Copy link
Collaborator

swcurran commented Aug 2, 2024

Andrew has found that text/jsonl is the right thing to use:

I updated the demo DID on anywhy.ca, and set the mime type for jsonl to 'text/jsonl' as that helps it render properly in a browser (apparently that's what Shopify uses)

@brianorwhatever
Copy link
Contributor Author

brianorwhatever commented Aug 2, 2024 via email

@PatStLouis
Copy link

I was looking into this as well, I also landed on application/octet-stream as there is no registered MIME type for jsonlines. Is there documentation about text/jsonl?

@swcurran swcurran added the discuss Let's talk about this at our next meeting label Oct 22, 2024
@swcurran
Copy link
Collaborator

All -- we need to nail this down. Someone be bold here :-) . Once decided, clarification to the specification.

@PatStLouis
Copy link

I think regardless of the decision we use in the spec, it's not an official media type. I have settled for text/jsonl in the tdw server. This can easily be changed.

@andrewwhitehead
Copy link
Contributor

I still like text/jsonl. As the MDN web docs describe the text type:

Text-only data including any human-readable content, source code, or textual data such as comma-separated value (CSV) formatted data. Examples include: text/plain, text/csv, and text/html.

It also has the benefit that you can specify the charset parameter as utf-8.

@brianorwhatever
Copy link
Contributor Author

I think we have consensus on text/jsonl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Let's talk about this at our next meeting
Projects
None yet
Development

No branches or pull requests

4 participants