<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 12/10/2019 9:41 AM, Nigel T wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADaGzk52LMwNuOuh0_jqBcX8jX4nwrdUK95PdqiV2hKrNS0v=A@mail.gmail.com">
<div><font face="arial, sans-serif">The <b>software is not a
safety deposit box</b> because of the requirement that you
must also return <i>"</i><span
style="background-color:transparent"><i style="color:rgb(0,0,0);white-space:pre-wrap">data has been generated by, for, or has been assigned to the Recipient". </i><font
color="#000000"><span style="white-space:pre-wrap">Safety deposit boxes don't generate new content for users. Software often does. </span></font></span></font></div>
<div><span style="color:rgb(0,0,0);font-family:arial,sans-serif;white-space:pre-wrap;background-color:transparent">
</span></div>
<div><span style="background-color:transparent"><font face="arial,
sans-serif" color="#000000"><span style="white-space:pre-wrap">Even ignoring generated data that you'd have go though each and every UI screen and make sure all inputs provided by user are correctly mapped to an export field...and you have to do this every time you update from upstream.</span></font></span></div>
<div><font face="arial, sans-serif"><span
style="background-color:transparent"><font color="#000000"><span style="white-space:pre-wrap">
</span></font></span></font></div>
<div><font face="arial, sans-serif"><span
style="background-color:transparent"><font color="#000000"><span style="white-space:pre-wrap"><b>If the original software cannot export all of the data required to meet the requirements of 4.2 then all subsequent users of the software are in breach of the license.</b> </span></font></span></font><span
style="color:rgb(0,0,0)"><font face="arial, sans-serif"><b>This
is a point that you continue to dance around. </b></font></span><span
style="background-color:transparent"><font face="Calibri,
sans-serif"><font color="#000000"><span style="white-space:pre-wrap">You are handwaving significant legal and technical burden you are placing on users of CAL licensed software because you want to extend licensing requirements beyond open </span><b style="white-space:pre-wrap">source</b><span style="white-space:pre-wrap"> into open </span><b style="white-space:pre-wrap">data </b></font></font></span><span
style="background-color:transparent"><font face="Calibri,
sans-serif"><font color="#000000"><span style="white-space:pre-wrap">and non-technical users who just use the software out of the box don't control that at all. There are no exceptions for non-compliance of the original code in this license so it's <b>a compliance nightmare</b></span></font></font></span><font
face="Calibri, sans-serif" color="#000000"><span style="white-space:pre-wrap"><b> for every downstream user whether they change the code or not</b>.</span></font></div>
<div><span style="background-color:transparent"><font
face="Calibri, sans-serif"><font color="#000000"><span style="white-space:pre-wrap">
</span></font></font></span></div>
</blockquote>
Hi Nigel,<br>
<br>
Can you help me understand your point better? Section 4.2.1 says
"Throughout any period in which You exercise any of the permissions
granted to You under this License, You must also provide to any
Recipient <i>to whom you provide services via the Work</i>, ... the
Recipient's User Data in your possession, <i>to the extent that
such User Data is available to You</i> for use in conjunction with
the Work." <br>
<br>
I acknowledge your dislike of the ambiguity of "to the extent that
such User Data is available to You," but I'd like to put that point
aside. For the purposes of argument let's assume that it is an
easily ascertainable set of data, something like "any User Data you
received in plain text." The scenario is that I have received data
about a Recipient from upstream, and now I am providing services to
that same Recipient, which is the only situation in which I would
have to provide User Data. Is your point that the program
architecture may make it too difficult to extract and provide the
plain text that upstream provided to me? Is your argument that there
is something that is not open source about this arrangement, or is
it that the license will be used in situations for which it is
poorly suited?<br>
<br>
Pam<br>
<br>
Pamela S. Chestek<br>
Chestek Legal<br>
PO Box 2492<br>
Raleigh, NC 27602<br>
919-800-8033<br>
<a class="moz-txt-link-abbreviated" href="mailto:pamela@chesteklegal.com">pamela@chesteklegal.com</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.chesteklegal.com">www.chesteklegal.com</a><br>
</body>
</html>