Ha, right, thanks for clarifying that. Public Domain is a legal mess on its own - and in fact, CC0 may not be a perfect license to use if you want to dedicate your software to Public Domain because it's explicit that it doesn't grant any patent rights (which is why CC0 code has been recently disallowed in Fedora [0]). 0BSD [1] and MIT-0 [2] are good alternatives with same practical effect, even though they don't try to use the actual institution of Public Domain where it's available.
How so? Who’s confused about what public domain means? Are you thinking of specific cases or precedent?
Assigning something to the public domain is equivalent to waiving all copyrights and license restrictions. Unlike OSI’s definition of open source, public domain comes with no agenda and no protections of any kind for the author, and no restrictions of any kind for the consumer/redistributor.
I don’t know if you’re misinterpreting my opinion on open source, but I’m in favor of Open Source restricitions, I happen to agree with OSI’s reasoning. I’m just also in favor of open language, where words are allowed to have multiple reasonable meanings, where it’s okay and a good thing if it takes time to explain subtle points, and where we don’t expect people to have to know that innocent sounding words are somebody’s slogan, and also know the complete history and special meanings behind the slogan before using it.
How so? Who’s confused about what public domain means?
Laws.
You see, what various countries regard as Public Domain differs a lot. In Germany, for example, there's no way for someone to dedicate something to Public Domain at all. You simply can't waive your copyrights, period. Public Domain exists there, but it only consists of works which had their copyright expired or which have never had any copyrights assigned. If all you say is "I waive my copyright and dedicate this to Public Domain", then such declaration is simply invalid in Germany and may have no legal effect. This is why people use licenses such as CC0 to effectively emulate the effect of dedicating works to Public Domain even where there's no way provided by the law to do it.
There are more subtle effects involved when it comes to considering Public Domain status even between countries that happen to allow dedicating your works to it. It's very complicated. I still stand with all my comments about Public Domain being perfectly valid Open Source, but it has to be added that this assumes a CC0-like license (and patent grant if necessary) to make Public Domain dedication actually valid and non-ambiguous worldwide.
So, then public domain is only “open source” in theory but not in practice? You’re right, I’m wrong. OSI doesn’t recommend against public domain for the reasons I claimed, and I’m making mistakes in this discussion. Thanks for clarifying.
It can be Open Source in practice too, as long as you make sure that your Public Domain dedication is actually effective around the world. The best way to do that could be something like CC0, but CC0 itself is problematic because of its explicit no-patent-grant clause, so it's not recommended to use on software. Instead, licenses like 0BSD or MIT-0 are probably your best bet, practically emulating Public Domain and being officially recognized Open Source licenses.
The problem is that there's no such thing as "public domain" that is consistent in jurisdictions around the world. If you want to make something "public domain," the best way is to slap an OSI-approved license on it.
Comments
Ha, right, thanks for clarifying that. Public Domain is a legal mess on its own - and in fact, CC0 may not be a perfect license to use if you want to dedicate your software to Public Domain because it's explicit that it doesn't grant any patent rights (which is why CC0 code has been recently disallowed in Fedora [0]). 0BSD [1] and MIT-0 [2] are good alternatives with same practical effect, even though they don't try to use the actual institution of Public Domain where it's available.
[0] https://lists.fedoraproject.org/archives/list/legal@lists.fe...
[1] https://opensource.org/licenses/0BSD
[2] https://opensource.org/licenses/MIT-0
How so? Who’s confused about what public domain means? Are you thinking of specific cases or precedent?
Assigning something to the public domain is equivalent to waiving all copyrights and license restrictions. Unlike OSI’s definition of open source, public domain comes with no agenda and no protections of any kind for the author, and no restrictions of any kind for the consumer/redistributor.
I don’t know if you’re misinterpreting my opinion on open source, but I’m in favor of Open Source restricitions, I happen to agree with OSI’s reasoning. I’m just also in favor of open language, where words are allowed to have multiple reasonable meanings, where it’s okay and a good thing if it takes time to explain subtle points, and where we don’t expect people to have to know that innocent sounding words are somebody’s slogan, and also know the complete history and special meanings behind the slogan before using it.
Laws.
You see, what various countries regard as Public Domain differs a lot. In Germany, for example, there's no way for someone to dedicate something to Public Domain at all. You simply can't waive your copyrights, period. Public Domain exists there, but it only consists of works which had their copyright expired or which have never had any copyrights assigned. If all you say is "I waive my copyright and dedicate this to Public Domain", then such declaration is simply invalid in Germany and may have no legal effect. This is why people use licenses such as CC0 to effectively emulate the effect of dedicating works to Public Domain even where there's no way provided by the law to do it.
There are more subtle effects involved when it comes to considering Public Domain status even between countries that happen to allow dedicating your works to it. It's very complicated. I still stand with all my comments about Public Domain being perfectly valid Open Source, but it has to be added that this assumes a CC0-like license (and patent grant if necessary) to make Public Domain dedication actually valid and non-ambiguous worldwide.
See also: https://opensource.org/faq#public-domain
So, then public domain is only “open source” in theory but not in practice? You’re right, I’m wrong. OSI doesn’t recommend against public domain for the reasons I claimed, and I’m making mistakes in this discussion. Thanks for clarifying.
It can be Open Source in practice too, as long as you make sure that your Public Domain dedication is actually effective around the world. The best way to do that could be something like CC0, but CC0 itself is problematic because of its explicit no-patent-grant clause, so it's not recommended to use on software. Instead, licenses like 0BSD or MIT-0 are probably your best bet, practically emulating Public Domain and being officially recognized Open Source licenses.
The problem is that there's no such thing as "public domain" that is consistent in jurisdictions around the world. If you want to make something "public domain," the best way is to slap an OSI-approved license on it.