Difference between revisions of "CC Registry Ideas"
(→API) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | == People == | ||
| + | |||
| + | * Project lead: [http://littlesvr.ca/grumble/category/opensource/creative-commons/ Andrew Smith] | ||
| + | * Research assistants: [https://hosunghwang.wordpress.com/category/cdot/creative-commons/ Hosung Hwang], [http://annafatsevych.com/blog/ Anna Fatsevych] | ||
| + | |||
== Overview == | == Overview == | ||
| Line 46: | Line 51: | ||
As the API this is neither certain nor complete, it's just a representation of our ideas in DB schema form - to make it easier to see both flaws and possibilities in what we're thinking. | As the API this is neither certain nor complete, it's just a representation of our ideas in DB schema form - to make it easier to see both flaws and possibilities in what we're thinking. | ||
| + | |||
| + | [[Category:CC]] | ||
Latest revision as of 12:10, 29 May 2015
People
- Project lead: Andrew Smith
- Research assistants: Hosung Hwang, Anna Fatsevych
Overview
This page is a dump of various ideas we've had related to the goal of making CC-licenced material easier to find and to use.
At the core is a registry. It will:
- Store a blockhash (or similar) of an image.
- Associate that with licence information.
- Provide that information via an API for consumption by other websites and a simple web interface.
- Provide a revocation mechanism to deal with potential copyright claims quickly.
- Perhaps one day work with other kinds of works, not just images.
It is not intended to:
- Be a store of images, though it may be worthwhile to store the image as well as the blockhash for future upgrades/features)
- Be authoritative. That's impossible. But it will source the images from relatively trustworthy places.
Big Picture
Here are potentials subprojects to take on to get this done:
API
This is nowhere near certain and complete. It is the current dump of ideas in the form of an API. Once it's better defined it will be better documented.
| Method | Parameters and Tasks | Description |
| sampleMethod1 |
parameter1 (required)
parameter2 (optional)
|
Method description |
Database Schema
As the API this is neither certain nor complete, it's just a representation of our ideas in DB schema form - to make it easier to see both flaws and possibilities in what we're thinking.
