CC & Open Access

921 views

Published on

Presented at University of Michigan Open Access Week, Monday, March 23, 2009.

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
921
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
14
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

CC & Open Access

  1. 1. CC & Open Access Nathan R. Yergler Creative Commons
  2. 2. share, reuse, and remix— legally
  3. 3. “Creative Commons provides free tools that let authors, scientists, artists, and educators easily mark their creative work with the freedoms they want it to carry.” 3
  4. 4. 4
  5. 5. <a    href=”http://creativecommons.org/licenses/by/3.0/”     rel=”license”>     Attribution 3.0 Unported </a> 5
  6. 6. 6
  7. 7. Open Access 7
  8. 8. “...free availability on the public internet, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers...” 8
  9. 9. “...free availability on the public internet, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers...” 9
  10. 10. My OA Tasklist ● Upload to Interweb ● Select a [CC] license ● Declare success? 10
  11. 11. An Aside: Why A CC License? ● Publishers/consumers are not all lawyers ● CC is a recognizable “brand” ● Network effect benefit: ● Use of a common license is beneficial if I'm reusing a single work ● Even more beneficial if I'm mixing works 11
  12. 12. “Without Technical Barriers” 12
  13. 13. “...free availability on the public internet, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers...” 13
  14. 14. “...free availability on the public internet, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers...” 14
  15. 15. “...free availability on the public internet, permitting any users to read, download, copy, distribute, print, search, or link to the full texts of these articles, crawl them for indexing, pass them as data to software, or use them for any other lawful purpose, without financial, legal, or technical barriers...” 15
  16. 16. Technical Implications ● Stable URL – we can link directly to it ● No user agent discrimination ● Resources are in a useful format [as data] ● “Open” ● Unencumbered ● XHTML? 16
  17. 17. CC Rights Expression Language 17
  18. 18. Previous Recommendation
  19. 19. <!­­   metadata ­­>
  20. 20. Pervasive Problems ● Opaque to parsers ● Opaque to humans ● Easy to screw up ● Overly verbose
  21. 21. Principles for Encoding in HTML ● Independence & Extensibility ● Don't Repeat Yourself (DRY) ● Visual Locality ● Remix Friendliness 21
  22. 22. RDFa ● Builds on [X]HTML ● Uses a few attributes (rel, rev, about, href, property, resource) to encode RDF triples in [X]HTML ● Extensible for emerging applications 22
  23. 23. <a    href=”http://creativecommons.org/licenses/by/3.0/”     rel=”license”>     Attribution 3.0 Unported </a> 23
  24. 24. 24
  25. 25. ccREL for OA Works ● What license is this work available under? ● How should I attribute the author? ● Can I obtain additional rights, if needed? 25
  26. 26. 26
  27. 27. 27
  28. 28. Building an “Open” Ecosystem 28
  29. 29. CC0 ● “No Rights Reserved” ● A Waiver, not a License ● Waives copyright and neighboring rights ● Replaces Dedication part of old PDDC ● Launched March, 2009 ● http://creativecommons.org/publicdomain/ 29
  30. 30. Norms ● Behavior expected for use of a work ● Enforced by social norms, not legal code ● For example: Citation ● Modeled using metadata, to be included on the deed ● Launch: 2009 Q4 30
  31. 31. Public Domain Assertion Tool ● Lots of PD works already exist ● How do people help identify them? ● Timeline: unknown; currently seeking support 31
  32. 32. CC Network ● Launched October 2008 ● A place creators to collect work references ● A platform for digital copyright registry exploration ● “Real world” demonstration of using distributed metadata ● Lays the foundation for exploring provenance 32
  33. 33. Profile Page 33
  34. 34. Network + License Badges 34
  35. 35. 35
  36. 36. Reciprocal Metadata Owner of “Identity” Work Has Owner 36
  37. 37. “Reproducible Research” ● Papers are only one part of research ● What about software, data, etc? ● Currently exploring how we might help ● Recommendations for appropriate licensing for each piece ● Metadata to describe the “bundle” 37
  38. 38. Metadata Enhanced Search ● GOOG/YHOO index basic license metadata ● What if we were able to search any metadata? ● Developed prototype around Open Education ● Exploring new YHOO possibilities 38
  39. 39. 39
  40. 40. Summary ● CC licenses are a natural choice for OA ● BOAI Definition implies very desirable technical characteristics for works ● ccREL/RDFa can be leveraged to add value ● Provide additional copyright information ● Add any metadata relevant to the publisher ● CC is building new tools on this core that we believe will enhance the “open” ecosystem 40
  41. 41. Nathan R. Yergler Chief Technology Officer Creative Commons nathan@creativecommons.org http://wiki.creativecommons.org/CC_and_OA

×