W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: Obsolescence notices on old specifications, again

From: Glenn Adams <glenn@skynav.com>
Date: Mon, 23 Jan 2012 13:38:08 -0700
Message-ID: <CACQ=j+eP3iUeDvvz-cSeSmU9gtT16iVbP61R5dZLhbqrCzkDBg@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Ms2ger <ms2ger@gmail.com>, "public-webapps@w3.org" <public-webapps@w3.org>
I work in an industry where devices are certified against final
specifications, some of which are mandated by laws and regulations. The
current DOM-2 specs are still relevant with respect to these certification
processes and regulations.

I do not object to adding an informative, warning notice to the status
sections of these docs that new work is underway to replace, and eventually
formally obsolete older DOM RECs. However, until replacement specs exist
that have achieved sufficient maturity (namely, REC status), it would not
be appropriate to formally obsolete the existing DOM specs.


On Mon, Jan 23, 2012 at 12:09 PM, Glenn Maynard <glenn@zewt.org> wrote:

> On Mon, Jan 23, 2012 at 12:06 PM, Glenn Adams <glenn@skynav.com> wrote:
>> I object to adding such notice until all of the proposed replacement
>> specs reach REC status.
> Why?
> The real world of modern spec use and authoring is no longer tightly tied
> to reaching REC (or even CR or PR), and the current situation of outdated
> specs with no warnings, misleadingly presented as if they represent modern
> practice, repeatedly leads to both user and implementer confusion.
> I don't know if this is the right thing to do for all of the listed specs,
> but in general this is important to fix.
> --
> Glenn Maynard
Received on Monday, 23 January 2012 20:39:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:31 UTC