SVG Tiny 1.2 – 20081222

E Conformance to QA Framework Specification Guidelines


E.1 Introduction

This appendix is informative.

This table is derived from the checklist of all defined requirements and good practices from the QA Framework: Specification Guidelines [QAF-SPEC]. For each requirement and good practice, the table links to the part of the SVG Tiny 1.2 specification that satisfied the requirement or best practice.

E.2 Checklist table

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

E.3 List of deprecated features