Re: Agenda: Jan 26 QA WG teleconf

Hi Dom,

Sorry for the belated email. Is it at all possible to switch days, so  
that I take minutes next week instead of this week? I have a meeting I  
cannot reschedule.

Sorry for the inconvenience.

Best,

/Dimitris

On 26 Jan 2005, at 11:42, Dominique Hazaël-Massieux wrote:

QAWG telecon participants --

   Here is the final agenda for today teleconf.

The principal topic will be SpecGL LC issues resolution; issues list:
http://www.w3.org/Bugs/Public/buglist.cgi? 
query_format=specific&order=relevance+desc&bug_status=__open__&product=Q 
A&content=

Agenda
   =====
   Scribe: Dimitris
   Chair: Dom
   Template: http://www.w3.org/QA/Group/telcon-template.txt
   Regrets from Karl, Lofton, Mark, possibly from Lynne

1.) roll call 11am EDT, membership

2.) routine business
* Technical Plenary registration: please register!
http://www.w3.org/2002/09/wbs/35125/TP2005/registrants#qa

3.) Changing teleconf day back to Monday?
Based on the quick email survey, there seems to be a small preference to
get back to meeting on Mondays. We need to confirm this, and decide the
next meeting dates.

4.) Test FAQ updates:
AI-20050111-03: DH to provide example of TCMS? (not yet done)
AI-20050111-04: TB to provide pointer to CSS Selectors Implementation
Report Template? (integrated in test FAQ?)
AI-20050111-05: DH to provide XSLT stylesheet used in HTML? (not yet
done)
AI-20050111-07: PC to create issues list related to TEST FAQ? (status?)
AI-20050111-08: PC/DH to "formally" publish revised TEST FAQ (with
date/version) in WG space within several weeks (status?)

5.) SpecGL issues
Dom's analysis:
http://lists.w3.org/Archives/Public/www-qa-wg/2005Jan/0074.html

http://www.w3.org/Bugs/Public/buglist.cgi? 
query_format=specific&order=relevance+desc&bug_status=__open__&product=Q 
A&content=
* Classes of products unclear and dagenrous
* Conformance is not a yes/no proposition
* Avoiding device-dependent profiles
* Additions to error mechanism section
* Additions to "write tests"
* Formal vs prose language normativity
* Modesty requirement
Editorial(?):
* Structure/Numbering confusing
* Scope also helps reviewers determine when the specificati...
* Comment about HTML spec examples needs refinement
* Case of RFC2119 terms
* Correction to example about CSS extensibility
* "Identify depreacted features" too strong

   Logistics
   =====
   Zakim bridge: +1-617-761-6200
   11:00am-12noon EST.
   code: 7294 ("QAWG")
   IRC, see: http://www.w3.org/QA/Group/2001/12/07-QA-logistics#telcon

-- 
Dominique Hazaël-Massieux - http://www.w3.org/People/Dom/
W3C/ERCIM
mailto:dom@w3.org

Received on Wednesday, 26 January 2005 15:06:19 UTC