Bug 673 - Lots of IANA-registered media types incorrect.
Summary: Lots of IANA-registered media types incorrect.
Status: RESOLVED WONTFIX
Alias: None
Product: shared-mime-info
Classification: Unclassified
Component: freedesktop.org.xml (show other bugs)
Version: unspecified
Hardware: All All
: high normal
Assignee: Jonathan Blandford
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 42369
Blocks: 38267
  Show dependency treegraph
 
Reported: 2004-05-25 18:51 UTC by Dave Cridland
Modified: 2013-02-12 17:49 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
List of incorrect types. (1.06 KB, text/plain)
2004-05-25 18:53 UTC, Dave Cridland
Details
XSL thingy to extract the IANA registered types. (1.38 KB, application/xml)
2004-05-25 18:57 UTC, Dave Cridland
Details

Description Dave Cridland 2004-05-25 18:51:10 UTC
A significant portion of the IANA media types are incorrect. By this, I mean
that the media types that are not prefixed with 'x-' or 'x.', and therefore must
be registered, and under the control of IANA, are largely unregistered.

In total, there are 112 IANA media types in XDG, of which 49 don't exist at
IANA, assuming my horrible XSL works.

I'll attach everything in a sec.
Comment 1 Dave Cridland 2004-05-25 18:53:11 UTC
Created attachment 321 [details]
List of incorrect types.

This contains a list of incorrect types - specifically, those in registered
'format' in the freeedesktop.org.xml file, but not actually registered at IANA.
Comment 2 Dave Cridland 2004-05-25 18:57:48 UTC
Created attachment 322 [details]
XSL thingy to extract the IANA registered types.

This will extract the media types from each IANA page, using xsltproc:

xsltproc -o audio --stringparam type audio --html iana-parser.xsl
http://www.iana.org/assignments/media-types/audio/

About half the IANA files have bad HTML, though, and require manual parsing.

Note also that the types you'll get are not in entirely lower case, although
they do appear to be sorted case insensitively.
Comment 3 Ghee Teo 2004-08-11 03:42:54 UTC
Dave, 
   As I offered to help out a bit of this area of fo and had ramdonly picked up
this bug. In order for me to fully understand the problem here, I like to ask a
few questions by use of examples.

(1)

Attachment 1 [details]               IANA site            freedesktop.org.xml  
============               ==========           ====================
application/vnd.ms-word    msword               application/vnd.ms-word
                                                now alias to msword

So I believed this one is fixed.

(2)

application/illustrator    NONE found           application/illustrator

Does this mean this one has to be registered at IANA ?

In fact, there are many more of those in attachment 1 [details] [review] is not found at IANA,
so is the main task here is to registered at IANA?

Thanks for any exaplanation here :)
Comment 4 Ghee Teo 2004-08-30 09:55:29 UTC
Updated this bug report with excerpts of the e-mail from Dave.
----------
In general:

If a media type looks like it belongs in IANA, then it either must be listed by
IANA, or it's wrong.

So for every such media type, one of three things needs to happen:

1) The correct type is found, hence we change it.
2) There's no correct type, and we help the project developers (or encourage the
company) to register a media type.
3) There's no correct type, the project developers aren't interested in
registration, hence we use an x- prefix. [This also applies to the enthusiastic
use of media types to describe non-streams.]

I reckon:

A) IANA types should get moved to an iana.org.xml file.
B) Deprecated aliases for the types we've changed go into a
deprecated.freedesktop.org.xml file or similar. That keeps the "main" file clear
of cruft.
C) Category (3) above stays in freedesktop.org.xml

Secondly, since we're changing the standard anyway to do this slightly, it might
be really nice to add in a reference URI, as IANA has.

-------

The proposal here is to manage the whole things in 3 files:

- IANA registered types in iana.org.xml
- "Official" freedesktop.org.xml types in freedesktop.org.xml (should all be
"x-" prefixed)
- Deprecated aliases and other stuff we need to understand, but should never
generate, in deprecated.freedesktop.org.xml 

Really updated this report for a bit of discussion whether this is a good approach.

Comment 5 Christophe Fergeau 2004-11-26 14:48:11 UTC
application/smil is being registered it seems
http://www.ietf.org/internet-drafts/draft-hoschka-smil-media-type-12.txt
Comment 6 Bastien Nocera 2005-11-01 03:14:24 UTC
Many of those mime-types are indeed broken.
1. mime-types that don't have an equivalent in the IANA list can stay, as they
are there because used in the wild (another option would be to make up decent
third-party mime-types and add the "broken" mime-types to the list.
2. mime-types present as aliases can be broken, as long as the parent is a
proper IANA type.

Dave, could you make a list of the top-level mime-types (not the aliases) that
aren't in the IANA list?
Comment 7 Benjamin Close 2008-01-11 02:36:53 UTC
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 8 Bastien Nocera 2008-06-11 09:55:29 UTC
No updates in 3 years.
Comment 9 Christopher Yeleighton 2011-06-13 13:48:15 UTC
I reopen in hope to get at least an explanation why it was RESOLVED WONTFIX, and also in concert with Bug 38267.
Comment 10 Bastien Nocera 2011-06-14 02:28:07 UTC
(In reply to comment #9)
> I reopen in hope to get at least an explanation why it was RESOLVED WONTFIX,
> and also in concert with Bug 38267.

Because nobody bothered to provide any patches in 3 years.
Comment 11 Bastien Nocera 2013-02-12 17:49:00 UTC
(In reply to comment #10)
> (In reply to comment #9)
> > I reopen in hope to get at least an explanation why it was RESOLVED WONTFIX,
> > and also in concert with Bug 38267.
> 
> Because nobody bothered to provide any patches in 3 years.

And no patches since requested in 2005, so closing again.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.