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

IPython notebooks extension support #176

Closed
dmvieira opened this issue Oct 29, 2019 · 12 comments · May be fixed by #282
Closed

IPython notebooks extension support #176

dmvieira opened this issue Oct 29, 2019 · 12 comments · May be fixed by #282

Comments

@dmvieira
Copy link

We have no sources with this standard for ipynb extension: https://jupyter.readthedocs.io/en/latest/reference/mimetype.html

@dougwilson
Copy link
Contributor

I don't see anything about a .ipynb file extension on that page?

@dmvieira
Copy link
Author

I see that it's alread in shared mime info in this line. What do you think about include this source in mime-db?

@dougwilson
Copy link
Contributor

This module only pulls from the three sources listed at the top of the readme. To pull it in, the best method is relly to get it into the IANA database.

@dougwilson
Copy link
Contributor

As a stop gap measure, types can be added directly to this module, but you would need to find a primary source so I can vet it. Sites that are just aggregate mime types are a secondary source. So if you can find out where that site sourced the data from for this mapping that should work.

@flying-sheep
Copy link

Well, that’s a mirror of freedesktop’s “shared mime info” list. freedesktop is an initiative for interoperability in *NIXoids, to which end they define standards. They aren’t an official standards body, but followed by all bigger desktop environments on Linux like GNOME and KDE Plasma.

I consider a DB compiled by them second to IANA, and much more official than any specific server software’s collection. So if you aggregate from nginx and Apache, you should definitely also aggregate from freedesktop’s shared-mime-info.

@dougwilson
Copy link
Contributor

If we were to add that as a source, where is the shared mime info list hosted for us to pull from it directly? Do they have any policy against automated pulling of their data?

@flying-sheep
Copy link

On the linked page are “Sources” and “Releases”, both linking to their GitLab instance. Linux distros like e.g. Arch pull from there.

@dougwilson
Copy link
Contributor

Nice! But yea, a new source can definitely be added if that is the desired method to move forward here. Pull requests are welcome, otherwise I'll just add this work to my backlog and get to it eventually :)

@flying-sheep
Copy link

@dmvieira is the one interested in this, I’m mainly writing my thesis right now and offering a bit of knowledge here and there 😄

@dmvieira
Copy link
Author

hahaha thank you for your support @flying-sheep . Now I'm doing the same, but I'll try in some months

@dougwilson
Copy link
Contributor

I'm going to close this as it has been a few years and it is still neither (a) registered with IANA nor (b) just clarified on their own documentation what file extension for what MIME type. If the project is not interested in even documenting it on their own site, it would seem they don't want the association known, and so won't be included here without at least one of those being done.

@dougwilson dougwilson closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2022
@julien-c
Copy link

FYI, following up with a narrower-scoped proposed solution to this in #282

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants