<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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;
color:black;}
.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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText style='margin-left:.5in'><a name="_MailEndCompose">Nigel Tzeng correctly noted about U.S. public domain code:<o:p></o:p></a></p><p class=MsoPlainText style='margin-left:.5in'><span style='mso-bookmark:_MailEndCompose'>> There isn¹t a lot of code that has aged out. Only code written between before 1963 and didn¹t get a renewal.<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'>There are other important reasons besides "aging out" why the claims of copyright on parts of functional works like software are often denied. (See 17 U.S.C. 102(b), for example.) Aging out isn't the only obstacle to copyright claims that make the <u>copyright</u> aspects of FOSS licenses unenforceable while they remain <u>contracts</u> to disclaim warranties. So when several here suggested that ALL FOSS WORKS probably contain public domain content, this is ANOTHER example not involving aging. <o:p></o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'>The USG and ARL are not unique. Public domain is what it is for software works for everyone here (and probably abroad too). A unique FOSS license isn't necessary to "protect copyrights" in public domain works. Almost any FOSS contract will work to protect the licensor. <o:p></o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'>/Larry<o:p></o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-bookmark:_MailEndCompose'><o:p> </o:p></span></p><span style='mso-bookmark:_MailEndCompose'></span><p class=MsoPlainText>-----Original Message-----<br>From: Tzeng, Nigel H. [mailto:Nigel.Tzeng@jhuapl.edu] <br>Sent: Thursday, August 18, 2016 2:59 PM<br>To: Lawrence Rosen <lrosen@rosenlaw.com>; license-discuss@opensource.org<br>Subject: Re: [License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. Army Research Laboratory Open Source License (ARL OSL) 0.4.0</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On 8/18/16, 3:57 PM, "License-discuss on behalf of Lawrence Rosen"<o:p></o:p></p><p class=MsoPlainText><<a href="mailto:license-discuss-bounces@opensource.org%20on%20behalf%20of%20lrosen@rosenlaw.com"><span style='color:black;text-decoration:none'>license-discuss-bounces@opensource.org on behalf of lrosen@rosenlaw.com</span></a>><o:p></o:p></p><p class=MsoPlainText>wrote:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>>Nigel Tzeng wrote:<o:p></o:p></p><p class=MsoPlainText>>> The issue here is for code that is potentially quite substantial. I <o:p></o:p></p><p class=MsoPlainText>>>would think that would be a different scenario.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>>If I include the works of Shakespeare in my software, it would of <o:p></o:p></p><p class=MsoPlainText>>course be substantial and yet still be public domain almost everywhere (?).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If patents aren't a concern then okay. Copyright lasts longer than patents so for anything that is in the public domain because of age then no patents would still apply.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>There isn¹t a lot of code that has aged out. Only code written between before 1963 and didn¹t get a renewal.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>License-discuss mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:License-discuss@opensource.org"><span style='color:black;text-decoration:none'>License-discuss@opensource.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss"><span style='color:black;text-decoration:none'>https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</span></a><o:p></o:p></p></div></body></html>