Skip to content
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

Add clarification on license IRIs #73

Open
bencomp opened this issue Sep 21, 2022 · 3 comments
Open

Add clarification on license IRIs #73

bencomp opened this issue Sep 21, 2022 · 3 comments

Comments

@bencomp
Copy link

bencomp commented Sep 21, 2022

The Dataset Registry contains over 400 datasets without a license, even though a license is required.
Other datasets have varying license IRIs that appear to refer to the same terms. For example, public domain 'licenses':

  • https://creativecommons.org/publicdomain/zero/1.0/
  • http://creativecommons.org/publicdomain/zero/1.0/
  • http://creativecommons.org/publicdomain/zero/1.0/deed.nl
  • "http://creativecommons.org/publicdomain/zero/1.0/deed.nl"@nl (a language string instead of an IRI)
  • "http://creativecommons.org/publicdomain/zero/1.0/" (a regular string instead of an IRI)
  • "http://www.opendefinition.org/licenses/cc-zero" (string, new to me)
  • http://creativecommons.org/publicdomain/mark/1.0
  • https://creativecommons.org/publicdomain/mark/1.0/
  • https://creativecommons.org/share-your-work/public-domain/pdm/

There is of course a difference between the CC0 waiver and the PD mark, but it would be good to have more guidance on which IRIs to use for each. I see that the SHACL propertyShape accepts literals, but this doesn't help users looking for datasets with specific licenses. The conceptual model also shows that the target of a license predicate is an IRI, so hopefully newly added licenses are always IRIs (not full license terms or acronyms).

@coret
Copy link
Contributor

coret commented Sep 21, 2022

Thanks, good observation. That the validation of datasetdescriptions allows literals for license doesn't help indeed, this should be fixed in the specification and the validation.

The diversity of IRI's for specific licenses does beg for more guidance. We need to find a good resource for this. The current "for example one of the Creative Commons licenses" line doesn't directly help you find a IRI, but a license.

@EnnoMeijers
Copy link

Would it possible to reuse some of the work that is being done by the DALICC project? See https://github.com/dalicc

@bencomp
Copy link
Author

bencomp commented Sep 22, 2022

@EnnoMeijers that looks very interesting, but I couldn't quickly find a list of CC license IRIs in their repositories. https://raw.githubusercontent.com/dalicc/dalicc/main/licensedata/licenselibrary/licenselibrary.ttl refers to yet different IRIs (e.g. <https://creativecommons.org/licenses/by-nc/2.0/au/legalcode>) for the CC licenses.
They do link to licenses that are for specific jurisdictions, which I haven't seen much yet in "our" datasets.

A list of suggested IRIs would be most helpful. For example, "If you want to waive rights using CC0 1.0, use ... as license IRI".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants