<div><br>Possibly this article?</div>
<div> </div>
<div><a href="http://www.news.com/8301-13580_3-9881858-39.html">http://www.news.com/8301-13580_3-9881858-39.html</a></div>
<div> </div>
<div>Apparently France and Germany don't have public domain. . .</div>
<div>There are certainly good reasons to use open licenses, but I think that there sould be no problem applying a CC license to a derivative work of a public domain work like a translation. Again, IANAL.</div>
<div> </div>
<div>cjl</div>
<div><br> </div>
<div class="gmail_quote">On Wed, Apr 30, 2008 at 12:38 AM, Bryan Berry <<a href="mailto:bryan.berry@gmail.com">bryan.berry@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">good to know, I had read the opposite in an interview of the founder of<br>SQLite, which is also under public domain. He said that releasing SQLite<br>
under public domain caused a whole host of problems.<br>
<div>
<div></div>
<div class="Wj3C7c">On Wed, 2008-04-30 at 00:27 -0400, Benjamin M. Schwartz wrote:<br>> -----BEGIN PGP SIGNED MESSAGE-----<br>> Hash: SHA1<br>><br>> Bryan Berry wrote:<br>> | Public domain license is a notoriously fuzzy legal realm that isn't<br>
> | recognized by the Open Source Institute as an open source license.<br>><br>> Perhaps you are already aware, but to be clear, in US law:<br>> Public Domain means "you can do absolutely whatever you want."<br>
><br>> To be specific:<br>> 1. The US government has explicitly stated, in legally binding fashion,<br>> that they waive all rights to enforce any copyright on this material.<br>> 2. This material was placed into the public domain by its authors, so no<br>
> one else has any standing in any jurisdiction to enforce any copyright<br>> claim against this material.<br>><br>> You can do absolutely whatever you want with this material, and so can<br>> anyone else. It's in the public domain.<br>
><br>> Public Domain is not a copyright license; it is instead the absence of any<br>> copyright at all. Neither the OSI nor the FSF has any problem with you<br>> placing your source into the public domain. The reason that people don't<br>
> do this is because they want the CC-BY/MIT/BSD license's attribution<br>> protection, or the GPL/CC-BY-SA license's copyleft provision.<br>><br>> - --Ben<br>> -----BEGIN PGP SIGNATURE-----<br>> Version: GnuPG v2.0.7 (GNU/Linux)<br>
> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org</a><br>><br>> iD8DBQFIF/U2UJT6e6HFtqQRAkWHAJ9h/F5iWJkbOKhCdn7SNOMnvRZ3ZACgmRgF<br>> wV8/jOZz8U8+vzp+lP6k5lg=<br>
> =Q7z9<br>> -----END PGP SIGNATURE-----<br><br></div></div></blockquote></div><br>