Copyright © 2002 W3C ® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This document is part of the of the Quality Assurance (QA) Activity. It presents examples and describes the techniques of producing specifications (Technical Reports) that are clearer, more implementable, and better testable. It complements QA Framework: Specification Guidelines [QAF-SPEC], illustrating how specification authors and Working Groups might meet the specification guidelines and checkpoints of that document.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest version of this document series is maintained at the W3C.
This document is a W3C Working Draft (WD), made available by the W3C Quality Assurance (QA) Activity for discussion by W3C members and other interested parties. For more information about the QA Activity, please see the QA Activity statement.
This version is the first public Working Draft, and supersedes all previous WG-only drafts. It is expected that updated WD versions of this document will be produced regularly, along with other members of the Framework documents family. Future progression of this document beyond Working Draft is possible, but has not yet been determined. This version should be published the 28th of November 2003.
In this version, example case studies are presented depending on their ability to illustrate the checkpoint -- how in all W3C specifications the checkpoints of the specifications guidelines [QAF-SPEC] have been implemented. As the specifications predate the QA Specificaton Guidelines, no W3C specifications meet all the specifications checkpoints, and some meet them partially inside a checkpoint.
This version lacks any enumeration of techniques -- what Working Groups must or should do to satisfy the specification guidelines checkpoints, and what constitutes conformance to the checkpoints. This is a significant planned addition in a future version. A future version will also derive a final chapter (after the "Guidelines in action") that will provide a retrospective assessment of the case studies, lessons learned, what was effective, and what was not. For each guidelines we will separate the examples from the techniques in two different sections.
Please send comments to www-qa@w3.org, the publicly archived list of the QA Interest Group [QAIG]. Please note that any mail sent to this list will be publicly archived and available, do not send information you wouldn't want to see distributed, such as private data.
Publication of this document does not imply endorsement by the W3C, its
membership or its staff. This is a draft document and may be updated,
replaced, or obsoleted by other documents at any time. It is inappropriate to
use W3C Working Drafts as reference material or to cite them as other than
work in progress
.
A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.
You will be able to find a previous public version of this document which was synchronized with the QA Specification Guidelines at that time. QA Specification Guidelines has been drastically modified and this version will be completely different from the previous version.
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
(Under construction, please check back on or after 20021128.)
There is no concept of conformance to this document. Rather, conformance is measured relative to the checkpoints of the companion document, QA Framework: Specification Guidelines[QAF-SPEC]. This document relates real-world examples to the checkpoints' requirements, and also presents techniques by which the checkpoints may be satisfied. In that sense, it defines conformance criteria for the conformance requirements (checkpoints) of the operational guidelines document.
The following QA Working Group and Interest Group participants have contributed significantly to the content of this document:
Added Front and Back content for the Examples and Techniques
Skeleton to start to edit the Examples and Techniques for QA Specification Guidelines.
A version which has been organized to help and define which belongs to the example techniques.
The way it has been organized is slightly different from the QA Operational Guidelines Examples and Techniques which review only 3 Specs. This publication has taken examples in all specifications when the examples were available.
The editing has been made difficult by the verbosity of examples already given in QA Specification Guidelines