<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 8/23/2019 11:30 AM, VanL wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFQvZENNa-rsrQCLF3EJKiNhwxbe5YBQ1hLuQsrfQsNSwM0ZKQ@mail.gmail.com">
<div dir="ltr" class="gmail_attr">On Fri, Aug 23, 2019 at 9:58 AM
Pamela Chestek <<a href="mailto:pamela@chesteklegal.com"
moz-do-not-send="true">pamela@chesteklegal.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 bgcolor="#FFFFFF"> <br>
<div class="gmail-m_-1390335439492428248moz-cite-prefix">On
8/23/2019 10:39 AM, VanL wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">For example, if your Twitter widget only
worked on your server, and it didn't communicate any
aspect of itself to a visitor to your website, the CAL
wouldn't reach it. You would have no compliance burden at
all.</div>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<div>In this scenario, the widget runs entirely server side. The
widget creates an output that is consumed by a visitor to the
website, but the widget itself does not interact with the user
and does not include any of its own expression in the output.</div>
<div><br>
</div>
<div>The result under this scenario is that no compliance actions
are required, neither under the CAL nor under the AGPL.</div>
</blockquote>
<br>
So you are saying that the html generated by the Work and displayed
on a webpage is not the Work or a "modification, elaboration or
implementation" of the Work and accordingly also subject to the CAL?<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>