This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
A while back Ian Hickson added a subtitle to the spec named HTML5. This may have been made in good faith, but it certainly wasn't a wise thing to do nor was it fair to the others in the HTML WG as many people weren't happy with the title and were hoping for it to be changed. Ian knew the title was very controversial, and knew that myself and others wanted to have the title changed. At the time of this illegal change to the spec I had been spending many hours working on a proposal to change the title from HTML5 to something else, by the time I posted my proposal to the group, Ian had already dived in and added his misleading subtitle which made it impossible for anyone else to fix the problem. If myself or someone else puts forward a proposal to change the title saying it's misleading, then our proposals are unlikely to be accepted as people will say the problem is already been fixed by Ian, and this is what has happened. We still have a ridiculous for the spec. If the title had just been left as HTML5, the HTML WG would have fixed it by now, instead, people have said that the problem's already fixed when it certainly is not. If the HTML WG are going to make changes to the title, then everyone should have an equal opportunity to submit their ideas to the group. I don't believe that Ian had the authority to do this and I believe that Ian's subtitle has prevented the title problem from being resolved. Please remove Ian's subtitle until someone in the HTML WG can come up with a title that is not misleading and confusing. Thanks Dean
I believe it would help your case if you explained * what text exactly you consider controversial; * why you do; * what the mentioned proposals are; * which problem you are trying to solve. Also, please try to stay on the topic of this particular bug. If all that were possible without personal attacks, and split in multiple paragraphs, that would be useful as well. Finally, I believe it is sensible to give an editor the authority to edit the specification, if that's what you're trying to protest against.
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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: The subtitle ("A vocabulary and associated APIs for HTML and XHTML") was added as part of a compromise to address publication concerns. If you disagree with this, please get the chairs to tell me what subtitle, if any, I should use to ensure that the draft can be published.
(In reply to comment #2) > 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: > http://dev.w3.org/html5/decision-policy/decision-policy.html > > Status: Rejected > Change Description: no spec change > Rationale: The subtitle ("A vocabulary and associated APIs for HTML and XHTML") > was added as part of a compromise to address publication concerns. If you > disagree with this, please get the chairs to tell me what subtitle, if any, I > should use to ensure that the draft can be published. And you had no authority, whatsoever, to make that change Ian. You excluded the HTML WG from that change. You have no authority to "compromise" the spec. It was for the HTML WG to decide what subtitle, if any, the W3C's spec should have. You have no more authority to add a subtitle to the spec than I do, Ian. You have refused to accept that the title of the spec needs to be "fixed". You have refused to accept that there is a contradiction within the spec, moreover, you have continued to prevent this problem from being fixed.
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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: no new information added since rejection in comment 2.