<div dir="ltr">Lothar sent me an interesting paper yesterday: Nobody Owns Data
<a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3123957">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3123957</a></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 9, 2019 at 4:22 PM Diane Peters <<a href="mailto:diane@creativecommons.org">diane@creativecommons.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Perhaps useful as a point of reference: <a href="https://wiki.creativecommons.org/wiki/version_4#Private_adaptations_expressly_authorized_under_4.0_ND_licenses" target="_blank">CC 4.0 ND</a> licenses allow private modifications. This feature is included to support text and data mining activities and similar. As long as what is ultimately shared publicly isn't a derivative of the original, rare in the TDM world particularly, the ND restriction is not violated.<div><br></div><div>Diane<br><div><br></div><div><br><div><br></div><div>Diane</div><div><br clear="all"><div><div dir="ltr" class="gmail-m_-9171645192226486836gmail_signature"><div dir="ltr"><div><div dir="ltr">Diane M. Peters<div>General Counsel, Creative Commons<div><br></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 9, 2019 at 1:15 PM Smith, McCoy <<a href="mailto:mccoy.smith@intel.com" target="_blank">mccoy.smith@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-9171645192226486836gmail-m_4500740928891310413WordSection1">
<p class="MsoNormal"><a name="m_-9171645192226486836_m_4500740928891310413______replyseparator"></a><b><span style="font-size:11pt;font-family:Calibri,sans-serif">>>From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> License-discuss [mailto:<a href="mailto:license-discuss-bounces@lists.opensource.org" target="_blank">license-discuss-bounces@lists.opensource.org</a>]
<b>On Behalf Of </b>Brendan Hickey<br>
<b>>>Sent:</b> Thursday, August 8, 2019 5:20 PM<br>
<b>>>To:</b> <a href="mailto:license-discuss@lists.opensource.org" target="_blank">license-discuss@lists.opensource.org</a><br>
<b>>>Subject:</b> [License-discuss] Private modification<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">>></span>What are some good policy arguments in favor of restrictions on private modification? My own impression is that these licenses are so onerous as to discourage any serious use. Are there any significant
projects using the RPL or similar licenses?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I’m a lawyer, not a policy person or philosopher (at least not professionally), but I can think of at least 3:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph"><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span>1.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Onerousness (as you have identified). If you have to make public or disclose all your private modifications, when and how often one must publish the
modifications, and what modification quantum triggers the obligation, introduces compliance burdens and complications for the user.<u></u><u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph"><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span>2.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Privacy. There may be many changes which as a user you may not wish to be made public; forcing you to do so when you have not otherwise made those
modifications visible to the public in general or others specifically forces you to give up some of that privacy.<u></u><u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph"><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span>3.<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Proliferation of bad, incomplete or nonuseful code. During code development, there is a reasonable amount of modified code which is undeveloped, untested,
bad, or incomplete (pre-beta). If this code is required to be made public, it potentially increases the ratio of bad to good code accessible to the public.<u></u><u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph" style="margin-left:0in"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">There are probably other reasons others on the list can enumerate; those just come off the top of my head.<u></u><u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph" style="margin-left:0in"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="gmail-m_-9171645192226486836gmail-m_4500740928891310413MsoListParagraph" style="margin-left:0in"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">IMHO, AGPL and other licenses like it draw a boundary which reduce these factors (and don’t touch true private modification), by
only triggering obligations once the user has given access to their modifications to others. Some of the more recent submissions to the license approval list don’t draw that boundary in such a way, and do indeed reach toward true private modifications (and
push against the concept of Freedom Zero). <u></u><u></u></span></p>
</div>
</div>
</div>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
</blockquote></div>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Bruce Perens - Partner, <a href="http://OSS.Capital" target="_blank">OSS.Capital</a>.</div></div></div></div>