W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2010

[Bug 8321] change controller for HTML media type

From: <bugzilla@wiggum.w3.org>
Date: Wed, 06 Jan 2010 08:53:40 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NSRe8-0005yV-NQ@wiggum.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |LATER

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-06 08:53:40 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change

For #1, I assume that this will be checked when the change is submitted with

For #2, I guess in practice it would be whoever got there first. :-) In
practice the whole "change control" field doesn't much matter — if IANA
doesn't recognise the authority of whoever is actually writing the specs that
are being used, then that will just make the IANA irrelevant and another
registry will effectively have to take over.  If the IANA _does_ recognise the
authority of whoever is writing the specs that are being used, then they would
have to ignore the change control field if it referenced a group that no longer
was writing those specs.

Personally I would much rather we just made the change control blank, and let
the community handle it via mutual recognition of authority — for example, if
the W3C and the WHATWG go crazy and start making specs that the implementors
are ignoring, then another group should be able to come along and write a new
spec and take over text/html over the objections of the W3C and the WHATWG, so
long as the community as a whole supports (via implementations and deployment)
that group rather than the W3C and the WHATWG.

(Marking LATER since #1 is an LC-transition issue.)

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, 6 January 2010 08:53:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC