Announcing the Open Definition Licenses Service
The service is ultra simple in purpose and function. It provides:
- Information on licenses for open data, open content, and open-source software in machine readable form (JSON)
In addition to the service there’s also:
There’s data on more than 100 open (and a few closed) licenses including all OSI-approved open source licenses and all Open Definition conformant open data and content licenses. Also included are a few closed licenses as well as ‘generics’ — licensed representing a category (useful where a user does not know the exact license but knows, for example, that the material only requires attribution).
In addition various generic groups are provided that are useful when constructing license choice lists, including non-commercial options, generic Public Domain and more. Pre-packaged groups include:
- All licenses
- OSI compliant
- Open Definition compliant
- Specially selected set developed for CKAN that is perfect for data and content site license choosers.
The source for all this material is a git licenses repo on github. Not only does it provide another way to get the data, but also means that if you spot an error, or have a suggestion for an improvement, you can file an issue on the Github repo or fork, patch and submit a pull request.
Why this Service?
The first reason is the most obvious: having a place to record license data in a machine readable way, especially for open licenses (i.e. for content and data those conforming to the Open Defnition and for Software the Open Source Definition).
The second reason is to make it easier for other people to include license info into their own apps and services. Literally daily, new sites and services are being created that allow users to share or create content and data. But when they do that, if there’s any intention for that data to get used and reused by others it’s essential that the material get licensed — and preferably, openly licensed.
By providing license data in a simple machine-usable, web friendly format we hope to make it easier for people to integrate license choosers — and good license defaults — into their sites. This will provide not only greater clarify, but also, more open content and data — remember, no license usually means defaulting to the most restrictive, all rights reserved, condition.