Linux.com

Feature: Legal

Defence statement released in Israeli GPL test

By Bruce Byfield on April 03, 2007 (8:00:00 AM)

Share    Print    Comments   

The defence in the Jin vs. Ichessu case, in which the GNU General Public License (GPL) is being tested in Israeli court, has filed a detailed defence, which moves the lawsuit from the fast-track short proceedings option into a regular court, where arguments are longer and possible settlements are unlimited. More importantly for the free and open source software community, the case now seems to hinge either on interpretations of the GPL or whether the GPL is valid under Israeli copyright law.

As we reported previously, Alexander Maryanovsky, the plaintiff in the case, first filed against Alexander Rabinovitch and IChessU in 2006. Maryanovksy alleges that the defendants engaged in bad faith negotiations because, after consulting him, the defendants used his work without pay, and that they are in violation of the GPL on several points. In addition, Maryanovsky states that screenshots of Jin on the IChessU site are violation of his copyright because "they were made by running the program in a non-licensed manner." He originally asked a permanent injunction to prevent the defendants from distributing the program, and 110,000 NIS ($25,000) in damages, 80,000 NIS ($18,000) of which are for the screenshots on the site.

Maryanovsky originally filed the suit under the short proceedings option, which according to Jonathan J. Klinger, his lawyer, is used for cases in which "there is little defence or factual disputes, and where the case is clear and cut already -- since the damages are statutory, there is no dispute on the amount to be paid."

However, since the defendants have denied almost every fact alleged by Maryanovsky, the case is now being treated in the normal manner, and a statement of defence was released a few weeks ago. This statement, written in Hebrew, was briefly published by Maryanovsky on his Web page about the case, but is now marked as "Removed per request from IChessU's lawyers." Fortunately, we were able to download a copy of the statement before it was removed.

Preliminary statements in the defence statement

Rabinovitch has outlined the defence before, both in the correspondence published on Maryanovsky's Web page about the case and in Linux.com's first story about the case. The statement of defence is broadly similar to Rabinovitch's informal comments, although a number of points made directly by Rabinovitch are dropped and some are added, and it includes replies to the text of the lawsuit point by point.

Before delving into the details of the case, the statement begins by saying that the lawsuit "was submitted in bad faith, and without legal or factual basis as a mere publicity stunt. As such, the plaintiff has widely publicized the lawsuit on Internet sites both in Israel and abroad." The statement goes on to say that the lawsuit did not follow "proper legal procedure" -- presumably a reference to the attempt to have the case settled as a short proceeding. Describing the case as "frivolous," the defendants threatens the possibility of countersuing for "serious damage to their good name and reputation." Surprisingly after this beginning, the statement later objects to "the coarse, inappropriate tone" of one item in the lawsuit, adding that "the court is requested to note its displeasure as well."

As a final preliminary, the statement also seeks to remove Rabinovitch as a defendant, arguing that he is "at most, a director" of IChessU and that, because "he is not a programmer" that he has "no relations to the claims in the lawsuit," as though only programmers could violate a license agreement.

Defence claims and the GPL

For most of the statement's length, its arguments implicitly or explicitly concern the GPL. Many of its statements seem direct contradictions of the GPL. These statements include:

  • The claim that "'running the program' does not in any way require displaying the license." However, section 2c of the GPL states, "If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice."
  • The IChessU client uses the Jin software legally since, "as the license explicitly states, using the software requires no license." In fact, when section 0 of the GPL talks about running the program, it is referring to "Activities other than copying, distribution and modification" -- the issues that the case is about. Section 5 of the GPL makes clear that copying, modifying, or distributing GPL-licensed software is "prohibited by law if you do not accept the License."
  • The IChessu software consists of the Jin software and a library that IChessu developed separately. These two pieces of software are described as two separate programs that do not communicate directly with each other, and can therefore have two separate licenses. Yet the download from the IChessu site includes both, and requires users to agree to an end-user license agreement (EULA) that, although listing Jin as not falling under the EULA still ties its use to the license. Not only does the EULA reserve the right to remove the exclusion, but the statement that a hardcopy version of the EULA takes precedence over any other means that deliberately or accidentally removing the exclusion would place Jin under the general EULA. Possibly, the library "can reasonably be considered independent and separate," under the definition in section 2 of the GPL, but the point is that the EULA, which is clearly non-free, appears potentially to cover Jin as well.
  • Documentation copied by IChessu "are a non-protected description of method and process" -- a statement that would surprise most companies that distribute documentation. At any rate, because the documentation is distributed with Jin, it is also covered by the GPL as described in section 2, unless licensed separately under a GPL-compatible license.
  • Maryanovsky cannot own the copyright to Jin. The statement of defence does not specify why, but presumably the reason is because the lawsuit acknwoledges that other sources of code were used in its creation.
  • The only place where the statement of defence seems to interpret the GPL reliably is in the statement that the license does not prevent screen shots from being displayed on the IChessu site. These shots would likely fall under fair use. However, the importance of whether they were made while running the program illegally is another matter, and one that might be difficult to prove.

    The defence ends by calling for a complete dismissal of the plaintiff's case. If the case is settled by reference to the GPL, it seems that defence may carry one or two points, but has a strong chance of being found guilty of numerous other GPL violations. In particular, the defence repeatedly seems to ignore the GPL's terms for distribution, and to treat GPL-licensed software as being in the public domain, two misapprehensions that seem to greatly weaken its case.

    Outcome in doubt

    However, whether the case will be decided by reference to the GPL seems doubtful. Any analysis of the defence's claim in the case is difficult for several reasons. For one thing, some of Maryanovsky's original objections, such as the failure to preserve his copyright notice on the IChessu site, now seem to have been addressed.

    Still another difficulty is that, as the case continues, many details change -- whether deliberately or naturally is difficult to say. For example, whether Rabinovitch should be listed in the case depends upon his exact status. Currently, Rabinovitch, who has moved to Canada since the case began, is listed only as "Dean of a Faculty" on the IChessu site. Yet a few months ago, he was signing emails as "CEO of International Chess University," and the defence statement itself admits that he owns the domain name used by the company. Rabinovitch's exact status in the privately owned company at the time of the violation seems likely to become a major factor in determining whether he remains a defendant in the case, and it currently appears indeterminate.

    More importantly, although the defence's understand of the GPL seems minimal throughout the statement, probably what the defence would really like to do is have the GPL declared inapplicable under Israeli law. The statement claims that the the plaintiff's case depends on the concept of "derivative works" -- and that this is a concept derived from American law that is not recognized under Israeli law. This claim is based on the differences between Anglo-American and European-Israeli copyright jurisdictions, and is such a large issue that it is likely to form the basis of the case. It could be that, contrary to the defence statement, the concept of moral rights in the European tradition would actually increase a creator's control over derivative works -- but how it will play out is anybody's guess.

    Since both parties in the case seem relatively small, a settlement is not out of the question. Otherwise, however, the case raises so many technical arguments that it seems likely to drag on for months. Meanwhile, the free software communities will have to wait to see if the license that so many of its projects depend on will survive a challenge in Israeli court.

    Thanks to Alon Zakai for providing an English translation of the Hebrew Statement of Defence.

    Bruce Byfield is a computer journalist who writes regularly for NewsForge, Linux.com, and IT Manager's Journal.

Bruce Byfield is a computer journalist who writes regularly for Linux.com.

Share    Print    Comments   

Comments

on Defence statement released in Israeli GPL test

Note: Comments are owned by the poster. We are not responsible for their content.

Article is incorrect

Posted by: Anonymous Coward on April 04, 2007 01:03 AM
I don't know why people do this, but guys, read
the GPL before you start commenting on it.

About the defese claims:


  - second bullet: Yes, the GPL *does* excplicitly

      state that the license does not cover use. See

      the very first paragraph: paragraph 0. It

      clearly says that only copying is limited, not

      running the program. There really *is* a

      difference between "using" and "distributing"

      as far as the GPL is concerned.


      For example, the "only using it" really *is*

      a defense if it's (a) mere aggregation, or

      (b) a network service (the so-called "ASP

      loophole") or (c) if you distribute just the

      *results* of the program (for example, I do

      not think a screen-shot can really be validly

      protected under the GPL - the screenshot is

      itself not really under the GPL).


      Stating otherwise is simply incorrect.


  - third bullet: "since the two are distributed

      together, they must both be released under the

      GPL".


      That's another *total* misreading of the GPL.


      READ the thing before commenting on it! In

      this case, look for "mere aggregation".


      People do it all the time - distributing GPL'd

      programs on the same CD with non-GPL'd

      programs, and it's even a requirement in the

      OSI definition that an open source license has

      to accept that!


      So it sounds like their defense is that it's

      "mere aggregation", and that really is a valid

      defense. Don't try to make it anything else!

In other words, people who defend the GPL should
do so with *correct* arguments, and should read
the GPL carefully before they do so, otherwise
the GPL-defense only looks bogus.

I don't know who is in the wrong in the case, and
since I don't read Hebrew, I can't really tell.
But stop writing obviously bogus GPL defenses that
have nothing to do with reality. That just makes
the GPL look bad, and it makes all your *other*
arguments suspect too.

For example, some of the other arguments really
do make it look like a GPL violation. There are
*real* things that the GPL requires, and that it
sounds like might have been violated, like the
requirement that you make the license for the
GPLv2 portions clear to people when you distribute
it, even if it's just "mere aggregation" and it's
not *all* GPLv2.

(Not to mention the obvious requirement of making
source available for all GPLv2 projects you do
distribute, etc etc. The GPL requires you to
do many things, but I'm pointing out that it does
*not* require you to do the things you state in
the article)

But having seen the bogus arguments, why would
anybody trust your *real* ones? There is clearly
mis-information about the GPL in the article,
maybe there is misinformation about the case
itself too?

It's entirely possible that it's a GPL violation,
but spreading incorrect information about the GPL
is certainly not going to help "protect" it.
Quite the reverse. It just makes the *valid*
arguments look weaker and more suspect!


                                  Linus

#

Re:Article is incorrect

Posted by: nanday on April 04, 2007 02:55 AM
You're not reading the comments in the context of the discussion:

1.) The defendants are taking the mention of "use" and expanding it to include their distribution and modification of the program, which is unquestionably counter to the license.

2.) The point is that it is not "mere aggregation." The EULA is written so as to cover both.

I've made a couple of revisions to make these points clearer.

- Bruce Byfield (nanday)

#

Re:Article is incorrect

Posted by: Anonymous Coward on April 04, 2007 04:41 AM
Thanks, the new version of those bullet points looks
much better.

You just pushed one of my buttons - a lot of
people really do mis-read the GPL, so I went on
a rant.


                            Linus

#

The Linus?

Posted by: Anonymous Coward on April 04, 2007 10:54 PM
Who used to speak to me confirming that my soundcard was config'd properly. If so, that's awsome. Cheers and thanks for the fantastic kernel.

#

Re:Article is incorrect

Posted by: nanday on April 05, 2007 01:12 AM
Not a problem. Your rant alerted me to the fact that I'd summarized so briefly that the point was lost. That's part of what comments are for, so far as I'm concerned.

#

backup a legal document with real case law?

Posted by: Anonymous Coward on April 04, 2007 10:45 PM
Say it isn't so! Say, it, isn't, SOOO!

#

Sounds a bit like the Daniel Wallace case

Posted by: Administrator on April 04, 2007 12:24 AM
Daniel Wallace challenged the GPL in court on spectacularly weak grounds, not to defend a copyright infringement - he brought a sort of anti-trust case - and ended up helping the FSF quite a lot because they now have the judge's comments to cite in other cases. The defense's statement in this case indicates that they are just the sort of sucker that FSF would want to further back up GPL with case law. However, given the shallow pockets of the defendant, it's possible that they might not allow the case to run to completion.

Bruce

#

Couldn't happen at a better time

Posted by: Administrator on April 03, 2007 10:33 PM

The timing is very useful for <a href="http://fsfeurope.org/projects/gplv3/" title="fsfeurope.org">the GPLv3 process</a fsfeurope.org>. This is sure to generate some useful material which can be studied while thinking about the internationalisation efforts in the wording of v3.

#

Screenshot Nonesense Does More Harm Than Good

Posted by: Administrator on April 04, 2007 04:15 PM
It's truly a shame that people 'dilute' the intensity of their claims by making all sorts of 'sidal' arguments. While the GPL should clearly lead to damages being paid, the whole copyright issue just hurts the credibility of the plaintiff. This is not about art. It is about code misuse. That -- and that alone -- should matter here. The GPL has already won in the Germany courts, FWIW, so this isn't unprecedented.

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya