Draft Minutes: Telcon 3 May 2004

QA Working Group Teleconference
Monday, 3 May 2004
--
Scribe: Lynne

Attendees:
(PC) Patrick Curran (Sun Microsystems)
(DD) Dimitris Dimitriadis (Ontologicon)
(KD) Karl Dubost (W3C, WG co-chair)
(DH) Dominique Hazaël-Massieux (W3C)
  (LR) Lynne Rosenthal (NIST - IG co-chair)
(MS) Mark Skall (NIST)

(DM) David Marston

Regrets:
(MC) Martin Chamberlain (Microsoft)
(LH) Lofton Henderson (CGMO - WG co-chair)
(AT) Andrew Thackrah (Open Group)
(VV) Vanitha Venkatraman (Sun Microsystems)

Absent:


Summary of New Action Items: No new action item
AI-20040403-01: Mark to review and modify Extensions text and provide 
definition of extensibility.  7 May 2003
AI-20040403-02:

Agenda:

Previous Telcon Minutes:

Minutes:
1) Rollcall

2.) routine business
- F2F logistics.  Patrick to supply information by Friday.  Dates: June 
15-17, 2004, Santa Clara, CA. Need to create Website at: 
http://www.w3.org/QA/2004/06/f2f.html
  San Jose Airport closest airport.  San Francisco Airport about 45 minutes 
away. There is a train from San Francisco.  CALTrain has a good website.  - 
Publication dates for Spec and Test after Moratorium.  QAH will be 
published May 10. Karl to request publication.

3. SpecLite:
--Overview of SpecLite. Section on Extensions has been updated, new text 
for deprecation and Quality Control has been added.  Comments and examples 
requested.  Current version available 
at:  http://www.w3.org/QA/WG/2004/04/specgl-lite.html
Priority of review should be Extensions.  Karl will provide some examples. 
David may also provide some examples from his experience with XSLT

--Discussion of definitions for Extensions and extensibility.
Karl’s reasons for defining extensions and extensibility.  We need to 
define what we mean by extensible.
Mark: extensions derived because of the IT industry.  Extensible, is 
generic, it is the ability to add things, providing hooks.  Don’t like the 
definition to be so narrow.
Karl: Agree, that it needs to allow for flexibility.  We need to be careful 
that we don’t add confusion.  Should we not define it?
Mark: Recommend not using the word  extensible. If I was writing, I 
wouldn’t use the word.  Will review the text and propose a new definition 
for extensible or extensibility.


4. TestLite:
Patrick will be working with Dimitris on the document.

5.  CR Issue about error handling of specifications.  (Bjoern #29)

Should this be discussed in SpecLite, if so, what error handling should be 
discussed?  Of interest may be, what are the different error handling 
mechanisms used across specifications they know? A Wiki was started on 
this.  The WebArch discusses error handling from an agent viewpoint, not 
from a specification view.  The more examples we have, the more we will be 
able to discuss the various techniques.  Use the mailing list for 
discussion.  Use the Wiki for adding examples. Wiki on 
ErrorHandling:  http://esw.w3.org/topic/ErrorHandling