EGCG 9.0 and beyond

Peter Rice pmr at sanger.ac.uk
Sat Mar 22 06:22:25 EST 1997

In article <333102D3.6E46 at igbmc.u-strasbg.fr> Frederic PLEWNIAK <plewniak at igbmc.u-strasbg.fr> writes:
>>C.  Use of SDK Source Code; Use and Distribution of Derivative Works. GCG
>> grants to Customer a nonassignable, nonexclusive perpetual license:
>>(i) to adapt the SDK Source Code to create derivative works containing the
>        ^^^^^         ^^^^^^^^^^^                            ^^^^^^^^^^^^^^
>>   SDK Source Code (the "Derivative Works");
>    ^^^^^^^^^^^^^^^------------^

>If I'm not mistaken, the "Derivative Works" are defined here as "works 
>containing the SDK Source Code", not as original programs making calls 
>to GCG libraries. The way I read this section, such original works could 
>still be distributed (binaries only?). Am I wrong? 
>I guess that EGCG needs an amendment only for those EGCG programs derived
>from GCG source code and including parts of it (there are a few in EGCG).

Well, section "C." does indeed seem to cover work containing, or
derived from, SDK source code.

But there is a separate licence section "B." which covers use of the API
and does not seem to explicitly allow distribution.

Also, even works which just call the API are likely to bear some
resemblance to similar GCG works, if only because their fortran coding
style is so nice by comparison to "normal" fortran. So there is an
argument that even "original" works could be "derived". The difference
is not made clear, and the API is only available as part of the full SDK.
Peter Rice                           | Informatics Division,
E-mail: pmr at sanger.ac.uk             | The Sanger Centre,
Tel: (44) 1223 494967                | Wellcome Trust Genome Campus,
Fax: (44) 1223 494919                | Hinxton, Cambridge, CB10 1SA,
URL: http://www.sanger.ac.uk/~pmr/   | England

More information about the Info-gcg mailing list

Send comments to us at biosci-help [At] net.bio.net