Final minutes: QA WG Telecon of 21-Dec-2004

QA Working Group Teleconference
Wednesday, 21 December 2004

Scribe: Lynne

Attendees:

(TB) Tim Boland (NIST)
(PC) Patrick Curran (Sun Microsystems)
(KD) Karl Dubost (W3C, Chair)
(LH) Lofton Henderson (CGMO)
(LR) Lynne Rosenthal (NIST)
(MS) Mark Skall (NIST)

(DM) David Marston (IBM)

Regrets:
(DH) Dominique Hazaël-Massieux (W3C)
(DD) Dimitris Dimitriadis (Ontologicon)
(RK) Richard Kennedy (Boeing)

Absent:

Summary of New Action Items:
AI-20041221-01:
AI-20041221-02:
AI-20041221-03:

Agenda: 
<http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0047.html>http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0047.html
Previous Telcon 
Minutes: 
<http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0057.html>http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0057.html

Minutes:
1) Roll call
2) Routine Business
Next teleconferences:
             29 Dec – cancelled.
             5 Jan – discuss implementation report status and results
             12 Jan – Topic open
             19 Jan – cancelled
             26 Jan – review of SpecGL issues (Last Call ends 28 Jan)
Tech Plenary – registration open.

3. Versioning (Lynne and Karl lead)
Should we address versioning?  Agreed that we will not include versioning 
in current version of SpecGL. However, we should address it and can start 
working on it now. It can be included in either future SpecGL, working 
papers and/or Wiki.  There is overlap with the TAG – will need to 
distinguish what would be our value added in addressing versioning.

Discussion: David is in favor of exploring versioning and including more in 
a future SpecGL.  It is type of DOV.  Since we already have deprecation, we 
already have touched a bit on versioning [1].  Lynne agrees that it is a 
good next topic for the WG and wants to make sure there is value added 
between what we do and what the TAG addresses.  Karl gave background and 
also, via examples (CSS) showed how this is a real problem that needs to be 
addressed.  It makes sense to address the ability of a spec to move forward 
and have next version and how do you organize the technology.  How do you 
put versioning into a document that doesn’t have versioning (e.g., CSS) For 
example, the  parser doesn’t know which version of CSS it is using – no 
clear indicator.

Overlap with the TAG.  Spec should address how to handle versioning.  Not 
understand how this is applicable to all specifications, e.g., WCAG – how 
does it apply when looking at content.  Understand how this applies to 
markup language.  May not apply to every type of specification.

4. FAQ: Test Document. (Patrick lead)
New draft FAQ circulated [3].  Patrick reviewed document, pointing out 
differences between this version and the previous version, as well as 
reviewing the last several questions.  Continue working on document which 
will eventually be published in QA space.

Discussion: Ways to indicate progress – some groups use A+, but have 
abandoned this.  Another way is to indicate the absolute number of 
tests.  You are either conforming or you are not.  Only way to explain this 
well, is to open the question of certification. Patrick will add an 
additional question on branding.  There are W3C icons – the right to put an 
icon on a web page. Self-certification.

Where we go with this? Is this the right level of detail?  Need more 
examples, e.g., here is an example of a WG that has done this, point to 
templates, other existing tools.  Will be published in QA space.

5. Adjourn.


[1] 
<http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0035.html>http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0035.html
[2] http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/0042.html
[3] 
<http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/att-0046/TestFAQ-20041221.html>http://lists.w3.org/Archives/Public/www-qa-wg/2004Dec/att-0046/TestFAQ-20041221.html