<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/13/2019 2:37 AM, Henrik Ingo
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKHykeuizeub-FtC+4=r3XkgcS1uPNmuXdr05sFdynnRMQGtNg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Dec 13, 2019 at
12:32 AM Josh Berkus <<a href="mailto:josh@berkus.org"
moz-do-not-send="true">josh@berkus.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">People build applications
in layers. Imagine the sofware I'm copying is<br>
a CAL-licensed database, but what I'm building is some
node.js-based<br>
end-user app.<br>
</blockquote>
<div><br>
</div>
<div>Just to interject on this specific point: This is a great
and relevant example. <br>
</div>
<div><br>
</div>
<div>And this is exactly a situation where IMHO opinion the
approach in CAL is a good one. You have an obligation to
fulfill your obligations under CAL, but the CAL doesn't
mandate you to implement some particular API in your node.js
app. You can choose to use a more manual export procedure if
you wish.</div>
<br>
</div>
</div>
</blockquote>
The CAL is a very strong copyleft license. How does that affect this
hypothetical? Can a CAL-licensed database be used for a
node.js-based end-user app?<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>