<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Thank you very much, Bruce Perens, McCoy Smith and Josh Berkus for taking the time to review and comment on our proposed license. We greatly appreciate it.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
It is correct that the proposed license, like Clear BSD, for example, explicitly does not grant a patent license, whereas many other OSI approved open-source licenses remain silent on the issue. Further, some OSI-approved licenses contain similar, but of course
not identical, restrictions on or exclusions from the licenses to various types of IP, e.g., RPL-1.5, which states the following in Clause 5.0:</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<i>5.0 Exclusions From License Grant. Nothing in this License shall be deemed to grant any rights to trademarks, copyrights, patents, trade secrets or any other intellectual property of Licensor or any Contributor except as expressly stated herein. Except
as expressly stated in Sections 3 and 4, no other patent rights, express or implied, are granted herein. Your Extensions may require additional patent licenses from Licensor or Contributors which each may grant in its sole discretion. No right is granted to
the trademarks of Licensor or any Contributor even if such marks are included in the Licensed Software. Nothing in this License shall be interpreted to prohibit Licensor from licensing under different terms from this License any code that Licensor otherwise
would have a right to license</i></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
As Bruce points out, if the subject of patents is not regulated in the license text, it will have to be determined under applicable law, which may or may not lead to a patent license being considered granted as well, e.g., under the common law principle of
estoppel and/or as an implied license by virtue of contract interpretation, particularly, in civil law jurisdictions, the courts of which are probably, in general, less likely to consider a(n implied) license to have been granted than the courts of common
law jurisdictions. Lothar Determanns background in German (civil) law could also explain why he arrives at a different conclusion compared to the other experts Bruce has spoken to about this. In any event, not explicitly regulating the patent license leads
to significant uncertainty for the licensors as well as for the users, especially seeing as the license may be subject to the laws of differing jurisdictions by virtue of Clause 8 Governing Law and Venue, which calls for the laws of the licensors home
jurisdiction to govern and subjects conflicts to the courts of this jurisdiction as well.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
Seeing as Teradyne Robotics A/S domicile is Denmark, with respect to the material that we license under the proposed license, the license would be subject to Danish law and, under Danish law, it is unlikely that the proposed license would be considered to
include the grant of an implied patent license, i.e., in the absence of explicit regulation.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Consequently, we believe it is better explicitly not to grant a patent license than to leave the matter open even if it would likely lead to the same result at least in our particular case</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="font-family: Verdana, sans-serif; font-size: 9pt; color: rgb(36, 36, 36);"></span><span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(36, 36, 36);">Best Regards<br>
</span></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(36, 36, 36);"><br>
<b>Morten Fruelund</b><br>
<i>IPR Manager</i></span><span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"><br>
<br>
</span><span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(36, 36, 36);">Energivej 51</span><span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"><br>
</span><span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(36, 36, 36);">5260 Odense S</span><span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"><br>
</span><span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(36, 36, 36);">Denmark</span><span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"><br>
</span><span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(36, 36, 36);">Cell: +45 28 93 03 22</span><span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"><br>
</span><span style="font-family: Arial, sans-serif; font-size: 10pt; color: rgb(70, 120, 134);"><a style="color: rgb(70, 120, 134); margin-top: 0px; margin-bottom: 0px;" class="x_OWAAutoLink" id="OWA6cc36256-cc40-23b8-f563-b703aa047d8b" href="mailto:morten.fruelund@teradyne-robotics.com">morten.fruelund@teradyne-robotics.com</a></span></div>
<div class="elementToProof" id="Signature">
<p style="direction: ltr; background-color: white; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
<span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"> </span></p>
<p style="direction: ltr; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
<span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36); background-color: white;"> </span></p>
<p style="direction: ltr; background-color: white; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
<span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"><img size="17612" style="width: 2.083in; height: 0.937in; margin-top: 0px; margin-bottom: 0px;" height="89" width="199" alt="A black and grey logo
Description automatically generated" data-outlook-trace="F:1|T:1" src="cid:3096247f-dfb4-4586-ae4f-a12c475410a9"></span></p>
<p style="direction: ltr; background-color: white; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
<span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"> </span></p>
<p style="direction: ltr; background-color: white; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
<span style="font-size: 8pt; color: rgb(36, 36, 36);">Please note that this message may contain confidential information. If you have received this message by mistake,</span><span style="color: black;"><br>
</span><span style="font-size: 8pt; color: rgb(36, 36, 36);">please inform the sender of the mistake, then delete the message from your system without making,</span><span style="color: black;"><br>
</span><span style="font-size: 8pt; color: rgb(36, 36, 36);">distributing or retaining any copies of it. Although we believe that the message and any attachments are free</span><span style="color: black;"><br>
</span><span style="font-size: 8pt; color: rgb(36, 36, 36);">from viruses and other errors that might affect the computer or IT system where it is received and read,</span><span style="color: black;"><br>
</span><span style="font-size: 8pt; color: rgb(36, 36, 36);">the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.</span><span style="color: black;"><br>
<br>
</span><span style="font-size: 8pt; color: rgb(36, 36, 36);">If Universal Robots A/S processes personal data relating to physical persons, such processing will meet the requirements of applicable data protection legislation.</span><span style="color: black;"><br>
</span><span style="font-size: 8pt; color: black;"><a style="margin-top: 0px; margin-bottom: 0px;" data-auth="NotApplicable" class="x_OWAAutoLink" id="OWAbfbcabea-8c33-9d57-ada7-c6bee253ad9a" href="https://www.universal-robots.com/about-universal-robots/privacy-policy/">Please
see our Privacy Policy here</a></span><span style="font-size: 8pt; color: rgb(36, 36, 36);">.</span></p>
<p style="direction: ltr; background-color: white; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
<span style="font-family: "Segoe UI", sans-serif; font-size: 11.5pt; color: rgb(36, 36, 36);"> </span></p>
<p style="direction: ltr; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
</p>
<p style="direction: ltr; margin-top: 1em; margin-bottom: 1em;" class="elementToProof">
</p>
</div>
<hr style="direction: ltr; display: inline-block; width: 98%;">
<div class="elementToProof" id="x_divRplyFwdMsg">
<div style="direction: ltr; font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<b>From:</b> Bruce Perens <bruce@perens.com><br>
<b>Sent:</b> Monday, November 3, 2025 23:57<br>
<b>To:</b> license-discuss@lists.opensource.org <license-discuss@lists.opensource.org><br>
<b>Cc:</b> Morten Fruelund <morten.fruelund@teradyne-robotics.com><br>
<b>Subject:</b> Re: [License-discuss] Proposal of new new open-source license for graphics (TERO-GL-1.0)</div>
<div style="direction: ltr;" class="elementToProof"> </div>
</div>
<div style="direction: ltr;" class="elementToProof"><span style="color: red;"><b>CAUTION - EXTERNAL EMAIL:
</b></span>Do not open attachments or links unless you recognize the sender and the content is safe.<br>
<br>
<br>
</div>
<div style="direction: ltr;" class="elementToProof">Josh, I don't think you're taking estoppel doctrine into account.</div>
<div style="direction: ltr;" class="elementToProof"><br>
</div>
<div style="direction: ltr;" class="elementToProof">While BSD, for example, does not include an explicit patent grant, there are many qualified people who believe it has an implicit one through the doctrine of estoppel. I think Lotar Determann (Berkeley Law
professor, legal textbook author, of counsel at Baker and McKenzie, and my sometime co-author) is the highest status attorney to say no (to me), a lot of other attorneys I've talked to say yes. IMO this could be likely to be resolved in a long and expensive
litigation, which would be great for the people who want certainty but a pyrric victory for the plaintiff and defendant.</div>
<div style="direction: ltr;" class="elementToProof"><br>
</div>
<div style="direction: ltr;" class="elementToProof">Bruce Perens K6BP</div>
<div style="direction: ltr;" class="elementToProof"><br>
</div>
<div style="direction: ltr;" class="elementToProof">On Mon, Nov 3, 2025, 14:38 Josh Berkus <<a class="OWAAutoLink" id="OWA76c854c0-d0a1-ba12-18e1-034b820d201f" href="mailto:josh@berkus.org">josh@berkus.org</a>> wrote:</div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);" class="elementToProof">
<div style="direction: ltr;" class="elementToProof">On 11/3/25 1:01 AM, Morten Fruelund wrote:<br>
> The license text does not contain any restrictions with regard to fields<br>
> of endeavor, and it does not distinguish between virtual and physical<br>
> use or the purpose of the use. In order to achieve the goal, you<br>
> mention, we simply opted to only grant a copyright license to the<br>
> licensed material, and not include, e.g., a patent license like many<br>
> other open-source licenses also do not do.<br>
<br>
That's an interesting approach, a big hedging on the spirit of OSS, but<br>
allowable (in my individual opinion) as long as you don't explicitly<br>
deny patent rights. When you have updated your text from other<br>
commentary, go ahead and submit it to license-review and we'll delve<br>
into the actual text.<br>
<br>
--<br>
Josh Berkus<br>
<br>
_______________________________________________<br>
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an
<a data-auth="NotApplicable" class="OWAAutoLink" id="OWAe5dd8d23-11a0-694f-31bc-b0c21b4d787e" href="https://urldefense.com/v3/__http://opensource.org__;!!GenOTVeOfQ!QwL1u9n0Ar71oUDP7zssh39pAE9I9Vwm28tqjaZjISTN5Sd97fV8Ule1OTkk7mA_JH8geJWc33tzDK9DXBF_K0ktpjo$">
opensource.org [opensource.org]</a> email address.<br>
<br>
License-discuss mailing list<br>
<a class="OWAAutoLink" id="OWA8d9b94ec-b435-c4f1-d5c4-257364633436" href="mailto:License-discuss@lists.opensource.org">License-discuss@lists.opensource.org</a><br>
<a data-auth="NotApplicable" class="OWAAutoLink" id="OWAf742f1fe-f0ae-22f8-1a00-d946b2763635" href="https://urldefense.com/v3/__http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org__;!!GenOTVeOfQ!QwL1u9n0Ar71oUDP7zssh39pAE9I9Vwm28tqjaZjISTN5Sd97fV8Ule1OTkk7mA_JH8geJWc33tzDK9DXBF_Pn5Fj8g$">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
[lists.opensource.org]</a></div>
</blockquote>
<hr>
<p>Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake, then delete the message from your system without making, distributing or retaining any copies of it.
Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for
any loss or damage arising from the receipt or use of this message. When we process personal data relating to physical persons, such processing will meet the requirements of applicable data protection legislation and will be in accordance with our
<a href="https://www.teradyne.com/privacy-statement">Privacy Policy.</a></p>
</body>
</html>