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

Re: Shelving "Device APIs Requirements"

From: Giuseppe Pascale <giuseppep@opera.com>
Date: Wed, 16 Nov 2011 12:23:18 +0100
To: "Deepanshu gautam" <deepanshu.gautam@huawei.com>, "Robin Berjon" <robin@berjon.com>
Cc: DAP <public-device-apis@w3.org>
Message-ID: <op.v41dw4dj6ugkrk@giuseppep-x220>
On Wed, 16 Nov 2011 10:40:54 +0100, Robin Berjon <robin@berjon.com> wrote:

>> But, anyway in this case I suggest to remove (expired??) this document  
>> completely not shelved. If shelved then it is creating confusion i.e  
>> requirement document is shelved bcz group thinks it is not needed  
>> whereas Messaging API is shelved bcz group is working on something else  
>> which works better.
>
> The difference between the two situations is genuine, which is why I  
> think that the warning/shelving message needs to be adapted to each  
> situation. However we can't remove things from /TR/. These URIs are  
> meant to be persistent in time. There are documents (outside of our  
> control) that link to http://www.w3.org/TR/dap-api-reqs/. Those should  
> not get a 404 (or even a 410), but are better served by getting an  
> updated document that is self-describing as outdated.
>

+1

-- 
Giuseppe Pascale
TV & Connected Devices
Opera Software
Received on Wednesday, 16 November 2011 11:23:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT