Your SlideShare is downloading. ×
0
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Integrating CC Licensing with Applications
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Integrating CC Licensing with Applications

7,120

Published on

Published in: Technology, Design
2 Comments
6 Likes
Statistics
Notes
No Downloads
Views
Total Views
7,120
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
89
Comments
2
Likes
6
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1.
      • Building the Commons: Integrating CC in Your Application
  • 2. Nathan Yergler, CTO [email_address] Jon Phillips BizDev + Community Developer [email_address]
  • 3. Audience Assumptions
  • 4. Software Developers
  • 5. 70/30 Web/Desktop
  • 6. Developing Content Creation or Reuse Applications
  • 7. What does Integration look like?
  • 8. Flickr
  • 9.  
  • 10.  
  • 11. Internet Archive
  • 12. CC Publisher
  • 13. What is “Integration” ?
  • 14. Applying Licenses to Content
  • 15. Publishing Metadata
  • 16. Content/Metadata Consumption
  • 17. Applying Licenses to Content
  • 18. Selecting a License
    • Partner Interface
    • Simple Chooser
    • cc.js
    • Web Services
  • 19. Partner Interface
    • Pop-up or iframe for web applications
    • Utilizes the same license selection rules as creativecommons.org/license
    • Returns a license URL, name to your application via HTTP GET
  • 20. Partner Interface example.com/app Partner Interface example.com/app/exit
  • 21. cc.js
    • Javascript “widget” for web applications
    • Currently in development
    • Simplified, straight-forward integration
    • Localized by CC partners
  • 22. cc.js
    • <script src=&quot;http://api.creativecommons.org/jswidget/tags/0.1/complete.js? locale=en_US&quot;>
    • </script>
  • 23. cc.js
  • 24. The Simple Chooser
    • Drop-down license selector
    • Optionally exclude licenses by attribute code
      • ie, ?exclude=nd
    • <script type=&quot;text/javascript&quot; src=&quot;http://api.creativecommons.org/rest/dev/simple/chooser.js&quot; >
    • </script>
  • 25. The Simple Chooser
  • 26. Web Services
    • Provide access to the full licensing dataset
    • Localized “questions” for implementing your own version of cc.org/license
    • HTTP interface; take as little or as much as you need
    • But... requires more work to use.
    • http://api.creativecommons.org/docs
  • 27. CC Publisher
  • 28. Publishing Metadata
  • 29. Metadata
    • Discovery is at least as important as licensing
    • Publishing metadata for works enables discovery (among other things)
    • Google, Yahoo both index basic CC metadata
  • 30. CC Metadata
    • Copy-and-paste was important
    • Semantic web seemed the way to go
  • 31. RDF/XML in an HTML Comment
    • so, so ugly
    • hidden to humans
    • hidden to parsers
    • easy to screw up
    • overly verbose
  • 32. Microformats
    • rel=&quot;license&quot; since 2004
    • Colocated with human visible markup
    • Concise
    • Problems:
      • Page level; what about audio, images, video, etc?
      • Scalability and interoperability of microformats
  • 33. rel=”license” microformat
    • This work is licensed under Creative Commons <a rel=&quot;license&quot; href=&quot;http://creativecommons.org/licenses/by/2.5/&quot;>Attribution</a>
  • 34. Wanted:
    • Metadata solution:
      • ...for any page, fragment, link, embedded object
      • Colocated with human visible markup
      • Publisher and consumer friendly
      • Flexible, interoperable
  • 35. RDFa
    • RDF
    • a stands for attributes
    • The mythical RDF-in-HTML is finally here
  • 36. 30 seconds of RDF
    • Triples:
      • Subject: always a URI
      • Predicate (verb): always a URI
      • Object: URI or literal (text)
    • One can say lots of things with these primitives.
    • And do things with what is said.
  • 37. 30 seconds of RDFa
    • Subject denoted by about attribute (defaults to current document).
    • Predicate denoted by rel (or rev ) if the object is a URI.
    • Predicate denoted by property if the object is a literal.
    • See http://rdfa.info
  • 38. CC Metadata Today
    • Publishing RDFa from the license chooser
    • Web services return RDFa
    • Looking for implementations:
      • audio, video, image sharing on the web that publishes RDFa
      • RDFa aware search
  • 39. Commerce, and then some
    • Metadata “hooks”
      • cc:morePermissions
      • cc:attributionURL
      • cc:attributionName
  • 40.  
  • 41.  
  • 42. Content/Metadata Consumption
  • 43. Syndication / Aggregation
    • Specs exist for asserting licenses for RSS, RSS 2, Atom
    • Aggregators could easily display hints to users about content licenses
  • 44. Metadata Browsing
    • Expose embedded metadata to users in a non-intrusive way
    • MozCC for CC metadata
    • Operator for microformats
  • 45. MozCC
  • 46. Flickr + Think Free
    • Flickr exposes license metadata through their API
    • Think Free office reuses content based on this metadata
    • Content creators gain greater exposure
  • 47.  
  • 48. Coming Soon...
  • 49. liblicense
    • C library
    • Allows querying of license metadata
    • Provides pluggable architecture for embedding/reading licenses from files
    • Builds on XMP work for embedded metadata
    • Allows us to build license selection UI in a straightforward manner
  • 50. GTK+ widget
  • 51. Nautilus Integration
  • 52.
      • Thanks!
      • http://wiki.creativecommons.org/Integration
      • http://wiki.creativecommons.org/Developer

×