-
Notifications
You must be signed in to change notification settings - Fork 53
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
Normalize licenses and license names and display in dataset view #55
Comments
We're moving to just having a license id mostly. We then need to look up on licenses.opendefinition.org or similar. This is somewhat blocked on resolving okfn/opendefinition#27 and okfn/opendefinition#7 |
I would go ahead and use https://github.com/okfn/licenses/blob/master/licenses/groups/all.json fix issues there. okfn/opendefinition#27 will obtain license texts repo from SPDX, probably not useful for this. okfn/opendefinition#7 seems to be a wishlist item that requires a substantial site migration and can benefit from any work done on okfn/licenses in the meantime. |
It feels that all.json has multiple issues, including that CC-BY-NC is labeled as "Creative Commons Non-Commercial (Any)" whereas the URL point to a specific license version. This can be corrected, but what's the compelling reason for not maintaining compatibility with CC-REL et al and using the URIs as the unique identifiers? The ID's seem most useful as a shorthand when browsing datasets. I guess it's a minor point though - as long as both URIs and ID's are unique, it should be fairly easy to convert between them :-) |
Hi Jonas, all.json does have issues. Any missing should be filed and/or fixed on okfn/licenses repo. :-) |
This issue was moved to rufuspollock-okfn/data.okfn.org-new#4 |
At the moment not clear exactly what is required for licenses and some of the time we just have ids and other times names and urls. We want to ensure given an id we always have a name and url - we could look this up from licenses.opendefinition.org ...
In terms of the interface we want to also handle the unknown case (should that ever happen!!)
This would be part of the tools datapackage normalize code.
The text was updated successfully, but these errors were encountered: