> [ca] The SourceForge Project page will only say that the license is "Other".
> On the test submittal mockup, I used a placeholder for a statement of the
> test process IPR. That text could be anything that you want it to be. Any
> download (.zip, etc) should have the full statement of IPR. Should each test
> have a "Copyright (c) 2001, MIT..." boilerplate?
Yes, they should.
"Arnold, Curt" wrote:
> >From the DOM Conformance Test Process Document:
>
> The W3C Document Notice and License will apply for the DOM Test suites.
>
> ----------
>
> This would require those notices to get removed before submission. However,
> I can see some issues with those statements.
>
> First, wouldn't the Software Notice be more appropriate? With the Document
> Notice, you couldn't make deriviative works, even if your intent
> was to submit the test back to the work group. Also, generating testing
> code for a specific language might be problematic under the document
> license since that could be considered a deriviative work.
No. The tests will be endorsed by the W3C and therefore, you won't be allowed
to modify them and still claim conformance with the test suites. NIST and W3C
agreed that the W3C Document Notice and License is the appropriate one. Note
that I said the tests, not the framework used to produce them. The
user/developer must be able to download the tests from the W3C web site
http://www.w3.org/DOM/Test and check his implementation for DOM conformance.
> http://www.w3.org/Consortium/Legal/IPR-FAQ-20000620.html#holds
> would indicate that the original author could maintain the
> copyright as long as the W3C license is asserted.
>
> [dd] You're right, let me investigate this. Thanks for pointing it out.
I sent a note to our copyright expert asking to consider the proposal.
> I think the test "repository" needs to be in CVS and the W3C
> CVS server seems more "official" than a non-W3C CVS server would.
This service is already online: http://dev.w3.org/cvsweb/
> Bugzilla/Jitterbug/SF Tracker or other hosted by W3C, NIST, Apache, Mozilla
> or other.
> SourceForge Tracker within the xmlconf project or within a DOM TS related
> project.
Just had a discussion with our System manager. It is possible to install and
setup a SF server in the w3.org domain. There is a Bugzilla system in the W3C
but we're still testing it so it is not ready yet.
> Though the bug tracking system isn't the meat of the test suite.
> It would be a useful thing to have fairly long lived, but it needs
> to come alive quickly.
Depending on how hard it is to setup the SF system, I could do it at the end of
next week after the DOM face-to-face if I get the formal approval from Tim. I
just need the go-ahead from th TS
Philippe