Difference between revisions of "Web Integration"

From Creative Commons
Jump to: navigation, search
(→‎Search)
(De-SMW.)
 
(100 intermediate revisions by 24 users not shown)
Line 1: Line 1:
−
[[Category:Business]]
+
[[Category:Integration]]
−
[[Category:Media]]
+
[[Category:Documentation]]
−
[[Category:Best Case]]
 
−
[[Category:Best Practice]]
 
−
[[Category:Wishlist]]
 
−
[[Category:Challenge]]
 
 
[[Category:Guide]]
 
[[Category:Guide]]
 +
[[Category:Developer]]
 +
{{Best Practice}}
 +
__NOTOC__
 +
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
 +
This is a page describing ''everything'' a web-based (media) hosting site could do to integrate CC and CC-related features. From simple blogs to elaborate user-generated content communities, there are easy ways to share website content by publishing it under a Creative Commons license. Below we provide a basic overview of how you may integrate Creative Commons licensing into your website.
 +
</div>
  
−
This is a page describing "everything" a media hosting site could do to integrate CC and CC-related features.
+
<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;">
 +
== Tools of the Trade ==
 +
{{PageColumn|
 +
== [[Web Integration/HowTo | HowTo Guide]] ==
 +
While knowing about the various tools Creative Commons provides to integrate CC licenses in your web application, seeing examples of implementations is even better!
  
−
Also install and see the [[ccHost]] software which implements many of these wishes as best practices.
+
== [[LicenseChooser.js]] ==
  
 +
LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense.
  
−
==Choose license==
+
== [[Partner Interface]] ==
 +
This interface provides another method of integrating CC license choice in your web application using an <code>iframe</code> or HTML popup.
 +
}}
  
−
=== Default License ===
+
{{PageColumn|
 +
== [[Web Services | Web Services (API)]] ==
 +
The web services are designed to be a more flexible option for building a custom, fully integrated solution.
  
−
There should be a default license to govern all content that is project-wide. For websites, this involves adding a license with proper marking somewhere on the site and using this as the default for all other selections when applicable (feeds, default for user-generated-content, etc). Sites like [http://technorati.com/ Technorati] have licensed all content on their site under a specific license and note this at the bottom of their website on every page.
+
== ThirdParty Tools ==
 +
* [[Acts As License]] is a Ruby on Rails plugin that allows for integrating of CC license choice in your Rails web application as a server application building tool.
 +
}}
  
−
=== Individual Licenses ===
+
<br clear="all"/>
  
−
After a default license is applied on a project, then consider making an atomic approach to licensing where individual pieces of media have licenses applied both with physical marking and in technology, such as in [[Syndication]].
+
== Underlying Technology ==
  
−
=== User Preference ===
+
{{PageColumn|
 +
=== [[RDFa]] ===
  
−
Users should also be given the preference to set their default license and/or set the license per media item. And, all technologies should adapt to this user selection as with [[Syndication]]. For example, [http://flickr.com/ Flickr] allows users to select a license for uploaded photos as time of upload, but also have default license which is selected to reduce the amount of work a user must undertake for this task.
+
RDFa is a way of expressing RDF in XHTML. Creative Commons uses RDFa to express license and other information about works for the semantic web.
 +
}}
  
−
=== User Interface ===
+
{{PageColumn|
 +
=== [[CcREL]] ===
 +
A specification describing how license information may be described and attached to works.
 +
}}
  
−
==== Default ====
+
</div>
−
 
 
−
The default approach for marking a licensed piece of content is demonstrated on our [http://creativecommons.org/license license page].
 
−
 
 
−
==== Dropdown ====
 
−
 
 
−
A drop-down list for selecting licenses seems to be quite effective. See how this is done on [http://flickr.com/ Flickr] and others sites.
 
−
 
 
−
=== API ===
 
−
 
 
−
There should be a licensing API that might be part of a restful api that allows querying of the site, and outputting of possibly [[Syndication]] with proper license attribution, etc. There are other ways an API could specify license as well.
 
−
 
 
−
 
 
−
== Publish License on the Web ==
 
−
 
 
−
=== Link to License ===
 
−
 
 
−
The best way to show a license use is to link to the full URL back to the CC license. See the [http://creativecommons.org/license license page] for how this is done.
 
−
 
 
−
=== Use [[RDFa]] ===
 
−
 
 
−
RDFa is RDF in attributes and CC current recommendation for exhibiting semantic relationships for search engines and other machines to understand content relationships. See examples of this on http://labs.creativecommons.org
 
−
 
 
−
 
 
−
== Search ==
 
−
 
 
−
=== Commercial Use ===
 
−
 
 
−
Search by "Allows Commerical Use" A great example of this is on the http://www.google.com/advanced_search and http://search.yahoo.com/search/options
 
−
 
 
−
=== Remix ===
 
−
 
 
−
Search by "Allows Remix" See the examples in [[#Commercial Use]] Also, a great example is http://spinxpress.com/getmedia
 
−
 
 
−
=== Specific License ===
 
−
 
 
−
Search by specific licenses by name, such as Creative Commons Attribution 3.0 Germany. A great example of this is on http://spinxpress.com/getmedia
 
−
 
 
−
=== Use [[CcOpenSearch|OpenSearch]] ===
 
−
 
 
−
We recommend the usage of the [[CcOpenSearch|OpenSearch]] standard for empowering searching of content in an open manner with proper licensing.
 
−
 
 
−
==Browse==
 
−
=== CC Portal (Channel) on Site ===
 
−
=== Limit Browsing to CC Licensed Content ===
 
−
 
 
−
==Feeds==
 
−
=== [[Syndication|CC annotations]] ===
 
−
=== Feed URLs Facilitating CC Restrictions  ===
 
−
(give some options)
 
−
 
 
−
==Embed WebStatement==
 
−
=== [[ID3]] ===
 
−
=== [[XMP]] ===
 
−
 
 
−
==Publish client-verifiable ID on web==
 
−
=== Hash ===
 
−
=== Authority Lookup ===
 
−
 
 
−
==[Re]use tracking==
 
−
=== link: search ===
 
−
=== [[Sample Pool API]] ===
 
−
 
 
−
==.com integration==
 
−
 
 
−
{{incomplete}}
 

Latest revision as of 23:49, 30 August 2016


This is a page describing everything a web-based (media) hosting site could do to integrate CC and CC-related features. From simple blogs to elaborate user-generated content communities, there are easy ways to share website content by publishing it under a Creative Commons license. Below we provide a basic overview of how you may integrate Creative Commons licensing into your website.

Tools of the Trade

HowTo Guide

While knowing about the various tools Creative Commons provides to integrate CC licenses in your web application, seeing examples of implementations is even better!

LicenseChooser.js

LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense.

Partner Interface

This interface provides another method of integrating CC license choice in your web application using an iframe or HTML popup.

Web Services (API)

The web services are designed to be a more flexible option for building a custom, fully integrated solution.

ThirdParty Tools

  • Acts As License is a Ruby on Rails plugin that allows for integrating of CC license choice in your Rails web application as a server application building tool.


Underlying Technology

RDFa

RDFa is a way of expressing RDF in XHTML. Creative Commons uses RDFa to express license and other information about works for the semantic web.

CcREL

A specification describing how license information may be described and attached to works.

Retrieved from "https://wiki.creativecommons.org/index.php?title=Web_Integration&oldid=115420"