Skip to content
This repository has been archived by the owner on May 27, 2024. It is now read-only.

Explain the namespace use in SPDX 3.0 for custom licenses #79

Open
silverhook opened this issue Apr 20, 2021 · 1 comment
Open

Explain the namespace use in SPDX 3.0 for custom licenses #79

silverhook opened this issue Apr 20, 2021 · 1 comment
Labels
blocked Blocked by another issue faq FAQ

Comments

@silverhook
Copy link
Collaborator

Would probably fit in FAQ, and is pending spdx/spdx-spec#113 and SPDX Spec 3.0 to release, but wanted to include it here for tracking purposes.

This change would avoid potential clashes between two people naming their licenses the same way, while the content is different, because a new custom license’s SPDX ID would include the namespace of the project or company that wrote it.

@mxmehl
Copy link
Member

mxmehl commented Apr 27, 2021

Thanks! Indeed, the FAQ seems to be the most appropriate place to add this info. I don't see it touching the REUSE spec since it's under the License-Ref hood.

@mxmehl mxmehl added the faq FAQ label Apr 27, 2021
@mxmehl mxmehl added the blocked Blocked by another issue label Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked Blocked by another issue faq FAQ
Projects
None yet
Development

No branches or pull requests

2 participants