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

SpecGL comments on Introduction

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Mon, 04 Oct 2004 19:45:44 -0400
Message-Id: <5.1.0.14.2.20041004194152.00ba1960@mailserver.nist.gov>
To: www-qa-wg@w3.org
Cc: karl Dubost <karl@w3.org>

Most of what follows is editorial - rewording suggestions, correction of 
grammar, typo.  I do have 1 question with regards to the RFC keywords and 
why we include this as written, since we don't CAPITALIZE the words.  We do 
however, use 'must' in our conformance clause. (see 4 below)

Introduction
About this Document
1. Reword last sentence of section
Current: ….the conformance clause may be an explanation of why there is no 
“conformance to this document” which may not be a separate section  but 
incorporated into another section.

Proposed: ….the conformance clause may be an explanation of why there is no 
“conformance to this document” and may be presented in another section 
rather than in a separate conformance section.

2. Next paragraph, first sentence, add ‘herein’
Propose: The topics presented herein are inclusive….

Structure of this document
3. Reword first paragraph
Current:  This document is organized in a series of main topics like 
Conformance or Extensibility.  In each of this main topics, a few 
principles are developed and explained.  Theses principles are accompanied 
by techniques and examples. The techniques….

Propose: This document is organized into a series of main topics such as 
Specifying Conformance and Managing Variability.  In each of these topic 
areas, Principles and Good Practices are presented and explained.  Each 
Principle and Good Practice is accompanied by techniques and examples.  The 
techniques illustrate basic (and non exhaustive) questions or methods to 
help you to realize the Principle/Good Practice and write bits of the 
specification.  The examples are explanations or extractions from W3C 
specifications which specifically illustrate the point which has been made 
in the Principle/Good Practice.

4. The keywords, MUST, MUST NOT, etc.  We don’t actually use these in our 
document.  Do we still need to include this statement?

The last sentence, “Occurrences of these words in lowercase… with no 
normative implications” is NOT true.  Our Conformance Clause uses ‘must’ 
and has a normative implication.

5. Other QA Framework Documents
QA Test Framework.  Lets indicate that this is a ‘planned’ document or 
‘under development’.


--regards
lynne
Received on Monday, 4 October 2004 23:46:23 GMT

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