W3C home > Mailing lists > Public > www-dom-ts@w3.org > June 2001

SV: Recap and action items

From: Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
Date: Sun, 10 Jun 2001 19:24:52 +0200
Message-ID: <9F67DC27F4CCD311ABA600508B6A66A44A67AB@VXOIMP1>
To: "'Arnold, Curt'" <Curt.Arnold@hyprotech.com>, "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
My understanding of what we're doing is that people will not take the
transorm and change it. If they want another transform, they'll probalby
write it. Another ambition we have is to provide as many transforms as
possible (except for the two default ones, Java and ECMA) in order to
increase use.

-----Ursprungligt meddelande-----
Från: Arnold, Curt [mailto:Curt.Arnold@hyprotech.com]
Skickat: den 7 juni 2001 23:57
Till: 'www-dom-ts@w3.org'
Ämne: RE: Recap and action items


I think http://home.houston.rr.com/curta/domtest/domtest.zip is my latest
schema and http://home.houston.rr.com/curta/domtest/test2java.xsl is my
latest transform.

Definitely if the DOM TS provides something like the test2java.xsl
transform, 
that must be under the Software notice so that people can modify it to other
languages and other frameworks.

I'm thinking that the tests might be more appropriate 
under the software notice also.  The Document license goes into
a lot of detail on the process to translate a Document into another human
language (prior approval, etc) which would be conceptually similar to
translating tests into a specific computer language.  Maybe the
document license with a specific grant of rights to generate code
from the tests would both preserve the sanctity of the "official"
test suite and still let people run the tests on arbitrary
languages and frameworks.

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.

Any bug tracking system that allows attachments would be adequate 
for the test submission process.  Options are:

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.

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.
Received on Sunday, 10 June 2001 13:25:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:44 GMT