Edit ISSUE-106: Return the concept of Obsolete but conforming back to using obsolete and deprecated

Nickname:

Title:

State:
RAISED OPEN PENDINGREVIEW CLOSED POSTPONED

Product:
None alt techniques authoring guide canvas 2d context Encrypted Media Extensions HTML 5 spec HTML 5: The Markup Language HTML Principles/Requirements HTML WG website HTML+RDFa HTML5 differences from HTML4 HTML5 Spec - PR Blockers Media Source Extensions Microdata Polyglot pre-LC1 alt techniques pre-LC1 authoring guide pre-LC1 HTML 5 spec pre-LC1 HTML+RDFa testsuite W3C publications

Raised By:
Glenn Adams Adrian Bateman Michael Cooper Paul Cotton Erika Doyle Navara Steve Faulkner James Graham Ian Hickson Lachlan Hunt Kris Krueger Philippe Le Hégaret Larry Masinter Matthew May Shawn Medero Ben Millard Jay Munro Joshue O Connor Theresa O'Connor Frank Olivier Julian Reschke Gregory Rosmaita Sam Ruby Mark Sadecki Janina Sajka Doug Schepers Cynthia Shelly David Singer Henri Sivonen Jerry Smith Michael[tm] Smith Manu Sporny Maciej Stachowiak Everett Zufelt Shelley Powers

Description:
The text of the current HTML 5 draft does not contain the sections in previous versions of HTML in regards to Deprecated and Obsolete HTML elements[1]. Instead, the current document references terms such as "obsolete but conforming" [2], leaving a great deal of confusion about just what this means, and about the state of the elements so described. [3][4]. Escalated from: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9122 In addition, several valid HTML 4 elements and attributes have been described as obsolete in HTML 5, not deprecated, which does not provide a graceful transition period for people to remove these elements/attributes from their web documents. Considering how widespread the support for deprecated is within the technology industry[5], the HTML 5 specification should return to the previously defined sections describing deprecated and obsolete as listed in the HTML 4 document. Doing so will ensure that older HTML elements aren't abruptly dropped, causing confusion. This move will also ensure that there is a procedure in place to ensure that when an element is dropped, it's dropped in favor of a replacement that provides the same, or enhanced functionality. It will also help clarify confusion caused by using terminology not used previously with any other known specification. [1] http://www.w3.org/TR/html4/conform.html#deprecated [2] http://dev.w3.org/html5/spec/Overview.html#obsolete [3] http://lists.w3.org/Archives/Public/public-html/2009Aug/0121.html [4] http://realtech.burningbird.net/deprecated-is-now-obsolete [5] http://en.wikipedia.org/wiki/Deprecation

Add notes (no markup allowed, URIs get automatically hyperlinked):