From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1025b4,43ae7f61992b3213 X-Google-Attributes: gid1025b4,public X-Google-Thread: 103376,faf964ea4531e6af X-Google-Attributes: gid103376,public From: les@MCS.COM (Leslie Mikesell) Subject: Re: [O/T 4 cla] Re: GPL and "free" software Date: 1999/05/08 Message-ID: <7h2aca$2mqq$1@Mercury.mcs.net>#1/1 X-Deja-AN: 475636984 References: <7fibd5$jc7$1@news2.tor.accglobal.net> <7gprnj$pau$1@nnrp1.dejanews.com> <7gr768$kqe$1@Jupiter.mcs.net> <7grvur$li2$1@nnrp1.deja.com> Organization: /usr/lib/news/organi[sz]ation Newsgroups: comp.lang.ada,gnu.misc.discuss Date: 1999-05-08T00:00:00+00:00 List-Id: In article <7grvur$li2$1@nnrp1.deja.com>, Robert Dewar wrote: > >> There are lawsuits over nearly everything. Is there any court >> decision that states that something you write is covered by >> someone else's copyright when it contains none of the other >> work? > >If by "contains none of the other work" you mean contains no literal >characters copied from the other work, then of course the answer >is yes. No, it wasn't a trick question. Obviously you could encode the original work in some other representation and it would still be covered. However, the concept of a 'diff' is exactly the opposite. It conveys, by definition, the parts that were not in the original. >The process for evaluation of copyright violation involves looking >for protected elements at successive levels of abstraction. It is >pretty clear to me that this abstraction process in the case of >a patch file will necessarily involve looking at the combined work. If the only part copied is the patch, how can anything else be involved? A normal patch file does contain bits of the surrounding context; even in the ed form there will be original content as parts of some lines. I'd think this would be 'fair use' particularly since the recipient must already have his own copy of the original to use the patch. However that objection could be eliminated by a different patch format that used character offsets with the lines to anchor the changes instead of containing any of the original content. >Note that software copright is definitely NOT simply a matter of >comparing two texts, it is a far more complicated process, as anyone >who has been involved in such cases is aware. Like they say, if the two lawyers can't agree, how are the jurors supposed to... Les Mikesell les@mcs.com