search

jshttp / mime-db

Media Type Database
MIT License
1.11k stars 256 forks source link

Added the `wav` extension to `audio/vnd.wave` #255

Closed aarongeorge closed 2 years ago

aarongeorge commented 2 years ago

Resolves issues with https://github.com/oakserver/media_types/pull/12

aarongeorge commented 2 years ago

@dougwilson Sorry, I have added a source

dougwilson commented 2 years ago

Thanks. Please add a primary source. That seems like a secondary source at best.

aarongeorge commented 2 years ago

@dougwilson I've linked the webkit bug. Is that primary enough?

dougwilson commented 2 years ago

No, i don't think so. Can you explain how that would be a primary source? It looks like Jeremy Jones works for Apple there (i.e. webkit) and it's just a tracking issue of Jeremy adding it. No source was cited there and I assume Apple didn't make this mime type.

aarongeorge commented 2 years ago

Fair enough. Is the ietf.org source primary?

I'm not trying to be difficult. I'm trying to resolve an issue in a downstream project that relies on your DB.

dougwilson commented 2 years ago

Thanks. I don't see anywhere in that document that is says the file extension you are adding is associated to this mime type, but to be fair it is a large doc. Can you point me to that piece of information?

dougwilson commented 2 years ago

Reading that document it seems that the ;codec=YYY is required, but there are a lot to choose from. I guess that is why it does not declare any file extension for this, as one would not have a way to know what the code value would be from such a simple mapping (or perhaps each code YYY typically would have a different file extension?).

aarongeorge commented 2 years ago

I'm not sure what else to say really. Multiple apps use the raw audio/vnd.wave as a mime-type and people seem to not wish to use anything other than your DB as a resource and so it's breaking many tools that require uploading a .wav file.

Any ideas?

aarongeorge commented 2 years ago

As far as the web and mime-types are concerned it seems like they treat the properties as optional. https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types

dougwilson commented 2 years ago

Since this module is the aggregate of the threw data sources listed at the top of the readme, perhaps you should get this added to one of them and it'll just pull in here?

As a curtosy, we do accept entries directly, but only with definite sources, as we are not here to argue about these things. This was just made to aggregate the three sources for our usage, made available to whoever chooses to use it under MIT license.

As far as others using this module, I cannot speak for them. I have no contact with anyone and if they want to use it, they are free to or not. What this module does is written in the readme (aggregates from the three daya sources).

Not all media types have file extensions (just look at the db). I'm not sure who you are and what authority you have to declare that this media type does indee have a file extension when the documentation you provides about the media type doesn't have one.

Like I said, the goal of this module is not to be a registry, arbitrator or anything similar, just was a little project to aggregate from the three sources and make a json file. Perhaps plead you case to those sources.