<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div><style><!--
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Nur Text Zchn";
margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;}
span.E-MailFormatvorlage20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.NurTextZchn
{mso-style-name:"Nur Text Zchn";
mso-style-priority:99;
mso-style-link:"Nur Text";
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></div><div>Andreas, <br></div><div><br data-mce-bogus="1"></div><div>definitely not authoritative, but since I am the one who raised the subject, I feel an obligation to provide a potential solution.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>I would not depart from the common practice of requesting that the recipients of distributed software be notified of the legal language in some form, by including the whole text of the license along the distribution, or by making reference to a canonical online resource, and by requesting an appropriate legal notice. There are plenty of examples out there, all remixing the same concepts and language. See e.g. the GNU *GPLv3.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>All the best,<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Carlo<br data-mce-bogus="1"></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>Da: </b>"Andreas Nettsträter" <andreas.nettstraeter@openlogisticsfoundation.org><br><b>A: </b>"License submissions for OSI review" <license-review@lists.opensource.org><br><b>Inviato: </b>Venerdì, 23 dicembre 2022 15:01:24<br><b>Oggetto: </b>Re: [License-review] For Approval: Open Logistics License v1.2<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Dear Pam, dear Carlo,</span><span lang="EN-GB"></span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoPlainText"><span lang="EN-GB">the last bulletpoint of Article 4 was meant to implement an obligation to flow down the obligations of the other bulletpoints of Article 4; if the provision requires modification to make this clear, we can make the
respective amendments.</span></p>
<p class="MsoPlainText"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">How could we formulate it in a better way?</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Regards</span></p>
<p class="MsoNormal"><span lang="EN-GB">Andreas</span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>Von:</b> License-review <license-review-bounces@lists.opensource.org>
<b>Im Auftrag von </b>Pamela Chestek<br>
<b>Gesendet:</b> Mittwoch, 14. Dezember 2022 18:05<br>
<b>An:</b> license-review@lists.opensource.org<br>
<b>Betreff:</b> Re: [License-review] For Approval: Open Logistics License v1.2</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On 12/14/2022 4:24 AM, Carlo Piana wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif;color:black">On 12/5/2022 2:45 PM, Carlo Piana wrote:</span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style="color:#007CFF">You must ensure that the recipients of the Subject Matter of the License or</span></pre>
<pre><span style="color:#007CFF">Derivative Works are obligated to incorporate the provisions of this Section 4</span></pre>
<pre><span style="color:#007CFF">into any license under which they distribute the Subject Matter of the License</span></pre>
<pre><span style="color:#007CFF">or Derivative Works to any other recipients.</span></pre>
<pre><span style="color:#007CFF"> </span></pre>
</blockquote>
<pre><span style="color:black">This provision requires the "You" to a legal effect. As a general remark, this is an open ended obligation and IMVHO a bad design decision, since the legal effect depends on many different circumstances outside the control of the "You", including intent, capacity, errors, lack of proper form etc. You can surely include perform an obligation as a condition of the grant, but including a legal effect is to me really really seeking for trouble.</span></pre>
<pre><span style="color:black"> </span></pre>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif;color:black">Carlo, I'm not following what you're saying. Are you saying that the Licensor has some liability if the user doesn't actually incorporate the provisions of Section
4 into their downstream license?</span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Sorry Pam, I have written poorly</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I meant "This provision requires the "You" to **achieve** a legal effect." The obligation requires that *the recipients** be "obligated". Here it is more of a guarantee, something that you are liable for and not necessarily control, so
the risk is on you whatever it happens.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</blockquote>
<p class="MsoNormal">Thanks, that's very helpful.<br>
<br>
Pam<br>
<br>
Pamela S. Chestek<br>
Chestek Legal<br>
PO Box 2492<br>
Raleigh, NC 27602<br>
<a href="mailto:pamela@chesteklegal.com" target="_blank">pamela@chesteklegal.com</a><br>
(919) 800-8033<br>
<a href="https://deu01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.chesteklegal.com%2F&data=05%7C01%7Candreas.nettstraeter%40openlogisticsfoundation.org%7Cf8d1c3a7b6c3497a1b2008daddf56a24%7Cb346d634acfb42c7bd44f1557ee89b1b%7C1%7C0%7C638066343365425048%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mkOKR7GkzVnwxG4YgGLoaJWmhUlwqS0dOME0E81Qb9Y%3D&reserved=0" target="_blank">www.chesteklegal.com</a><br data-mce-bogus="1"></p>
</div>
<br>_______________________________________________<br>The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.<br><br>License-review mailing list<br>License-review@lists.opensource.org<br>http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org<br></blockquote></div></div></body></html>