<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Microsoft Word - summit source doc 1 0</title>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>MIT may be considered a single legal entity but is composed of many different colleges, laboratories, etc with their own office of tech transfer. While supporting open source is valuable so is supporting entrepreneurs and IP policies at research universities
will have to support both. Universities, researchers and entrepreneurs depend on IP protection for both revenue and grants.</div>
<div><br>
</div>
<div>The issues are covered in the ECL v2 discussions from 2006 and apply also to the USG. They are covered on page 12 of the report:</div>
<div><br>
</div>
<div>"<span style="font-family: Arial; font-size: 12pt; font-style: italic;">Two outputs of the Summit addressed these concerns: the ECL 2.0 outbound license and the new form of institutional contribution agreement. These revisions were designed to accommodate
concerns about the reach of the patent license provisions in the contributor agreement. The patent license provision was modified so that no license would be granted to patents developed by anyone other than the author of the contribution, and also to recognize
the possibility that there may be funding agreements or other prior commitments that limit the institution’s flexibility to grant a license.</span></div>
<div class="page" title="Page 16">
<div class="layoutArea">
<div class="column">
<p><span style="font-size: 12.000000pt; font-family: 'Arial'; font-style: italic">While these licenses represent progress, they also reflect some policy decisions by participating institutions that bear long-term thought. For example, a license to patents that
arise only out of the work of contributors to the project does not cover patents that arise out of other work at the university, reflecting a choice to protect the ability of individual inventors at the university, and the ability of the university itself,
to benefit from the commercialization of the patent, where licensing these patents in connection with community projects may be beneficial to the community as a whole." </span></p>
</div>
</div>
</div>
<div><a href="https://scholarworks.iu.edu/dspace/bitstream/handle/2022/3076/Licensing_and_Policy_Summit_Report_2007.pdf?sequence=1&isAllowed=y">https://scholarworks.iu.edu/dspace/bitstream/handle/2022/3076/Licensing_and_Policy_Summit_Report_2007.p</a>df</div>
<div><br>
</div>
<div>I don’t have any software patents. I don’t support software patents. But I am very very disinclined to give away another researcher’s software patents just because I open sourced code and my OTT didn’t realize that it tread on a patent that someone else
at the university created. ECL v2 is designed to make this impossible to do accidentally.</div>
<div>
<div><br>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>License-discuss <<a href="mailto:license-discuss-bounces@opensource.org">license-discuss-bounces@opensource.org</a>> on behalf of John Cowan <<a href="mailto:cowan@ccil.org">cowan@ccil.org</a>><br>
<span style="font-weight:bold">Reply-To: </span>License Discuss <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, December 12, 2016 at 5:47 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:lrosen@rosenlaw.com">lrosen@rosenlaw.com</a>" <<a href="mailto:lrosen@rosenlaw.com">lrosen@rosenlaw.com</a>><br>
<span style="font-weight:bold">Cc: </span>License Discuss <<a href="mailto:license-discuss@opensource.org">license-discuss@opensource.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [License-discuss] Views on React licensing?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Dec 12, 2016 at 4:16 PM, Lawrence Rosen <span dir="ltr">
<<a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a>></span> wrote:</div>
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p class="MsoNormal"><span style="font-family:calibri,sans-serif">If Yoyodyne or Soylent sue MIT because they had previous exclusive patent licenses or contracts, that is court fun for them. It doesn't involve me.</span></p>
</div>
</blockquote>
<div><br>
</div>
<div>Agreed. I only mentioned this hypo to defend my claim that if MIT can't keep track of what they have licensed to whom, the word "incompetent" is fit for purpose, not in any specifically legal sense but in the sense of not being ordinarily prudent in the
management of their property. MIT would get a short sharp shock if they tried to sell the same piece of real estate to two different purchasers on the grounds that proper records were too expensive to maintain.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<p class="MsoNormal" style="margin-left:0.5in"><u></u></p>
<p class="MsoNormal"><span style="font-family:calibri,sans-serif">[<LER>] I would tell Yoyodyne to take up their dispute with MIT. I'm not a party. The worldwide open source user community is not a party to some secret exclusive deal between Yoyodyne and MIT.</span></p>
</blockquote>
<div><br>
</div>
<div>Now this I do not understand. If Yoyodyne is the exclusive licensee, then surely it has the right to sue/enjoin you as a user of their patented technology, and your claim to have a subsequent license from the former patent holder isn't going to help you,
particularly if that former patent holder disclaims it. This follows from the fact that if Charlie writes a program that unknowingly infringes Alice's patent and then allow Bob to use it, Alice can take action against either Bob or Charlie. In this case,
MIT is Charlie, and the fact that MIT originally handed over the patent to Alice shouldn't matter: when Alice asks for one more nickel, Charlie won't be able to get off the train.</div>
<div><br>
</div>
<div>I know that it's not typical for a patent holder to sue Bobs who merely use a patented article that they obtain from a non-licensed manufacturer, but that's a matter of it being economically inefficient to sue a huge list of known and unknown customers,
not a derogation of their right to do so.</div>
</div>
<br>
-- </div>
<div class="gmail_extra">
<div class="gmail_extra">John Cowan <a href="http://vrici.lojban.org/~cowan">http://vrici.lojban.org/~cowan</a> <a href="mailto:cowan@ccil.org">cowan@ccil.org</a></div>
<div class="gmail_extra">Knowledge studies others / Wisdom is self-known;</div>
<div class="gmail_extra">Muscle masters brothers / Self-mastery is bone;</div>
<div class="gmail_extra">Content need never borrow / Ambition wanders blind;</div>
<div class="gmail_extra">Vitality cleaves to the marrow / Leaving death behind. --Tao 33 (Bynner)</div>
<div class="gmail_extra"><br>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>