W3C home > Mailing lists > Public > www-tag@w3.org > April 2010

Re: TAG ACTION-407 -- text/html media type and legacy

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Thu, 22 Apr 2010 19:25:38 +0100
To: Maciej Stachowiak <mjs@apple.com>
Cc: public-html@w3.org, Paul Cotton <Paul.Cotton@microsoft.com>, "noah_mendelsohn@us.ibm.com" <noah_mendelsohn@us.ibm.com>, "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <f5beii78hul.fsf@calexico.inf.ed.ac.uk>
Hash: SHA1

Maciej Stachowiak writes:

> <commenting with HTML WG chair hat off>

Likewise speaking only for myself

> I understand the desire to satisfy the MIME registration compatibility
> requirements. However, it looks to me like this proposed text makes
> HTML 2.0, HTML 3.2, and HTML 4.0 conforming for the text/html MIME
> type, whereas RFC2854 only allowed HTM 4.01. Are these additions
> intentional? I don't understand the purpose of expanding conformance
> relative to the previous registration to include these long-obsolete
> specifications.

We have to be very careful with language here.  IETF policy for
reregistration of media types in general, and RFC2854 in particular,
is that they have _nothing_ to say about conformance to the language
specs that they reference -- that is left to those specifications.
Furthermore, although it's fine for successive language specs
referenced by successive RFCs (re)registering a particular media type
to add/subtract/change language features, that does _not_ affect the
core commitment that documents from the earlier language versions, as
referenced in preceding media type (re)registrations, are OK to
_serve_ with the specified media type.  That's _all_ that's at issue
in the media type registration.  So RFC2854 says "Now you can serve
HTML 4 as text/html" as well as saying "and all that stuff you used to
be able to serve as text/html -- still OK to serve as text/html".

I think Ian and I are on the same page now wrt this issue, if I
understand his earlier response correctly.

> Also: RFC2854 allows a profile of XHTML 1.0 (presumably Appendix C) to
> be sent as text/html, whereas the proposed text below does not. Is the
> omission intentional?

I'll pick that up in a separate message.

- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)

Received on Thursday, 22 April 2010 18:26:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:33 UTC