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

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.

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.

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].

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.