Building the Commons: Integrating CC in Your Application

Building the Commons: Integrating CC in Your Application

Nathan Yergler, CTO [email_address] Jon Phillips BizDev + Community Developer [email_address]

Audience Assumptions

Software Developers

70/30 Web/Desktop

Developing Content Creation or Reuse Applications

What does Integration look like?

Flickr

Internet Archive

CC Publisher

What is “Integration” ?

Applying Licenses to Content

Publishing Metadata

Content/Metadata Consumption

Applying Licenses to Content

Selecting a License Partner Interface Simple Chooser cc.js Web Services

Partner Interface

Simple Chooser

cc.js

Web Services

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

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

Partner Interface example.com/app Partner Interface example.com/app/exit

cc.js Javascript “widget” for web applications Currently in development Simplified, straight-forward integration Localized by CC partners

Javascript “widget” for web applications

Currently in development

Simplified, straight-forward integration

Localized by CC partners

cc.js <script src=&quot;http://api.creativecommons.org/jswidget/tags/0.1/complete.js? locale=en_US&quot;> </script>

<script src=&quot;http://api.creativecommons.org/jswidget/tags/0.1/complete.js? locale=en_US&quot;>

</script>

cc.js

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>

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>

The Simple Chooser

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

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

CC Publisher

Publishing Metadata

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

Discovery is at least as important as licensing

Publishing metadata for works enables discovery (among other things)

Google, Yahoo both index basic CC metadata

CC Metadata Copy-and-paste was important Semantic web seemed the way to go

Copy-and-paste was important

Semantic web seemed the way to go

RDF/XML in an HTML Comment so, so ugly hidden to humans hidden to parsers easy to screw up overly verbose

so, so ugly

hidden to humans

hidden to parsers

easy to screw up

overly verbose

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

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

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>

This work is licensed under Creative Commons <a rel=&quot;license&quot; href=&quot;http://creativecommons.org/licenses/by/2.5/&quot;>Attribution</a>

Wanted: Metadata solution: ...for any page, fragment, link, embedded object Colocated with human visible markup Publisher and consumer friendly Flexible, interoperable

Metadata solution:

...for any page, fragment, link, embedded object

Colocated with human visible markup

Publisher and consumer friendly

Flexible, interoperable

RDFa RDF a stands for attributes The mythical RDF-in-HTML is finally here

RDF

a stands for attributes

The mythical RDF-in-HTML is finally here

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.

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.

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

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

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

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

Commerce, and then some Metadata “hooks” cc:morePermissions cc:attributionURL cc:attributionName

Metadata “hooks”

cc:morePermissions

cc:attributionURL

cc:attributionName

Content/Metadata Consumption

Syndication / Aggregation Specs exist for asserting licenses for RSS, RSS 2, Atom Aggregators could easily display hints to users about content licenses

Specs exist for asserting licenses for RSS, RSS 2, Atom

Aggregators could easily display hints to users about content licenses

Metadata Browsing Expose embedded metadata to users in a non-intrusive way MozCC for CC metadata Operator for microformats

Expose embedded metadata to users in a non-intrusive way

MozCC for CC metadata

Operator for microformats

MozCC

Flickr + Think Free Flickr exposes license metadata through their API Think Free office reuses content based on this metadata Content creators gain greater exposure

Flickr exposes license metadata through their API

Think Free office reuses content based on this metadata

Content creators gain greater exposure

Coming Soon...

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

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

GTK+ widget

Nautilus Integration

Thanks! http://wiki.creativecommons.org/Integration http://wiki.creativecommons.org/Developer

Thanks!

http://wiki.creativecommons.org/Integration

http://wiki.creativecommons.org/Developer