- From: David Baron via WBS Mailer <sysbot+wbs@w3.org>
- Date: Sat, 26 May 2018 06:00:02 +0000
- To: public-new-work@w3.org
The following answers have been successfully submitted to 'Call for Review: CSS 1 as Superseded Recommendation' (Advisory Committee) for Mozilla Foundation by David Baron. > > --------------------------------- > Decision > > ---- > Regarding the proposal to supersede this Recommendation, my > organization: > > * (x) supports republishing this Recommendation as Superseded Recommendation. * ( ) does not support to republish this Recommendation as Superseded Recommendation for the reasons included below [Formal Objection]. These are the Recommendations my organization supports as Obsolete Recommendations, for the following reasons: > > > --------------------------------- > Other Comments > > ---- > Please add here any other comments you have. > > Comments: It's not clear to me if we should be using the Superseded process for Recommendations that are superseded by another W3C Recommendation of the same name with a higher version number; that wasn't how I imagined it being used when it was added to the process. I understood that addition as being to remedy objections in https://www.w3.org/2002/09/wbs/101147/cors-obs-2017-09/results to obsoleting CORS because it was superseded by a specification of a different name, at a different organization. This seems to me like a lot of AC ballots for something that's relatively obvious, and that should be an implicit part of the process rather than something that requires a lot of AC ballots. > > These answers were last modified on 26 May 2018 at 05:59:04 U.T.C. > by David Baron > Answers to this questionnaire can be set and changed at https://www.w3.org/2002/09/wbs/101147/css1-sup/ until 2018-06-21. Regards, The Automatic WBS Mailer
Received on Saturday, 26 May 2018 06:00:04 UTC