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

obsconf

Return the concept of Obsolete but conforming back to using obsolete and deprecated

State:
CLOSED
Product:
HTML 5 spec
Raised by:
Shelley Powers
Opened on:
2010-03-31
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
Related Actions Items:
No related actions
Related emails:
  1. RE: {agenda} HTML WG telcon 2010-05-06: Action items, issues, decision policy, calls, surveys, publishing - minutes (from adrianba@microsoft.com on 2010-05-06)
  2. {agenda} HTML WG telcon 2010-05-06: Action items, issues, decision policy, calls, surveys, publishing (from rubys@intertwingly.net on 2010-05-05)
  3. Re: ISSUE-106 (obsconf): Chairs Solicit Proposals (from rubys@intertwingly.net on 2010-05-05)
  4. RE: {agenda} HTML WG telcon 2010-04-29: Action items, new issues, Task Force reports - minutes of the meeting (from adrianba@microsoft.com on 2010-04-29)
  5. {agenda} HTML WG telcon 2010-04-29: Action items, new issues, Task Force reports (from mjs@apple.com on 2010-04-28)
  6. will write change proposal for ISSUE-106 (from shelley.just@gmail.com on 2010-04-15)
  7. Re: ISSUE-100, ISSUE-89, ISSUE-106 (from mjs@apple.com on 2010-04-14)
  8. Minutes of HTML WG meeting, Apr 8 2010 (from Paul.Cotton@microsoft.com on 2010-04-08)
  9. {agenda} HTML WG telcon 2010-04-08: calls for proposals, issue status (from mjs@apple.com on 2010-04-07)
  10. ISSUE-106 (obsconf): Chairs Solicit Proposals (from mjs@apple.com on 2010-04-06)
  11. Re: ISSUE-106 (obsconf): Return the concept of Obsolete but conforming, back to using obsolete and deprecated [HTML 5 spec] (from joshue.oconnor@cfit.ie on 2010-04-05)
  12. [minutes] 2010-04-01 HTML Teleconference (from rubys@intertwingly.net on 2010-04-01)
  13. [Bug 9122] Obsolete but Conforming (from bugzilla@wiggum.w3.org on 2010-03-31)
  14. ISSUE-106 (obsconf): Return the concept of Obsolete but conforming, back to using obsolete and deprecated [HTML 5 spec] (from sysbot+tracker@w3.org on 2010-03-31)

Related notes:

[rubys]: closed without prejudice, as nobody has volunteered to write a change proposal

6 May 2010, 16:14:48

Changelog:

Created issue 'Return the concept of Obsolete but conforming, back to using obsolete and deprecated' nickname obsconf owned by Shelley Powers on product HTML 5 spec, 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].

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
' non-public

Shelley Powers, 31 Mar 2010, 22:42:24

Description changed to '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
'

Maciej Stachowiak, 31 Mar 2010, 22:51:00

title changed to 'Return the concept of Obsolete but conforming back to using obsolete and deprecated'

Maciej Stachowiak, 1 Apr 2010, 16:17:40

Status changed to 'closed'

6 May 2010, 16:14:30


Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>, Chairs, Michael[tm] Smith <mike@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $