Difference between revisions of "Web Integration"
Revision as of 20:52, 26 July 2007
This is a page describing "everything" a media hosting site could do to integrate CC and CC-related features.
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
- 1 Choose license
- 2 Publish License on the Web
- 3 Search
- 4 Browse
- 5 Feeds
- 6 Embed WebStatement
- 7 Education
- 8 Publish Client-Verifiable ID on Web
- 9 Re-use tracking
- 10 "More Rights" integration
- 11 Adopters
- 12 Future Adopters
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 Technorati have licensed all content on their site under a specific license and note this at the bottom of their website on every page.
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.
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, 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.
The default approach for marking a licensed piece of content is demonstrated on our license page.
A drop-down list for selecting licenses seems to be quite effective. See how this is done on Flickr and others sites.
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 license page for how this is done.
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.
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 CC search integration for several examples.
CC Portal (Channel) on Site
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.
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
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.
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.
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.
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
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
"More Rights" integration
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 information and examples and a license generator that will create a more permissions link.
If you support 100% of the media hosting wishlist relevant to your site, you get major kudos and your name here.
- Put your project here!
If you are hoping to adopt this, put your name down here to be contacted and worked with by Jon Phillips
- Sylvain ZIMMER / www.jamendo.com
- put your name here!