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

SpecGL edits based on 22 Dec Telecon

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Fri, 02 Jan 2004 13:56:18 -0500
Message-Id: <5.1.0.14.2.20040102135320.01bd73b0@mailserver.nist.gov>
To: www-qa-wg@w3.org
Happy New Year All

Based on the last telecon (22 Dec), I have made the following changes to SpecGL

3.4  If modules are chosen, indicate any mandatory conditions or 
constraints on their usage.

Conformance requirements
The specification MUSTindicate, either (1) that there are no 
interrelationships or dependencies among the modules or (2) enumerate the 
interrelationships or dependencies.
This checkpoint is not applicable if modules are not used.

Discussion
The conditions or constraints normally will be tailored according to class 
of product. Examples of conditions and constraints include:
       atomicity of modules.
       mandatory module(s),
       modules that are optional,
       dependencies among modules,
       modules that require and build on functionally related modules,
       modules that require modules from other functional areas,
       constraints against combined occurrence of particular pairs of modules.

3.5  If profiles, modules or levels are used, define their relationships 
and interactions with other dimensions of variability.

Conformance requirements
The specification
       MUST address and discuss the relationships and interactions between 
the defined profiles and all other dimensions of variability that are used,
       MUST address and discuss the relationships and interactions between 
the defined modules and all other dimensions of variability that are used,
       MUST address and discuss the relationships and interactions between 
the defined levels and all other dimensions of variability that are used.

4.1 Identify each deprecated feature.

Conformance requirements
The specification MUST list document in a single normative section each 
deprecated feature. This checkpoint is not applicable if there are no 
deprecated features.

Discussion
List is understood here and in later conformance requirements as either an 
inline list of items or a list of links to each item in the body of the 
specification.

4.6 Identify each obsolete feature.

Conformance requirements
The specification MUST list each obsolete feature.  This checkpoint is not 
applicable if there are no obsolete features.
Received on Friday, 2 January 2004 13:56:49 GMT

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