<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
En/na Kevin Amerson ha escrit:
<blockquote
cite="mid:68f7cf9d0801251138q56cf9ffak69599984f73593cf@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Or, to take it to a further extreme, you hire a lawyer to write up a<br>
contract for you. Then you claim you own the words in the contract<br>
and the lawyer cannot use those words in any other contract. The<br>
lawyer will just laugh.<br>
</blockquote>
<div><br>
Yeah but we're not saying the words, we're saying the contract as a
whole that has been written specifically for you. </div>
</div>
</blockquote>
Not really. We are saying actually the words. If you sign a contract
where you loose the copyright of it, you can sued by using just a
portion (some words) of that code for other project, isn't?<br>
<br>
Let's say that the lawyer comes up with a special clause really useful
for the client. That client will not be able to own the concept, nor
the exact words, of that clause so the lawyer could not apply it for a
new client with similar needs.<br>
<br>
I see this is a matter of identifying a piece of code as property vs.
knowhow (as Laura stated) or a final product vs. a tool. And you might
find that your contractor may understand this or she may not. However,
there are always our own assumptions, our believes (very important for
a developer working with OS, otherwise it would be better not use it)
and we need to have our minimum requirements, whether the contractor
understands them or not.<br>
<br>
<br>
<div class="moz-signature">-- <br>
<p><font face="Verdana, Arial, Helvetica, sans-serif" size="2">Robert
Garrigós</font></p>
</div>
</body>
</html>