- From: Robin Berjon <robin@berjon.com>
- Date: Thu, 31 Mar 2011 16:04:42 +0200
- To: Arthur Barstow <art.barstow@nokia.com>
- Cc: public-webapps <public-webapps@w3.org>
On Mar 31, 2011, at 14:04 , Arthur Barstow wrote: > 1. What is the level of uptake of testharness.js within the HTML WG and other WGs? If any of these groups provide "usage" information, what are the URIs? Do any WGs make testharness.js's use Mandatory? Currently, its usage in the above documents makes its usage a "Should". DAP hasn't yet started writing tests in earnest, but as some of our documents are nearing LC we're getting ready for it. We've resolved to use testharness.js as well. We haven't captured it as a MUST, but given that we have a bunch of specs and that we expect work to be distributed to many people we expect to use it throughout — so pretty much a tacit MUST. > 2. What, if any, requirements/guidelines are there regarding copyrights in test files? For example, does every file in a test suite need a W3C copyright? Are external contributors allowed to include their own copyright(s)? My understanding is that the W3C Test License (under which tests have to be released) essentially is a copyright license, which I'm guessing precludes other copyrights (as well as derivative works in many situations). I could be wrong though — it's probably worth asking Rigo. There's precedent for test suites being done externally, notably the XML test suite was largely created by OASIS. A quick look through it couldn't find any licensing or copyright information though, so it might just have been built on warm fuzzy feelings (as most good things are). http://www.w3.org/Consortium/Legal/2008/04-testsuite-license.html -- Robin Berjon - http://berjon.com/
Received on Thursday, 31 March 2011 14:05:12 UTC