Difference between revisions of "CCPlus"

From Creative Commons
Jump to: navigation, search
(→‎Graphical Examples)
(→‎Adopters)
 
(78 intermediate revisions by 22 users not shown)
Line 1: Line 1:
 
{{Project}}
 
{{Project}}
 
{{Initiative}}
 
{{Initiative}}
 +
 +
{{Infobox|
 +
'''CC+''' denotes the combination of a '''CC official license (unmodified and verbatim)''' + '''another separate and independent agreement granting more permissions'''.
 +
 +
It is '''NOT''' a new or different license or any license at all, but a facilitation of '''more Permissions''' beyond '''ANY''' standard CC licenses.  Worth emphasizing is that CC+ (and use of that mark) requires that the work be licensed under a standard CC license that provides a baseline set of permissions that have not been modified or customized but reproduces the license verbatim.  The plus (+) signifies that all of those same permissions are granted, plus more. 
 +
 +
 +
Note that in order to use CC+ the additional permissions must be set forth in a separate document or resource -- the official legal code within the "corners" of the license cannot be added to or changed.
 +
 +
 +
If you want to adopt CC+, please '''(1)''' implement [[#Easy_CC.2B_Markups|CC+]] on your site, '''(2)''' [[#Adopters|add your project/company name]], and '''(3)''' [http://creativecommons.org/contact let us know!]
 +
|}}
 +
 +
 +
== Simple Explanation ==
 +
 +
The basic concept is to have a Creative Commons license + some other agreement which provides morePermissions.
 +
 +
[[Image:Cc-by-nc-3.0-88x31.png]] <span style="font-size: 280%">+</span> [[Image:Commercial-license-button.png]]
 +
 +
<span style="font-size: 80%">
 +
NOTE: Above, the CC license should link to the human deed and the generic commercial license would link to a place to get a commercial license for a work. The COMMERCIAL LICENSE is generic and should be tailored for specific uses with specific names of copyright holders.
 +
</span>
 +
 +
<span style="font-size: 80%">
 +
[http://wiki.creativecommons.org/images/b/b4/Commercial-license-button.svg Here is the SVG (vector graphic)] to the generic button if you would like to construct a commercial licensing button for your usage. The button is [http://creativecommons.org/publicdomain/zero/1.0/deed.en released into the public domain].
 +
</span>
  
 
== Summary ==
 
== Summary ==
−
CC+ is CC license + Another agreement.
 
  
−
CC+ is a protocol to enable a simple way for users to get rights
+
CC+ is a protocol providing a simple way for users to get rights
−
beyond the rights granted by a CC license. For example, a Creative
+
beyond the rights granted by a CC license. For example, a work's Creative
 
Commons license might offer noncommercial rights. With CC+, the
 
Commons license might offer noncommercial rights. With CC+, the
−
license can also provide a link to secure rights beyond noncommercial
+
license can link to a resource indicating how a reuser may secure commercial rights or other additional permissions or
−
rights -- most obviously commercial rights, but also services of use
+
services such as warranty, permission to use without attribution, or even access to physical media.
−
even when commercial use is permitted, such as warranty, ability to
 
−
use without attribution, or even access to performance or physical
 
−
media.
 
  
−
The CC+ architecture gives businesses a simple way to move
 
−
between the sharing and commercial economies. CC+ provides a
 
−
lightweight standard around these best practices and is available for
 
−
implementation immediately.
 
  
 
==Solvable Problems==
 
==Solvable Problems==
Line 31: Line 50:
 
Creative Commons has structured this so that you and/or your project can implement the rest of the social part to this equation.
 
Creative Commons has structured this so that you and/or your project can implement the rest of the social part to this equation.
  
−
* [[Image:Ccplus-general.pdf]] - CC and CC+ Overview for the World Wide Web (pdf)
+
* [[Media:Ccplus-general.pdf|CC+ General.pdf]] - CC and CC+ Overview for the World Wide Web (pdf)
 
* Concepts and Pieces
 
* Concepts and Pieces
 
** healthy ecosystem
 
** healthy ecosystem
Line 39: Line 58:
 
Similar to [[#Human]], CC has structured the Technical part of CC+ so that you can implement the technical standard to be in compliance.  
 
Similar to [[#Human]], CC has structured the Technical part of CC+ so that you can implement the technical standard to be in compliance.  
  
−
* [[Image:Ccplus-technical.pdf]] - CC+ Technical Implementation for the World Wide Web (pdf) explaining how to add CC+ functionality to your site.
+
* [[Media:Ccplus-technical.pdf|CC+ Technical.pdf]] - CC+ Technical Implementation for the World Wide Web (pdf) explaining how to add CC+ functionality to your site.
 
* Concepts and Pieces
 
* Concepts and Pieces
 
** [[RDFa]] and morePermissions
 
** [[RDFa]] and morePermissions
 
** [[OpenStar]]
 
** [[OpenStar]]
−
 
−
 
−
== Simple Explanation ==
 
−
The basic concept is to have a Creative Commons license + some other agreement which provides morePermissions.
 
−
 
−
''NOTE: Below, the CC license should link to the human deed and the generic commercial license would like to a place to get a commercial license for a work.''
 
−
 
−
http://i.creativecommons.org/l/by/3.0/88x31.png <span style="font-size: 280%">+</span> [[Image:Commercial-license-button.png]]
 
  
 
==Easy CC+ Markups==
 
==Easy CC+ Markups==
Line 63: Line 74:
  
 
Permissions beyond the scope of this license may be available at  
 
Permissions beyond the scope of this license may be available at  
−
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions" href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.
+
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions"  
 +
href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.
 
</pre>
 
</pre>
  
Line 102: Line 114:
 
   rel="cc:morePermissions" href="mailto:someuser@somedomain.com">custom license</a>
 
   rel="cc:morePermissions" href="mailto:someuser@somedomain.com">custom license</a>
 
</pre>
 
</pre>
 +
<br\>
 +
<b>Please note: the additional CC+ section in the deed will appear only if the document you're clicking to the deed <u>from</u> is accessible on the public Internet.</b>
  
−
== Examples ==
+
== Use Cases ==
  
−
=== Actual ===
+
* Restrict commercial use with a CC license with the NonCommercial condition, and then use a separate agreement with some party (could be yourself or third-party) to broker commercial rights (licensing, sales, reproduction, etc).
 +
* Require that adaptions are shared with a CC license with the ShareAlike condition, but offer a separate agreement (as above) for parties that do not want to release derivatives under the same license. Similar use cases for offering a private agreement for parties that wish to avoid fulfilling the Attribution or NoDerivatives properties of applicable CC licenses.
 +
* Offer a private agreement for parties that require one (eg for institutional policy or insurance reasons), even if their use would be within the scope of the public license grant.
 +
* To implement some type of [http://en.wikipedia.org/wiki/Street_Performer_Protocol Street Performer Protocol] system to put works to the public domain or into another license, preferably more free and in the community interest.
  
−
=== [[Strayform CCPlus Integration|Strayform CC+ Integration]] ===
+
== Media ==
  
−
=== Mockups ===
+
* The basics of this idea were formulated for [http://www.slideshare.net/rejon/phillips-remix-cycle-pixelodeon-2007 Pixelodeon 2007 slides].
 +
* [http://support.creativecommons.org/videos#ccp CC+ Video] by Eric Steuer. Script text [[CCPlus_video_script|here]].
 +
* [[Media:Ccplus-general.pdf|CC+ general.pdf]] - CC and CC+ Overview for the World Wide Web (pdf)
 +
* [[Media:Ccplus-technical.pdf|CC+ technical.pdf]] - CC+ Technical Implementation for the World Wide Web (pdf)
 +
* [[Media:Cc_plus_cc_zero_pr.pdf|Press Release.pdf]] - CC+ Official Press Release (pdf)
  
−
==== [[Yahoo Flickr CCPlus Integration|Yahoo! Flickr CC+ Integration]] ====
+
<gallery>
 +
Image:Ccplus slides.035.jpg
 +
Image:Ccplus slides.039.jpg
 +
Image:Ccplus_slides.044.jpg
 +
</gallery>
  
−
==== [[Yahoo Jumpcut CCPlus Integration|Yahoo! Jumpcut CC+ Integration]] ====
+
== Examples ==
  
−
==== [[Facebook CC+ Integration]] ====
+
===Jamendo===
 +
<gallery>
 +
Image:Ccplus_slides.046.jpg
 +
Image:Ccplus_slides.047.jpg
 +
Image:Ccplus_slides.048.jpg
 +
Image:Ccplus_slides.050.jpg
 +
Image:Ccplus_slides.051.jpg
 +
</gallery>
  
−
==== [[Virb CC Integration|Virb CC+ Integration]] ====
+
===Magnatune===
 +
<gallery>
 +
Image:Ccplus_slides.052.jpg
 +
Image:Ccplus_slides.053.jpg
 +
Image:Ccplus_slides.054.jpg
 +
Image:Ccplus_slides.055.jpg
 +
Image:Ccplus_slides.057.jpg
 +
Image:Ccplus_slides.058.jpg
 +
Image:Ccplus_slides.059.jpg
 +
</gallery>
  
−
== Usage ==
+
===BeatPick===
 +
<gallery>
 +
Image:Ccplus_slides.061.jpg
 +
Image:Ccplus_slides.062.jpg
 +
Image:Ccplus_slides.063.jpg
 +
Image:Ccplus_slides.064.jpg
 +
Image:Ccplus_slides.065.jpg
 +
</gallery>
  
−
* To restrict commercial use with a CC license with NC condition, and then use a separate agreement with some party (could be yourself or third-party) to broker commercial rights (licensing, sales, reproduction, etc).
+
=== Mockups ===
−
* To implement some type of [http://en.wikipedia.org/wiki/Street_Performer_Protocol Street Performer Protocol] system to put works to the public domain or into another license, preferably more free and in the community interest.
+
 
 +
* [[CCPlus Integration Mockups]]
 +
* [[Facebook CC+ Integration]]
 +
* [[Virb CC Integration|Virb CC+ Integration]]
 +
* [[Myspace CCPlus Integration|Myspace CC+ Integration]]
 +
* [[Imeem CCPlus Integration|imeem CC+ Integration]]
 +
* [[Blip CCPlus Integration|Blip.tv CC+ Integration]]
  
−
== Media ==
+
=== Actual ===
  
−
* The basics of this idea were formulated for [http://www.slideshare.net/rejon/phillips-remix-cycle-pixelodeon-2007 Pixelodeon 2007 slides].
+
* [[Strayform CCPlus Integration|Strayform CC+ Integration]]
−
* [http://support.creativecommons.org/videos#ccp CC+ Video] by Eric Steuer. Script text [[CCPlus_video_script|here]].
 
−
* [[Image:Ccplus-general.pdf]] - CC and CC+ Overview for the World Wide Web (pdf)
 
−
* [[Image:Ccplus-technical.pdf]] - CC+ Technical Implementation for the World Wide Web (pdf)
 
  
−
== Collaborators ==
+
== Adopters ==
  
 +
* [[Yahoo]]
 
* [[Blip.tv]]
 
* [[Blip.tv]]
 
* [[Jamendo]]
 
* [[Jamendo]]
 
* [[Magnatune]]
 
* [[Magnatune]]
−
* [[Pump Audio]]
 
 
* [[Beatpick]]
 
* [[Beatpick]]
 
* [[RightsAgent]]
 
* [[RightsAgent]]
Line 142: Line 193:
 
* [[Strayform]]
 
* [[Strayform]]
 
* [[Cloakx]]  
 
* [[Cloakx]]  
−
* [[Copyright Clearance Center]]  
+
* [[Copyright Clearance Center]] via http://ozmo.com/
−
* Add your project here!
+
* [[RRT Group]]
 +
* [[WIPmania]]
 +
* [[Uncensored Interview]]
 +
* [[LIFE Computers]]
 +
* [[New York State Senate]]
 +
* [[RightsPro]]
 +
* [[2lifeCast]]
 +
* [[Проект: Центр адаптации научной работы: Основы сексологии]]
 +
* [[rightclearing.com]]
 +
* [[comDB]]
 +
* add your project here!
 +
 
 +
== FAQ ==
 +
 
 +
=== What is a simple way of explaining CC+? ===
 +
 
 +
CC+ is just what it sounds like, a Creative Commons license plus another agreement. A copyright holder might pair a Creative Commons Attribution-NonCommercial license [CC] with a non-exclusive commercial agreement [+] enabling a company to license the work commercially for a fee.
 +
 
 +
=== Isn't CC+ just a technological facilitation of dual licensing? ===
 +
 
 +
Yes. A copyright holder who uses a Creative Commons license is already adding a license on top of their copyright. CC+ can make it easier for that copyright-holder to add other non-exclusive licenses/agreements as alternatives.
  
 
== External Links ==
 
== External Links ==
  
 
* http://labs.creativecommons.org/metadata
 
* http://labs.creativecommons.org/metadata
 +
* Press
 +
** http://blogs.magnatune.com/buckman/2007/12/creative-common.html
 +
** http://www.linuxelectrons.com/news/general/15548/creative-commons-launches-cc0-cc-programs
 +
** http://yro.slashdot.org/yro/07/12/19/1948209.shtml
 +
** http://reddevnews.com/news/article.aspx?editorialsid=9377
 +
** http://www.adtmag.com/article.aspx?id=21771
 
* Research
 
* Research
 
** http://www.warsystems.hu/?p=517
 
** http://www.warsystems.hu/?p=517
 
** http://creativecommons.org/weblog/entry/7711
 
** http://creativecommons.org/weblog/entry/7711
 +
** http://blogs.photopreneur.com/how-to-get-paid-for-your-flickr-photos
 +
* Links to CCPlus licenses
 +
** http://www.nysenate.gov/copyright-policy
  
−
== Relevant External Links ==
+
==How do you get involved?==
 +
Jump on over to the [http://creativecommons.org/contact CC-Community and/or CC-Licenses email lists] for further discussion on CCPlus.
  
−
* * [http://blogs.photopreneur.com/how-to-get-paid-for-your-flickr-photos Article] provides a tangential argument supporting tools like CC+ that can help get photographers paid for their work.
+
[[category:protocol]]
 +
[[Category:License and CCPlus]]

Latest revision as of 15:05, 21 December 2017


CC+ denotes the combination of a CC official license (unmodified and verbatim) + another separate and independent agreement granting more permissions.

It is NOT a new or different license or any license at all, but a facilitation of more Permissions beyond ANY standard CC licenses. Worth emphasizing is that CC+ (and use of that mark) requires that the work be licensed under a standard CC license that provides a baseline set of permissions that have not been modified or customized but reproduces the license verbatim. The plus (+) signifies that all of those same permissions are granted, plus more.


Note that in order to use CC+ the additional permissions must be set forth in a separate document or resource -- the official legal code within the "corners" of the license cannot be added to or changed.


If you want to adopt CC+, please (1) implement CC+ on your site, (2) add your project/company name, and (3) let us know!


Simple Explanation

The basic concept is to have a Creative Commons license + some other agreement which provides morePermissions.

Cc-by-nc-3.0-88x31.png + Commercial-license-button.png

NOTE: Above, the CC license should link to the human deed and the generic commercial license would link to a place to get a commercial license for a work. The COMMERCIAL LICENSE is generic and should be tailored for specific uses with specific names of copyright holders.

Here is the SVG (vector graphic) to the generic button if you would like to construct a commercial licensing button for your usage. The button is released into the public domain.

Summary

CC+ is a protocol providing a simple way for users to get rights beyond the rights granted by a CC license. For example, a work's Creative Commons license might offer noncommercial rights. With CC+, the license can link to a resource indicating how a reuser may secure commercial rights or other additional permissions or services such as warranty, permission to use without attribution, or even access to physical media.


Solvable Problems

Legal

Creative Commons has solved this with Creative Commons licensing. Creative Commons has this one locked down. Rely on CC.

Human

Creative Commons has structured this so that you and/or your project can implement the rest of the social part to this equation.

  • CC+ General.pdf - CC and CC+ Overview for the World Wide Web (pdf)
  • Concepts and Pieces
    • healthy ecosystem

Technical

Similar to #Human, CC has structured the Technical part of CC+ so that you can implement the technical standard to be in compliance.

  • CC+ Technical.pdf - CC+ Technical Implementation for the World Wide Web (pdf) explaining how to add CC+ functionality to your site.
  • Concepts and Pieces

Easy CC+ Markups

Simplest CC+ Example

My Book by Jon Phillips is licensed under a 

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons 
Attribution Non-Commercial 3.0 License</a>. 

Permissions beyond the scope of this license may be available at 
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions" 
href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.

A complete CC+ Implementation

<span xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/">

<span rel="dc:type" href="http://purl.org/dc/dcmitype/Text" property="dc:title">My Book</span> by 
<a rel="cc:attributionURL" property="cc:attributionName" href="http://rejon.org/my_book">Jon Phillips</a> 

is licensed under a 

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons 
Attribution Non-Commercial 3.0 License</a>. 

<span rel="dc:source" href="http://deerfang.org/her_book"/>
Permissions beyond the scope of this license may be available at 
<a rel="cc:morePermissions" 
href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.

</span>

A simple example of custom agreement on the same page

<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions" href="#agreement">below</a>

<a id="agreement">The Agreement</a>
... agreement text...

A simple agreement leading to mailto

<a xmlns:cc="http://creativecommons.org/ns#" 
   rel="cc:morePermissions" href="mailto:someuser@somedomain.com">custom license</a>

<br\> Please note: the additional CC+ section in the deed will appear only if the document you're clicking to the deed from is accessible on the public Internet.

Use Cases

  • Restrict commercial use with a CC license with the NonCommercial condition, and then use a separate agreement with some party (could be yourself or third-party) to broker commercial rights (licensing, sales, reproduction, etc).
  • Require that adaptions are shared with a CC license with the ShareAlike condition, but offer a separate agreement (as above) for parties that do not want to release derivatives under the same license. Similar use cases for offering a private agreement for parties that wish to avoid fulfilling the Attribution or NoDerivatives properties of applicable CC licenses.
  • Offer a private agreement for parties that require one (eg for institutional policy or insurance reasons), even if their use would be within the scope of the public license grant.
  • To implement some type of Street Performer Protocol system to put works to the public domain or into another license, preferably more free and in the community interest.

Media

  • Ccplus slides.035.jpg
  • Ccplus slides.039.jpg
  • Ccplus slides.044.jpg

Examples

Jamendo

  • Ccplus slides.046.jpg
  • Ccplus slides.047.jpg
  • Ccplus slides.048.jpg
  • Ccplus slides.050.jpg
  • Ccplus slides.051.jpg

Magnatune

  • Ccplus slides.052.jpg
  • Ccplus slides.053.jpg
  • Ccplus slides.054.jpg
  • Ccplus slides.055.jpg
  • Ccplus slides.057.jpg
  • Ccplus slides.058.jpg
  • Ccplus slides.059.jpg

BeatPick

  • Ccplus slides.061.jpg
  • Ccplus slides.062.jpg
  • Ccplus slides.063.jpg
  • Ccplus slides.064.jpg
  • Ccplus slides.065.jpg

Mockups

Actual

Adopters

FAQ

What is a simple way of explaining CC+?

CC+ is just what it sounds like, a Creative Commons license plus another agreement. A copyright holder might pair a Creative Commons Attribution-NonCommercial license [CC] with a non-exclusive commercial agreement [+] enabling a company to license the work commercially for a fee.

Isn't CC+ just a technological facilitation of dual licensing?

Yes. A copyright holder who uses a Creative Commons license is already adding a license on top of their copyright. CC+ can make it easier for that copyright-holder to add other non-exclusive licenses/agreements as alternatives.

External Links

How do you get involved?

Jump on over to the CC-Community and/or CC-Licenses email lists for further discussion on CCPlus.

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