|
|
| (73 intermediate revisions by 22 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Business]] | + | [[Category:Integration]] |
| − | [[Category:Media]] | + | [[Category:Documentation]] |
| − | [[Category:Challenge]]
| |
| | [[Category:Guide]] | | [[Category:Guide]] |
| − | | + | [[Category:Developer]] |
| | {{Best Practice}} | | {{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> |
| | | | |
| | + | <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! |
| | | | |
| − | This is a page describing "everything" a media hosting site could do to integrate CC and CC-related features.
| + | == [[LicenseChooser.js]] == |
| − | | |
| − | Imitation of Flickr's CC integration is a recommended first pass:
| |
| − | * http://flickr.com/account/prefs/license/ -- user license selection (must be logged in to see)
| |
| − | * http://flickr.com/creativecommons -- CC browse
| |
| − | * http://flickr.com/search/advanced/ -- CC search
| |
| − | | |
| − | | |
| − | ==Choose license==
| |
| − | | |
| − | === Default License ===
| |
| − | | |
| − | 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.
| |
| − | | |
| − | === Individual Licenses ===
| |
| − | | |
| − | 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]].
| |
| − | | |
| − | === User Preference ===
| |
| − | | |
| − | 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.
| |
| − | | |
| − | === User Interface ===
| |
| − | | |
| − | ==== Default ====
| |
| − | | |
| − | 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
| |
| − | | |
| − | * See [[#"More Rights" integration]]
| |
| − | * Similarly, machine-readable attribution should be included, see examples on ccLabs.
| |
| − | | |
| − | == Search ==
| |
| − | | |
| − | Facilitate search based on license properties, typically:
| |
| − | * Any CC license
| |
| − | * CC licenses that allow remix
| |
| − | * CC licenses that allow commercial use
| |
| − | | |
| − | Examples include engines built into http://search.creativecommons.org
| |
| − | | |
| − | Ideally these search parameters may be set on the URL. See [[CcSearch_integration|CC search integration]] for several examples.
| |
| − | | |
| − | ==Browse==
| |
| − | === CC Portal (Channel) on Site ===
| |
| − | | |
| − | Create a channel on your project for all the CC licensed content. Good examples include http://flickr.com/creativecommons and http://jamendo.com/creativecommons/
| |
| − | | |
| − | === Limit Browsing to CC Licensed Content ===
| |
| − | | |
| − | This could be based upon tag, internal marking of licensing, and or any way a project sees fit to limit browsing possibly in connection with [[#Search]].
| |
| − | | |
| − | ==Feeds==
| |
| − | === [[Syndication|CC annotations]] ===
| |
| − | | |
| − | There should be a license for the entire feed as default (if your site uses default licensing) and then a per-item license. If you only have default license for your site, it is recommended to add the license to each item in the feed. See more about how to do this technically on our [[Syndication]] page.
| |
| − | | |
| − | === Feed URLs Facilitating CC Restrictions ===
| |
| − | | |
| − | Similar to [[#Browse]], provide a way to limit content in feeds based upon CC Restrictions similar to how its done in [[#Search]].
| |
| − | | |
| − | ==Embed WebStatement==
| |
| − | | |
| − | '''NOTE''': While it is important to embed metadata, it is a much higher priority to [[#Publish License on the Web]] and to mark what license you are using using the media you have licensed.
| |
| − | | |
| − | === [[ID3]] ===
| |
| − | | |
| − | For MP3s, it is recommended to use the standard [[ID3]] fields at the present time for embedding information about CC licenses for the content. This is the one exception to using [[XMP]], and it is recommended to search file-types that use [[ID3]] for [[XMP]] as well.
| |
| − | | |
| − | === [[XMP]] ===
| |
| − | | |
| − | We recommend that all use [[XMP]] for metadata embedding of CC licenses. This is de-facto metadata standard now with support from Adobe, Microsoft, and more.
| |
| − | | |
| − | ==Education==
| |
| − | | |
| − | While Creative Commons provides the necessary education about how Creative Commons licensing, technology and standards works, there are some key ways to explain Creative Commons on your media hosting site in relationship to your own project goals. Great examples of explaining Creative Commons should be linked to http://creativecommons.org/learnmore with emphasis on our explanatory videos. Also, http://makeinternettv.org/ does a great job of explaining generically how Creative Commons licensing works for media hosting sites. Specifically see their licensing page: http://makeinternettv.org/license/cc.php
| |
| − | | |
| − | ==Publish Client-Verifiable ID on Web==
| |
| − | | |
| − | See [[Marking_Works_Technical#Web_Statement]].
| |
| − | | |
| − | == Re-use tracking ==
| |
| − | === link: search ===
| |
| − | | |
| − | Reuse external to your repository should link back to the source work hosted by you. You can provide a service to your users by gathering reuse links via link: queries (e.g., via Yahoo! Site Explorer API), Technorati, and others.
| |
| | | | |
| − | === Sample Pool API ===
| + | LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense. |
| | | | |
| − | The [[Sample Pool API]] facilitates searching for content to reuse across repositories and notification upon reuse. See [[ccHost]] for a sample implementation.
| + | == [[Partner Interface]] == |
| | + | This interface provides another method of integrating CC license choice in your web application using an <code>iframe</code> or HTML popup. |
| | + | }} |
| | | | |
| − | == "More Rights" integration== | + | {{PageColumn| |
| | + | == [[Web Services | Web Services (API)]] == |
| | + | The web services are designed to be a more flexible option for building a custom, fully integrated solution. |
| | | | |
| − | Use rel="cc:morePermissions" to denote links allowing a user to do more than the CC public license permits, e.g., purchase commercial rights, warranty, purchase media, tickets, patronage... See ccLabs for [http://labs.creativecommons.org/metadata information and examples] and a [http://labs.creativecommons.org/dhtmllicense license generator] that will create a more permissions link.
| + | == 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. |
| | + | }} |
| | | | |
| − | = Adopters = | + | <br clear="all"/> |
| | | | |
| − | If you support 100% of the media hosting wishlist relevant to your site, you get major kudos and your name here.
| + | == Underlying Technology == |
| | | | |
| − | * Put your project here!
| + | {{PageColumn| |
| | + | === [[RDFa]] === |
| | | | |
| − | = Future Adopters =
| + | 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. |
| | + | }} |
| | | | |
| − | If you are hoping to adopt this, put your name down here to be contacted and worked with by [[User:Jon Phillips|Jon Phillips]]
| + | {{PageColumn| |
| | + | === [[CcREL]] === |
| | + | A specification describing how license information may be described and attached to works. |
| | + | }} |
| | | | |
| − | * Sylvain ZIMMER / www.jamendo.com
| + | </div> |
| − | * put your name here!
| |
