W3C home > Mailing lists > Public > www-qa-wg@w3.org > November 2004

SpecGL: 4.2A need for optional feature

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Tue, 09 Nov 2004 14:37:24 -0500
Message-Id: <6.0.0.22.2.20041109143548.01c5e130@wsxg03.nist.gov>
To: www-qa-wg@w3.org

Assignment: 4.2A Need for the option

Change 4.2 Good Practice A to
Make sure there is a need for the optional feature

What does this mean?
Add as the 2nd to last sentence.
Don't make something an option just because the Working Group can't decide 
on what to do or can't reach consensus

Why care?
No change

Techniques
(replace what is there with the following)

* Make a list of use cases with the optional feature.

* Look at the optional feature and each class of product.  Is it something 
that this class of product would implement?  Consider if it really is an 
option - perhaps, for this class of product it isn’t really an option but 
should be mandatory.

* Develop an analyzer or set of tests to determine if options are 
needed.  Use the analyzer/tests to capture what implementations are doing – 
are they doing basically the same thing or is there variety and is that 
variety desired. 
Received on Tuesday, 9 November 2004 19:37:00 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:18 GMT