Creative Commons License Errors

[J-J-Chiarella]

On this page of the most common licenses <github.com/Podcastindex-org/podcast-namespace/blob/main/license/licenses.json>, the Creative Commons licenses should not have the hyphen after the “CC” part or before the version number. Also, the full suite of licenses includes all of these <creativecommons.org/share-your-work/cclicenses>:

CC BY 4.0
CC BY-SA 4.0
CC BY-NC 4.0
CC BY-NC-SA 4.0
CC BY-ND 4.0
CC BY-NC-ND 4.0
CC0 1.0

The emphasized licenses do not appear on the list. Did they not make the cut for some reason?

As for the hyphen, I do not see why it needs to replace white space. Maybe I am missing something here. I also do not see why “All Rights Reserved” must be initialized, especially when the documentation says to use lowercase. (Why lowercase? Was this copy-pasted from the podcast:guid entry?) Again, I may be misunderstanding a technical point, which nullifies what I wrote above about “intrusive” hyphens.

While I am on the topic of writing and punctuation, this line does not need a comma:

For new, or custom licenses it is required.

Just this is fine:

For new or custom licenses it is required.

As is this:

For new or custom licenses, it is required.

You only use the comma when you have three or more modifiers.

For new, rare, or custom licenses it is required.
or
For new, rare, or custom licenses, it is required.

Even then, newspapers stand apart from Chicago Style and almost all books. A comma does not follow the penultimate modifier:

For new, rare or custom licenses it is required.
or
For new, rare or custom licenses, it is required.

[jamescridland]

The "extra" hyphens are in the identifier column in the the SPDX license list, which the podcast:license specification refers to; so they are correct in this case.

For writing and punctuation concerns in documentation, please submit a pull request (aka you can fix these yourself! Please do!)

American English style is to capitalise words if they're used as headings; British English style is not to do so. A quick search online reveals that both styles are in use for "All Rights Reserved". It's unlikely that this is an issue.

(I, too, don't understand the requirement for these to be lower-cased; nor do I understand why some licenses are listed and some aren't. I've not followed the podcast:license discussion, since everything I do in audio is fully copyrighted. But I hope the first two parts here are helpful to you).

[J-J-Chiarella]

Hello. Thank you for the speedy reply and the SPDX link. That is a great resource.

The thing with All Rights Reserved was shortening it. I have never seen it as “ARR” and wondered if it would be legally enforceable.

I would submit a pull request, but I am not technically inclined. On other projects, I can just report the bugs. For something purely text that was on GitHub, I ran into a brick wall trying to get it working. In the near future, I will try again.

nor do I understand why some licenses are listed and some aren't

That of course raises questions as to the SPDX license list not being a one-to-one match. For example, All Rights Reserved does not appear there, but dozens of licenses there do not appear on the GitHub here. (Maybe this part is still a work in progress?)

Anyhow, thank you for your time.