Difference between revisions of "CC Registry Ideas"
(→API) |
|||
| Line 25: | Line 25: | ||
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. | 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. | ||
| + | |||
| + | <table cellspacing="0" cellpadding="5" width="100%" style="border-top: thin solid black;"> | ||
| + | <tr valign="top> | ||
| + | <td width="20%" style="border-bottom: thin solid black;font-weight:bold;background-color:#f0f0f5;">Method</td> | ||
| + | <td style="border-bottom: thin solid black;font-weight:bold;background-color:#f0f0f5;">Parameters and Tasks</td> | ||
| + | <td style="border-bottom: thin solid black;font-weight:bold;background-color:#f0f0f5;">Description</td> | ||
| + | </tr> | ||
| + | <tr valign="top"> | ||
| + | <td width="20%" style="border-bottom: thin solid black;">'''sampleMethod1'''</td> | ||
| + | <td style="border-bottom: thin solid black;">'''parameter1''' (required)<ul><li>Description</li></ul> | ||
| + | parameter2 (optional)<ul><li>Description</li></ul></td> | ||
| + | <td style="border-bottom: thin solid black;">Method description</td> | ||
| + | </tr> | ||
| + | </table> | ||
== Database Schema == | == 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. | 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 11:56, 16 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.
| Method | Parameters and Tasks | Description |
| sampleMethod1 | parameter1 (required)
|
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.
