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

Licenses, list of most used ones #118

Open
ppKrauss opened this issue Sep 21, 2015 · 6 comments
Open

Licenses, list of most used ones #118

ppKrauss opened this issue Sep 21, 2015 · 6 comments

Comments

@ppKrauss
Copy link

List all useful (non-vanity) licenses, not only the open ones. Of course, the main are the open, and there are a lot of JSON materal at okfn/licenses, about licenses, but no "official CSV dataset". This licenses.csv is a draft proposal.


The prepare and maintenance will be simple, :

  1. converts the JSON data, as examplified at https://github.com/ppKrauss/dataset_licenses
  2. Use the context column (that was empty at JSON data), with a new semantic: the inferred "canonical license" of each license, to group similar ones.
  3. Add some more licenses, because the license list is a "knowledge source", not only a tool for open-licence advocacy.

Example of family: the licences OGL-UK-1.0, OPL-1.0, CC-BY-2.0, CC-BY-4.0, etc.are similar and can be grouped into a family. We elected the CC-BY as representant of the group, so cc-by is the label of the family (and CC-BY is the canonical license of the family).

@ppKrauss
Copy link
Author

Sorry, I changed the text of the issue, now is more simple and readable... ignore email text and use updated at datasets/registry/issues/118.

@pdehaye
Copy link

pdehaye commented Dec 1, 2015

This looks very good, and useful. I would recommend adding rows for intermediate licenses though: if this is meant as a reference, it might be that someone wants to mark their stuff using now obsolete licenses?
Also, the maintainer type is a string, not a number, in the datapackage.json

@ppKrauss
Copy link
Author

ppKrauss commented Dec 5, 2015

Hi @pdehaye , thanks (!), now I review, adding more 2 csv files, and correctiong datapackage.json. See dataset_licenses... I think now the project have a more definitive aspect.

@pdehaye
Copy link

pdehaye commented Dec 10, 2015

I think the name has to match what is in the datapackage.json, so the name of this dataset should be changed from dataset_licenses to licenses.

The sources listed in the datapackage.json don't match the sources in the README.md.

Also, implied.csv 's format is not documented in datapackage.json. (also, spelling wrong: "inffering" is actually "inferring")

@ppKrauss
Copy link
Author

@pdehaye , thanks. I changed the project's name to licenses, corrected spelling problems, and added the cited (in progress) implied.csv in the datapackage.

@ppKrauss
Copy link
Author

Hi @pdehaye , do you see okfn/licenses/issues/45? Perhaps we can join efforts there...

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

No branches or pull requests

3 participants