<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Van,<br>
<br>
I have one more scenario that occurred to me when I was re-reading
the license. I'd like to know if I understand correctly:<br>
<br>
Assume that the CAL is used for front-end software. A website uses
the software for its website. Through a webform I order a gift that
is for my daughter, who lives at a different address. It appears to
me that, under the CAL:<br>
<br>
My daughter's name and address are "User Data," that is, they are
data that is input to the Work and my daughter, a third party, has a
Lawful Interest in the data.<br>
The website has Publicly Performed, that is, it has made an
interface available that is used for access to User Data, my
daughter's name and address.<br>
As a result, this interaction means that under 2.2.1 and 2.2.2 the
website has to provide me (the Recipient) with a copy of the source
code.<br>
<br>
Is that correct?<br>
<br>
Pam<br>
<br>
<div class="moz-signature">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>
<br>
</div>
<div class="moz-cite-prefix">On 4/22/2019 2:43 PM, VanL wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFQvZENr0qBdz40xR2aCTD+vvQyw+WmNL-tDtuXMPqHR345zMQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>I'd like to thank everyone who provided feedback on
earlier drafts of the Cryptographic Autonomy License
(CAL). Since we presented the draft license in
February, we have received hundreds of comments and
suggestions, all of which have helped us fine-tune the
license.</div>
<div><br>
</div>
<div>We now present the CAL 1.0-Beta for approval at the
next board meeting:</div>
<div> Google Docs link: <a
href="https://docs.google.com/document/d/1sWUREQN02YJ-q91gXOCflRB57Q1YcU1G7UMS_a8WOTI/edit#"
moz-do-not-send="true">https://docs.google.com/document/d/1sWUREQN02YJ-q91gXOCflRB57Q1YcU1G7UMS_a8WOTI/edit#</a></div>
<div> PDF Link: <a
href="https://www.processmechanics.com/static/CAL-1.0-Beta.pdf"
moz-do-not-send="true">https://www.processmechanics.com/static/CAL-1.0-Beta.pdf</a>
<br>
</div>
<div><br>
</div>
<div>The CAL is still open for revision until it is
approved by the Board, and the links above will be
updated as appropriate. <br>
</div>
<div><br>
</div>
<div>I also refer everyone here again to the blog post
describing the legal foundations of the license (<a
href="https://www.processmechanics.com/2019/03/15/the-cryptographic-autonomy-license/"
moz-do-not-send="true">https://www.processmechanics.com/2019/03/15/the-cryptographic-autonomy-license/</a>)
as well as the discussion on license-discuss,
summarized by Lukas Atkinson here: <a
href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2019-April/020394.html"
moz-do-not-send="true">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/2019-April/020394.html</a><br>
</div>
<div><br>
</div>
<div>Thanks,<br>
</div>
<div>Van<br>
</div>
<div> <br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</body>
</html>