W3C home > Mailing lists > Public > public-w3process@w3.org > April 2016

Strawman for the process on declaring a Recommendation 'obsolete'

From: David (Standards) Singer <singer@apple.com>
Date: Fri, 22 Apr 2016 09:39:12 -0500
Message-id: <AD7065BF-8699-4386-A445-A8D7F32ECEB1@apple.com>
Cc: Tantek Çelik <tantek@cs.stanford.edu>, Peter Linss <peter.linss@hp.com>, Daniel Appelquist <appelquist@gmail.com>
To: public-w3process@w3.org
Here’s a starting point for discussion.  I have emailed the TAG chairs to ask them if the TAG can accept the responsibility to do the ‘technical sanity check’ asked for here.

* * * *

Declaring a Recommendation to be Obsolete

Anyone may request of the W3C that a previously published Recommendation be marked as Obsolete. The request should include justification: for example, that the Recommendation has not been implemented, and no new implementations are expected; that there are better alternative specifications; that the Recommendation in question is not in alignment with best design practices, and so on.

The TAG MUST make the decision to proceed, by formal decision of the TAG. The TAG SHOULD consult with any pertinent working groups, especially if there is an obvious successor to the working group that developed the Recommendation. On the TAG’s decision to proceed, the Team prepares a vote of the Advisory Committee, who MUST approve the request to obsolete. 

If there is dissent in the Advisory Committee (votes against, or formal objections) the usual process to find consensus will be followed. If consensus cannot be found, the Recommendation is not obsoleted.

Finally, the Director approves the decision to obsolete. An obsoleted Recommendation is marked as such (a) in the document itself and (b) on the TR page. The status ‘Obsoleted’ links to a standing page which explains the meaning of the term.

David Singer
Manager, Software Standards, Apple Inc.
Received on Friday, 22 April 2016 14:39:42 UTC

This archive was generated by hypermail 2.3.1 : Friday, 22 April 2016 14:39:42 UTC