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

Normalize licenses and license names and display in dataset view #4

Open
rufuspollock opened this issue Apr 29, 2016 · 4 comments
Open

Comments

@rufuspollock
Copy link
Collaborator

From @rgrp on July 3, 2013 9:6

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.

Copied from original issue: frictionlessdata/frictionlessdata.io#55

@rufuspollock
Copy link
Collaborator Author

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

@rufuspollock
Copy link
Collaborator Author

From @mlinksva on August 6, 2014 20:32

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.

@rufuspollock
Copy link
Collaborator Author

From @jonasob on August 10, 2014 11:18

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 :-)

@rufuspollock
Copy link
Collaborator Author

From @mlinksva on August 10, 2014 18:59

Hi Jonas,

all.json does have issues. Any missing should be filed and/or fixed on okfn/licenses repo. :-)

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

No branches or pull requests

1 participant