-
-
Notifications
You must be signed in to change notification settings - Fork 67
License should use SPDX identifiers #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
You mean, this is how an author should refer to a license within the metadata of a CWL file/description? |
Yes, previously we recommend using a URL to a copy of the license. Now we should recommend using an SPDX URI if available, falling back to the old advice for non-standard licenses. |
Ok, PR coming soon |
do you have an example of SPDX id usage to hand? I'd like to keep a link to an example if possible. No worries if you can't provide one easily - I will track one down |
or actually, I can't! Perhaps I can include an example instead of linking to one? |
|
Formula is: short identifer from the list at https://spdx.org/licenses/ appended to |
The recommend metadata should look like this:
|
@tetron Sure, though if we are only using a namespace once then we don't have to define the namespace So for most CWL files that could be:
|
https://spdx.org/licenses/
https://github.com/common-workflow-language/user_guide/edit/gh-pages/_extras/recommended-practices.md
The text was updated successfully, but these errors were encountered: