Bug#570621: Parsing output = derivative work?
Le mercredi 09 mars 2011 à 11:27 +0000, Noel David Torres Taño a
> > Miriam Ruiz <firstname.lastname@example.org> wrote:
> > In general, I do agree with Miriam that parsing the output of another
> > program does not make a derivative work. But just to give an example
> > of where it does happen, git is largely comprised of many small
> > utilities that communicate over pipes and command-line arguments.
> It happens (to me) to be as simple as this:
> If the parsed program is susbtituted by a clone will the parsing program
> continue working?
If the shared library is substituted by a clone reimplementing the same
API/ABI, will the program linking to it continue working?
> If the answer is yes, since it is absurd that the parsing program is a
> derivative work of all possible clones at the same time, then clearly it is
> not a derivative work. If the answer is no, then clearly the parsing program
> depends on the parsed one 'in an intimate way'.
> Can a clone or sucessor of nmap be used with gnetworktester?
I agree that if such clone exists (and that holds for libraries too), it
is not a derivative work.
Nothing specific to parsing the output of another program here.
: :' : “You would need to ask a lawyer if you don't know
`. `' that a handshake of course makes a valid contract.”
`- -- J???rg Schilling