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

Re: Obsoleting a Recommendation, round three

From: Stephen Zilles <szilles@adobe.com>
Date: Sun, 1 May 2016 14:36:36 +0000
To: Daniel Appelquist <appelquist@gmail.com>, David Singer <singer@apple.com>, "public-w3process@w3.org" <public-w3process@w3.org>
CC: Peter Linss <peter.linss@hp.com>
Message-ID: <43y79f86owkpgin0oe1jil5y.1462111280025@email.android.com>
This discussion was not at the AB, by within the Process Document Task Force using the W3Process CG mailing list. That said, there has not been much discussion of another body to do a technical evaluation of a Proposal to Obsolete a Recommendation.The problem we were concerned with is that there may be no existing WG (either the original one or a succesor to it) that can act on the Proposal. Action needs a technical evaluation and the TAG is chartered to address "cross WG technical questions." Although this responsibility is a bit different than evaluating a Proposal to Obsolete a Recommendation, there was no other obvious technical group to turn to. That is why the TAG was proposed.

If there is an existing WG that owns the Recommendation whose obsolence is proposed, then we could specify that that WG should handle the request instead of the TAG, with the same rules for appealing a negative (do not obsolete) decision as if the TAG had made such a decision. That might lessen the TAG's load. In any case, except for some obvious candidates, this process is not likely to see much usage.

Since the TAG owns the Web Architecture,  it would seem that evaluating whether a given Recommendation is obsolete would fall within that purview.

Steve Z

Sent from Samsung tablet

-------- Original message --------
From: Daniel Appelquist <appelquist@gmail.com>
Date: 05/01/2016 13:37 (GMT+02:00)
To: David Singer <singer@apple.com>,public-w3process@w3.org
Cc: Peter Linss <peter.linss@hp.com>
Subject: Re: Obsoleting a Recommendation, round three

Hi David –

I think we need to tee this up for discussion on our next TAG call in order to get you a coherent response. I'm not sure if the TAG wants to get into the business of being the “obsolesce committee.” What other options have been discussed by the AB? Why can't this be first and foremost the responsibility of the working group which produced the specification in the first place, with the TAG only getting involved in the cases where the working group doesn't exist any more? Also, when you say "Anyone" can you clarify that a bit?


On Fri, 29 Apr 2016 at 10:49 David Singer <singer@apple.com<mailto:singer@apple.com>> wrote:
Added SZ’s point, and Wayne’s about being clear about Appeals, and added “if it exists” to the need to consult with the WG.  I think we need to be clearer about announcing “to other W3C Groups” — like, which ones? How? Maybe the Chairs list? The AC?

* * * *

After offline discussion with some AB members, and the call today, I offer the following.

1) A new page, or section of a page, that defines what an Obsoleted Recommendation is.

An Obsoleted Recommendation is a Recommendation that the W3C membership no longer actively recommends be implemented; however, its formal status as a Recommendation (including its licensing status) remains.  (This is in contrast to a Rescinded Recommendation.)

A Recommendation may be considered obsolete if it is neither widely implemented nor expected to be. It may represent a technical direction that was not pursued further, or an architectural direction that is no longer in alignment with best practices in the industry. There may be alternative technologies better aligned with other parts of the Web Platform, or more in line with best practices. There may be technical drawbacks or even flaws associated with the Recommendation, but not so serious as to cause it to be Rescinded.

The W3C marks these as Obsolete to give guidance to the industry that new implementation is not sought or expected.

2) A new section of the Process Document, 6.X (6.10 if existing sections are not re-numbered, but it probably belongs before rescinded in logical order).

6.X Obsoleting a Recommendation

Anyone may request of the TAG that a Recommendation be considered for Obsoletion. The request to the TAG MUST identify the Recommendation and give reasons why it should be considered Obsolete; 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 announce its intent to consider the Request to Obsolete the Recommendation [[to other W3C groups]] and to the public and SHOULD consult with any pertinent working groups, especially the Working Group that developed the Recommendation if it exists, or any obvious successor WG. The TAG MUST make the decision to proceed, by formal decision of the TAG.

On the TAG’s decision to proceed, an Obsoleted Recommendation follows the process for a Proposed Edited Recommendation as defined in 6.7.2 and 6.5 for changes to a Recommendation that are Editorial only.

If there is dissent in the Advisory Committee (votes against, or formal objections) the usual process to find consensus will be followed. Objections SHOULD include evidence that the proposal is flawed; for example, that the Recommendation is widely implemented, or it is reasonably expected that it will soon be widely implemented.

Considering the advice of the Advisory Committee, the Director approves or denies the decision to obsolete. If there was any dissent in Advisory Committee review, the Advisory Committee may appeal the Director’s decision.

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 Sunday, 1 May 2016 14:37:08 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 1 May 2016 14:37:09 UTC