Action Item from Jun 12-13 AUWG f2f Meeting

Evaluating ATAG2.0 WD (dated 25 Jun 2004) and ATAG2.0 Techniques (dated 25 Jun 2004) against normative principles of QA Specification Guidelines WD 2 June 04. Note: all other parts of QA Specification Guidelines are non-normative.

• Include a conformance clause: Section 2 of the 06-25-04 ATAG2.0 WD describes conformance. The ATAG2.0 techniques also support the idea of conformance in that they suggest ways to meet the success criteria
• Provide the wording for conformance claims: There is some wording as to conformance in Section 2 of the ATAG 06-25-04 WD, and more specific wording in supplementary ATAG conformance evaluation materials related to the developing test suite. Does the WG need to provide more specific wording as to specific conformance claims? The ATAG2.0 techniques may also imply some wording for conformance claims indirectly? (NOTE: I think there is wording in the very latest ATAG2.0 draft Aug 2004?, so this principle may be satisfied now?)
• Define the scope. Describe what the specification is about: There is some introductory text in Section 1 of the 06-25-04 ATAG2.0 WD. Maybe there needs to be more?
• Deal with the likelihood of extensions. Consider whether some parts of the specification will benefit from extensibility. If so, define a mechanism to allow for the extension: Does the 06-25-04 ATAG2.0 WD adequately address extensibility? Would the specification benefit from allowing extensibility? Are there any extensions implied in the ATAG2.0 techniques?
• Prevent extensions from breaking conformance: If extensions are allowed/ addressed by the 06-25-04 ATAG2.0 WD, it would need to be ensured that ATAG conformance is not "broken" by such extensions. Are there any extensions implied in the ATAG2.0 techniques that might "break" conformance?
• Identify each deprecated feature. If there are deprecated features from a previous specification version, let the reader know about them: Are there deprecated "features" from ATAG1.0 to the 06-25-04 ATAG2.0 WD? If so, they need to be identified in ATAG2.0. There probably should be a "change record" between ATAG1.0 and ATAG2.0. Are there any deprecated "features" between the ATAG1.0 Techniques and the ATAG2.0 techniques? Perhaps there should be some sort of "change record" between ATAG1.0 techniques and ATAG2.0 techniques?
• Specify the degree of support required for each deprecated feature and its conformance consequence. Consider the effect of deprecation on all classes of products that implement the specification (e.g., authoring tools, user agents): If there are deprecated "features" from ATAG1.0 that need to be mentioned in the 06-25-04 ATAG2.0 WD, do they still need to be supported? Are there ATAG implementation implications? Is there full "upward compatibility" between ATAG1.0 and ATAG2.0?