Difference between revisions of "CC Registry Ideas"
(Created page with '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 block…') |
|||
| Line 1: | Line 1: | ||
| + | == 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. | 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. | ||
| Line 13: | Line 15: | ||
* Be a store of images, though it may be worthwhile to store the image as well as the blockhash for future upgrades/features) | * 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. | * 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: | Here are potentials subprojects to take on to get this done: | ||
[[File:CC_Registry_Ideas.png]] | [[File:CC_Registry_Ideas.png]] | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | == 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. | ||
Revision as of 14:26, 14 April 2015
Contents
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.
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.
