Re: Backward-compatibility of text/html media type (ACTION-334, ACTION-364)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anne van Kesteren writes:

> On Tue, 02 Feb 2010 16:06:41 +0100, Henry S. Thompson
> <ht@inf.ed.ac.uk>  wrote:
>> Sure, if the spec. is changed so that all past HTML docs conform to
>> the it, but as I said, I don't think that's a reasonable requirement
>> on this or any other spec.
>>
>> My understanding of the discontinuity wrt the text/html media type
>> registration prose is this:
>>
>>  1) Previous media type registrations for text/html have explicitly
>>     grandfathered in documents allowed by all earlier registrations of
>>     text/html;
>
> That does not seem to be true.
>
> http://tools.ietf.org/html/rfc2854 obsoletes various text/html media
> type  features of HTML2 (level parameter) and HTML32 (version
> parameter)

Those are parameters of the _media type_, not attributes or elements
in the HTML2 or HTML32 languages.

> and only references HTML4 and XHTML1 as published specifications
> related to the media type.

I see references to HTML20 and HTML30 and HTML32 as well.

>>  2) IETF rules for media type re-registrations requires that sort of
>>     grandfathering;
>
> It seems there is a precedent.

Not for restricting the class of documents which can be served.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      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 really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFLaEJCkjnJixAXWBoRAtUcAJ9UU8zANCJMUczsjw1ejp0jAs2W7ACfWF+A
XOUHFGo1UnVN/xCzMYrS9bg=
=pN1e
-----END PGP SIGNATURE-----

Received on Tuesday, 2 February 2010 15:19:07 UTC