Log of changes for QA Framework: Specification Guidelines

This document compiles the list of changes for the document QA Specification Guidelines (latest version).

History of changes

April 2005

20 April 2005

• Removed the example of the issue 1148
• Added prose for the issue 1149

18 April 2005

• A new clean version of the document has been created.
• The history of changes has been removed from the document to be put in this document.
• The text of section 3.3 about other potential topics that the Group should consider has been added
• Modified the introduction to add the reference to the numbering scheme and the history of changes.
• Added the CHARMOD in the list of references.
• Added the XAG in the list of references.

March 2005

17 March 2005

• Fixed the references to Good Practices and section with the new numbering scheme
• Edited the text for RFC2119 Issue 1044
• Added table with old classification
• Finishing the numbering Scheme of everything.
• Editing the part 1.2 A, 1.2 B, 1.2 C

16 March 2005

• Modifying the numbering Scheme of everything.
• Moving Appendix in a section Beyond Conformance, New section 3
• Conformance section becomes, section 4
• Move 5 GP E as GP 07 in 2.2.1 Scope (not logical)
• Rewrite Formal Language in section 2.3.2 What's mandatory

15 March 2005

• Fixing glossary

9 March 2005

• 1144: Creation of the appendix for Publication Workflow

8 March 2005

• 1040: Done. change structure/numbering
• 1042: Done. Added prose for the scope for reviewers
• 1043: Done. Added a "some" in the prose of the HTML 4.01 example
• 1046: Done. Change the example text from CSS 3.0 to CSS 2.1
• 1047: Done. Added new prose for error mechanism
• 1048: Done. Added the sentence for error.
• 1052: Done. editorial changes
• 1060: Done. Added text to replace Umbrella Specification

October 2004

• 2004-10-14 Fixed section 4 (old D)
• 2004-10-14 Fixed section 3.1 (old C.1)
• 2004-10-14 Changed numbering the document.
• 2004-10-14 Fixed section 1.2 (old A.2), 2.1 (old B.1)
• 2004-10-14 Added Conformance Keywords to the conformance clause.
• 2004-10-13 Renumbered only A.1 into 1.1 following suggestions of Lynnen if it's easier to read.
• 2004-10-13 Added Suggestions and Rewording of Lynne for Introduction.
• 2004-10-13 Added Suggestions and Rewording of Lynne for Section A.1 or 1.1.
• 2004-10-08 Started to add the references to the old CR Checkpoints. Stopped at C.1-GP_14
• 2004-10-08 Fixed the wording of Principles and Good Practices following the recommendation of the QA WG Teleconf 2004-10-04.
• 2004-10-08 Added Designation numbering
• 2004-10-04 Created the new Editor's Draft version and CSS rules ins, del and cr-cp to help to figure out the changes. cr-cp will is used to show the text that was used in the CR version of SpecGL. Use it with a div.

August 2004

• 2004-08-26 Finished the ICS, created an entry for the TOC
• 2004-08-26 Added definitions for Profiles, Modules and Levels.
• 2004-08-26 Fixed glitches, add prose here and there, fixed the citations.
• 2004-08-25 Added examples Define rules for creating profiles
• 2004-08-25 Added examples Indicate any limitations or constraints
• 2004-08-25 Added techniques Define rules for creating profiles
• 2004-08-25 Removed empty related from the If the technology is subdivided, then indicate which subdivisions are mandatory for conformance
• 2004-08-25 Fixed figure
• 2004-08-25 Removed empty related from the Explain which conformance requirements are mandatory, which are suggested and which are optional. Added the example.
• 2004-08-25 Removed empty related from the Use a consistent style for conformance requirements and explain how to distinguish them
• 2004-08-25 Removed empty related from the Re-use existing terms, and don't redefine them and added example about QA Spec Guidelines.
• 2004-08-25 Removed empty related from the define the terms in-line, and consolidate the definitions in a glossary section and fixed the technique prose.
• 2004-08-25 Removed empty related from the Create conformance labels for each part of the conformance model
• 2004-08-25 Removed empty related from the Define the terms used in the normative parts of the specification and polished the prose.
• 2004-08-25 Removed empty related from the Identify who or what will implement the specification
• 2004-08-25 Use examples or use cases to illustrate Lynne?
• 2004-08-25 Removed empty related from write simple, direct statement in the scope
• 2004-08-25 Removed empty related from the Define the scope
• 2004-08-25 Provide an ICS to be reviewed on the ML. Karl to write.
• 2004-08-25 Require ICS in claim to be reviewed on the ML
• 2004-08-25 Conformance Clause related and examples section
• 2004-08-25 Conformance Clause related and examples section
• 2004-08-25 Checking Intro and references.
• 2004-08-24 Creation of Implementation Conformance Statement. Need to make links in the text
• 2004-08-24 Table of Contents done
• 2004-08-24 Status section rewritten
• 2004-08-24 Patent Policy done
• 2004-08-24 fixed the URIs for the publication and the date
• 2004-08-24 Changed David Marston affiliation in acknowledgements (See Mail)
• 2004-08-24 Section D2. Optionality (See Mail thread)
• 2004-08-24 Issue Björn Höhrmann, B3. Make a list of normative references (See Mail thread)
• 2004-08-24 Section B2. What Must conform (See Mail thread 1, Mail Thread 2)
• 2004-08-24 Issues by David Marston about organization of modules and levels, for example what's a core module. Should it be explained in Spec GL or in ViS? (See Mail Thread)
• 2004-08-24 Issues by David Marston about Conformance section and content (See Mail Thread)
• 2004-08-24 Issue by Lynne Rosenthal Normative/informative labelling. How do we label? Which level of details? (See Mail Thread)
• 2004-08-24 Rewriting Conformance Clause as proposed by Lynne. (See Mail thread 1, Mail Thread 2)
• 2004-08-24 Issues Lofton Henderson with regards to 1. In the conformance clause, define how normative language is expressed. (See Mail thread)
• 2004-08-24 Issues David Marston with regards to A2. wording for conformance claims. (See Mail)
• 2004-08-23 Added Informative references… again
• 2004-08-19 Added Informative references
• 2004-08-19 Fixing typos.
• 2004-08-19 Rewriting Principles for Subdivision to simplify conformance. (Mail Thread)
• 2004-08-18 Added Informative references
• 2004-08-17 Started to look for informative references
• 2004-08-17 Modified the Markup for headings
• 2004-08-16 Added wording for conformance section
• 2004-08-16 Added example for formal language
• 2004-08-11 Added example for quality control
• 2004-08-11 Fixed the markup for Good Practices and Principles so now, that the prose is part of the heading, more semantically correct.
• 2004-08-11 B.1 GP Write simple, direct statements in the scope. (Mail Thread)
• 2004-08-11 B.1 Principle:  Define the scope. (Mail Thread)
• 2004-08-11 B.1 Scope (Mail Thread)
• 2004-08-10 A.1 Include a conformance Clause + Intro (Mail Thread)
• 2004-08-10 Removed A.1 In the conformance clause, define how normative language is expressed (because it seems to be redundant with C.2) See thread
• 2004-08-10 A.2: Provide the wording for conformance claims. (Mail thread)
• 2004-08-10 A.1: Define the specification conformance model in the conformance clause (Mail Thread)
• 2004-08-10 A.1: Specify in the conformance clause how to distinguish normative from informative content. (Mail thread)
• 2004-08-09 D.5: Error handling (Mail Thread)
• 2004-08-09 C.2 Explain which conformance requirements are mandatory, which are suggested and which are optional (Mail thread)
• 2004-08-09 C.2 Use a consistent style for conformance requirements and explain how to distinguish them (Mail thread)
• 2004-08-09 Remove the old C.2, old C.3 has became the new C.2 (Mail Thread)
• 2004-08-09 D.1 Added the two lists of benefits and drawbacks CSS to make them two columns + graph to illustrate (Mail thread)
• 2004-08-09 C.1 define the terms in-line, and consolidate the definitions in a glossary section (Mail thread)
• 2004-08-09 D.1 Address subdivision conditions or constraints (Mail Thread)
• 2004-08-09 C.1 Define the terms used in the normative parts of the specification (Mail Thread)
• 2004-08-09 C.1 re-use existing terms, and don't redefine them (Mail Thread)
• 2004-08-09 C.1 Create conformance designations for each part of the conformance model (Mail Thread)
• 2004-08-09 Fixing a few things for patent policy etc
• 2004-08-09 Added D1. Define rules for creating profiles (Mail Thread)
• 2004-08-09 Added D1. Indicate which subdivisions are mandatory for conformance (Mail Thread 1 - Mail Thread 2)
• 2004-08-09 Added D1. Subdivide the technology to foster implementation (Mail Thread)

July 2004

• 2004-07-27 Added Good Practice: Write Test Assertions. (Mail Thread)
• 2004-07-27 Added Good Practice: Write sample code or tests. (Mail Thread)
• 2004-07-27 Added Good Practice: Do a systematic and thorough review. (Mail Thread)
• 2004-07-27 Added D.4 Deprecation intro (Mail Thread)
• 2004-07-27 Updated the glossary, added deprecated and obsolete, added id to definition items
• 2004-07-27 Included Define how to handle each deprecated feature (Mail Thread)
• 2004-07-27 Included Explain how to avoid using a deprecated feature (Mail Thread)
• 2004-07-27 Included Identify obsolete features (Mail Thread)
• 2004-07-27 Included Identify each deprecated feature (Mail Thread)
• 2004-07-26 Review and Write something about Normative References. Section B3. Owner Karl. Issue Björn Höhrmann
• 2004-07-26 Included Address the extensibility topic inside specification. (Mail Thread)
• 2004-07-26 Included Define error handling for unknown extensions. (Mail Thread)
• 2004-07-26 Included Define the extension mechanism (Mail Thread)
• 2004-07-26 Included Do quality control during the specification development. (Mail Thread)
• 2004-07-26 Modified guideline.css style sheet and HTML Markup to take into account Susan Lesch's comment

June 2004 - QA WG F2F in Santa Clara

• The sections have been distributed among QA WG members. Give the list of sections and their attributions.
• Templates for editing SpecGL Lite.