Successfully reported this slideshow.
Your SlideShare is downloading. ×

CC Tech Summit: Digital Copyright Registry Landscape

More Related Content

More from Mike Linksvayer

CC Tech Summit: Digital Copyright Registry Landscape

  1. 1. Creative Commons Technology Summit 2008 06 18 Digital Copyright Registry Landscape Mike Linksvayer Creative Commons Image by *saipal · Licensed under CC BY ·
  2. 5. “ We believe in the Net, not a centralized, Soviet-style information bank controlled by a single organization.” Creative Commons FAQ December 16, 2002
  3. 6. Q: Is Creative Commons building a database of licensed content? A: Absolutely not. We believe in the Net, not a centralized, Soviet-style information bank controlled by a single organization. We are building tools so that the semantic web can identify and sort licensed works in a distributed, decentralized manner. We are not in the business of collecting content, or building databases of content.
  4. 7. Why talk about digital copyright registries now?
  5. 8. Original photo by Brooke Novak · Licensed under CC BY · I AM NOT A
  6. 10.
  7. 11. Original photo by EffervescentEva · Licensed under CC BY ·
  8. 12. Why? (unordered) <ul><li>Orphans </li></ul><ul><li>+ [de]centralization </li></ul><ul><li>+ Need for provenance </li></ul><ul><li>+ Registry-like functionality is an aspiration/framing for CC technology </li></ul><ul><li>+ A gaggle of startups: explicit and accidental, for and non-profit </li></ul><ul><li>= Folks want to know what CC will do in this space </li></ul>
  9. 13. Outline <ul><li>What makes a copyright registry? </li></ul><ul><li>What makes a digital copyright registry? </li></ul><ul><li>Registry demand </li></ul><ul><li>Registry supply </li></ul><ul><li>Registry approaches </li></ul><ul><li>Challenges </li></ul><ul><li>Registry (as and for) Commons </li></ul>
  10. 14. <ul><li>For most of the history of copyright law in the U.S., registration was a necessary precondition to securing a copyright. </li></ul>
  11. 15. <ul><li>The aim of this traditional U.S. system was efficiency and clarity: registration (and the requirement to mark copyrighted work) made it relatively easy to identify a copyright holder to secure permission to use the copyrighted work in ways limited by copyright law. </li></ul>
  12. 16. <ul><li>In 1978, U.S. copyright became automatic. The U.S. Continues to maintain a copyright registry. </li></ul><ul><li>Because the registry is not mandatory, it is not a useful tool for identifying copyright owners. </li></ul>
  13. 17. <ul><li>In 2005 the U.S. Copyright Office received 531,720 registrations and recorded receipts from registration of $17,829,429. </li></ul><ul><li>In 2007 electronic filing went into beta. </li></ul>
  14. 18. What makes a digital copyright registry? <ul><li>Digital interfaces for copyright holders and users (of course) </li></ul><ul><li>Not necessarily defined or primarily motivated by “registration” </li></ul><ul><li>Scale </li></ul><ul><li>Global </li></ul>
  15. 19. Registry Demand <ul><li>UGC upload filtering </li></ul><ul><li>License management </li></ul><ul><li>User media organization </li></ul><ul><li>Collective rights management </li></ul><ul><li>Cultural heritage </li></ul><ul><li>Finding where content is posted </li></ul><ul><li>Timestamping (by copyright holders and users) </li></ul>
  16. 20. Supply: Build it and they will register <ul><li>RegisteredCommons (here) </li></ul><ul><li>SafeCreative (here) </li></ul><ul><li>Numly </li></ul><ul><li>DulyNoted </li></ul><ul><li>Probably others </li></ul>
  17. 21. Supply: Manage a domain / existing database <ul><li>Collecting societies </li></ul><ul><li>Cultural heritage institutions </li></ul><ul><li>MusicBrainz (here) </li></ul><ul><li>OpenLibrary (here) </li></ul>
  18. 22. Supply: Internal need or needed to provide other service <ul><li>Surely every big web/media company? </li></ul><ul><li>NoAnk Media (here) </li></ul>
  19. 23. Supply: ~Side effect of service <ul><li>Attributor (here) </li></ul><ul><li>Jamendo (here) </li></ul><ul><li> </li></ul><ul><li>Flickr </li></ul><ul><li>YouTube </li></ul>
  20. 24. Registry Approaches: Cataloging works <ul><li>User action/Attention </li></ul><ul><li>Crawl </li></ul><ul><li>Existing catalog curation by intermediary </li></ul><ul><li>Explicit registration by copyright holder </li></ul><ul><li>Penance for saying “crowdsource” ̶ read “Commercialization of Wikis” </li></ul>
  21. 25. Registry Approaches: Using the catalog <ul><li>Marked work with reference to registry </li></ul><ul><li>Content derived identifier lookup to registry </li></ul><ul><li>Search registry (many variants) </li></ul><ul><li>Processes naturally built on top of registry </li></ul>
  22. 26. Challenges <ul><li>Identifying works </li></ul><ul><li>Identifying owners </li></ul><ul><li>Namespace monopolists </li></ul><ul><li>Making it webby </li></ul><ul><li>Benefit>cost (for effort above what the web provides anyway) </li></ul><ul><li>Who pays? </li></ul><ul><li>Scams </li></ul><ul><li>METACRAP! </li></ul>
  23. 28. Commons <ul><li>Interoperable/SemWeb </li></ul><ul><li>Registries as open services </li></ul><ul><li>Registries with knowledge of public licenses </li></ul>
  24. 29. Beyond copyright <ul><li>Issues of provenance are of particular relevance to copyright licensing on the web, but the decentralized web presents trust of agents and data as a general problem. A commons registry could evolve to address these problems beyond the scope of copyright </li></ul>
  25. 30. Beyond copyright <ul><li>In line with CC relationship to the SemWeb and the shared interest of many in the CC community in addressing issues of commerce, privacy, trust, and transparency in a decentralized architecture (captured to some extent in ideas like “VRM”) </li></ul>
  26. 32. The Web is “the” registry <ul><li>What does your “registry” add to the web? </li></ul>
  27. 33. One view <ul><li>License </li></ul><ul><ul><li> </li></ul></ul><ul><li>Attribution </li></ul><ul><ul><li>Author: Mike Linksvayer </li></ul></ul><ul><ul><li>Link: </li></ul></ul><ul><li>Questions? </li></ul><ul><ul><li>[email_address] </li></ul></ul>Image by helmet13 · Licensed under CC BY ·