QA Specification Guidelines - Implementation Report

Summary

Guidelines	HTML 4.0.1	Ruby Annotation	SVG 1.1	CSS 2.1	Semantic Interpretation for Speech Recognition	XML:id	SVG Tiny	Spec GL
Requirement 01: Include a conformance clause.	yes	yes	yes	yes	yes	yes	yes	yes
Requirement 02: Define the scope.	yes	yes	yes	yes	yes	yes	yes	yes
Requirement 03: Identify who or what will implement the specification.	no	yes	yes	yes	yes	yes	yes	yes
Requirement 04: Make a list of normative references.	yes	yes	yes	yes	yes	yes	yes	yes
Requirement 05: Define the terms used in the normative parts of the specification.	yes	yes	yes	yes	no	yes	yes	yes
Requirement 06: Create conformance labels for each part of the conformance model.	no	yes	yes	no	yes	yes	yes	yes
Requirement 07: Use a consistent style for conformance requirements and explain how to distinguish them.	yes	no	yes	yes	yes	yes	yes	yes
Requirement 08: Indicate which conformance requirements are mandatory, which are recommended and which are optional.	yes	yes	yes	yes	yes	yes	yes	yes
Requirement 09: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance.	na	yes	na	yes	yes	na	yes	na
Requirement 10: If the technology is subdivided, then address subdivision constraints.	na	yes	na	yes	yes	na	yes	na
Requirement 11: Address Extensibility.	no	no	yes	yes	no	yes	yes	yes
Requirement 12: Identify deprecated features.	yes	na	no	yes	yes	na	na	na
Requirement 13: Define how each each class of product handles each deprecated feature.	yes	na	no	yes	yes	na	na	na
Good Practice 01: Define the specification's conformance model in the conformance clause.	no	yes	yes	yes	yes		yes	yes
Good Practice 02: Specify in the conformance clause how to distinguish normative from informative content.	no	no	no	no	yes		yes	yes
Good Practice 03: Provide the wording for conformance claims.	no	no	no	no	no		no	yes
Good Practice 04: Provide an Implementation Conformance Statement Pro Forma.	no	no	no	no	no		no	yes
Good Practice 05: Require an Implementation Conformance Statement as part of valid conformance claims.	no	no	no	no	no		no	yes
Good Practice 06: Provide examples, use cases, and graphics.	yes	yes	yes	yes	no		yes	yes
Good Practice 07: Write sample code or tests.	na	yes	yes	yes	yes		yes	yes
Good Practice 08: When imposing requirements by normative references, address conformance dependencies.	na		na	yes	na		no	na
Good Practice 09: Define the unfamiliar terms in-line, and consolidate the definitions in a glossary section.	yes	yes	yes	yes	no		no	yes
Good Practice 10: Use terms already defined without changing their definition.	yes		na	no	na		no	yes
Good Practice 11: Use formal languages when possible.	na	no	yes	yes	yes		yes	na
Good Practice 12: Write Test Assertions.	no	no	no	no	yes		no	no
Good Practice 13: Create subdivisions of the technology when warranted.	na	yes	yes	yes	yes		yes	na
Good Practice 14: If the technology is profiled, define rules for creating new profiles.	na	na	no	no	na		no	na
Good Practice 15:Use optional features as warranted.	na	yes	na	yes	na		yes
Good Practice 16: Clearly identify optional features.	na	yes	yes	yes	na		yes	yes
Good Practice 17: Indicate any limitations or constraints on optional features.	na	yes	na	yes	na		yes	yes
Good Practice 18: If extensibility is allowed, define an extension mechanism.	na	no	yes	no	na		yes	yes
Good Practice 19: Warn extension creators to create extensions that do not interfere with conformance.	na	no	no	no	na		no	yes
Good Practice 20: Define error-handling for unknown extensions.	yes	no	no	yes	yes		yes	na
Good Practice 21: Explain how to avoid using a deprecated feature.	yes	na	na	no	yes		na	na
Good Practice 22: Identify obsolete features.	yes	na	na	yes	yes		na	na
Good Practice 23: Define an error handling mechanism.	yes	yes	yes	yes	yes		yes	na