W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2009

Re: ISSUE-22: Should we have an umbrella requirements document?

From: Robin Berjon <robin@robineko.com>
Date: Mon, 28 Sep 2009 14:57:14 +0200
Cc: richard.tibbett@orange-ftgroup.com, public-device-apis@w3.org
Message-Id: <FAD36D0E-2B96-4DF2-91F7-F2D83F2096D3@robineko.com>
To: John Kemp <john@jkemp.net>
On Sep 23, 2009, at 19:03 , John Kemp wrote:
>> My view is that a general guidelines/requirements document would not
>> necessarily be a useful public output of the W3C DAP WG. All general
>> requirements will be implicitly included in all DAP API specs  
>> produced
>> (because we will check that those guidelines are followed before
>> publishing any spec).
>
> Is it possible to both create a separate requirements document, and  
> also link from individual specifications into that document? In  
> other words, you only do the work once, but you also give the  
> possibility of documenting requirements which may affect more than  
> one item in more than one specification?

Certainly. In fact, if we do create a requirements document (which  
seems like it will be the case), I believe we will have to link to it  
from specifications because otherwise no one will ever see it :)

--
Robin Berjon
   robineko  setting new standards
   http://robineko.com/
Received on Monday, 28 September 2009 12:58:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:38 UTC