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

draft Process document Outline

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Wed, 13 Nov 2002 07:20:20 -0500
Message-Id: <>
To: www-qa-wg@w3.org
DRAFT QAWG Process Document
Status:  This is a draft, detailed outline for a process document.  It 
presents ideas rather than complete, well-constructed sentences and 
paragraphs.  It captures the ideas presented in the first OpsGL draft , 
Karl’s earlier draft 
(http://lists.w3.org/Archives/Public/www-qa-wg/2002Jun/0078.html), as well 
as things that have been mentioned in email and at meetings.

Broken into 2 major sections. The first, Internal Operations, deals with 
process internal to the QAWG (items 1-5 below).  The second, External 
Relationships, deals with external influences  that is relationships with 
external parties (items 6-10 below).  These external parties can be other 
W3C groups or external to W3C, such as OASIS XSLT/XPath committee or just 
interested individuals.

Note: There is no implied order to the rambling text below.


1.      Invited Experts
There are 2 types of invited experts: those with full membership and those 
that are invited to participate on a specific topic.

1.1 Full membership in the WG
- Any WG member can request an expert be invited
- Non-W3C members can petition for membership by contacting the WG chair
- All invited experts must provide their credentials and state their 
ability to meet the WG commitment (attend meetings, 4-8 Hours/ week)
- Who approves acceptance of the expert  the WG votes or the chair decides?

1.2     Topic Experts
- An expert can be invited to participate in discussions and meetings on a 
specific topic.   - There are no membership commitment requirements.
- Any WG member can request the invitation and must present the credentials 
of the expert.
- The chair does the inviting, after the WG approves.
- Topic experts do not need to follow WG participation rules.  @@@ should 
they be limited in their participation  e.g., not invited to attend all 

2.      Quorum
- A quorum consists of having at least 1/3 the members present.
- Decisions can only be made if a quorum is present; else the decision is 
considered a preferred action or direction and not closed.  This applies to 
at least the following:
--- all votes, (note that the voting process is described in the Charter)
--- resolution of issues,
--- changes in the WG’s operation or process

3.      Notices - awareness of actions
3.1     Within the WG
- When an action item or assignment results in an unexpected change or 
modification to fulfill the assignment, it must be called to the attention 
of the WG.
- Announce and if necessary, present an overview of the change at a 
telecon. Not only does this ensure that the WG is aware, but it is also 
documented in the minutes.
- Examples:  Reformatting the OpsGL to look like the SpecGL.  Writing an 
issue resolution from a general agreement of what needed to be done.

3.2     To the IG
- When does something get publicized to the IG
- All deliverables get announced to the IG.  When?

4.      Action Items
Upon completion, email to AI editor with AI #.

5.      Issue processing
5.1     What becomes an issue?
- Issues pertain to the Framework Guidelines (intro, ops, spec, test) and 
their companion ExTech documents, process, and any other WG deliverables
- @@@ Do all comments on a document become issues?
- Issues are derived from comments received in email and/or from meeting 
- All comments on documents must be acknowledged, reviewed and if 
warranted, made into an issue, resolved, and commenter informed.  This 
includes comments from within the WG, IG, and public.

5.2 Roles and responsibilities
-Originator  either WG member or external party
         Sends in a comment or inquiry that results in an issue
-Chair (document editor?)  receiver of the issue.
Starts the process, puts issue discussion on agenda, and assigns ownership
- Owner  member of the WG who is responsible for the issue (may not be the 
  - Acts as liaison, if submitted by external party. If needed, formats the 
issue, presents it for discussion, contacts the originator regarding 
- Issues Editor  owns the Issues List

5.3 WG Actions
- The telecon following the receipt of a comment or inquiry is the start of 
the issue tracking.  The chair (or document editor) initiates the issue 
- The WG determines if this really is an issue, and if so, the Issues 
Editor enters it into the Issues List.  If the issue isn’t in the proper 
format, the task of formatting the issue can be delegated.
- Each issue is assigned an owner, who is responsible for ensuring the 
issue is processed.
If the comment is made from a member of the WG, then that member becomes 
the owner, else the chair or editor assigns an owner.  For issues received 
from non-WG members, the owner acts as liaison between the external party 
and the WG.  The owner sends an acknowledgement to the external party 
regarding receipt of the comment and provides the issue number and url of 
the issues list if appropriate, and upon resolution, informs the external 

- Issues are categorized and prioritized.  The chair or document editor 
decides the priority and requests time on a meeting agenda for 
discussion.  Issues can be discussed via email but resolved at meetings 
(telcon or f2f).  It may be necessary to continue discussions beyond a 
single meeting.  It may be necessary to assign an action item to a WG 
member to get more information and/or discuss the issue with the Team contact.

- When there is consensus on the outcome of the issue, a resolution is 
written and recorded in the Issues List. The Issues Editor can either write 
the resolution or delegate it. The issue is marked as closed.

5.4 Acknowledgements
- The issue owner informs the originator that the issue has been 
resolved.   This is an important step, especially when the originator is 
not a WG member.
- The WG is informed of updates to the Issues List by either announcing 
this at a meeting so it appears in the minutes or sending email to the QAWG 
mailing list.  Periodically, email is sent to the IG list to inform them of 
updates to the Issues List

5.5     Reopening Closed Issues
Once an issue is closed, the chair or editor rules on requests to reopen or 
continue arguments on closed issues (remember issues can only be closed if 
there was a quorum present when closed).  There must be new evidence 
uncovered or altered situation in order to reopen


Potential relationships with other W3C WGs include: (taken from the OpsGL)
--- Liaison and consultation,
--- reviews,
--- adjudicate entry and exit criteria,
--- QA resources supplement,
--- Resolution of external QA requests

6. Communiqués
- There are different types of communiqués - some more formal than others.
Communication with QAWG may be received as email to the chair, email to the 
WG mail list, IG mail list, or from a verbal request.

- All questions or inquiries must be answered.
- Any WG member can answer, however chair or chair’s designee is 
responsible for making sure the WG responds with some type of 
acknowledgement or answer.

7 Review of W3C Recommendations
An important function of QAWG is to review W3C work with QA issues in 
mind.  This is done as early as possible, at the charter stage, during the 
document process, and during the development of conformance materials.  The 
QAWG when resources are available will review and provide guidance to WGs.

7.1 How QAWG responds to requests
- Requests can be handled on a case by case basis  with the chair bringing 
the request to the attention of the QAWG.  Alternatively, the QAWG can 
appoint a team to handle all incoming requests.
- All requests are put on the agenda for the next meeting, where they are 
introduced and preliminary action is taken.
- Chair solicits interest.  A subgroup is formed and a leader is 
appointed.  A subgroup can consist of 1 person.  If there are no 
volunteers, the chair can appoint someone.
- If there is no one available that can do the review in the allotted time 
frame and/or this is outside the expertise of those who are available, the 
chair responds that the QAWG doesn’t have the resources or expertise to 
perform the review.

7.2 Actions
- If a subgroup is formed, the group makes comments. These comments are 
submitted to the QAWG for review and approval.  When approved, the comments 
are sent as QAWG comments.   The QAWG can waive review and allow the 
subgroup to send the comments directly as QAWG comments.  If time doesn’t 
permit a QAWG review, then the comments can be sent as an individual comment.
- Review of technical documents and test materials includes verifying that 
the checkpoints of the appropriate QA Framework documents are met and 
providing guidance to the requestors on how to meet the checkpoints.

8. Provide direct assistance
- QAWG is a source of information  people come to for guidance and tools.
- May get requests to help build conformance materials, including drafting 
documents or conformance sections and developing test suites.
- Upon receipt of request, chair evaluates the request, estimating the type 
of resources and expertise needed, and duration of effort.  Chair can 
appoint someone to do this. Present to QAWG, who then decides if we can do 
it.  If yes, a person or subgroup is formed to assist.  If no, the chair 
informs the requester.

9. Request from external organizations to submit test suites to W3C groups
- QAWG acts as liaison and facilitator between external organization and 
appropriate W3C WG.  Puts the right people in contact with each other.
- May need to ‘translate’ conformance terminology and technology for the 2 
- Provides lessons learned and examples from other groups that have already 
been through this.

10 Increase awareness of QA issues
- Asked to participate in or present QA to other groups and conferences.
Goal = education and outreach by
-Collaborate with other groups
-present work at conferences
-participate in other groups (WG, IG, etc) meetings, including workshops to 
establish a group.
Received on Wednesday, 13 November 2002 07:26:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:29 UTC