Test Task Force Charter comments

Dimitris

Some suggested changes on the TTF Charter.

For Mission I suggest the following reword:
The mission of the QA WG Test Task Force (TTF) is to ensure that guidelines 
in the QA test guidelines documents are put into practice by W3C Working 
Groups.

For Scope, I suggest the following reword and additions.
The TTF scope is to:
·       Ensure the use of practices required by the QAWG Guideline documents.
·       Provide technical expertise to assist and support W3C Working 
Groups in providing Test Materials for their specifications.
·       Find tools that implement the QAWG Guideline techniques and where 
there are none, prototype or participate in the development of a tool.

In addition, the TTF produces in association with others or on its own, 
Test Frameworks to ensure that test materials produced in the W3C Working 
Groups can be used, where applicable, by others.

-Lynne


>>X-Sieve: CMU Sieve 2.2
>>Resent-Date: Thu, 16 Jan 2003 23:46:00 -0500 (EST)
>>Date: Fri, 17 Jan 2003 05:46:47 +0100
>>Cc: ot@w3.org
>>To: www-qa-wg@w3.org
>>From: Dimitris Dimitriadis <dimitris@ontologicon.com>
>>X-Mailer: Apple Mail (2.551)
>>Subject: My action items AI-20030108-2 and AI-20030108-3 (Test Task Force 
>>Charter) completed
>>X-Archived-At: 
>>http://www.w3.org/mid/AFC04BD3-29D6-11D7-9F71-000393556882@ontologicon.com
>>Resent-From: www-qa-wg@w3.org
>>X-Mailing-List: <www-qa-wg@w3.org> archive/latest/1393
>>X-Loop: www-qa-wg@w3.org
>>Sender: www-qa-wg-request@w3.org
>>Resent-Sender: www-qa-wg-request@w3.org
>>List-Id: <www-qa-wg.w3.org>
>>List-Help: <http://www.w3.org/Mail/>
>>List-Unsubscribe: <mailto:www-qa-wg-request@w3.org?subject=unsubscribe>
>>
>>All,
>>
>>Attached please find the new version of the TTF charter, in time for AC 
>>contacts, as requested earlier this week.
>>
>>All minuted changes from the F2F were incorporated (except for the part 
>>on templates of test materials, which I cannot remember having either 
>>voted for or abstained from voting on during the F2F according to an 
>>earlier email to the list).
>>
>>For the archives, I again want to stress that I do not agree that we 
>>should strive for not enforcing that test techniques as defined and 
>>discussed in other QA WG materials be used. Our current wording (on which 
>>we reached consensus during the F2F) is "ensure". I cannot, on the one 
>>hand, understand what makes "ensure" different from "enforce", except if 
>>"ensure" means that we just check for something having been done by 
>>someone else (which means that in order to ensure, someone needs to have 
>>enforced, except for cases where all gets done voloutarily); on the other 
>>I think this is merely words and that it does not really make that big a 
>>difference.
>>
>>Again, I updated the draft as per the minutes, but I want it archived 
>>that I do not agree with this weaker wording. Some group needs to enforce 
>>that things be done, if not this group then some other. However, as this 
>>is my personal view and not that of the QA WG, the TTF charter does not 
>>reflect that.
>>
>>As for AI-20030108-2, assuring uniformity means, as mentioned in the 
>>updated draft, that QA WG "approved" test techniques as per our documents 
>>are used as much as possible (the set of those tools defining uniform use).
>>
>>Olivier, please update the action items list accordingly.
>>
>>/Dimitris
>>
>>
>
>