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

Action-140: Obsoleting a recommendation, one more minor fix

From: David Singer <singer@apple.com>
Date: Thu, 23 Jun 2016 14:01:05 +0200
Message-id: <0A632118-F88C-4DC0-B60F-22EA1C6EF2F7@apple.com>
To: W3C Advisory Board <ab@w3.org>, Revising W3C Process Community Group <public-w3process@w3.org>
The AB realized that we might, just possibly, make a mistake and obsolete something that we weren’t aware is actively used; or we might obsolete something and then later it starts getting traction and being used. It should be possible to reverse obsoletion, though we hope and expect that this will be rare.

The attached is a revision which adds the sentence:

"Obsoletion may be reversed, using the same process as for obsoleting a Recommendation. “

and then at the start of the two options, add that, viz.:

"The announcement:

must indicate that this is a Proposal to Rescind, or a proposal to Obsolete, or a proposal to reverse Obsoletion of, a Recommendation;”

Yes, I am aware that other parts of the text could be made more complex and more explicit about reversal, but I don’t think it’s worth it: we can surely work out what the intent of the text is in the rare case of reversal.

Yes, I am aware that we might end up with a case where, with the new knowledge, a decision to Obsolete would not pass, but the decision to reverse obsoletion also does not pass.  However, I think making the reversal process “reversal happens if it can be shown that obsoletion would have failed” is too complex to describe easily. I hope the community ‘does the right thing’ and we don’t get into this case.

David Singer
Manager, Software Standards, Apple Inc.

Received on Thursday, 23 June 2016 12:01:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 23 June 2016 12:01:43 UTC