W3C home > Mailing lists > Public > public-w3process@w3.org > November 2011

RE: End-of-lifing dead documents in /TR/

From: Carr, Wayne <wayne.carr@intel.com>
Date: Wed, 16 Nov 2011 22:15:06 +0000
To: fantasai <fantasai.lists@inkedblade.net>, "public-w3process@w3.org" <public-w3process@w3.org>
Message-ID: <52F8A45B68FD784E8E4FEE4DA9C6E52A16F0AAC1@ORSMSX101.amr.corp.intel.com>
That wouldn't be bad just for regular heartbeat drafts to have something change in the status section when a later draft was published -- like superseded by a later draft. 

>-----Original Message-----
>From: fantasai [mailto:fantasai.lists@inkedblade.net]
>Sent: Wednesday, November 16, 2011 1:41 PM
>To: public-w3process@w3.org
>Subject: Re: End-of-lifing dead documents in /TR/
>
>On 11/16/2011 01:37 PM, Karl Dubost wrote:
>>
>> Le 16 nov. 2011 à 15:33, fantasai a écrit :
>>> I'd also say that relying on JavaScript for important information is
>>> probably not the best idea ever. If it's important, it should be in
>>> the document's content.
>>
>> Same issue if we were going to use CSS.
>
>Agreed.
>
>> I see only two accessible ways of doing it.
>>
>> 1. Changing the content of the document itself 2. Applying an HTTP
>> redirection on a URI request to a specific page explaining the status
>> for this URI (to avoid touching what is "printed" in TR/ space)
>
>If the Status of the document has changed, then the Status section should be
>updated. Likewise the text at the top that says "Working Draft"
>could be changed to "Abandoned/Unmaintained Draft".
>
>If this requires republishing, so be it.
>
>~fantasai

Received on Wednesday, 16 November 2011 22:15:36 UTC

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