Difference between revisions of "Web Integration/HowTo"

From Creative Commons
Jump to: navigation, search
Line 2: Line 2:
  
 
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.
 
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 4 areas where integration can occur in your web application.  While each web application may not need each of the 4 integrations, Creative Commons recommends that as many as practical are implemented.
  
 
== 1. License Choice on file upload ==
 
== 1. License Choice on file upload ==
Line 13: Line 15:
  
 
== 2. Default License choice in account settings ==
 
== 2. Default License choice in account settings ==
* In account settings, users should be able to specify a default license for their work.
+
* In account settings, users should be able to specify a default license for their content they create on the site.
** Ex: A user licenses chooses CC-BY for all of their work and ignore license choice on upload.
+
** Ex: A user licenses chooses CC-BY for all of their work.
 +
* 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:
 
: Tools to use:
Line 22: Line 25:
  
 
== 3. Include license RDFa on content pages ==
 
== 3. Include license RDFa on content pages ==
* Part of Creative Commons' package is to include RDFa code that signals to machines how a work is licensed.
+
* Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.
* This will allow works to be scraped by search engines and other automatic content discovery services
+
* This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.
  
 
: Tools to use:
 
: Tools to use:
Line 31: Line 34:
  
 
== 4. Include "copyable" attribution language with RDFa ==
 
== 4. Include "copyable" attribution language with RDFa ==
* Similar to video embed code but this HTML is for bloggers and other republishers to use to fully attribute a work.
+
* 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:
 
: Tools to use:

Revision as of 22:20, 30 July 2009

How To Incorporate Creative Commons License Metadata into Your Web Application

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 4 areas where integration can occur in your web application. While each web application may not need each of the 4 integrations, Creative Commons recommends that as many as practical are implemented.

1. 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
Example Implementation (Pictures)

2. 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.
    • Ex: A user licenses chooses CC-BY for all of their work.
  • 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
Example Implementation (Pictures)

3. 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
Example Implementation (Pictures)

4. 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
Example Implementation (Pictures)

note: example of the cool use of the deeds