[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

computer-go: Re: Need help building Graded Gnu Go Problem Database



Pierce wrote:

> A while ago, there was a discussion about Graded Go Problems for 
> Beginners....
> 
> The problem with using GGPFB is that the problems are copyrighted...
> 
> So I asked Thomas Wolf the author of GoTools if he would be willing to 
> make a small fraction of his 24,000 problem set available as part of a 
> public domain benchmark for go program developers.
> 
> He agreed! He's willing to make somewhere between 500-1000 problems 
> available. Which is really cool, as the computer-go world will be able 
> to have a standard set of problems they can exchange. I'll put them 
> under the LGPL (Library Gnu Public License or "Lesser" GPL) so its clear 
> that by including them your program doesn't be come public too...
> 
> That was a month ago (I took time off to learn perl to parse his problem 
> database).
> 
> Now here's the rub: I need to now filter this problem set down to size 
> (from 24,000 problems down to 500-1000 problems). I've also found that 
> SGF isn't the best format for problem sets.

I just heard a lecture by Tristan Cazenave in which he proposed
ideas for a testsuite which would be of more general utility
than the testsuite we distribute. Perhaps he will comment on
this development. A subset of the GoTools problems would
indeed make a good cornerstone for such a testsuite.

It seems to me that a reasonable format would be that of the
GNU Go testsuite, a combination of SGF files and GTP files
stating the problem. The ``owl_attack'' and ``owl_defend'' GTP
commands should then be renamed something less GNU Go specific.

> As the problems are more static works, rather than source code which is
> expected to evolve and perform a function, applying the [L]GPL is an
> awkward fit, since much of the language in those licenses is peculiar to
> the issues of software.

Indeed, the LGPL does not seem to be the right license. It
contains the following definition:

  A "library" means a collection of software functions and/or data 
  prepared so as to be conveniently linked with application programs 
  (which use some of those functions and data) to form executables.

Your problem set will not be a library by this definition. 

Does Thomas Wolf have any input as to the selection of the
problems or the choice of license?

Daniel bump