- 1 Simple Explanation
- 2 Summary
- 3 Solvable Problems
- 4 Easy CC+ Markups
- 5 Use Cases
- 6 Media
- 7 Examples
- 8 Adopters
- 9 FAQ
- 10 External Links
- 11 How do you get involved?
The basic concept is to have a Creative Commons license + some other agreement which provides morePermissions.
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.
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 also provide a link by which a user might secure rights beyond noncommercial rights -- most obviously commercial rights, but also additional permissions or services such as warranty, permission 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.
Creative Commons has solved this with Creative Commons licensing. Creative Commons has this one locked down. Rely on CC.
- What is CC? - One Page (pdf)
Creative Commons has structured this so that you and/or your project can implement the rest of the social part to this equation.
- File:Ccplus-general.pdf - CC and CC+ Overview for the World Wide Web (pdf)
- Concepts and Pieces
- healthy ecosystem
Similar to #Human, CC has structured the Technical part of CC+ so that you can implement the technical standard to be in compliance.
- File:Ccplus-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:email@example.com">custom license</a>
- 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.
- The basics of this idea were formulated for Pixelodeon 2007 slides.
- CC+ Video by Eric Steuer. Script text here.
- CC+ general.pdf - CC and CC+ Overview for the World Wide Web (pdf)
- CC+ technical.pdf - CC+ Technical Implementation for the World Wide Web (pdf)
- Press Release.pdf - CC+ Official Press Release (pdf)
- CCPlus Integration Mockups
- Facebook CC+ Integration
- Virb CC+ Integration
- Myspace CC+ Integration
- imeem CC+ Integration
- Copyright Clearance Center
- Add your project here!
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.
How do you get involved?
Jump on over to the CC-Community and/or CC-Licenses email lists for further discussion on CCPlus.