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

RE: Shelving "Device APIs Requirements"

From: Deepanshu gautam <deepanshu.gautam@huawei.com>
Date: Wed, 16 Nov 2011 00:58:02 +0000
To: Robin Berjon <robin@berjon.com>
Cc: DAP <public-device-apis@w3.org>
Message-id: <DA22857AC9F15C469BB47FE88C0201292A92BB88@SZXEML510-MBS.china.huawei.com>
I don't see anything wrong in having a groups (DAP) requirements in one single document. 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.


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

-----Original Message-----
From: Robin Berjon [mailto:robin@berjon.com] 
Sent: Tuesday, November 15, 2011 5:44 PM
To: Deepanshu gautam
Subject: Re: Shelving "Device APIs Requirements"


On Nov 15, 2011, at 02:34 , Deepanshu gautam wrote:
> What does it mean to shelve the *Requirements* document?

It has not been updated or edited in a very long time, and is completely out of date. As such, it needs to be either removed, or (as you suggest) updated.

Last the group discussed this we reached agreement that we did not see the point in a single requirements document for all of our deliverables. These tend to be orthogonal in what the aim to achieve, and therefore their requirements should be documented individually (in the specifications themselves), without being muddied by mixing them all together.

Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 16 November 2011 00:59:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:32 UTC