W3C home > Mailing lists > Public > www-qa-wg@w3.org > April 2002

Ops-Extech Overview

From: Lofton Henderson <lofton@rockynet.com>
Date: Thu, 18 Apr 2002 11:45:00 -0600
Message-Id: <5.1.0.14.2.20020418113007.0402aec0@rockynet.com>
To: www-qa-wg@w3.org
QAWG Participants --

This is a brief overview about the topic #3 in the 4/18 telcon agenda, 
Ops-Extech plans.  The first draft of Ops-Extech is at [1].  The structure 
we propose is reflected in this draft:

a.) We will base the examples initially on DOM, SVG, XML, and (we hope) XSLT.

b.) There will be an introductory chapter that gives an overview/summary of 
the QA  and TS activities of each of these -- each in its owns subsection.

c.) Following each Guideline, there will be a brief prose summary of how 
each of these (each in its own subsection) relates to the guideline.

d.) Following each Checkpoint, there will for each of these specific 
comments about how they relate to the checkpoint, whether they satisfy it 
or not, and how.

e.) Each checkpoint will be hyperlinked (bi-directionally) between Ops 
Guidelines and Ops Extech.

f.) Eventually, for each Checkpoint, we would try to derive a list or set 
of valid ways to satisfy the checkpoint -- "verdict criteria".

We think that we can have a pretty good job done for a-e  by mid-May, but 
probably cannot make much progress on #f by mid-May.

So the questions:

1.) Do we approve of this overall structure and approach for Ops-Extech?

2.) Do we approve to go to FPWD in mid-May, with a-e done but #f not done 
("pending")?

Regards,
-Lofton.

[1] http://www.w3.org/QA/WG/2002/framework-20020405/qaframe-ops-extech
Received on Thursday, 18 April 2002 13:44:52 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:09 GMT