Difference between revisions of "Web Integration"
Jon Phillips (talk | contribs) |
Jon Phillips (talk | contribs) |
||
| Line 32: | Line 32: | ||
The default approach for marking a licensed piece of content is demonstrated on our [http://creativecommons.org/license license page]. | The default approach for marking a licensed piece of content is demonstrated on our [http://creativecommons.org/license license page]. | ||
| − | === Dropdown === | + | ==== 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. | 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. | ||
| Line 40: | Line 40: | ||
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. | 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 == | |
| − | |||
| − | ==Search== | + | === 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 === | ||
| + | === Remix === | ||
| + | === Specific License === | ||
| + | === Use OpenSearch === | ||
==Browse== | ==Browse== | ||
| − | + | === CC Portal (Channel) on Site === | |
| − | + | === Limit Browsing to CC Licensed Content === | |
==Feeds== | ==Feeds== | ||
| − | + | === [[Syndication|CC annotations]] === | |
| − | + | === Feed URLs Facilitating CC Restrictions === | |
| + | (give some options) | ||
==Embed WebStatement== | ==Embed WebStatement== | ||
| − | + | === [[ID3]] === | |
| − | + | === [[XMP]] === | |
==Publish client-verifiable ID on web== | ==Publish client-verifiable ID on web== | ||
| − | + | === Hash === | |
| − | + | === Authority Lookup === | |
==[Re]use tracking== | ==[Re]use tracking== | ||
| − | + | === link: search === | |
| − | + | === [[Sample Pool API]] === | |
==.com integration== | ==.com integration== | ||
{{incomplete}} | {{incomplete}} | ||
Revision as of 18:37, 17 April 2007
This is a page describing "everything" a media hosting site could do to integrate CC and CC-related features.
Also install and see the ccHost software which implements many of these wishes as best practices.
Contents
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 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, 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 license page.
Dropdown
A drop-down list for selecting licenses seems to be quite effective. See how this is done on 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 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
Remix
Specific License
Use OpenSearch
Browse
CC Portal (Channel) on Site
Limit Browsing to CC Licensed Content
Feeds
CC annotations
Feed URLs Facilitating CC Restrictions
(give some options)
