- From: Daniel W. Connolly <connolly@beach.w3.org>
- Date: Thu, 09 May 1996 19:38:40 -0400
- To: Paul Prescod <papresco@itrc.uwaterloo.ca>
- Cc: www-html@w3.org
In message <199605092116.RAA26993@itrc.uwaterloo.ca>, Paul Prescod writes: > >Since the IETF defines what text/html is I think that a HTTP server that >delivers HTML 3.2 as text/html would be in error unless the IETF (though the >HTML-WG) decides to update the definition of text/html to allow HTML 3.2, >which would, I expect, be a very long and painful process. About HTTP, I think you're right. The definition of text/html needs to change. I proposed putting that on the HTML WG charter, but it doesn't look likely. And strictly speaking, it doesn't have to be done there. The way I understand it, the IETF defines not what text/html is, but the binding between the name text/html and the relavent spec. That binding is stored at: ftp://venera.isi.edu/in-notes/iana/assignments/media-types/text/html and it currently points to RFC1866. Any updates/enhancements to RFC1866 in the IETF would go through the HTML working group, but changes to the binding between text/html and the relavent spec don't necessarily involve any working groups or the publication of any documents. You just send a request to IANA, after discussing it on the ietf-types mailing list. See: MIME media types Harald.T.Alvestrand@uninett.no Last modified: Mon Mar 11 11:25:32 1996 http://domen.uninett.no/~hta/ietf/media-types.html (found from the MIME FAQ, available at: http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/mime-faq/part3/faq.html ) Dan
Received on Thursday, 9 May 1996 19:38:55 UTC