Moving Requirements/Use-cases sections away from the main specification from Max Froumentin on 2010-03-04 (public-device-apis@w3.org from March 2010)

From: Max Froumentin <maxfro@opera.com>
Date: Thu, 04 Mar 2010 12:27:41 +0100
To: public-device-apis@w3.org
Message-ID: <4B8F992D.8080106@opera.com>

I would like to make the case for separate Requirements/Use Cases 
documents. For 2 reasons:

- a MUST in the requirements section doesn't mean the same thing as a 
MUST in the main specification. The former applies to the specification 
itself while the latter applies to a user agent. That could be confusing.

- Splitting makes the specification shorter. Use cases may still make 
sense in the specification to help users, but they should be very simple 
and just shown as examples.

feedback?

Max.

Received on Thursday, 4 March 2010 12:01:30 UTC