- From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
- Date: Fri, 08 Oct 2004 14:01:38 -0400
- To: www-qa-wg@w3.org
- Message-Id: <6.0.0.22.2.20041008140049.01c6f2a8@wsxg03.nist.gov>
This concludes my reading/review of SpecGL D Managing Variability 1. Intro text is awkward. Suggest: Specifications allow for variation between conforming implementations for different reasons, e.g., adaptation to hardware capacities and extensibility. Variability, while it can provide for broader usage of the technology, may impede interoperability. Watch out for excessive variability – that which goes beyond what is needed. Look for a balance between what is needed to allow for flexibility while still achieving the desired interoperability. This section gives advice on finding the right balance. The reader will also benefit from reading, Variability in Specifications [VIS] which goes into more details on the analysis of this variability. 2. P If the technology is subdivided, then indicate which subdivisions are mandatory for conformance -Why care Delete the Chinese menu syndrome. In the last sentence, s/and be conformant/and still be conforming/ 3. GP If the technology is profiled, define rules for creating new profiles -Techniques #3 s/done/down/ D2 Optionality and Options Suggest changing the Story to an Example. We don’t have any other Stories in this document.
Received on Friday, 8 October 2004 18:01:34 UTC