For what it's worth, looks like someone tried to come up with something along these lines, and called it the Worldwide Public Domain Dedication https://wpdd.info/wpdd.html Looks to be based on CC0,

really, McCoy, you are not going to suggest https://spdx.org/licenses/BSD-2-Clause-Patent.html ?!? Don’t be coy now… :) (McCoy drafted that license, for those who are not aware.) J. > > > >

It's interesting that you mention CC0, as it has recently been decided that CC0 is no longer suitable for Fedora code packages due to its explicit non-grant of patent licences. I imagine other

Dear Russ, The points you make are very pertinent indeed. I think that statements of the third type should probably be included in the SPDX License List, as they are usually very distinctive and

This was for OpenEmbedded-Core, there will be other issues in other layers which we'll no doubt hit as other they adopt the identifiers but it at least let us resolve things for our

"J Lovejoy" <opensource@...> writes: I think it would be useful to understand the split between three classes of things that I suspect SPDX will want to treat differently: * A pure statement

Hi Warner, McCoy, You both raise some good points which has made me realized I should clarify this topic a bit: First, yes, some "public domain dedications" or things

Thanks Richard, that's interesting. I'm really surprised Yocto only ran into one example of this kind of thing though!

I’m not sure SPDX makes qualitative assessments of licenses or statements (nor should it, since practically every license does have some degree of ambiguity). So a PD dedication that is

I was using beerware as an example to ask the question: what separates it from PD, especially with the public domain dedications that try to work around EU law in different ways. Is it the grant of

There is an obligation in there (“as long as you retain this notice”) so it really is a license not a PD dedication (if something is PD, it comes with no obligations). Plus, beerware is already

On a related question, there's several licenses that are close to the public domain. Eg: "THE BEER-WARE LICENSE" (Revision 42): <phk@...> wrote this file. As long as you retain this notice you can do

I support the idea of Mike. In particular, this would help for both use and license compliance in (most) European countries. Please note that in many countries there is no "public domain" in

Thanks for the clarification Jilayne! If the idea is to collect information about the different forms used to say "this is in the public domain" with an eye towards option 3, then yes, I think your

Yocto Project ran into this in a single case in our core layer for a single file which was listed as "PD". This was the one source file we couldn't therefore put an SPDX license identifier on. After

Thanks for the quick responses, Steve and Mike! I should have been more clear on what I needed input on ASAP - which was, a) what info would be helpful to collect (now) about any public domain

In addition to Steve's thoughts... I will respond quickly as that was the request ... and likely miss issues. My only additional though is could we add a generic public domain license reference to the

Hi Jilayne, since you asked for input ASAP, here are a few immediate gut reactions :) I think getting the data of seeing a bunch of different ways that people said "this code is released into the

Hi SPDX-legal, I have raised this a couple times in the past few months or so, but now that it is more of a "ripe" topic, I wanted to get some input on preliminary ideas: