W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2009

[Bug 6684] Disregard of RFC 4329 and IANA MIME Media Types

From: <bugzilla@wiggum.w3.org>
Date: Wed, 01 Apr 2009 23:30:25 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Lp9t3-00079e-Ss@wiggum.w3.org>

--- Comment #18 from Nicholas Stimpson <nickw3c@nfstimpson.co.uk>  2009-04-01 23:30:25 ---
(In reply to comment #16)
> > > Because HTML5 introduces all kinds of new features. What do the new JS MIME
> > > types introduce?
> > 
> > At least a new notation for Script-Mimetypes.
> What benefit does this bring to the user or the author?
Clarity. For an author who tries to follow specs as best I can, to be faced
with two specs where one says "Do A, don't do B" and another spec that says "Do
B, don't do A", what am I to do?

The HTML5 spec does not live on it's own, but in a environment with all the
other specs, and there's no obvious reason why the HTML5 spec should "win" such
a conflict.

It would at least be easier if the HTML5 spec said "Do A or B, in this context
it doesn't matter".

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 1 April 2009 23:30:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:00:52 UTC