W3C home > Mailing lists > Public > public-webapi@w3.org > February 2006

[REX]: REX Requirements does not seem like a requirements document

From: Maciej Stachowiak <mjs@apple.com>
Date: Sat, 11 Feb 2006 18:55:11 -0800
Message-Id: <0F956EA0-CC0D-4E4E-9E00-05CFBF0A7AC5@apple.com>
To: public-webapi@w3.org


Hi everyone,

I expect a requirements document to start with use cases and then  
state functional requirements that satisfy these uses cases. But the  
REX requirements document instead starts out by stating a list of  
mandatory technology dependencies. It says that the spec must depend  
on DOM Level 3 Events, DOM Mutation Events, XPath, and some DOM  
(either the compatible DOM 2 and DOM 3 core, or the currently  
incompatible SVG uDOM) and XML.

Perhaps these portions of the reqs document could be put in a  
separate "Mandated Dependencies on Other Specifications" document.  
The remainder could be rewritten to start with use cases and justify  
the requirements based on those or on demands of constituencies /  
process.

Alternately, the dependencies on other technologies could be  
justified as the best way to satisfy use-case driven requirements,  
instead of being simply asserted.

Regards,
Maciej
Received on Sunday, 12 February 2006 02:55:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT