Difference between revisions of "Web Integration/HowTo"

From Creative Commons
Jump to: navigation, search
m (Reverted edits by Fred Benenson (Talk) to last revision by Greg.grossmeier)
Line 6: Line 6:
  
 
<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
 
<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
== 1. [[Web Integration/FileUploadExample|License Choice on file upload]] ==
+
{{PageColumn|
 +
== [[Web Integration/FileUploadExample|License Choice on file upload]] ==
 
Users should be able to choose which license they want for each file they upload.
 
Users should be able to choose which license they want for each file they upload.
  
Line 14: Line 15:
 
:: [[LicenseChooser.js]] or [[Web Services]]
 
:: [[LicenseChooser.js]] or [[Web Services]]
  
== 2. [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
+
== [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
 
In account settings, users should be able to specify a default license for their content they create on the site.
 
In account settings, users should be able to specify a default license for their content they create on the site.
  
Line 22: Line 23:
 
:: [[LicenseChooser.js]] or [[Web Services]]
 
:: [[LicenseChooser.js]] or [[Web Services]]
  
== 3. [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
+
== [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
 
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.
 
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.
  
Line 29: Line 30:
 
: Tools to use:
 
: Tools to use:
 
:: [[RDFa]] and [[CcREL|ccREL]]
 
:: [[RDFa]] and [[CcREL|ccREL]]
 +
}}
  
== 4. [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
+
{{PageColumn|
 +
== [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
 
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.
 
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.
  
Line 36: Line 39:
 
:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]
 
:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]
  
== 5. [[Web Integration/InterfaceExample|License aware user interfaces]] ==
+
== [[Web Integration/InterfaceExample|License aware user interfaces]] ==
 
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.
 
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.
  
Line 42: Line 45:
 
:: [[RDFa]], and [[CcREL|ccREL]]
 
:: [[RDFa]], and [[CcREL|ccREL]]
  
 
+
}}
</div>
 
 
 
<br clear="all"/>
 
  
 
== Adopters ==
 
== Adopters ==
Line 56: Line 56:
  
 
<br clear="all"/>
 
<br clear="all"/>
 +
</div>
  
 
=== See also ===
 
=== See also ===

Revision as of 21:30, 4 August 2009

The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporating CC license metadata functionality into your web application. This guide has been generalized from various plans for video, audio, or image sharing sites.

Below are 5 areas where integration can occur in your web application. While each web application may not need each of the 5 integrations, Creative Commons recommends that as many as practical are implemented.

License Choice on file upload

Users should be able to choose which license they want for each file they upload.

This will allow users to make fine-grain decisions about their works (so that some are CC and some are still All Rights Reserved)

Tools to use:
LicenseChooser.js or Web Services

Default License choice in account settings

In account settings, users should be able to specify a default license for their content they create on the site.

This can be combined with License Choice on File Upload to allow users to have the default license be, for example, CC:BY and in special cases some others be CC:BY-SA, or even All Rights Reserved.

Tools to use:
LicenseChooser.js or Web Services

Include license RDFa on content pages

Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.

This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.

Tools to use:
RDFa and ccREL

Include copyable attribution language with RDFa

This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.

Tools to use:
Web Services, RDFa, and ccREL

License aware user interfaces

Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.

Tools to use:
RDFa, and ccREL


Adopters

We have a long list of Content Directories which are basically sites, projects and people who have implemented CC licensing and/or have some type of CC licensing. This is the best list of high level CC license adopters, all generated from the community. NOTE: CC does not have a database of content or keep a defacto list of all those who use CC licenses. The list above is used to provide examples.

Assistance

If you are hoping to adopt this, please contact Fred Benenson (fred [at] creativecommons.org) and/or http://creativecommons.org/contact


See also

Back to Web Integration
Desktop Integration
Developers