<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>>From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> License-discuss [mailto:license-discuss-bounces@lists.opensource.org]
<b>On Behalf Of </b>VanL<br>
<b>>>Sent:</b> Tuesday, July 2, 2019 11:13 AM<br>
<b>>>To:</b> license-discuss@lists.opensource.org<br>
<b>>>Subject:</b> Re: [License-discuss] Data portability as an obligation under an open source license<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">>></span>Thought experiment: What about Lisp? Or DSLs?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">>></span>It is a fundamental element of LISP that "data" and "program" are expressed (or expressable) using the same syntax. Also, various DSLs are expressible using program code (see, e.g., Ansible, JSON).
So does that mean that the scope of a license changes depending on how you look at it?
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">>></span>A bit more theoretically, does "software" comprise its input and configuration data? It seems like that can be included in the GPLv3 concept of corresponding source.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I think a better analogy would be the inclusion of the Installation Information requirement in the *GPLv3 family of licenses. That imposes an obligation to provide
data which is potentially completely divorced from the executable code distributed under the license, and thus the source code that must be provided. For example, a checksum or other hardware-instantiated feature which one needs to know in order to reinstall
modified executables derived from the *GPLv3 license source.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>