W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

RE: Moving Requirements/Use-cases sections away from the main specification

From: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
Date: Thu, 4 Mar 2010 13:21:33 +0100
To: 'Max Froumentin' <maxfro@opera.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA3232A1FB310@seldmbx03.corpusers.net>
Ok for me assuming that you mean moving section B out but keeping the ECMAScript examples in the main specification.

Regards
 Claes

> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Max Froumentin
> Sent: torsdag den 4 mars 2010 12:28
> To: public-device-apis@w3.org
> Subject: Moving Requirements/Use-cases sections away from the main
> specification
> 
> 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:22:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:06 GMT