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

superseding a recommendation

From: Charles McCathie Nevile <chaals@yandex-team.ru>
Date: Wed, 29 May 2013 20:17:24 +0500
To: "public-w3process@w3.org" <public-w3process@w3.org>
Message-ID: <op.wxuyfam2y3oazb@dhcp-218-192-wifi.yandex.net>

in general, W3C Recommendations live forever as Recommendations. There is  
a process to rescind them, but there is no process to supersede them.  
Formally a new version of a spec at W3C doesn't have any way to replace an  
older one, which doesn't really make sense.

I think it would be useful to have such a process. I believe there are  
versioned specifications that don't actually supersede the previous  
version, such as some CSS modules, where the two versions live happily  
side-by-side. (What about HTML 3.2? Do people use it? Is that a good idea?  
Maybe we just need a spec for "HTML for email clients"...)

If we had such a process, what would we use it on? Should we just be more  
active about rescinding recommendations?



Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com
Received on Wednesday, 29 May 2013 18:18:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:08 UTC