Reuse tracking

From Creative Commons
Revision as of 22:24, 8 August 2012 by Jonathan Palecek (talk | contribs) (Created page with "= Reuse Tracking = RDF metadata presents information about a work's ancestry in a machine readable way. The websites of users who properly used our license chooser tool alre...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Reuse Tracking

RDF metadata presents information about a work's ancestry in a machine readable way. The websites of users who properly used our license chooser tool already have this setup. While it is possible to trace backwards to find a derived work's source, it is impossible to trace forwards to find all of a source work's derivatives without the aid of extra infrastructure.

In this page, you will find proposals for several ethical (respects user's privacy, does not involve radio-tagging people with malware or drm) solutions to this problem. These may either be systems that Creative Commons would prototype with the intention of being a reference for other organizations to build their own infrastructure; or systems that we would build an maintain our self, and provide an api to interested parties (either free in the spirit of open, or for a small fee to help offset hosting costs). All of the proposed systems below have their own advantages and disadvantages; none of them the silver bullet.


Proposal 1: Refback Tracking

Proposal 2: Hosted API