W3C home > Mailing lists > Public > www-qa-wg@w3.org > February 2003

RE: 2/24 telecon & TM license issue [2nd]

From: Kirill Gavrylyuk <kirillg@microsoft.com>
Date: Sun, 23 Feb 2003 21:43:50 -0800
Message-ID: <37DA476A2BC9F64C95379BF66BA2690206F492DD@red-msg-09.redmond.corp.microsoft.com>
To: "Lofton Henderson" <lofton@rockynet.com>, <www-qa-wg@w3.org>
Cc: "Joseph Reagle" <reagle@w3.org>

Looking at all of the threads we had so far, I would suggest the
following break-out of the Test License discussion agenda item:

1. Discuss the nature of test materials (terminology)
1.1. test cases (I call them documents)
1.2. test software/harness (I call them software)
1.3. Granularity - is test collection treated by a License as a whole or
in parts? 

2. Discuss Common license requirements for test materials. What are the
risks and how are they mitigated?
2.1. warranties/liabilities
2.2. scope of use
2.3. redistribution
2.4. modification/derivation work
2.5  Link (invoke, apply)

3. Usage scenarios for Test Materials (from Patrick's email)

> -----Original Message-----
> From: Lofton Henderson [mailto:lofton@rockynet.com]
> Sent: Saturday, February 08, 2003 9:52 AM
> To: www-qa-wg@w3.org
> Cc: Joseph Reagle
> Subject: 2/24 telecon & TM license issue [2nd]
> [Sorry, forgot to copy Joseph first time...]
> The issue of licenses for test materials will be discussed on our
> 24-february QAWG teleconference.  The purpose of this session is to
> and clarify requirements for licenses, or at least to begin that
> process.  Defining a policy and/or legal word-smithing are
> for
> this session.
> Anyone who has an interest in this, please speak to your company
> beforehand and come to the call ready to discuss your requirements and
> corresponding scenarios with respect to three issues, which Joseph has
> extracted from the email discussion to date:
> 1. warranties/liabilities: is there anything wrong specifically with
> text in the software license?
>    http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
> 2. scope of use: why must scope be constrained, what abuse are we
> to
> prevent, how will the scope be defined and tested against?
> 3. redistribution: is there any requirement (scenarios?) where we need
> prevent the test suite from being redistributed (e.g., distributed
with a
> toolkit, or mirrored even) under the same license, of course, from
> it
> was obtained from the W3C?
> These issues need to be considered in the context of the need to
> distinguish between the license under which you want to use a test
> versus contribute materials to a test suite.
> Sending email to the QAWG list beforehand would facilitate
> discussion.  (Note that we can spend at most half of the telecon on
> topic, as we have final pre-Boston outreach kit stuff to discuss as
> Regards,
> -Lofton.
Received on Monday, 24 February 2003 00:44:29 UTC

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