The Comprehensive Knowledge Archive Network (CKAN) Launched Today
CKAN is the place to search for open knowledge resources as well as register your own. Those familiar with freshmeat (a registry of open source software), CPAN (Perl) or PyPI (python package index) can think of CKAN as providing an analogous service for open knowledge.
CKAN is a key part of our long-term roadmap and completes our work on the first layer of open knowledge tools:
- The Open Knowledge Definition which sets out what we mean by open knowledge.
- KForge/KnowledgeForge which provide a system for managing open knowledge projects and the services (repositories/wikis/mailing lists) they need.
- Comprehensive Knowledge Archive Network (CKAN) which provides a registry so that open knowledge creators and users can find other open knowledge projects and resources.
CKAN links in especially closely with our recent discussions of componentization: we envision a future in which open knowledge is provided in a much more componentized form (packages) so as to facilitate greater reuse and recombination similar to what occurs with software today (see the recent XTech presentation for more details). For this to occur we need to make it much easier for people to share, find, download, and ‘plug into’ the open knowledge packages that are produced. An essential first step in achieving this is to have a metadata registry where people can register their work and where relevant metadata (both structured and unstructured) can be gradually added over time.
We also make no bones that fact what we have is present is very simple, certainly when compared to the long-term vision — after all, we should remember it has taken software over thirty years to reach its present level of sophistication. Thus, rather than attempting to pre-judge the solution to open knowledge componentisation question (for example in the choice of metadata attached to each package), this beta version is the simplest possible thing that will provide value, and we look to user feedback (and we include ourselves here as users) to determine the future direction of development of the system.
What kinds of things do you expect people to register in CKAN?
Anything and everything — when we say knowledge we mean any kind of content, data or information. That said there are two main recommendations regarding what you register:
- First, we are looking for people to register ‘packages’ that is collections with some kind of structure rather than individual items. So a substantial set of photos, a datasets of all kinds, the writings of Shakespeare but not an individual blog, or your flickr photo collection (unless it is really big!).
- Second, we’re looking for stuff that’s open: that is material that people are free to use, reuse and redistribute without restriction (other than, perhaps, a requirement to share-alike).
Why Not Just Use the Creative Commons Search Facility in Google/Yahoo/etc
Two main reasons:
We focus on work that is open. Simply put the set of open work and the set of CC-licensed works are not identical because (a) not all Creative Commons licensed work is open (for example those which use the non-commercial provision are not) and (b) there are plenty of open works which do not use CC licenses (e.g. Wikipedia)
The registry is designed to support holding much more metadata than simply whether the work is open on not. In particular we want to be able to support automated installation of knowledge packages in the future (which requires things like dependency and version information).
Is CKAN itself open?
Of course, both the code that CKAN runs on and the data itself is open, see the license page: http://www.ckan.net/license/.
How Can I Get Involved
Start enter things into CKAN and editing existing entries — you don’t need to be the developer of a particular project or resource to enter it into the registry.
If you want to get more deeply involved join the okfn-discuss list and and introduce yourself or just drop an email to info [at] okfn [dot] org. If you want to just start hacking with the code see our development project page (then follow the links to subversion):