RE: Shelving "Device APIs Requirements"

What does it mean to shelve the *Requirements* document?

Are the requirements in the document should no longer be fulfilled by the related specs?
Is the group is trying to create new requirements? (.....that we are working on an approach that we believe works better.)


I think some part of requirements should be removed (or clearly differed) instead of shelving the entire document. I think there must be a active requirements document for community/contributors to refer in case they want to contribute or anything else....


Regards

Deepanshu Gautam
Service Standards, Huawei Software
T: +86 25 5260008 M: +86 135 85147627


-----Original Message-----
From: Robin Berjon [mailto:robin@berjon.com] 
Sent: Wednesday, November 09, 2011 12:23 AM
To: DAP
Subject: CfC: Shelving "Device APIs Requirements"

Dear all,

following the process outlined in http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0026.html I am proposing that we shelve:

Device APIs Requirements
    http://dev.w3.org/2009/dap/api-reqs/
    http://www.w3.org/TR/dap-api-reqs/

Please answer this CfC before our next call on Nov 16. Thanks!

-- 
Robin Berjon - http://berjon.com/ - @robinberjon

Received on Tuesday, 15 November 2011 01:35:45 UTC