Creative Commons - User contributions [en]

Jswidget new

2013-05-10T05:49:12Z

Sanfang: /* Goals */

{{Software Project
|Description=LicenseChooser.js provides a lightweight method for integrating license selection into web applications.
|Bug tracker=http://code.creativecommons.org/issues/
|Code repository=http://code.creativecommons.org/viewsvn/jswidget/
|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
}}
{{Project}}
__NOTOC__

Creative Commons currently provides two methods for integrating license selection into applications: the [[Partner Interface]] and the [[Creative Commons Web Services|web service API]]. The CC Javascript Widget (LicenseChooser.js) provides an additional, lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as [[WpLicense]].

'''LicenseChooser.js is nearly ready! Please try the [http://code.creativecommons.org/viewsvn/jswidget/tags/0.97/ 0.97 preview].'''

== Users ==
* [[WpLicense]] uses LicenseChooser.js to provide a license selector for WordPress
* TypePad provides [http://everything.typepad.com/cc/ a widget] for adding a license to hosted blogs.

== Sample Usage ==

You can read the source of these examples; they demonstrate some (but not all) of the combinations for advanced usage described below.

* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/definitely-want-license.html CC License selector only]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/definitely-want-openness.html Selector without the choice of "No license"]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/ Basic usage (all options visible)]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/inside_form.html Basic usage from inside another form tag]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/default-is-no-license.html Selector where "no license" is the starting point]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/without-jurisdiction.html Selector without a jurisdiction choice]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/with-seed.html Selector with a specific license used as a starting point]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/with-seed-without-jurisdiction.html Selector with a specific license as a starting point with no jurisdiction selector, always using the "seeded" jurisdiction]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/with-seed-old-version.html Selector where an old license version was given as the seed]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/language-detect.html Selector that relies on Apache Content Negotiation for translations]

== Availability ==

You can play with a 0.97 pre-release right now!
* 2009-04-29: [http://mirrors.creativecommons.org/software/licensechooser-js/licensechooser-js-0.97.tar.gz Released 0.97]. '''This is the latest preview that is very close to 1.0.''' This release allows you to embed LicenseChooser.js inside a form tag. Thanks to John Horigan for reporting this issue and providing a patch (which we merged with some changes).
* 2009-03-16: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.96]. The help text for "Share alike" was wrong, mistakenly giving you the non-commercial help text. Fixed! This is an important update.
* 2008-09-23: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.95]. An anonymous bug reporter indicated that we overwrite the first JavaScript file found, even if it is not LicenseChooser.js. Fixed! This is an important update.
* 2008-08-27: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.94]. Stylistic issue found: image not always properly aligned with text in pop-up describing e.g. Share-Alike. We no longer user document.write() (yuck) to insert the HTML of the widget into the document; we now modify the innerHTML of a div we create ourselves. We may further harden the JS against namespace collisions with [http://kentbrewster.com/badges Kent Brewster's badges] strategy.
* 2007-10-10: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.92]. Stylistic updates: Alex has gone to town on the chooser and styled it. It only shows jurisdictions that have launched. There are no known pending technical or visual issues.
* 2007-08-23: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.91]. The license selector allows one to remove the jurisdiction selector. There is a "No license" choice. Translation is done using JavaScript and not hidden DOM elements. Application developers have more control over the defaults, including "no license" being choosable as the default.
* 2007-08-09: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.9]. We've changed the plan to add some features before 1.0 based on talking with potential users. All DOM elements are '''really''' prefixed with cc_js_ this time, and all strings '''really''' are available for translation this time. Documentation is updated for the 0.9 release, including a way to have the application developer specify only a single jurisdiction for the license. JSON output is validated before being sent to a web browser. Removed dependency on prototype.js. Server code changes to improve performance. Massive reduction of unused JS and CSS (this process began with 0.4).
* 2007-08-06: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.4]. All DOM elements are prefixed with cc_js_. The widget works in Opera and Safari and works with degraded functionality in Konqueror.
* 2007-08-01: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.3]. This release introduces Internet Explorer compatibility, Apache Content Negotiation to handle user language selection even if the server doesn't provide it for us, a hopefully-stable API for selecting a license, and license seeding.
* 2007-07-25: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.2]. The UI now doesn't ask or contain spurious questions, plus translation is halfway there.
* 2007-07-19: [http://sourceforge.net/project/showfiles.php?group_id=80503&package_id=239510 Released 0.1]. Don't try to use this in production, but DO let us know how it fits into your systems and what you would want us to change.

== Extra features ==
=== "Seeding" ===
* If the user has already selected a license through some other means, and you want to "seed" the JavaScript widget with the choices the user has already made, just create a hidden form field whose ID is cc_js_seed_uri with the URI of the license you want to start with.
** NOTE that whatever license version you provide, we always upgrade it to the most recent version the jurisdiction offers. We do display a '''Message''' underneath the license icon saying we did this.

=== Forcing a particular jurisdiction ===
To force the user to choose a license in a particular jurisdiction:
* First, use the "seeding" feature to seed the Attribution ("by") license in your jurisdiction
* Then, disable jurisdiction selection

=== Disabling jurisdiction selection ===
If you want to not offer the user a choice of jurisdictions:
* just append ?show_jurisdiction_chooser=n to the complete.js call.

=== Setting the license chooser to no license by default ===
If you want to set the license chooser to no license by default:
* just append ?default_option=no-license

=== Removing the "No license" option ===
If you want to not offer the user the option of selecting "no license:
* just append ?show_no-license_option=n to the query string
=== Language selection ===
* You can append ?locale=XX to your call to complete.js to choose a language. The example distributed as index.html in the distribution package sets the language to US English this way.
* If omitted, Apache Content Negotiation will select the most appropriate language based on the user's preferences, defaulting to US English.
=== Extracting results ===
All of these result extraction systems are demonstrated in the examples.
* There are two hidden form fields called '''cc_js_result_uri''' and '''cc_js_result_name''' that respectively store the URI and name of the license selected by the user. Just do <code>document.getElementById("cc_js_result_uri").value</code> (or "cc_js_result_name" instead) and you'll have the license information.
* There is an extra hidden form field containing the link to the image used. Simply get the element whose ID is '''cc_js_result_img''' and you will have a URL that is a permanent image. [http://en.wikipedia.org/wiki/Inline_linking Hotlink]ing these images is allowed and encouraged.

=== Styling ===
* Jswidget uses javascript magic to pull in a stylesheet, whether you want it to or not. Luckily, it puts the stylesheet at the very top of the header, so that you can easily override styles by including your own style sheet.

=== Namespacing ===
* All LicenseChooser.js HTML elements that have IDs or classes start with "cc_js_" to avoid namespace collisions.
* Similarly, all LicenseChooser.js JavaScript functions start with cc_js_. This is '''not''' true for the bundled Prototype.js library.

=== Full List of Query String Variables ===

* show_jurisdiction_chooser=(y/n)
**show/hide jurisdiction chooser
* show_cc0_option=(y/n);
**show/hide "CC0" option
* show_cc-license_option=(y/n);
**show/hide "CC license" option
* show_no-license_option=(y/n);
**show/hide "No license" option
*default_option=(cc0/cc-license/no-license);
**choose which option is present to the user first
*locale=(locale, ie 'en_US')
**choose language

You can specify as many of these options as you like by simply putting an '&' between them.

==== Examples: ====

*complete.js?locale=en_US&show_jurisdiction_chooser=n&default_option=cc-license&show_no-license_option=n
**Selector defaults to CC license chooser, is in US English, does not include a jurisdiction chooser, and does not include a "No license" option
*?locale=en_US&default_option=no-license&show_cc0_option=n
**Selector in US English which defaults to the "No license" option and doesn't include the cc0 option

==== Defaults ====

Currently, by default everything is displayed, and the CC license chooser is the default option. Thus, this query will return the exact same widget as the empty "complete.js"

complete.js?show_jurisdiction_chooser=y&show_cc0_option=y&show_cc-license_option=y&show_no-license_option=y&default_option=cc-license

(note that in this case, Apache content negotiation will be used to determine which language to use)

You might consider passing query string variables that assert settings that would be true due to default behavior anyway--this ensures that on the off chance that default behavior changes, your widget's behavior does not.

== Goals ==

The following list of general goals to remind us what we want out of LicenseChooser.js. You can expect most of it for 1.0.

See [[JsWidget/Plan]] to see what features are planned for what versions.

* Generate HTML suitable for use in a form which presents the basic license selector
* Provide compatibility with all [http://developer.yahoo.com/yui/articles/gbs/ A-grade browsers]
* Provide up to date license information by
** Utilizing licenses.xml to generate the appropriate Javascript on the server side. This may be done using a dynamic language such as PHP or through pre-processing to a static file when licenses are updated.
* Support new, expanded metadata including attributionName, attributionUrl and morePermissions.
* Provide a robust, scalable serving solution (if any server-side processing is needed) in order to support CC-hosted Javascript resources for the general public [http://www.articleeveryday.com/ article directory]

== Version expectations ==
=== Zero point something (like 0.4) ===
There are no guarantees, but we'd like to keep to the same promises as a 1.0 release
=== Something point zero (like 1.0) ===
We guarantee (outside of really urgent situation where we exercise a judgement call) that these will '''not''' change:
* The programmatic interface for the widget will not change
* The user interface for selecting licenses will not change

The following are the only things that '''may'' change:
* As new translations become available, the text may become increasingly internationalized
* As jurisdictions offer new licenses, the engine will update the choices available to a user

== Resources ==

* [http://code.creativecommons.org/viewsvn/jswidget/ LicenseChooser.js development in Subversion]
* [http://cctools.svn.sourceforge.net/viewvc/cctools/cclib/trunk/js/ cclib/trunk/js] in Subversion contains the Javascript used for the [http://labs.creativecommons.org/dhtmllicense/ DHTML License Selector]
* [[JsWidget/Security|Security considerations]]

[[Category:Developer]]
[[Category:Opensource]]
[[Category:Integration]]

CcMixter

2013-05-10T05:47:07Z

Sanfang: /* Setting up a Contest */

ccMixter uses [[ccHost]], an Open Source project sponsored by Creative Commons to build web infrastructure to support legal media sharing and remixing.

This page is to support ccMixter's use of ccHost:

----

== General ==

{{ContentDirectory|format=Sound|
mainurl=http://ccmixter.org/|
ccportal=|
ccfeed=http://ccmixter.org/rss/remix|
size=8871|
}}

* CC-only portal: everything is CC-licensed
* Notes: Runs on [[CcHost]], supports [[Sample Pool API]]
* Size last updated 20071006.

[[Category:Content_Directory]]

=== [[ccMixter Communication|Communication]] ===

=== [[ccMixter Press Releases|Press Releases]] ===

=== [[ccMixter Winner Announcements|Winner Announcements]] ===

=== [[ccMixter Roadmap|Roadmap / Timeline]] ===

== Procedures ==

=== [[Setting Up a Contest]] ===

=== [[Syncing Magnatune DB|Syncing Magnatune DB]] ===

== Administration ==

=== [[Restarting CC Mixter]] ===

=== Daily Administration Tasks ===

1. Read all forum posts -- look especially for:
:a. People reporting bugs/issues
:b. Flame wars

2. check out all uploads -- look for:
:a. Illegal media
:b. Mis-labled uploads ('sample' is really an a cappella)
:c. un-attributed remixes (uses samples from brad sucks but doesn't mark it as such)

3. handle requests/posts to cchost list

=== Regular ===

1. '''ccHost releases'''

2. '''mixter contests:''' at this point we can assume there will always be at least one contest in some stage of production -- currently we have the LisaD contest wrapping up and the Copyright Criminals one ramping up

3. '''Special projects:''' CC folks (like Mia and Mike) generate special deals/projects that need some kind of attenion.

4. Overall quality music quality management on mixter - this is a vague one but I spent a fair amount of time on a personal mission making sure the music on mixter was actually good -- reviewing/rewarding real
musicians/producers who upload.

=== Contests ===

==== Setting up a Contest ====

The process of creating a contest is basically like a wizard, admin
fills out some forms and a new virtual root is created with the relevant
tabs ('submit', 'entries', 'winners', etc.) the tabs visibility are
controlled by the dates of the contest.

The 'submit' tab is a form that knows how to add tags 'contest_entry'
and the contest name (e.g. '[http://www.articleeveryday.com/ free article directory]')

There is a 'submit entries' tab that only admins can see that mark the
uploads as [http://credit-protection.net credit protection] and the admin can additionally mark the
upload as the 'main source' or an extra upload (for stuff like loop
libraries or a cappellas, etc.)

the only part that's not automated is tagging the winners with the
'winner' tag (which I wrote a scriptlet for but that needs editing in
the winner's names and song title to work, so it's easier to just use
the admin screens for each song and click on 'winner' under 'system tags')

It's all pretty self evident except for this last part which could
probably stand to be part of a how-to faq on the wiki (which is the next part I added)

>>I guess the relevant pages for Magnatune were<br />
>>http://ccmixter.org/contests/magnatune/loops and<br />
>>http://ccmixter.org/contests/magnatune<br />
>><br />
>>Were these pretty much custom creations for the Magnatune contest?<br />
>><br />

The contest 'about' tab has the default behavior of showing the contest
description, logo and with relevant dates including online polling
information. If there is an online poll for the contest, the current
results/tally is shown here. On Mixter we replace this default with our
own beautiful contest home page.

The 'sources' tab has the default behavior of listing out all uploads
with the 'contest_source' tags.

http://www.ccmixter.co.za/yfm/view/contest/sources

for Magnatune we replace the default behavior with a completely custom
engine because none of the source was actually on the site. We publish
the source to that in CVS but (up until now) isn't really part of the
mainline cchost installation.

> One other dumb question -- how did Magnatune "receive" the entries. You<br />
> just pointed them to http://ccmixter.org/magnatune/view/contest/entries<br />
> or did you package them in a zip or something else like [http://www.repairpartstock.com/ laptop repair parts]?<br />

All contest entries end up in their own tree on the server (under the
local server path './contest/contest_name/user_name' as opposed to
'./people/user_name' (aka contrib). This lets you just zip up or ftp
point or whatever to just that directory.

For magnatune I wrote a script that, at one minute after the deadline,
zipped up the contest root and ftp'd the result to John's server[http://uslifeinsurancecompanies.com .]

==== Release Procedure Post-Contest ====

''The contest process is mostly automated except for the final stage of publicity.''

* Make release page
* test links
* make release text
* send off release text to be checked by contest sponsors
* update website
* update winners (contact them)
* submit release to release outlets

[[Category:CcMixter]]
[[Category:Content Communities]]

Photography

2013-05-10T05:11:29Z

Sanfang: /* Finding CC-licensed photos */

The internet and technology have changed how people access images, and photographers are responding by employing new methods to reach audiences. These methods include personal websites, social media tools, photo-sharing platforms and communities, and tools such as Creative Commons licenses that enable easy sharing and reuse of creative works.

CC licenses are a flexible way to share images while building on the strong foundation of traditional copyright law. Simply put, Creative Commons licenses allow the shift from “all rights reserved” to “some rights reserved,” enabling you to share your images under terms of your own choosing. This gives you control over distribution, and the non-exclusivity of the licenses means you can retain all commercial rights if desired.

[[#Photographers_using_CC_licenses|Photographers using CC licenses]] gain new audiences for their work on photo-sharing platforms like [http://www.flickr.com/creativecommons Flickr] and communities like [http://www.wikipedia.org/ Wikipedia]. Mohamed Nanabhay, Head of Online, Al Jazeera English, [http://creativecommons.org/weblog/entry/18213 writes]:
:“When launching our [CC] repository, we had thought that it would be a key resource for anyone producing content on the war and that it would primarily be used by other news organisations and documentary filmmakers. What we saw was both surprising and delightful. Soon after posting our first video, Wikipedia editors had extracted images to enhance the encyclopedia entries on the War on Gaza. Soon thereafter educators, filmmakers, video game developers, aid agencies and music video producers all used and built upon our footage.”

Wikipedia is a heavily-trafficked website with over 400 million unique visitors a month. Flickr contains over 200 million CC-licensed photos, establishing it as the Web’s single largest source of CC-licensed content.

In 2008, DigitalPhotoPro published an [http://www.digitalphotopro.com/business/creative-commons.html article on the use of CC licenses by professional photographers] with advice for those thinking of using CC themselves.

==Photographers using CC licenses==

===[[The_Power_of_Open/Text#Jonathan_Worth|Jonathan Worth]]===
:“Creative Commons enables me to use existing architecture really smoothly and to address the digital natives’ social media habits. The mode of information is the same, but the mode of distribution has changed. We don’t have all the answers, but CC lets me choose my ﬂavor and helps me take advantage of the things working against me.”

British photographer Jonathan Worth’s work hangs in the National Portrait Gallery in London. He teaches photography at Coventry University in the U.K, and [http://www.phonar.covmedia.co.uk/ his course materials] are released as open educational resources (OER) under [http://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA]. He has photographed actors Colin Firth, Rachel Hunter, Jude Law and Heath Ledger. He is also one of an emerging group of photographers experimenting with sustainable working practices for professional image makers in the digital age. Jonathan Worth has been featured in:
*[http://www.telegraph.co.uk/technology/news/8623680/How-the-Power-of-Open-can-benefit-photographers.html The Telegraph] - How the Power of Open can benefit photographers
*[http://www.bbc.co.uk/news/technology-13961051 BBC News] - "Photographer Jonathan Worth explained that Creative Commons allowed him to sell his work for commercial use while still giving it free to individuals who wanted it for other reasons."
*[http://www.bbc.co.uk/news/in-pictures-20495489 BBC News] - "Photography and open education"
*[http://thepowerofopen.org/ The Power of Open] - Stories of creators sharing knowledge, art, & data using Creative Commons

===[[Case_Studies/Lan_Bui|Lan Bui]]===
<div class="smimg">{{#show: Case_Studies/Lan_Bui|?Image Header|link=none}}
Lan Bui "makes media." From photography of tech celebrities (Veronica Belmont, Zadi Diaz, Casey McKinnon) and The Ninja to videos for professionals and events (Comic Con and Pixelodeon), Lan (with help from his brother Vu) makes them all from start to finish. Lan echoes the thoughts of other artists using Creative Commons; the idea that your work is, in a way, an advertisement for yourself and future work. Lan expresses this in this way: "I think that people pay me for my time and talent, not for the actual images I deliver."
</div>

===[[Case_Studies/Monkeyc.net|Monkeyc.net]]===
<div class="smimg">{{#show: Case_Studies/Monkeyc.net|?Image Header|link=none}}
Monkeyc.net is the moniker of John Harvey, a Brisbane-based former photojournalist who licenses his Flickr photo stream under Creative Commons. John is an active member of the Flickr community, having first uploaded a photo on 26 September 2004 and now sporting a collection of close to 1,000 images, and encourages others to engage likewise. Several of John’s photographs have been featured on Flickr’s ‘Explore’ page, as an indication of their popularity in the Flickr community.
</div>

===Vinoth Chandar===
Vinoth Chandar is a professional photographer who releases many of his photographs under the [[Creative Commons Attribution]] licence, saying that "I use [the] Attribution Creative Commons licence for all my photos because I want everybody to use my photo and credit me ... This way, my photos reach every corner of the world without any effort from my side except taking the photos and uploading it to Flickr."<ref>http://www.wired.co.uk/news/archive/2011-12/16/creative-commons-gallery</ref>

One example he used of the exposure provided by free culture licensing was the use of one of his photos for the cover of a popular Italian magazine. "I am an Indian and how else in the world can an Indian photographer expect his photo to be published in an Italian magazine? CC licence made this possible."<ref>http://www.wired.co.uk/news/archive/2011-12/16/creative-commons-gallery</ref>

==Enforceability of CC licenses in photography==
CC licenses have been upheld in several [[Case_Law|court cases]] around the world. A few of these cases pertain specifically to CC-licensed images.

*In [[Curry_v._Audax |Curry v. Audax]], Adam Curry, a former MTV VJ and one of the pioneers of podcasting, published photos onto his Flickr account under a BY-NC-SA license. A Dutch tabloid reprinted four of the photos in a story about the Curry family's public persona verses real private life. Curry sued the tabloid for violating the portrait rights of his family and for copyright violation over the improper user of his Flickr photos. The Dutch court held that, in the future, the tabloid could not use any of the photos from Flickr in the future unless under the terms of the photos' CC license or with permission from Curry.
*In [[Gerlach_vs._DVU|Gerlach vs. DVU]], Gerlach took a picture of the German politician Thilo Sarrazin at a public event and published it online under the Creative Commons license BY SA 3.0 Unported. Later the DVU, a German political party used the picture on their website without the plaintiff's name, the license notice or any other requirement of the license. The applicant sent a notice and takedown letter to which the party didn't react. Subsequently the applicant sought preliminary injunction before the Disctrict Court of Berlin against the unauthorized publication of the picture. The District Court of Berlin granted the injunction because the applicant had successfully established prima-facie evidence of authorship, of the licensing and of the breach of the license.
*In [[TA_3560/09,_3561/09,_Avi_Re%27uveni_v._Mapa_inc._%D7%99%D7%A9%D7%A8%D7%90%D7%9C:_%D7%9C%D7%A8%D7%90%D7%A9%D7%95%D7%A0%D7%94,_%D7%91%D7%99%D7%94%D7%9E%22%D7%A9_%D7%90%D7%9B%D7%A3_%D7%A8%D7%99%D7%A9%D7%99%D7%95%D7%9F_%D7%A7%D7%A8%D7%99%D7%90%D7%99%D7%99%D7%98%D7%99%D7%91_%D7%A7%D7%95%D7%9E%D7%95%D7%A0%D7%A1 |Avi Re’uveni v. Mapa inc.]], plaintiffs uploaded photographs to Flickr and and offered them under a Creative Commons BY-NC-ND license. The defendant made a collage from the plaintiffs’ and other photographs and sold them without attribution. The court found the defendant guilty of copyright infringement. The defendant claimed ignorance of the copyright and license, but the court found that this did not matter.

==Photo-sharing sites that have enabled CC licenses==

===[[Case_Studies/Flickr|Flickr]]===
<div class="smimg">{{#show: Case_Studies/Flickr|?Image Header|link=none}}
Flickr was one of the first major online communities to incorporate Creative Commons licensing options into its user interface, giving photographers around the world the easy ability to share photos on terms of their choosing. As the Flickr community grew, so did the number of CC-licensed images — currently there are well over 200 million on the site — establishing Flickr as the Web’s single largest source of CC-licensed content.
</div>

===[[Case_Studies/DeviantART|DeviantART]]===
<div class="smimg">{{#show: Case_Studies/DeviantART|?Image Header|link=none}}
deviantART is an online community dedicated to showcasing art as prints, videos and literature. CC license options are built into deviantArt's UI, allowing users to set the permissions they want their works to carry. Naturally, different users choose different options for their works, including All Rights Reserved.
</div>

===[http://creativecommons.org/weblog/entry/22882 Fotopedia]===
Fotopedia is a breathtaking application for the iPhone and iPad. The app builds on the concept of a coffee table book, updating and enhancing the browsing experience for the web. This project is possible thanks to Creative Commons, as over 18,000 of the pictures in Fotopedia Heritage book are under one of the CC licenses. The pictures come from all around the world; as individual photographers and organizations license their high quality photos under Creative Commons, the book will only grow as a community contributed and shareable resource.

===[[Case_Studies/National_Library_of_Australia_'Click_and_Flick'|National Library of Australia: 'Click and Flick']]===
<div class="smimg">{{#show: Case_Studies/National_Library_of_Australia_'Click_and_Flick'|?Image Header|link=none}}
'Click and Flick' is a National Library of Australia (NLA) initiative to open their online pictorial gateway, PictureAustralia, to contributions from the Australian public. PictureAustralia encourages people to make their material available on the archive under the CC licenses, as part of two dedicated Flickr image pools: ‘PictureAustralia: Ourtown’ and ‘PictureAustralia: People, Places and Events’.
</div>

===[[Case_Studies/Newsbank_Image|Newsbank Image]]===
<div class="smimg">{{#show: Case_Studies/Newsbank_Image|?Image Header|link=none}}
Newsbank Image is one of South Korea's largest and most comprehensive photo-archives. The photograph archive website provides images produced by Media companies, photographers as well as web-friendly versions containing watermarks, original images, all which maintain the marking of original creators. Users can choose to upload their photos under CC licenses.
</div>

===[[Case_Studies/Culture.si|Culture.si]]===
<div class="smimg">{{#show: Case_Studies/Culture.si|?Image Header|link=none}}
A comprehensive online guide to Slovene culture, Culture.si covers contemporary art, culture, and heritage in Slovenia. Over 2,300 articles in English and the fastest growing independent free image bank (currently over 1,500 images) are offered for reuse under Creative Commons licenses.
</div>

==How To Publish photos in an online community==
One way to increase visibility and access to your photos is to share it with an existing community that has enabled CC licensing, making it easy for you to indicate the license along with other information, such as who to attribute. In addition, search engines like Google and Yahoo! will index your work as CC licensed if the metadata is properly attached. See [[Publish/Images]] for more info.

==Finding CC-licensed photos==
Thanks to the machine-readability of CC licenses, CC-licensed images can be found via:

*[http://images.google.com/advanced_image_search?hl=en Google Advanced Image Search] by specifying options under "Usage Rights"
*[http://images.search.yahoo.com/images/advanced?ei=UTF-8 Yahoo! Advanced Image Search] by specifying options under "Creative Commons License"
*It appears that Yahoo Advanced Image Search no longer offers this option. Can anyone else confirm this?
*[http://docs.google.com/support/bin/answer.py?answer=179622 Google Docs], where Google Image Search has been integrated
*[http://search.creativecommons.org/ CC Search Portal], which is not a search engine, but a tool that offers convenient access to search services provided by independent organizations, such as Flickr, Google, and Wikimedia Commons (media repository for [http://www.articleeveryday.com/ articles] featured on Wikipedia).

==Related resources==
*[[Journalism|CC in Journalism]]
*[[CC_Factsheet|CC Factsheet]]

==References==
<references>

Version 3

2013-05-10T05:09:13Z

Sanfang: /* International Harmonization – Moral Rights */

= Creative Commons Version 3.0 Licenses — A Brief Explanation =

===''by Mia Garlick, General Counsel Creative Commons''===

Since April 2005, Creative Commons has been working on versioning up its core licensing suite. The Creative Commons licenses (For an overview of the licenses, ''see:'' [http://creativecommons.org/about/licenses/meet-the-licenses]) serve as an important vehicle by which many millions of creators clearly signal to the world that they are happy for members of the public to engage in some of the exciting new uses of content that are made possible by digital technologies. Using a CC license, an artist can, for example, invite the public to share their work or mash it up (on certain conditions).

A distinctive feature of CC’s licensing infrastructure is ensuring that it is comprehensible to both humans (the Commons Deed) and machines (the metadata) as well as enforceable in a court of law (the Legal Code, which is the actual license). But another important aspect of the CC licensing system is to ensure that it respected by the community of people who apply our licenses to their content, who use CC-licensed content and who are committed to enabling free culture.

Creative Commons regularly invites and receives feedback about its licenses and how they may be able to be improved to better serve the people who use them and who use CC-licensed content. Obviously, all things can be improved with the benefit of hindsight and experience; also, the environment within which CC licenses are used is always changing. When CC first released its licenses, for example, the use of video and video-sharing sites had not yet been deployed, let alone used to the extent they are today.

We released version 1.0 of our licenses in December 2002 (''See'' CC Weblog, Creative Commons Launches, December 15, 2002, [http://creativecommons.org/weblog/entry/3484]). Like software releases, we track the different licenses by version. In May 2004, we versioned to 2.0 (''See'' CC Weblog, Announcing (and explaining) our new 2.0 licenses, May 25, 2004, [http://creativecommons.org/weblog/entry/4216]) and then made a minor tweak to the attribution clause in June 2005 (''See'' CC Weblog, Comments Period Drawing to a Close for Draft License Version 2.5, May 29, 2006, [http://creativecommons.org/weblog/entry/5457]) and versioned to 2.5. Now, CC is versioning to 3.0. We announced a timetable for versioning to 3.0 back in May 2006 (''See'' Mia Garlick, ‘Getting to Version 3.0,’ May 17, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-May/003557.html]); and we have followed the consultation process in the timetable even though the schedule itself has been considerably delayed while we take account of all of the different interest groups that are relevant to CC licenses.

==Background to Version 3.0==

The process of versioning to 3.0 began back around April 2005 as part of discussions with Debian [http://www.debian.org/] and the Massachusetts Institute of Technology (MIT) [http://mit.edu/] about ways to improve the clarity of our licenses. Although discussions with Debian and MIT initiated consideration of a new license version, ultimately, version 3.0 grew to be about much more than these two projects — it focused on internationalizing the “generic” license and international harmonization of the CC licenses. Additionally, it expanded to encompass Creative Commons' long-held vision [http://creativecommons.org/weblog/entry/5709] of establishing a compatibility structure to allow interoperability between different flexible content copyright licenses.

===''Debian''===

As you may know, Debian describes itself as “an association of individuals who have made common cause to create a free operating system” [http://www.us.debian.org/intro/about] and the volunteer group has worked together to create an operating system called Debian GNU/Linux. The project and all developers working on the project adhere to the Debian Social Contract [http://www.us.debian.org/social_contract]. The Debian Free Software Guidelines (DSFG) [http://www.us.debian.org/social_contract#guidelines] form part of the Debian Social Contract and define the criteria for “free software” and so what software is permissible in the distribution.

One part of the Debian community is debian-legal [http://lists.debian.org/debian-legal/] — a mailing list whose members provide “guidance for the Debian project on, among other things, the acceptability of software and other content for inclusion in the Debian operating system.” [http://people.debian.org/~evan/ccsummary.html] They work primarily involves reviewing software against the DFSG to determine if the packages constitute “free software” per the DFSG. Contributors to the Debian project can then take these determination into account when making decisions about what to include in individual packages.

From time to time the debian-legal list provides a review of a well-known software license to express a rough consensus opinion on whether software released solely under the license would satisfy the definition of “free software” according to the DSFG. Although these summaries are not binding, they do provide some basis for the Debian project to make decisions about individual packages. Although debian-legal work primarily in reviewing software programs and Creative Commons licenses are not designed for software, debian-legal notes that the:

“Creative Commons licenses are still of interest to the Debian project. Debian includes documentation for programs, and many programs included in Debian use digital data such as images, sounds, video, or text that are included with the programs in Debian.” (''Id.'')

Consequently, debian-legal reviewed the CC licenses and concluded that none of the Creative Commons core licensees were free according to the DFSG and recommended that works released under these license “should not be included in Debian.” (''Id.'')

It is clear that the licenses that contain a NonCommercial or a NoDerivatives restriction (e.g. Attribution-NonCommercial, Attribution-NonCommercial-ShareAlike, Attribution-NoDerivatives, Attribution-NonCommercial-NoDerivatives ) will never be able to comply with the DFSG because these violate basic principles articulate in the DSFG — specifically, DSFG 1 which requires that a licensee be able to sell copies of the work, DSFG 3 which requires a license to permit the making of derivative works and DSFG 6 which proscribes discrimination against any field of endeavor.

====DRM====

But this should still leave the CC Attribution and Attribution-ShareAlike licenses as DSFG-compliant. On reviewing debian-legal’s issues with these licenses, it seemed clear to Creative Commons that, for the most part, minor amendments and clarifications to the licenses should be able to address debian-legal’s concerns. (For an outline of these concerns, see [http://evan.prodromou.name/ccsummary/ccsummary.html]) One topic, however, that was not minor and proved to be much debated as part of the version 3.0 license discussions was the anti-TPM clause in the CC licenses; TPM being technological protection measures such as encryption which have received legal protection in many jurisdictions around the world, which make it a civil (and sometimes) a criminal offence to circumvent these measures.

The Creative Commons licenses prohibit a licensee applying a TPM to a licensed work that restricts the rights granted under the license. (''See e.g.,'' clause 4(a) “You may not distribute, publicly display, publicly perform, or publicly digitally perform the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement.” of the CC Attribution license ([http://creativecommons.org/licenses/by/2.5/legalcode])) In essence, this clause is intended to ensure that a person cannot exercise the freedoms granted by a CC license to apply technologies that restrict those freedoms for others.

In Debian’s view, this prohibition violates DSFG #1 because it prevents a licensee from being able to distribute works in the format of their choice. The consequence of this is that CC-licensed content cannot, for example, be included by a licensee in a Sony Playstation game or other platforms that exist on TPM.

An important thing to note, however, is that this limitation only applied to CC licensees. CC licensors are of course free to license their works on a Sony or other TPM-ed platform whilst also CC licensing it. One example of this is the Beastie Boys track ‘Now Get Busy’ that appeared on the WIRED CD under a CC Sampling license [http://creativecommons.org/wired] but was then also made available on iTunes [http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewAlbum?playlistId=15146499&selectedItemId=15146497&s=143441 ].

To avoid interfering with the freedom of the licensed content and allowing a licensee to lock up the content on a TPM-ed platform, Debian proposed that CC’s so-called “anti-TPM” provision to allow a licensee to distribute the CC-licensed work in any format, including a TPM-ed format, provided that the license distributed the work in at least one format that did not restrict another person’s exercise of rights under the license. This proposal became known as the “parallel distribution” proposal.

Creative Commons initially agreed to include the parallel distribution proposal as part of the discussion draft for the Version 3.0 amendments. The rationale for this initial acceptance was that it could accommodate the objectives of the anti-TPM clause (being free culture) whilst also addressing Debian’s concerns that people be free to create works for distribution on TPM-ed platforms.

The parallel distribution proposal did not, however, survive discussions with the Creative Commons International affiliates [http://creativecommons.org/worldwide/]. The affiliates are responsible for “porting” the CC licenses to their local jurisdiction (discussed in greater detail below) and for fielding a wide range of questions about CC licenses and their implementation in various projects throughout the world. Based on their experience with the diverse communities that use and rely on CC licenses and explaining the licenses to different constituencies, the CCi affiliates were strongly opposed to the introduction of a parallel distribution scenario for various reasons, including: (1) the lack of demonstrated use cases showing a strong need among CC licensees for this kind of an exception to the existing “anti-TPM” language; (2) risks of unduly complicating the licenses which defeats alot of the purpose of CC licenses, namely to be simple and easy to use and to understand; and, (3) the strong opposition to technological protection measures in general by many in the CC community.

CC did, however, include the parallel distribution proposal as part of the public license discussions when those were launched in August 2006 (''See'' Mia Garlick, Version 3.0 – Public Discussion, August 9, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/003857.html]) so that the community on those lists could debate the merits of the proposal.

The discussions about the parallel distribution proposal on the cc-licenses email list were very intense. Various participants argued in favor of the parallel distribution amendment on the grounds that the “anti-TPM” clause violated DSFG #1 and achieved little, if anything. Taking the advantage of a Sony Playstation again, if CC-licensed content cannot be included in games for the PS2 platform, the CC licensee is restricted in what they can do with the content, the PS2 gamer cannot play a game with CC-licensed content and Sony are unlikely to notice the absence of this content and will continue along as business as usual with a TPM-ed platform, irrespective of any anti-TPM ban in the CC licenses.

When asked about the extent to which there was a demonstrated need by developers (as licensees) to be able to utilize CC-licensed content in TPM-ed environments, advocates of the parallel distribution amendment argued that it was better to address the problem before a need arose.

However, the overall tenor of the cc-licenses list discussions tended not to favor adoption of the parallel distribution proposal. There was concern that if parallel distribution were permitted in the CC licenses this would reinforce, if not expand, a platform monopoly enjoyed by a TPM-ed platform that only allows the playing of TPM-ed content (''See'' Greg London, Re:Subject: Version 3.0 – List Discussion Responses, September 28, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/004130.html]; ''see also,'' Terry Hancock, Debian and Creative Commons, October 18, 2006, at [http://www.freesoftwaremagazine.com/blogs/debian_and_the_creative_commons]). Other concerns were voiced that the non-TPMed copy may not be able to played as well as the TPM-ed copy and, generally, that the community was not in favor of supporting a TPM option at this stage (For an overview of the discussions, ''see ''the discussion archives for August [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/thread.html], September [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/thread.html] and October [http://lists.ibiblio.org/pipermail/cc-licenses/2006-October/thread.html].)

Whether Debian now declare the CC Attribution and Attribution-ShareAlike licenses to be free according to the DSFG or not — given all negotiated amendments are included in version 3.0 with the exception of the parallel distribution provision — remains an open question.

Certainly, Debian voted (''See'' ‘General Resolution: Why the GNU Free Documentation License is not suitable for Debian main, [http://www.debian.org/vote/2006/vote_001]). earlier in 2006 to allow works licensed under the Free Documentation License to be used in Debian projects. The vote specifically says that the anti-TPM clause in the FDL does not render the FDL incompatible with the DSFG. However, it is not clear whether this treatment is an exception or will also enable the CC Attribution and Attribution-ShareAlike license to also be held to be compatible with the DSFG.

===''MIT''===

With MIT, their OpenCourseWare (OCW) project [http://ocw.mit.edu/index.html] was initially launched in September 2002 prior to the formal release of the Creative Commons core licensing suite in December 2002 and thus, used an early version of the Attribution-NonCommercial-ShareAlike license. “OpenCourseWare” is the free and open digital publication of high quality educational materials, organized as courses. Flexible licenses such as Creative Commons licenses are key to enabling the openness of these materials.

MIT’s OpenCourseWare project has initiated a global opencourseware movement. Most recently, the OpenCourseWare Consortium [http://ocwconsortium.org/] has been formed which involves the collaboration of more than 100 higher education institutions and associated organizations from around the world — including China, France, Japan, the UK, the USA and Vietnam — who are committed to creating a broad and deep body of open educational content using a shared model.

Given CC licenses have improved over time, both CC and MIT wanted to work together to address any issues MIT had about the CC licenses so that MIT could switch over to a more recent version of the CC BY-NC-SA license. However, a key concern for MIT, given its illustrious reputation, is to ensure that when people translate and locally adapt MIT content under the terms of the BY-NC-SA license, they make it clear that they are doing so under the terms of the license and not as a result of a special relationship between MIT and that person — essentially, a “No Endorsement” clause.

Given “No Endorsement” clauses are a standard feature of free and open source software, CC felt that it would be easy issue to make this express in the CC licenses. In CC’s view, a licensee should not interpret the attribution requirement of the CC licenses as a basis (whether intentionally or not) to misrepresent the nature of the relationship with the licensor. Certainly, in most jurisdictions laws other than copyright law will proscribe this misconduct by a licensee. But CC agreed with MIT that it was useful to make this express in the license — both to give the licensor comfort and to ensure that the licensee was under no misapprehensions.

This feedback from both Debian and MIT was the impetus for CC commencing the version 3.0 process. However, as many projects do — versioning to 3.0 rapidly developed to encompass new and additional issues. These issues can effectively be described as further internationalization and international harmonization of the CC licenses

==Further Internationalization==

When CC’s core licensing suite was first released in December 2002, the licenses were drafted based on US copyright law and referred to as the “generic” license because the license did not identify a specific jurisdiction or governing law to apply to the interpretation of the license. Towards the end of 2003, Creative Commons launched its license internationalization project [http://creativecommons.org/international/], which involves the “porting” of the generic licenses to different jurisdictions around the world.

Since this project started, the CC core licenses have been “ported” to over 45 jurisdictions around the world to countries as diverse as Argentina, Australia, Brazil, Croatia, China, France, Italy, Japan, Malaysia, Mexico, South Africa and South Korea. (''Id.'')

While the internationalization has taken off far beyond Creative Commons’ expectations and has demonstrated the amazing energy around the globe for a more flexible and permissive copyright licensing approach, two issues arose.

The first is that as Creative Commons’ license internationalization project continued to grow, the “generic” license and the US license were one and the same. For the casual visitor to the CC International page (''Id.''), it seemed that the licenses had not been “ported” to the US, when in fact they had started out there. The challenge becomes though — if CC recognizes a specific US license, on what law should the “generic” license be based?

The approach Creative Commons adopted to respond this issue required further internationalization of our licenses. We decided to spin off the “generic” license to be a US license and recraft the “generic” license to have it utilize the language of the international intellectual property treaties, in place of the language of US copyright law.

The new license relies on the language of the Berne Convention for the Protection of Literary and Artistic Works [http://wipo.int/treaties/en/ip/berne/], the Rome Convention of 1961 [http://wipo.int/treaties/en/ip/rome/], the WIPO Copyright Treaty of 1996 [http://wipo.int/treaties/en/ip/wct/], the WIPO Performances and Phonograms Treaty of 1996 [http://wipo.int/treaties/en/ip/wppt/] and the Universal Copyright Convention [http://www.unesco.org/culture/laws/copyright/html_eng/page1.shtml ]. Because treaties are matters of international agreement between countries and, as a general rule, require adoption into national law to be effective in a particular country, simply basing the license wording on these treaties is not, of itself, sufficient. Consequently, clause 8(f) of the new generic specifically provides that the license takes effect according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law.

To reflect the nature of the new “generic” license we also decided to change its name to “unported.” This description is intended to highlight the different nature of the new generic license and to utilize the “porting” terminology that Creative Commons has been using in its license internationalization project since its launch in 2003 to more clearly illustrate the nature of the license that has not been adapted for a local jurisdiction.

The result of this further internationalization is that CC will now offer both an “unported” license and a US license, in addition to the 45-plus ported licenses; the unported license can be selected by those creators to whose jurisdiction CC has not yet ported a license.

===''International Harmonization – Moral Rights''===

The second more major issue that arose through the porting process was that different jurisdictions had different approaches to issues relating to moral rights and collecting societies.

Moral rights, to describe them briefly, are author’s right that are distinct from the economic copyright that can be bought and sold (''See generally,'' [http://en.wikipedia.org/wiki/Moral_rights]). Moral rights recognize an author’s personal attachment to their creativity and seek to protect that connection.

While there can be many different moral rights depending on the jurisdiction, the two main ones that are consistently present in most countries around the globe are the moral right of attribution and the moral right of integrity (''See ''[http://www.articleeveryday.com/ Article] 6bis of the Berne Convention (as amended September 1979) [http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html#P123_20726]). Obviously, since attribution became a default CC license characteristic with version 2.0 there is less of an issue regarding the moral right of attribution.

However, the moral right of integrity presents a more complex issue for Creative Commons licenses. CC licenses are intended to enable and promote reuse of creative content, particularly the making of derivative works. And those copyright owners who use CC licenses have acknowledged this with over two-thirds of CC licensors consistently choosing to allow derivative works.

But the moral right of integrity, as a general rule, gives the author of a creative work the right to object to alterations or mutilations of the work that are prejudicial to their reputation or honor. Obviously, this has potential to impact the freedom to exercise the right to make derivatives — a derivative will likely always qualify as an alteration of the original work and there may be some instances where it is arguable that it is prejudicial to the original author’s reputation or honor.

Obviously, the first generic version 1.0 license suite released in December 2002 did not mention moral rights because it was based on US copyright law and US copyright law only grants very limited moral rights to works of fine art. However, as the CC licenses began the porting process to other countries, it became necessary for CC licenses to address the moral right of integrity.

To do so, the Creative Commons licenses, with one exception, have taken the approach of not interfering with the author’s moral right of integrity in those jurisdictions that recognize this right.

The one exception is in Canada where the moral right of integrity is waivable. Because Canada was one of the first ten countries to port the CC licenses and one of the first (if not the only) to have a waivable moral right of integrity, on advice of our local affiliate, the CC Canada licenses choose to waive the right of integrity in order to ensure that the licensor’s intention in choosing to permit derivative works was not compromised. However, in all other CC licenses for jurisdictions that recognize the moral right of integrity, the right was retained albeit in different forms; again, on advice from local affiliates.

For example, in most European jurisdictions, the right was expressly retained in the Legal Code because of the strong level of protection for the right in these jurisdictions, as evidenced by the fact that courts would take a dim view of a license that did not expressly include it. In most Latin American jurisdictions, the license was not expressly retained in the Legal Code on the rationale that courts would read it in the license. In Japan, the moral right of integrity was retained in those licenses that prohibited derivative works but not fully retained in those licenses that permit derivative works. The local CC Japan team recommended this approach because the moral right of integrity can be interpreted so broadly as to render any change or alteration to the original work a violation of the right.

Although there is overall consistency in the treatment of the moral right of integrity at the Legal Code level (with the exception of Canada) among the CC licenses, now that the licenses have been ported to over 30 jurisdictions, we felt that it was time to harmonize the approach to this issue at both the Legal Code level and the Commons Deed level. The different approaches towards recognizing the right of integrity in the CC licenses arose because, as CC engaged in the novel process of license porting, we became familiar with the different treatment of this right in different jurisdictions. With the benefit of experience with more than 30 different treatments, CC now felt comfortable to adopt a unified approach.

As a consequence, as part of version 3.0 all CC licenses for jurisdictions that recognize the moral right of integrity will expressly retain that right in the Legal Code to the extent that this is feasible given the status of derivative works under the license. In those jurisdictions in which retention of the moral right of integrity may be completely block exercise of the derivative works right (ie. in Japan) the right will be tempered to the extent necessary to enable the exercise of the derivative works right in a manner intended by the licensor.

In addition, because of the importance of the moral right of integrity in protecting both the author’s rights and for its impact on the derivative works right, from version 3.0 the CC Commons Deeds will clearly state that the author retains their moral rights.

===International Harmonization — Collecting Societies===

Collecting societies are organizations that are established either by private agreements between copyright owners or by copyright law (''See generally,'' [http://en.wikipedia.org/wiki/Collecting_society]). Societies license works and process royalty payments from various individuals and groups who use copyrighted works either as part of a statutory scheme (compulsory schemes) or by entering into an agreement with the copyright owner to represent the owners interests when dealing with licensees and potential licensees (voluntary schemes). The rationale underlying societies is that it is more efficient and effective for copyright holders to be represented collectively in negotiating and levying license fees.

CC licenses also contained different treatments of whether and how a licensor can collect royalties via collecting societies because of the differences in the status of collecting societies amongst different jurisdictions.

In the United States, where the CC licenses originated, an artist can be a member of a collecting society and use CC licenses for those of their works that suit them. This is because of the rigorous enforcement of antitrust laws in the US during the early 20th century that requires that US collecting societies take a non-exclusive license from artists. This allows artists to then engage in direct licensing, including via CC licenses, to their fans and others who wish to share and remix their music.

Consequently, in the original CC licenses language was introduced into the licenses as part of version 2.0 to clarify what was considered to be the obvious interaction between CC licenses and collecting society membership. This initial approach stated that under those licenses that permitted commercial use (Attribution, Attribution-NoDerivatives and Attribution-ShareAlike) the licensor waived the right to collect both compulsory and voluntary royalties. Under those licenses that permitted noncommercial use only, the licensor reserved the right to collect royalties for any uses that were commercial in nature but otherwise authorized royalty-free noncommercial use of the work under the CC license. This approach reflected the fact that by choosing to apply a CC license to their work, a CC licensor clearly intends to permit “free” (as in both price and freedom) uses under the terms of the applicable CC license.

However, the situation regarding collecting society membership in many other jurisdictions around the world is remarkably different to the US position. Elsewhere, collecting societies take either an assignment of copyright ownership or an exclusive license to a work of the rights that they represent (which tends to include all of the works an artist creates). This means, for the most part, that an artist cannot directly license their works online, including via CC licenses. The consequence of this is that artists who use CC licenses cannot receive voluntary royalties collected by a society because they are not able to become a member of the society.

Thus, the treatment of collecting society royalties in the CC licenses differed according to the jurisdiction — in many jurisdictions the collection of voluntary royalties was not mentioned so as not to give any misleading impression that membership of a collecting society was possible for a CC licensor. In addition, many CC licenses retained the right to collect compulsory royalties in all licenses, both those that permitted commercial use and those that permit noncommercial use only, because of the advice of local affiliates that local law would not permit the waiver of such a right.

In version 3.0, after the benefit of seeing the different permutations of collecting society membership in over 30 countries and having had a dedicated team working on the issue of the interaction of CC licenses and collecting society membership for more than a year, CC has decided to harmonize the treatment of collecting societies in the CC licenses.

The harmonized approach still allows different jurisdictions to adopt an approach towards collective royalty collection that suits their jurisdiction but ensures that this is consistently applied across jurisdictions. Specifically, as regards compulsory royalty collection, the licensor will reserve the right to collect these royalties in those jurisdictions in which this cannot be waived. In those jurisdictions in compulsory royalty collection can be waived, it will be waived completely for those licenses that permit commercial use and reserved only for commercial uses in those licenses that permit noncommercial use only.

For voluntary royalties, the licensor will reserve the right to collect this “in the event that they are a member of a collecting society” that collects such royalties. This then allows for those jurisdictions in which an artist can be a member of a collecting society and use CC licenses. It also allows for flexibility for those artists who are members of collecting societies and use CC licenses anyway or if in future collecting society membership structures do allow some use of CC licenses, to also enjoy the benefits of their membership if their collecting society moves towards being able to collect for commercial uses of CC-licensed works.

==BY-SA — Compatibility Structure Introduced==

A final change incorporated into Version 3.0 is that the CC BY-SA 3.0 licenses now include a compatibility structure that will enable CC to certify particular licenses, stewarded by other organizations similarly committed to promoting a freer culture, as being compatible with the CC BY-SA. Once certified as compatible [http://creativecommons.org/compatiblelicenses], licensees of both the BY-SA 3.0 and the certified CC compatible license will be able to relicense derivatives under either license (eg., under either the BY-SA or the certified CC compatible license).

Creative Commons CEO Lawrence Lessig first outlined the vision of allowing an ecology of flexible content licenses to flourish in November 2005 (''See'' CC in Review: Lawrence Lessig on Compatibility, [http://creativecommons.org/weblog/entry/5709]). As Lessig explained:

"Even if all the creative work you want to remix is licensed under a copyleft license, because those licenses are different licenses, you can’t take creative work from one, and remix it in another. Wikipedia, for example, is licensed under the FDL. It requires derivatives be licensed under the FDL only. And the same is true of the Creative Commons Attribution-ShareAlike license that governs Opsound content, as well as much of the creativity within Flickr. All of these licenses were written without regard to the fundamental value of every significant advance in the digital age — interoperability."

This incompatibility also serves as a barrier to dual licensing works under the FDL and [http://hotels-ferienhaus.blogage.de CC BY-SA] (''See'' Evan Prodromou, Derivatives of dual-licensed Creative Commons Attribution-ShareAlike and GFDL works, May 3, 2005 [http://lists.ibiblio.org/pipermail/cc-licenses/2005-May/002265.html]).

Simply put, the problem is that any license with a "ShareAlike" or similar copyleft provision requires that any derivatives be licensed under exactly the same license (or family of licenses) as the original. This means that an article about Rio de Janeiro on Wikipedia [http://wikipedia.org/] (which is currently licensed under the FDL) cannot be mixed with an article about Rio on Wikitravel [http://wikitravel.org/en/Main_Page] (which is currently licensed under the CC BY-SA 1.0). Even if a project were dual licensed, none of the derivatives of the project could be returned back to the dual-licensed project (because they must be licensed under one ''or'' the other license), thus causing "project bleed." The result of the ShareAlike or "copyleft" license terms is seemingly antithetical to the very purpose of the licenses that contain them. Content, rather than being "free" to remix, is instead locked within particular licensing systems.

Consequently, CC has been working to ensure that, to again quote Lessig:

"[C]reative work[s] will more easily be able to move from one license to another, as creativity is remixed. And this ability for creative work to move to compatible free licenses will provide a market signal about which licenses are deemed more stable, or reliable, by the free licensing community. Free culture will no longer be ghettoized within a particular free license. It will instead be able to move among all relevantly compatible licenses. And the world of “autistic freedom” that governs much of the free software world will be avoided in the free culture world."

There are several obvious candidates for compatibility with the [http://lifestyle.blogpaint.com CC BY-SA]. The Free Art License [http://artlibre.org/licence/lal/en/] and the Free Software Foundation's Free Documentation License (FDL) [http://www.gnu.org/copyleft/fdl.html].

Creative Commons' initial work has focused on achieving compatibility with the FDL. As part of this work, CC explored the possibility of introducing one-way compatibility with the FDL. (''See'' Discussion Draft — Proposed License Amendment to Avoid Content Ghettos in the Commons [http://creativecommons.org/weblog/entry/5701]), which generated some discussion. CC then responded to some of the concerns raised by this discussion [http://creativecommons.org/weblog/entry/5731] but ultimately concluded that one-way comaptibility with the FDL was not possible because CC licensors could not be guaranteed the same protections under the FDL that they enjoyed under the CC BY-SA.

Despite the inability to implement one-way compatibility with the [http://hamburgnagelstudio.wordpress.com FDL], Creative Commons is still hopeful of being able to announce licenses that effect the same freedoms as the CC BY-SA to be compatible with the CC BY-SA at some date in the future. To allow the compatibility negotiations to occur separate and apart from the timing of the license versioning process, we have included a structure for certifying licenses as compatible with CC BY-SA as part of Version 3.0 (''See'' Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]).

==Summary of Links==

The following list provides the CC blog posts that relate to Version 3.0:

* Getting to Version 3.0 [http://creativecommons.org/weblog/entry/5908]
* Version 3.0 — Public Discussion Launched [http://creativecommons.org/weblog/entry/6017]
* Version 3.0 — Revised License Drafts [http://creativecommons.org/weblog/entry/6120]
* Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]
* Version 3.0 — Launched [http://creativecommons.org/weblog/entry/7249]
* [[Versioning to 3.0]] - Legal Leads versioning to 3.0. Includes checklist, working document, sui generis database rights document, and CS document

[[Category:Project]]

Documentation

2013-05-10T05:07:10Z

Sanfang: /* Integration Best Practices */

{{Infobox|
'''Welcome to the Creative Commons Documentation project!'''

This is a page for critical documentation about large scale CC specifications, recommendations, white papers, tutorials and other pieces that need to be written to explain various facets of Creative Commons across the board.

'''Join the community'''

#'''WIKI''' - Sign up for an account on this wiki and contribute
#'''CHAT''' - Channel #CC at http://irc.freenode.net - http://wiki.creativecommons.org/IRC
#'''LIST''' - cc-community listserv - Creative Commons Community email list - http://wiki.creativecommons.org/Mailing_Lists

'''Many ways to contribute'''

#Help us [[Documentation#Help_Translate_Documents|translate documents]].
#Help us [[#Help_Create_Documents.21|create new documents]].
#Help us [[:Category:Press_Hit|log CC press articles]].
}}

{{Infobox|
'''Top 5 Docs'''

''These are in order of general relevance and promotion.''

# [[Media:Creativecommons-informational-flyer_eng.pdf|What is Creative Commons? flyer]] (pdf) ([http://www.scribd.com/doc/2227788/creativecommonsinformationalflyereng scribd.com])
# [[Media:Creativecommons-what-is-creative-commons_eng.pdf|What is Creative Commons?]] (pdf) ([http://www.scribd.com/doc/2227452/creativecommonswhatiscreativecommonseng scribd.com])
# [[Sharing_Creative_Works|Sharing Creative Works Comics]] - A general introduction to copyright and CC licensing
# [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
# [[Media:Creativecommons-integration-with-your-website_eng.pdf|Creative Commons Integration With Your Website]] (pdf)
}}

== Creative Commons Explained ==
Documents that aim to explain CC and licensing.

'''About Creative Commons'''
* [[Media:Creativecommons-informational-flyer_eng.pdf|What is Creative Commons? flyer]] (pdf) ([http://www.scribd.com/doc/2227788/creativecommonsinformationalflyereng scribd.com])
** [http://mirrors.creativecommons.org/assets/cc-info-flyer-final.zip InDesign source file]
* [[Media:Creativecommons-what-is-creative-commons_eng.pdf|What is Creative Commons?]] (pdf) ([http://www.scribd.com/doc/2227452/creativecommonswhatiscreativecommonseng scribd.com])
** [[Media:Cc-fullpage-promo-svg.zip|Inkscape SVG source files]] (zip)
* [[Media:Creativecommons-encouraging-the-ecology-of-creativity_eng.pdf|Encouraging the Ecology of Creativity]] (pdf) ([http://www.scribd.com/doc/2227443/creativecommonsencouragingtheecologyofcreativityeng scribd.com])
** [http://mirrors.creativecommons.org/assets/concept-paper-source.zip InDesign/Illustrator source files]
* [[Media:Wipo_info_sheet_nov6.pdf|CC info sheet for WIPO]] (pdf)
*[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]

'''Using the Creative Commons Licences'''
* [[Media:Creativecommons-how-to-license-poster_eng.pdf|How To License poster]] (pdf) ([http://www.scribd.com/doc/2227445/creativecommonshowtolicensepostereng scribd.com])
* [http://creativecommons.org.au/learn-more/fact-sheets/what-are-the-creative-commons-licences-factsheet Quick Guide to the Creative Commons Licences] (pdf) ([http://www.scribd.com/doc/16536016/What-are-the-Creative-Commons-licences-factsheet scribd.com])
** [http://creativecommons.org.au/www/materials/factsheets/cc-licences-indesign-package.zip Indesign files]
* [http://creativecommons.org.au/content/licensing-flowchart.pdf Creative Commons Licensing Flowchart] (pdf) ([http://www.scribd.com/doc/16540395/Which-Creative-Commons-licence-is-right-for-me-poster scribd.com])
* [http://wiki.creativecommons.org/Types_Of_Creative_Commoms_Licenses Types Of Creative Commons Licenses]
* [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Your Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
* [http://wiki.creativecommons.org/Creative_Commons_License_Misuse Creative Commons Misuse]

'''Using Creative Commons Content'''
* [http://creativecommons.org.au/content/findingmaterial.pdf Finding Creative Commons Material] (pdf) (created for the [http://creativecommons.org.au/poolingideas Pooling Ideas competition])
* [http://creativecommons.org.au/content/attributingccmaterials.pdf Attributing Creative Commons Material] (pdf) (created for the [http://creativecommons.org.au/poolingideas Pooling Ideas competition])
* [http://creativecommons.org.au/content/CC_Web_Resources.pdf Quick guide to Creative Commons resources] (pdf)

'''Multimedia'''
* [[Sharing_Creative_Works|Sharing Creative Works Comics]] - A general introduction to copyright and CC licensing ([http://www.scribd.com/doc/2227656/creativecommonssharingcreativeworkseng scribd.com])
** [[Media:Sharingcreativeworks.zip|Inkscape SVG source files]] (zip)
* [http://creativecommons.org/videos/ CC Videos]
** [[Translate#Videos | Video source files]]
* [http://wiki.creativecommons.org/Comics CC Comics]

==Sector-specific Information==
* '''for teachers''' - A [http://creativecommons.org.au/learn-more/educators-resources collection] of resources on finding and using Creative Commons specifically designed for teachers, including fact sheets, slideshows, videos and worksheets
* '''for citizen journalists''' - from CC Lebanon: 10 Legal Rules on social activism and copyright by Martin Wählisch:
** [[Media:CopyrightLawLEB_EN.pdf| English]]
** [[Media:CopyrightLawLEB_AR.pdf| Arabic]]
* '''for the public sector''' - [[Media:Creativecommons-licensing-for-public-sector-information_eng.pdf|Creative Commons Licensing for the Public Sector]] (pdf)
* '''business models''' - [[Media:BusinessModelsforCreativeWorks.pdf|Business Models for Creative Works and Creative Commons Licensing]] (pdf)

== Legal ==

* [http://creativecommons.org/about/license/ License Your Work]
* [[Before Licensing]]
* [[Legal Concepts]]
* [[Podcasting Legal Guide]]

== FAQ ==
* [[FAQ]] - Important documentation of frequently asked CC questions. A must read !

== CC Learn Productions==
'''Note: CC Learn is no longer a division of Creative Commons. Much of the information in the archive below may be outdated and/or incorrect. For the most up-to-date information about CC in education, see http://creativecommons.org/education.'''
====Organizational Media====
* CC Learn Informational Flyer ([[Media:Cclearn-information-flyer.pdf|pdf]]) ([[Media:Cclearn-information-flyer-print.pdf|pdf - print w/.125" bleed]]) ([http://www.scribd.com/doc/15058699/ccLearn-Informational-Flyer Scribd])

====CC Learn Reports====
* [http://learn.creativecommons.org/wp-content/uploads/2009/01/license-mapping-report-15_dec_-2008-color-v2.pdf What status for “open”? An examination of the licensing policies of open educational organizations and projects] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/01/license-mapping-report-15_dec_-2008-color-v2.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/What-status-for-open-Data-Supplement-v1.pdf Data Supplement to “What status for ‘open’?” A graphical view of the licensing policies of open educational organizations and projects] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/What-status-for-open-Data-Supplement-v1.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/discovered-paper-17-july-2009.pdf Enhanced Search for Educational Resources— A Perspective and a Prototype from CC Learn] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/discovered-paper-17-july-2009.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/09/Otherwise_Open_report.pdf Otherwise Open Managing Incompatible Content within Open Educational Resources] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/09/Otherwise_Open_report.odt odt])

====CC Learn Explanations====
*[http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-explanations-oer-and-cc-licenses-05-apr-09.pdf CC Learn Explanations: Open Educational Resources and Creative Commons Licensing] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-explanations-oer-and-cc-licenses-05-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-explanations-cc-license-compatability.pdf Remixing OER: A Guide to License Compatibility] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-explanations-cc-license-compatability.odt odt])

====CC Learn Step by Step Guides====
* [http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-step-by-step-applying-cc-licenses-06-apr-09.pdf Applying Creative Commons licenses to your educational resources] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-step-by-step-applying-cc-licenses-06-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/11/cclearn-step-by-step-discovered.pdf Preparing Your Educational Resources for DiscoverEd] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/11/cclearn-step-by-step-discovered.odt odt])

====CC Learn Recommendations====
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/cclearn-recommendations-increase-funding-impact-05-apr-09.pdf Increase Funding Impact] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/cclearn-recommendations-increase-funding-impact-05-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-recommendations-publishing-your-oer-on-the-internet-05-apr-09.pdf Publishing Your Open Educational Resources on the Internet] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-recommendations-publishing-your-oer-on-the-internet-05-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/ccLearn_primer-Why_CC_BY.pdf CC Learn Recommendations: Why CC BY?] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/ccLearn_primer-Why_CC_BY.odt odt] )
* [http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-recommendations-dealing-with-incompatible-content-in-OER.pdf Dealing with Legally Incompatible Content in OER] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-recommendations-dealing-with-incompatible-content-in-OER.odt odt])

==Technical Implementation==
=== Developer ===
* [[Developers]] - Documentation and information for software developers.

=== Integration Best Practices ===
* [[Web Integration]]
** [[Media:Creativecommons-integration-with-your-website_eng.pdf|Creative Commons Integration With Your Website]] (pdf) ([http://www.scribd.com/doc/2227446/creativecommonsintegrationwithyourwebsiteeng scribd.com])
* [[Application Integration]] [http://www.articleeveryday.com/ free article directory]
* [[Desktop Integration]]

=== Marking ===
* [[Marking]] - How to properly mark various media with Creative Commons licenses.
** [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
* [[Metadata]] - an overview of Creative Commons metadata - opening documentation.
** [[ccREL]] - describing license metadata in a machine readable way and attaching it to digital works.
** [[Marking_Works_Technical|Metadata Marking]] - technical background on machine-readable metadata.
* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material]

== Metrics ==

* [[Metrics|Metrics in progress to assess CC-license adoption]]
* [[License_statistics|License Statistics]]
* [[Media:Statistics-from-the-CC-Monitor-project_eng.pdf|Statistics from the CC Monitor Project]] (pdf)
* [[Media:Taking-stock-of-the-creative-commons-experiment_eng.pdf|Taking Stock of the CC Experiment]] (pdf)
* [[Media:License-use-five-years-on_eng.pdf|License Use Five Years On]] (pdf)

== Staff Contributions ==
* Explore [[:Category:Presentation|CC conference participation]].
* Explore staff presentations and slideshows online!
** [http://www.slideshare.net/ericcc/slideshows Eric Steuer], Creative Director
** Jon Phillips, Community + Business Developer
*** [http://www.slideshare.net/rejon/ Slideshare Slides]
*** [http://www.scribd.com/people/view/3525-jon-phillips Scribd Docs and Slides]
** [http://www.slideshare.net/Jessicacoates Jessica Coates], Global Network Manager

== Mailing list archives ==
* [http://lists.ibiblio.org/pipermail/cc-community/ cc-community]
* [http://lists.ibiblio.org/pipermail/cc-licenses/ cc-licenses]
* [http://lists.ibiblio.org/pipermail/cc-devel/ cc-devel]

== Technical Documentation ==
* [[Media:Creativecommons-embedded-metadata-with-xmp_eng.pdf|Embedded Metadata with XMP]] (pdf) ([http://www.scribd.com/doc/2227441/creativecommonsembeddedmetadatawithxmpeng scribd.com])

== Help Translate Documents ==

Please help CC translate these documents into other languages. For the documents written in English already uploaded to this site, we've included the standardized 3-character language code, [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes ISO 639-2]. For example, the Web Integration PDF is labeled "Creativecommons-webintegration_eng.pdf". A Japanese translation of the same document would be labeled "Creativecommons-webintegration_jpn.pdf".

Available translations can be found at [[Translate/Documentation]].

== Help Create Documents! ==
How do you see CC? While these documents can exist on this wiki just fine and is a great way to get started, below is a package consisting of the Scribus document and files necessary to make documentation. Please post up any of your creations on this page!

*[[Media:Cc-general-open.zip|Information page framework]] — Scribus source
*[[Media:Cc-info-doc-layout.zip|Information page framework]] — InDesign source

Please help us complete these, to make our wiki as informative as possible !

=== Teaching Creative Commons ===
How should you go about teaching Creative Commons ideas to a general audience?

CC Denmark has made a section "CC i undervisningen" (CC in education) containing video tutorials, pdf guides and other ressources for teachers. [http://www.creativecommons.dk/?page_id=88](In Danish)
{{stub}}

=== Creative Commons in the classroom ===
{{stub}}

=== Creative Commons Overview for your Company ===
An overview of Creative Commons for a company.
{{stub}}

=== Creative Commons + Open CourseWare Legal Guide ===
{{stub}}

{{Translations
| articles = Pt:Documentação
}}

[[Category:Documentation]]
[[Category:Media]]
[[Category:Critical]]
[[Category:Translation Project]]

CcHost

2013-04-24T06:36:32Z

Sanfang:

[[Category:ccHost]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
[[Category:ccMixter]]
{{Project}}
{{lowercase}}

'''ccHost''' is Creative Commons' open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) [http://en.wikipedia.org/wiki/Content_management_system content management system] project that powers [http://ccmixter.org ccMixter] and is the winner of the [http://creativecommons.org/weblog/entry/6026 Linux Journal LinuxWorldExpo Product Excellence Award] for '''Best Open Source Solution.''' Read more about ccHost [[#Zeitgeist|here]].

= Download =

Sign up for [http://sourceforge.net/export/rss2_projfiles.php?group_id=80503 our RSS release feed] to make sure you don't miss important bug fixes and feature updates.

=== Current Stable Release ===
Latest stable build of [https://sourceforge.net/projects/cctools/files/ccHost/ ccHost 5.1] is available in ZIP archive format.

=== Source Repository ===
http://code.creativecommons.org/svnroot/cchost/

For much more developer info, see [[Cchost/Developers]].

= Documentation =

[[cchost/Documentation|ccHost 5 Documentation]]

=Communication=

=== People ===
* [[User:fourstones|Victor Stone]]
* [[User:Jon Phillips|Jon Phillips]]
=== Contacting ===
The mailing list is the best way to get our attention. That and other methods are listed below:
* Mailing List: https://lists.sourceforge.net/mailman/listinfo/cctools-cchost
** [http://sourceforge.net/mailarchive/forum.php?forum=cctools-cchost Archive]
* Chat: #cc on irc.freenode.net
* Wiki: This page (http://wiki.creativecommons.org/CcHost)
* [[Cchost/Developers#Bugs_and_Feature_Requests|Bugs and feature requests]]

= Zeitgeist =
=== Goal ===
The goal of this project is to spread media content that is licensed under Creative Commons throughout the web in much the same way that weblogs spread CC licensed text.
=== Short Description ===
"Web-based System Supporting Remixing and Collaboration on Media"
=== Slightly Longer Description ===
'''ccHost''' is an open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) project that provides web-based infrastructure to support collaboration, sharing, and storage of multi-media using the Creative Commons licenses and metadata. It is the codebase used by [http://ccmixter.org ccMixter] and [[#Usage Examples|other sites]].

Besides its focus on sharing content, ccHost differentiates itself from other multi-media hosting programs by emphasizing the '''reuse''' (a.k.a. remixing) of content between artists, not only between artists on any given installation of ccHost, but between all installations across the web and any web site that implements the Creative Commons [http://ccmixter.org/media/viewfile/pool_api_doc.xml Sample Pool API], including non-ccHost sites such as the [http://freesound.iua.upf.edu/ freesound project].

=== Usage Examples ===

* [http://ccmixter.org ccMixter] - Primary usage of ccHost is the Creative Commons remix site, ccMixter.
* [http://fourstones.net fourstones.net] Victor's personal website
* [http://www.enciclopediacecilia.org/remix/ Remix Cecilia] at the Enciclopedia Cecilia project (Spanish).
* [http://audio.ibeat.org/ iBeat] Moderated Sample Archive
* [http://www.forpcphone.com pc componentes] Computer Componentes
----

= Appendix A: Compatibility =

=== Browsers ===

Recently tested on: Firefox 2/3 Mac/PC/Linux, IE 7 PC, Safari Mac (IE8 requires "compatibility" mode - see [[Cchost/guide/Troubleshooting#IE8_Layout_Issues|here]] for workaround)

Cookies must be enabled.

Most skins (the ones people will want to use) require Javascript enabled.

=== Servers ===

Primary development is done on Ubuntu 8.04 (hardy heron) using Apache, mySQL, and PHP. The actual dev setup is described in detail [[Cchost/Developers/Victor's_Dev_Setup|here]].

==== Linux ====
ccHost on Apache (2.0.49 up to at least apache-2.0.55-r1) on Linux,

One should be able to easily install mySQL, PHP, and Apache (if they are not already available) through their distributions packaging system. See the dev setup above.

==== Windows IIS Server ====

{{Infobox|ccHost has not been seen running or tested on Windows for a long time - several versions ago.}}

Windows users with their installation disks may install optionally the Windows IIS Web Server. This option has been tested. However, there might still be issues with it, and if so, [http://sourceforge.net/tracker2/?func=browse&group_id=80503&atid=559966 please file a bug].

Even if you using Apache on Windows you may need to have IIS installed if you plan to use mail contact functions.

==== Windows Apache ====
There are many good tutorials for setting up a Windows/Apache/MySQL/PHP site ([http://google.com/search?q=installing+WAMP Google search]) and all three subsystems now come with Windows installers making the job of installing relatively straightforward.

====== XAMPP ======
Windows installations without Apache, mySQL and PHP already installed should consider using [http://www.apachefriends.org/en/xampp.html XAMPP] for Windows, which provides an easy install of Apache web server, MySQL database server, and PHP and perl programming languages. This is an easy way to get up and running, with the underlying technology necessary to use ccHost.

Follow the instructions for installation of XAMPP to know where to put the uncompressed ccHost package to properly work with your local setup.

==== Mac OS X ====

''NOTE: This setup is similar to Linux.''

Verified:

* OS X 10.4.6
* default OS X MySQL build, 4.0.26
* GetID3 1.7.7
* default Apache/PHP

[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]

Photography

2013-04-17T01:39:17Z

Sanfang:

The internet and technology have changed how people access images, and photographers are responding by employing new methods to reach audiences. These methods include personal websites, social media tools, photo-sharing platforms and communities, and tools such as Creative Commons licenses that enable easy sharing and reuse of creative works.

CC licenses are a flexible way to share images while building on the strong foundation of traditional copyright law. Simply put, Creative Commons licenses allow the shift from “all rights reserved” to “some rights reserved,” enabling you to share your images under terms of your own choosing. This gives you control over distribution, and the non-exclusivity of the licenses means you can retain all commercial rights if desired.

[[#Photographers_using_CC_licenses|Photographers using CC licenses]] gain new audiences for their work on photo-sharing platforms like [http://www.flickr.com/creativecommons Flickr] and communities like [http://www.wikipedia.org/ Wikipedia]. Mohamed Nanabhay, Head of Online, Al Jazeera English, [http://creativecommons.org/weblog/entry/18213 writes]:
:“When launching our [CC] repository, we had thought that it would be a key resource for anyone producing content on the war and that it would primarily be used by other news organisations and documentary filmmakers. What we saw was both surprising and delightful. Soon after posting our first video, Wikipedia editors had extracted images to enhance the encyclopedia entries on the War on Gaza. Soon thereafter educators, filmmakers, video game developers, aid agencies and music video producers all used and built upon our footage.”

Wikipedia is a heavily-trafficked website with over 400 million unique visitors a month. Flickr contains over 200 million CC-licensed photos, establishing it as the Web’s single largest source of CC-licensed content.

In 2008, DigitalPhotoPro published an [http://www.digitalphotopro.com/business/creative-commons.html article on the use of CC licenses by professional photographers] with advice for those thinking of using CC themselves.

==Photographers using CC licenses==

===[[The_Power_of_Open/Text#Jonathan_Worth|Jonathan Worth]]===
:“Creative Commons enables me to use existing architecture really smoothly and to address the digital natives’ social media habits. The mode of information is the same, but the mode of distribution has changed. We don’t have all the answers, but CC lets me choose my ﬂavor and helps me take advantage of the things working against me.”

British photographer Jonathan Worth’s work hangs in the National Portrait Gallery in London. He teaches photography at Coventry University in the U.K, and [http://www.phonar.covmedia.co.uk/ his course materials] are released as open educational resources (OER) under [http://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA]. He has photographed actors Colin Firth, Rachel Hunter, Jude Law and Heath Ledger. He is also one of an emerging group of photographers experimenting with sustainable working practices for professional image makers in the digital age. Jonathan Worth has been featured in:
*[http://www.telegraph.co.uk/technology/news/8623680/How-the-Power-of-Open-can-benefit-photographers.html The Telegraph] - How the Power of Open can benefit photographers
*[http://www.bbc.co.uk/news/technology-13961051 BBC News] - "Photographer Jonathan Worth explained that Creative Commons allowed him to sell his work for commercial use while still giving it free to individuals who wanted it for other reasons."
*[http://www.bbc.co.uk/news/in-pictures-20495489 BBC News] - "Photography and open education"
*[http://thepowerofopen.org/ The Power of Open] - Stories of creators sharing knowledge, art, & data using Creative Commons

===[[Case_Studies/Lan_Bui|Lan Bui]]===
<div class="smimg">{{#show: Case_Studies/Lan_Bui|?Image Header|link=none}}
Lan Bui "makes media." From photography of tech celebrities (Veronica Belmont, Zadi Diaz, Casey McKinnon) and The Ninja to videos for professionals and events (Comic Con and Pixelodeon), Lan (with help from his brother Vu) makes them all from start to finish. Lan echoes the thoughts of other artists using Creative Commons; the idea that your work is, in a way, an advertisement for yourself and future work. Lan expresses this in this way: "I think that people pay me for my time and talent, not for the actual images I deliver."
</div>

===[[Case_Studies/Monkeyc.net|Monkeyc.net]]===
<div class="smimg">{{#show: Case_Studies/Monkeyc.net|?Image Header|link=none}}
Monkeyc.net is the moniker of John Harvey, a Brisbane-based former photojournalist who licenses his Flickr photo stream under Creative Commons. John is an active member of the Flickr community, having first uploaded a photo on 26 September 2004 and now sporting a collection of close to 1,000 images, and encourages others to engage likewise. Several of John’s photographs have been featured on Flickr’s ‘Explore’ page, as an indication of their popularity in the Flickr community.
</div>

===Vinoth Chandar===
Vinoth Chandar is a professional photographer who releases many of his photographs under the [[Creative Commons Attribution]] licence, saying that "I use [the] Attribution Creative Commons licence for all my photos because I want everybody to use my photo and credit me ... This way, my photos reach every corner of the world without any effort from my side except taking the photos and uploading it to Flickr."<ref>http://www.wired.co.uk/news/archive/2011-12/16/creative-commons-gallery</ref>

One example he used of the exposure provided by free culture licensing was the use of one of his photos for the cover of a popular Italian magazine. "I am an Indian and how else in the world can an Indian photographer expect his photo to be published in an Italian magazine? CC licence made this possible."<ref>http://www.wired.co.uk/news/archive/2011-12/16/creative-commons-gallery</ref>

==Enforceability of CC licenses in photography==
CC licenses have been upheld in several [[Case_Law|court cases]] around the world. A few of these cases pertain specifically to CC-licensed images.

*In [[Curry_v._Audax |Curry v. Audax]], Adam Curry, a former MTV VJ and one of the pioneers of podcasting, published photos onto his Flickr account under a BY-NC-SA license. A Dutch tabloid reprinted four of the photos in a story about the Curry family's public persona verses real private life. Curry sued the tabloid for violating the portrait rights of his family and for copyright violation over the improper user of his Flickr photos. The Dutch court held that, in the future, the tabloid could not use any of the photos from Flickr in the future unless under the terms of the photos' CC license or with permission from Curry.
*In [[Gerlach_vs._DVU|Gerlach vs. DVU]], Gerlach took a picture of the German politician Thilo Sarrazin at a public event and published it online under the Creative Commons license BY SA 3.0 Unported. Later the DVU, a German political party used the picture on their website without the plaintiff's name, the license notice or any other requirement of the license. The applicant sent a notice and takedown letter to which the party didn't react. Subsequently the applicant sought preliminary injunction before the Disctrict Court of Berlin against the unauthorized publication of the picture. The District Court of Berlin granted the injunction because the applicant had successfully established prima-facie evidence of authorship, of the licensing and of the breach of the license.
*In [[TA_3560/09,_3561/09,_Avi_Re%27uveni_v._Mapa_inc._%D7%99%D7%A9%D7%A8%D7%90%D7%9C:_%D7%9C%D7%A8%D7%90%D7%A9%D7%95%D7%A0%D7%94,_%D7%91%D7%99%D7%94%D7%9E%22%D7%A9_%D7%90%D7%9B%D7%A3_%D7%A8%D7%99%D7%A9%D7%99%D7%95%D7%9F_%D7%A7%D7%A8%D7%99%D7%90%D7%99%D7%99%D7%98%D7%99%D7%91_%D7%A7%D7%95%D7%9E%D7%95%D7%A0%D7%A1 |Avi Re’uveni v. Mapa inc.]], plaintiffs uploaded photographs to Flickr and and offered them under a Creative Commons BY-NC-ND license. The defendant made a collage from the plaintiffs’ and other photographs and sold them without attribution. The court found the defendant guilty of copyright infringement. The defendant claimed ignorance of the copyright and license, but the court found that this did not matter.

==Photo-sharing sites that have enabled CC licenses==

===[[Case_Studies/Flickr|Flickr]]===
<div class="smimg">{{#show: Case_Studies/Flickr|?Image Header|link=none}}
Flickr was one of the first major online communities to incorporate Creative Commons licensing options into its user interface, giving photographers around the world the easy ability to share photos on terms of their choosing. As the Flickr community grew, so did the number of CC-licensed images — currently there are well over 200 million on the site — establishing Flickr as the Web’s single largest source of CC-licensed content.
</div>

===[[Case_Studies/DeviantART|DeviantART]]===
<div class="smimg">{{#show: Case_Studies/DeviantART|?Image Header|link=none}}
deviantART is an online community dedicated to showcasing art as prints, videos and literature. CC license options are built into deviantArt's UI, allowing users to set the permissions they want their works to carry. Naturally, different users choose different options for their works, including All Rights Reserved.
</div>

===[http://creativecommons.org/weblog/entry/22882 Fotopedia]===
Fotopedia is a breathtaking application for the [http://www.repairpartstock.com/ iPhone and iPad parts]. The app builds on the concept of a coffee table book, updating and enhancing the browsing experience for the web. This project is possible thanks to Creative Commons, as over 18,000 of the pictures in Fotopedia Heritage book are under one of the CC licenses. The pictures come from all around the world; as individual photographers and organizations license their high quality photos under Creative Commons, the book will only grow as a community contributed and shareable resource.

===[[Case_Studies/National_Library_of_Australia_'Click_and_Flick'|National Library of Australia: 'Click and Flick']]===
<div class="smimg">{{#show: Case_Studies/National_Library_of_Australia_'Click_and_Flick'|?Image Header|link=none}}
'Click and Flick' is a National Library of Australia (NLA) initiative to open their online pictorial gateway, PictureAustralia, to contributions from the Australian public. PictureAustralia encourages people to make their material available on the archive under the CC licenses, as part of two dedicated Flickr image pools: ‘PictureAustralia: Ourtown’ and ‘PictureAustralia: People, Places and Events’.
</div>

===[[Case_Studies/Newsbank_Image|Newsbank Image]]===
<div class="smimg">{{#show: Case_Studies/Newsbank_Image|?Image Header|link=none}}
Newsbank Image is one of South Korea's largest and most comprehensive photo-archives. The photograph archive website provides images produced by Media companies, photographers as well as web-friendly versions containing watermarks, original images, all which maintain the marking of original creators. Users can choose to upload their photos under CC licenses.
</div>

===[[Case_Studies/Culture.si|Culture.si]]===
<div class="smimg">{{#show: Case_Studies/Culture.si|?Image Header|link=none}}
A comprehensive online guide to Slovene culture, Culture.si covers contemporary art, culture, and heritage in Slovenia. Over 2,300 articles in English and the fastest growing independent free image bank (currently over 1,500 images) are offered for reuse under Creative Commons licenses.
</div>

==How To Publish photos in an online community==
One way to increase visibility and access to your photos is to share it with an existing community that has enabled CC licensing, making it easy for you to indicate the license along with other information, such as who to attribute. In addition, search engines like Google and Yahoo! will index your work as CC licensed if the metadata is properly attached. See [[Publish/Images]] for more info.

==Finding CC-licensed photos==
Thanks to the machine-readability of CC licenses, CC-licensed images can be found via:

*[http://images.google.com/advanced_image_search?hl=en Google Advanced Image Search] by specifying options under "Usage Rights"
*[http://images.search.yahoo.com/images/advanced?ei=UTF-8 Yahoo! Advanced Image Search] by specifying options under "Creative Commons License"
*It appears that Yahoo Advanced Image Search no longer offers this option. Can anyone else confirm this?
*[http://docs.google.com/support/bin/answer.py?answer=179622 Google Docs], where Google Image Search has been integrated
*[http://search.creativecommons.org/ CC Search Portal], which is not a search engine, but a tool that offers convenient access to search services provided by independent organizations, such as Flickr, Google, and Wikimedia Commons (media repository for articles featured on Wikipedia).

==Related resources==
*[[Journalism|CC in Journalism]]
*[[CC_Factsheet|CC Factsheet]]

==References==
<references>

Applications Using CC

2013-04-17T01:35:55Z

Sanfang:

[[Category:Developer]]
[[Category:technology]]
{{SMW}}
== Applications with Creative Commons licensing built-in ==

The following list of software packages and web applications incorporated Creative Commons licensing, so you won't have to copy/paste HTML from licenses or add buttons to your pages.

=== Photography Applications ===

* [http://www.onfocus.com/snap/ SnapGallery]: [Windows] Drag a folder of photos on your desktop onto this script and it will automatically build you a Gallery of HTML pages. You can select a license during setup that will be embedded in each gallery page.

=== Graphics Applications ===

* [[Inkscape]], an open source drawing tool (that uses SVG). One may select a CC license for content directly from within the metadata dialog.

=== Blog Applications ===

* [http://movabletype.org/ Movable Type]: [server software] A robust weblogging system that allows you to select and apply a license to your individual blogs. Displays the button and metadata automatically.
* [http://manila.userland.com/ Manila]: [server software] Another weblog management system that allows authors to select licenses for their blogs, displaying the button and metadata in your site's template.
* [http://www.squarespace.com Squarespace]: [service] A website- and blog-publishing service that allows users to select a CC license for their sites and displays a license button and metadata automatically.
* [http://www.mediawiki.com Mediawiki]: [server software] The software which powers this wiki and http://www.wikipedia.org. During installation a user is allowed to select a license for their wiki.
* [http://avoir.uwc.ac.za/ AVOIR/Chisimba]: [server software] Full featured weblogging application built on top of the Chisimba PHP5 Framework. Allows individual post licences as well as providing RDF metadata.
* [http://kete.net.nz/ Kete]: [server software] Full featured collaborative web application that can be configured easily to allow for individual blogs, built on top of the Ruby on Rails Framework. Site administrators can set licences options for users to choose from, distributed with CC licenses. Licenses are then displayed and built into metadata. Uses [http://github.com/kete/acts_as_licensed/ Acts_as_Licensed] Rails plugin that can be used by other Rails apps to include licensing functionality.

=== Web Applications ===
* [http://www.archive.org/ Archive.org]: An archive of content, the [http://www.archive.org/movies/opensource_movies.php Open Source Movies] section displays Creative Commons licenses and lets anyone add their own movies under a license. The [http://www.archive.org/audio/collection.php?collection=opensource_audio Open Source Audio] section does the same, but for audio files.
* [http://ymdi.org YMDI]: Youth Media Distribution is a teen-themed offshoot of the documentary filmmaking non-profit Media Rights. Teens can upload films they have created, get information on how to distribute films, and license their films for use by others.
* [http://stories.about.ticketstubs.org/ Ticketstubs.org]: Share stories of past concerts, movies, and events. When you contribute a story, you can license your story for use by others.
* [http://bumperactive.com Bumperactive.com]: Create your own bumper sticker. The CC license engine is integrated to Bumperactive's [http://www.bumperactive.com/uploadSticker.jsp upload process].
* [http://www.flickr.com/ Flickr]: Create an account, set your default CC license, and start uploading photos today.
* [http://avoir.uwc.ac.za/ AVOIR/Chisimba]: Chisimba PHP5 Framework. Features include a CMS, Blog and many other content tools. Allows individual post licences as well as providing RDF metadata.
* [http://kete.net.nz/ Kete]: [server software] Full featured collaborative web application built on top of the Ruby on Rails Framework and open standards for content sharing and reuse. Site administrators can set licences options for users to choose from, distributed with CC licenses. Licenses are then displayed and built into metadata. Uses [http://github.com/kete/acts_as_licensed/ Acts_as_Licensed] Rails plugin that can be used by other Rails apps to include licensing functionality.
* [http://mahara.org/ Mahara]: is a user-centred environment with a permissions framework that enables different views of an e-portfolio to be easily managed. Mahara also features a weblog, resume builder and social networking system, connecting users and creating online learner communities. Pages can be placed under a Creative Commons license through the use of built-in CC blocks.
* [http://sensesproject.com/ Senses]: The HTML5 Media Center featuring Free and Creative Commons music, shows and movies. Open and community maintained.
* [https://www.coursesites.com/ CourseSites]: allows instructors to teach, create and share online courses. From the Course Control Panel expand the "Packages and Utilities" menu and click "Publish Open Resource" to make course materials available in a IMS Common Cartridge format with a CC-BY license.

=== Authoring Tools ===

* [http://www.screenbooks.net Screenbook Maker]: A tool for creating online visual tutorials, Windows HTML Help, or just web books (linked HTML pages). For an example of the kind of content that can be created with this tool, see the [http://help.joomla.org/component/option,com_wrapper/Itemid,253/ Joomla Visual Tutorial Bookshelf]. For a walkthrough of how to add the Creative Commons license to content created with Screenbook Maker see [http://www.screenbooks.net/e/sbhelp1.1/ScreenBook_Maker/B2_Basics/Books/N0_Copyrights/sbook2.htm Screenbook Copyrights]

=== Mobile Applications ===

* [http://winksite.com WINKsite]: A mobile publishing system that allows you to select and apply a license to your mobile site & blog. Displays the button and metadata is automatically included in feeds.

* [http://QRdvark.com/foneFrame foneFrame]: foneFrame is a mobile framework built with HTML5 + CSS3 that creates mobile pages for smartphones like Android & iPhone.
* [http://www.cyberworldltd.co.uk/cases-for-apple-model-iphone-4.htm iPhone 4 Cases]: An iphone accessories e-store showcasing iphone accessories, cases for a wide range of [http://www.repairpartstock.com/ iphone parts wholesale] & other smart phones

'''Note to developers:''' If you have incorporated Creative Commons licensing into your application (per our [[Web Integration|documentation]]), and you'd like your application to appear on this list, please create an account on this wiki and click 'edit' to add your application.

{{Challenge Enabled}}:

Italy

2013-04-13T01:25:38Z

Sanfang:

{{Jurisdiction
|jurstatus=Active
|status=3.0
|country code=it
|homepage=http://www.creativecommons.it/
|logourl=http://www.creativecommons.it/sites/creativecommons.it/files/ccitcolors_logo.png
|mailing list=http://www.creativecommons.it/Liste
|twitter=http://twitter.com/cc_italy
|social=http://www.facebook.com/cc.italia
|otherurl=http://selili.polito.it/
|region=Europe
|affiliated=NEXA Center for Internet & Society
|affurl=http://nexa.polito.it
|afffocus=Internet research
|afftype=academic institution
|plead1=Juan Carlos De Martin
|pemail1=juancarlos.demartin@polito.it
|flagurl=http://creativecommons.org/images/international/it.png
}}
Many thanks to all who contributed to the localization of the license suite.

Creative Commons is working with the NEXA Center for Internet & Society at the Politecnico di Torino to create Italy jurisdiction-specific licenses from the generic Creative Commons licenses.

=CC Italy List=
Project Lead: [http://www.swas.polito.it/rubrica/list.asp?freetext=de%20martin&cerca=1 Juan Carlos De Martin]

*[http://mirrors.creativecommons.org/international/it/translated-license License draft].
*[http://mirrors.creativecommons.org/international/it/it-legalchanges.pdf English explanation of substantive legal changes (PDF)].
*[mailto:cc-it%20-at-%20lists.ibiblio.org Post a message].
*[http://lists.ibiblio.org/mailman/listinfo/cc-it/ Subscribe to the discussion].
*[http://lists.ibiblio.org/pipermail/cc-it/ Read the discussion archives].

=More about the NEXA Center at the Politecnico di Torino=
The NEXA Center for Internet and Society of the Politecnico di Torino was founded in 2006 by [https://plus.google.com/101331298429373051293/ Juan Carlos De Martin], professor of Information Engineering, together with Marco Ricolfi, law professor at the University of Torino Law School. NEXA is a multidisciplinary research center on the impact of the Internet on society, with a focus on technical, economical and juridical issues. The NEXA research team includes academic researchers as well as law practitioners and technologists; many of them have been working together since 2003, when the Creative Commons Italy project was started.

The Politecnico di Torino (Turin Polytechnic University) has 26,000 students studying on about 120 courses (39 Bachelor’s degree courses; 35 Master of Science courses; 30 Doctorates and 18 specialization courses). The Politecnico di Torino offers excellence in technology from all points of view, from the strictly technical to the economical and juridical.

=Acknowledgements=

==The Department of Law of the University of Turin==

The Department of Law of the University of Turin, headed by Prof. Gianmaria Ajani, is aimed to coordinating all the research activity in the area of law of the University of Turin. It deals also with the fund raising for research purposes, the management of all the PhD programs and continuing education in the area of law. It is part of the University of Turin, which was founded in 1404 (it is one of the most antique universities in the world) and which today counts 65.000 students, 1.300 professors and nearly 800 researchers and assistants.

The Department of Law coordinates the research work of more than 130 law professors in the different areas of law. The main research program by now are in the field of:

*EC Private law and harmonization of contract law,
*International Human Rights,
*Criminal Jurisdiction,
*Harmonization of Civil Procedure,
*Intellectual Property law.

For more information about the Department of Law of the University of Turin, visit http://www.dsg.unito.it/.

=IEIIT-CNR=

IEIIT-CNR: Istituto di Elettronica e di Ingegneria dell’Informazione e delle Telecomunicazioni del CNR. (English: CNR Institute of Electronics and Information and Telecommunications Engineering).

The Consiglio Nazionale delle Ricerche (National Research Council of Italy), founded in 1923, is a multidisciplinary public research institution. The IEIIT is a CNR institute founded in 2002 by merging the forces of several preexisting CNR institutes and centers. The IEIIT-CNR headquarters are located in Torino, with territorial sections in Genoa, Milan, Bologna and Pisa; the Institute is directed by prof. Marco Ajmone Marsan. The IEIIT-CNR pursues advanced, multidisciplinary research in the field of information and communications technology (ICT).

For more information about IEIIT-CNR, visit http://www.ieiit.cnr.it/

=Affiliate Team Roadmap for 2011=

* Timespan of this roadmap: '''January 2011 - December 2011'''

== Team information ==
* Jurisdiction: '''Italy'''

* Complete list of all members of the Affiliate Team, their roles, and field(s) of expertise
** '''Juan Carlos De Martin''', ''Public Lead'' Creative Commons Italia (associate professor of informatics at the Politecnico di Torino; researcher in the field of on Internet sciences)
** Legal working group: '''Marco Ricolfi''', ''Legal lead'' (full professor of law at the University of Turin), '''Massimo Travostino''' (practicing lawyer, specialized in IP law), '''Deborah De Angelis''' (practicing lawyer, specialized in IP law), '''Thomas Margoni''' (assistant professor, specialized in IP and computer law), '''Marco Ciurcina''' (practicing lawyer, specialized in IP law), '''Nicola Bottero''' (practicing lawyer, specialized in IP law), '''Federico Morando''' (post-doc researcher, specialized in economic analysis of law), '''Alessandro Cogo''' (lawyer and currently full time researcher, specialized in IP law), '''Claudio Artusio''' (researcher in law)
*** Other legal experts cooperating with CCIT: Simone Aliprandi, Cristiana Sappa, Angelo Maria Rovati, Silvia Bisi
** Main editors of the website: Claudio Artusio, Federico Morando, Juan Carlos De Martin, Giuseppe Futia (media & communications manager at the NEXA Center)
** Webmaster: '''Luca Leschiutta''' (IT manager at the NEXA Center)

* Date of earliest MOU in jurisdiction: '''Summer 2003'''

* Self-Identified Region: '''Europe'''
** CC Italia is well connected with other European jurisdictions. Thanks to the COMMUNIA European Project and personal connections. Moreover, Italy has a typical European continental legal system (civil law), as far as law is concerned (and IP and contract law in particular), so CC Italia faced similar problems as many other European jurisdictions and interacted with them.

==Vision==

* Why is Creative Commons important for the jurisdiction?
** '''Connecting creators'''
*** In Italy, CC is important for the usual reasons, very well described, for instance, by Lawrence Lessig in his books. In fact, CC is probably more useful in Italy than in other countries, for instance because of the combination of these factors:
**** in Italy, there is a relatively high number of "creators" (for instance, according to [http://www.internetworldstats.com/ http://www.internetworldstats.com/] in Italy there are 12.9 websites per 1,000 people, despite an Internet penetration of 51.7%; as a comparison, in Finland and France there are respectively 13.3 and 10.5 websites per 1,000 people, with a penetration rate of 85.3% and 68.9%);
**** however, in Italy there is a relatively low number of associations and cultural institutions, including public libraries, chronically lack funding and are not always very used/usable: creators lack networking tools;
**** all this implies that several creators risk working on their own and this suggests that the virtuous cycle of use and re-use generated by Creative Commons licenses is especially valuable in Italy.
*** More generally, Italy has a limited number of open and free culture related projects and surely needs more open models and tools. A Creative Commons affiliate institutions is definitely needed (and this is testified by the number of emails and phone calls that the NEXA Center receives from people asking for information and help about Creative Commons).

* What do you think makes a successful jurisdiction project?
# '''Up-to-date licensing tools'''. A clear and user friendly website. A working mailing list to ask for an offer help.
# Once this is in place, one could think about '''increasing awareness''': in the general public (testified by the number of adoptions, for instance), in public institutions, private associations and foundations. Also firms and media (e.g. Wired Italia and La Stampa, in Italy) are becoming increasingly sensible and responsive to awareness and dissemination activities related to open licensing, so they should also be targeted.
# Once a sufficient degree of awareness has been reached, the '''"quality" of the adopted licenses''' should be improved: in particular, at least in Italy, new adopters tend to favor relatively closed licenses (es. CC BY-NC-ND or CC BY-NC-SA), but most of the time they are willing to move to relatively more open licenses, as soon as some key doubts and fears have been addressed.
Self evaluating ourselves, we find that the first point still needs more work. In a way, we compensated with significant results on point 2 (see CC Italy report for 2010).

* How do you see the jurisdiction project contributing to the CC Affiliate Network?
** The contribution of Creative Commons Italia and of the NEXA Center for Internet and Society to the CC Affiliate Network could be especially valuable in terms of:
*** '''legal expertise''' (civil law tradition);
*** '''networking''' with European players (members of the European Networks COMMUNIA and LAPSI, the European Commission, European Universities) and international institutions (WIPO, in particular, but also OECD);
*** '''policy support experience''', thanks to several policy support projects at the European and Italian level.

===Community===

* Describe the communities that are currently active in the project:
** CC Italia has '''an active community of experts: lawyers, consultants, open content/culture activists''', which is admittedly the core of our community;
** it also has '''some active creators''' in its community;
*** on top of individual creators, we have '''some preliminary contacts with associations supporting creators''' (e.g. Italian Association of Web Radios)
During 2011 the idea of approaching creators through some of their associations is worth experimenting (despite the fact that, as mentioned, cultural associations are not always very widespread and successful in Italy)

* Describe the communities (existing or new) that you plan to focus on during the time-frame covered by this road-map?
** On top of the traditional communities of users, we will focus on:
*** '''public institutions''' and
*** '''cultural institutions and associations'''.
** How do you plan to engage with these communities?
*** Thanks to the '''network''' of the NEXA Center and to the '''leading pilot project [http://www.dati.piemonte.it dati.piemonte.it]''', it's relatively easy to engage with other public institutions in Italy and some promising contacts are already in place.
*** To engage cultural institutions and associations, we will use both direct contacts and the '''support of third party initiatives''', such as the '''[http://www.lettera27.org/index.php?idlanguage=1&zone=9&idprj=47&idsubprj=1777 ShareYourKnowledge project] of [http://www.lettera27.org lettera27]'''.

==Priority Goals==

* What are the three most important focus areas on which the Affiliate Team will work during this time period? Please consider community building and adoption goals among your priorities.

1. Focus-area: '''Porting''' (and/or translation) of the legal tools
*Completing the porting of the 3.0 license suite; translate CC0 and the PD Mark
** Why is it important?
*** Apart from the obvious reasons, the availability of up-to-date licensing tools in Italian is Crucial for the adoption by public bodies, since they frequently release databases of public sector information (and the latest licensing tools deal much better with databases than the current 2.5 suite available in Italy).
** Which communities will benefit?
*** All Italian users will, of course, benefit from this porting and translation effort thanks to the availability in Italy and according to Italian law of the most up-to-date legal tools offered by Creative Commons. However, there is another particular benefit for public sector bodies (see also below), which may face obstacles in formally adopting licenses (or other legal documents) which do not have an official Italian translation.

2. Focus-area: '''Adoption by institutions'''
* Facilitate the adoption by public bodies, foundations and associations
** Why is it important?
*** Public sector data and content represent a "raw material" or "building block" for several intellectual, scientific and, in general, creative endeavors.
*** Moreover, public sector body adopting the licenses normally offer a significant boost in terms of visibility and credibility.
** Which communities will benefit ?
*** See above: not only public bodies and their citizens will benefit, but also creators in general, who will be able to use PSI as a building block for their original content.

3. Focus-area: '''Adoption by creators''': increase quality!
* Make more creators aware of the opportunities offered by the most open CC licenses
** in general, improve the FAQs and the website (in cooperation with the [http://selili.polito.it SeLiLi free licenses clinic])
*** specifically, highlight the benefits of CC BY and CC BY-SA in terms of freedom, openness, compatibility with existing projects and various approaches to the creation of new, original content
*** moreover, focus on the special needs of some categories of users:
**** prosumers and high profile amateurs;
***** including singers, musicians, etc.;
**** software developers which offer platform for online interaction, social networking and user generated content;
** Why is it important?
*** According to the CC Monitor project, with more than 5.5 millions of licenses, Italy scores very high in terms of CC adoptions (ranking 3rd out of 52 countries). Even if these are always relevant goals, this suggests that awareness and adoption in general should not be the top priority for Creative Commons Italia. However, Italy has a much poorer rank in terms of adoption of the most "free and open" licenses" (i.e. CC BY and CC BY-SA): in fact, its Freedom Rank is 38 out of 52. This is why it's important to encourage the use of the most open CC licenses in Italy (in particular, of the ones "[https://creativecommons.org/weblog/entry/8051 Approved for Free Cultural Works]").
** Which communities will benefit?
*** All creators will benefit, because using more open licenses you make creation easier "downstream"

==Project Outputs==

* Detail tangible project outputs (e.g., events, papers, blog posts, video/films, etc.) for each focus area including an expected date of completion.

The outputs we plan to complete are as follows:

# Focus-area: '''Porting & translation'''
## Project Output:
##* the legal tools (see below);
##* related press releases and blog post on CreativeCommons.it
## Expected start date - Expected date of completion (+ final approval from CC International)
##* '''''CCPL 3.0''''' : ongoing - '''February 2011'''
##* '''''CC0''''': March 2011 - '''May 2011'''
##** [http://wiki.creativecommons.org/Publicdomain/zero/1.0/LegalText_%28Italian%29]
##* '''''PD Mark''''': May 2011 - '''July 2011'''
## Team Member(s) Responsible
##* porting & translation: see legal working group;
##** communication: '''Giuseppe Futia''', Federico Morando, Claudio Artusio
# Focus-area: '''Adoption by public bodies'''
## Project Output
##* '''adoption''' of the CC licenses by more public bodies in Italy
##** for their '''institutional websites''' and content
##** for their '''public datasets''' (possibly CC0 or, at most, CC BY)
##*** there are ongoing contacts with various public bodies; ongoing public projects involve the Region of Piedmont and the Comune di Torino and we expect to have much '''more available datasets''' in 2011
##* '''guidelines''' for the use of CC licenses by public bodies
## Start/Completion dates: ongoing - open ended
## Team Member(s) Responsible: '''Federico Morando''', Juan Carlos De Martin
# Focus-area: '''Adoption by creators'''
## Project Output
##* informative content:
##** pages on creativecommons.it about the pros and cons of various licenses
##** news about best practices
##*** ongoing effort: goal: one post per week on the creativecommons.it website
##* SIAE (Italian collecting society) pilot mandate: '''Deborah De Angelis'''
##** actually completed since July 2009: awaiting for feedback from the collecting society, but we will have to keep this monitored carefully
## Team Member(s) Responsible
##* whole CC Italy team

==Metrics==
Please consider using trackable statistics (such as web traffic or number of license adoptions) when applicable, but only if meaningful.

* How will you measure and evaluate your impact on focus-area 1 (''"porting"'')?
** availability of the tools;
*** related press releases and blogposts;
*** visits to the (Italian) pages of each legal tool;
*** metrics on the adoption of the new tools (using CC Monitor, if possible, or other estimates)
* How will you measure and evaluate your impact on focus-area 2 (''"public adopters"'')?
** adoptions by public institutions (quite trackable), associations and foundations (relatively less trackable, but anecdotal evidence will be available)
*** number and relevance of new public bodies adopting CC licenses;
*** number and relevance of the contents (and data) made available by current adopters, such as the Region of Piedmont and the City of Torino;
* How will you measure and evaluate your impact on focus-area 3 (''"quality adoption"'')?
** visits to the FAQs webpage of CreativeCommons.it;
** visits to the [http://selili.polito.it | SeLiLi (free licenses clinic)] website;
** proportion of the various licensing tools according to available metrics (variations with respect to the previous year), for instance, as measured by the variation in the "Freedom score" of CC Monitor;
** number of posts on the website of Creative Commons Italia (www.creativecommons.it), as a proxy of the coverage of success stories, etc.

==Resources Required==

===People===
* What human resources or expertise must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?
** We do not expect to significantly modify the core team of CCIT, however we will work to involve:
*** a few selected new experts in the core legal team;
*** some new experts in parts of Italy that do not have a sufficient coverage at the moment (forcing the group of CCIT to miss some interesting opportunities, both in terms of potential adoptions and awareness and dissemination).
** How will you involve these people?
*** Mainly through word of mouth and/or deepening existing contacts for the core legal team;
**** plus awareness and dissemination activities targeting people already possessing some key skills (e.g. young lawyers at the university of Turin);
*** Possibly with a call on the mailing lists of CCIT for experts in other parts of Italy.

===Technology===
* Since the CC Italia affiliate institution is the NEXA Center for Internet & Society at the Politecnico di Torino, CC Italy has a good endowment in terms of technology resources and/or skills.
** No action point required.
** The usual maintenance activity will be performed by the webmaster, Luca Leschiutta (e.g. updating the software behind www.creativecommons.it).

===Materials===
* During 2011 we expect to be able to fund the project with existing or potentially available material resources. Synergies with other activities of the NEXA Center will provide additional resources.
** A more structured approach to the funding of the Creative Commons Italia project may be appropriate and it could be considered during 2011.

===Other===
* Time (of existing human resources) is definitely the scarcest resource.
** Mainly, this should be addressed in terms of finding additional people willing to contribute (and forming them).
** On top of that, we will improve our contacts with existing associations and organizations which share the philosophy and the goals of CC and of the NEXA Center.
*** The aforementioned cooperation with lettera27 in the context of the ShareYourKnowledge project is an example of this kind of contact.

==Sustainability and Scalability==

* How will you ensure your goals will be completed if unforeseen circumstances interrupt the project, such as changes in the leadership of the project or outputs taking longer to complete than anticipated?
** We will not be able to ensure anything, since this is volunteer work. However the NEXA Center offers a certain degree of stability.

* How will you communicate the project's on-going progress and setbacks within the jurisdiction and the CC Affiliate Network? (e.g. email list updates, meetings, press releases)
** When feasible, we will use email list updates, we will make all reasonable efforts to take part in CC meetings (at the International level and in Europe), and we will issues press releases on our website, plus English press releases in case of major news.

* How will you document the project so that others may replicate or learn from your efforts?
** We do not plan to systematically document the project, due to lack of resources.

==Collaboration==

* We will analyze the roadmaps of other jurisdictions as they become available.
** Would you be interested in mentoring new jurisdiction teams?
*** At the moment, we would prefer to focus our limited resource on our jurisdiction, working in order to enlarge the CC network within Italy, more than abroad. However, we are highly involved in the founding of the COMMUNIA Association, which will likely be in synergy with Creative Commons Europe and, also in this context, we may informally support new jurisdiction teams.
** Conversely, would you be interested in having a mentor from a more experienced jurisdiction team?
*** We are always interested in exchanging view, contacts and best practices, but at the moment we do not feel the need of specific mentoring. On a case-by-case basis, we may get in touch with some of the fellows from other jurisdictions, in order to learn from specific projects or best practices.

===Regional===

* Suggest three possible projects on which you can collaborate with other teams on a regional level:
** COMMUNIA Association http://www.repairpartstock.com/
*** work in progress amongst the CC Europe teams: an update about this will be available soon
** PSI related projects, such as [http://www.lapsi-project.eu/user LAPSI] and [http://share-psi.eu/ SharePSI]
** European cultural heritage projects, such as Europeana

** How do you plan to contribute to these projects?
*** COMMUNIA Association: we're going to contribute as one of the founding members and supporting the formal creation of the organization;
*** PSI related projects: we're deeply involved in these projects (also coordinating the LAPSI network) and we're constantly involving members of other CC affiliate institutions in the various activities that we perform;
*** European cultural heritage projects: we're studying various issues related to cultural heritage and IP law, the public domain and open licensing, focusing on Italy, but with a European perspective. We would be happy to be kept updated about possible synergies with other jurisdictions in this (and other) fields.

==Translation==

* In what language(s) will you promote CC in the jurisdiction and why?
** Italian, since this is the language spoken by the vast majority of Italians.
** In which of these languages are licenses already available? CC0?
*** The standard suite is available in Italian (version 2.5; 3.0 coming very soon). CC0 is not yet available, but a draft translation is ongoing.
** Into which of the remaining languages do you intend to translate the licenses? CC0?
*** None. Some other linguistic communities exist (both in terms of dialects and complex languages, such as ladino or sardo;see also [http://it.wikipedia.org/wiki/Lingue_parlate_in_Italia http://it.wikipedia.org/wiki/Lingue_parlate_in_Italia]), however we do not plan to translate the licenses for these linguistic groups, given an apparent lack of demand.
* How will you involve the local language(s) community?
** Even if we have no plan to translate the licenses in other languages, we're open to different suggestions (in particular if coupled with proposals to cooperate with respect to the translation).

Version 3

2013-04-10T01:28:50Z

Sanfang:

= Creative Commons Version 3.0 Licenses — A Brief Explanation =

===''by Mia Garlick, General Counsel Creative Commons''===

Since April 2005, Creative Commons has been working on versioning up its core licensing suite. The Creative Commons licenses (For an overview of the licenses, ''see:'' [http://creativecommons.org/about/licenses/meet-the-licenses]) serve as an important vehicle by which many millions of creators clearly signal to the world that they are happy for members of the public to engage in some of the exciting new uses of content that are made possible by digital technologies. Using a CC license, an artist can, for example, invite the public to share their work or mash it up (on certain conditions).

A distinctive feature of CC’s licensing infrastructure is ensuring that it is comprehensible to both humans (the Commons Deed) and machines (the metadata) as well as enforceable in a court of law (the Legal Code, which is the actual license). But another important aspect of the CC licensing system is to ensure that it respected by the community of people who apply our licenses to their content, who use CC-licensed content and who are committed to enabling free culture.

Creative Commons regularly invites and receives feedback about its licenses and how they may be able to be improved to better serve the people who use them and who use CC-licensed content. Obviously, all things can be improved with the benefit of hindsight and experience; also, the environment within which CC licenses are used is always changing. When CC first released its licenses, for example, the use of video and video-sharing sites had not yet been deployed, let alone used to the extent they are today.

We released version 1.0 of our licenses in December 2002 (''See'' CC Weblog, Creative Commons Launches, December 15, 2002, [http://creativecommons.org/weblog/entry/3484]). Like software releases, we track the different licenses by version. In May 2004, we versioned to 2.0 (''See'' CC Weblog, Announcing (and explaining) our new 2.0 licenses, May 25, 2004, [http://creativecommons.org/weblog/entry/4216]) and then made a minor tweak to the attribution clause in June 2005 (''See'' CC Weblog, Comments Period Drawing to a Close for Draft License Version 2.5, May 29, 2006, [http://creativecommons.org/weblog/entry/5457]) and versioned to 2.5. Now, CC is versioning to 3.0. We announced a timetable for versioning to 3.0 back in May 2006 (''See'' Mia Garlick, ‘Getting to Version 3.0,’ May 17, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-May/003557.html]); and we have followed the consultation process in the timetable even though the schedule itself has been considerably delayed while we take account of all of the different interest groups that are relevant to CC licenses.

==Background to Version 3.0==

The process of versioning to 3.0 began back around April 2005 as part of discussions with Debian [http://www.debian.org/] and the Massachusetts Institute of Technology (MIT) [http://mit.edu/] about ways to improve the clarity of our licenses. Although discussions with Debian and MIT initiated consideration of a new license version, ultimately, version 3.0 grew to be about much more than these two projects — it focused on internationalizing the “generic” license and international harmonization of the CC licenses. Additionally, it expanded to encompass Creative Commons' long-held vision [http://creativecommons.org/weblog/entry/5709] of establishing a compatibility structure to allow interoperability between different flexible content copyright licenses.

===''Debian''===

As you may know, Debian describes itself as “an association of individuals who have made common cause to create a free operating system” [http://www.us.debian.org/intro/about] and the volunteer group has worked together to create an operating system called Debian GNU/Linux. The project and all developers working on the project adhere to the Debian Social Contract [http://www.us.debian.org/social_contract]. The Debian Free Software Guidelines (DSFG) [http://www.us.debian.org/social_contract#guidelines] form part of the Debian Social Contract and define the criteria for “free software” and so what software is permissible in the distribution.

One part of the Debian community is debian-legal [http://lists.debian.org/debian-legal/] — a mailing list whose members provide “guidance for the Debian project on, among other things, the acceptability of software and other content for inclusion in the Debian operating system.” [http://people.debian.org/~evan/ccsummary.html] They work primarily involves reviewing software against the DFSG to determine if the packages constitute “free software” per the DFSG. Contributors to the Debian project can then take these determination into account when making decisions about what to include in individual packages.

From time to time the debian-legal list provides a review of a well-known software license to express a rough consensus opinion on whether software released solely under the license would satisfy the definition of “free software” according to the DSFG. Although these summaries are not binding, they do provide some basis for the Debian project to make decisions about individual packages. Although debian-legal work primarily in reviewing software programs and Creative Commons licenses are not designed for software, debian-legal notes that the:

“Creative Commons licenses are still of interest to the Debian project. Debian includes documentation for programs, and many programs included in Debian use digital data such as images, sounds, video, or text that are included with the programs in Debian.” (''Id.'')

Consequently, debian-legal reviewed the CC licenses and concluded that none of the Creative Commons core licensees were free according to the DFSG and recommended that works released under these license “should not be included in Debian.” (''Id.'')

It is clear that the licenses that contain a NonCommercial or a NoDerivatives restriction (e.g. Attribution-NonCommercial, Attribution-NonCommercial-ShareAlike, Attribution-NoDerivatives, Attribution-NonCommercial-NoDerivatives ) will never be able to comply with the DFSG because these violate basic principles articulate in the DSFG — specifically, DSFG 1 which requires that a licensee be able to sell copies of the work, DSFG 3 which requires a license to permit the making of derivative works and DSFG 6 which proscribes discrimination against any field of endeavor.

====DRM====

But this should still leave the CC Attribution and Attribution-ShareAlike licenses as DSFG-compliant. On reviewing debian-legal’s issues with these licenses, it seemed clear to Creative Commons that, for the most part, minor amendments and clarifications to the licenses should be able to address debian-legal’s concerns. (For an outline of these concerns, see [http://evan.prodromou.name/ccsummary/ccsummary.html]) One topic, however, that was not minor and proved to be much debated as part of the version 3.0 license discussions was the anti-TPM clause in the CC licenses; TPM being technological protection measures such as encryption which have received legal protection in many jurisdictions around the world, which make it a civil (and sometimes) a criminal offence to circumvent these measures.

The Creative Commons licenses prohibit a licensee applying a TPM to a licensed work that restricts the rights granted under the license. (''See e.g.,'' clause 4(a) “You may not distribute, publicly display, publicly perform, or publicly digitally perform the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement.” of the CC Attribution license ([http://creativecommons.org/licenses/by/2.5/legalcode])) In essence, this clause is intended to ensure that a person cannot exercise the freedoms granted by a CC license to apply technologies that restrict those freedoms for others.

In Debian’s view, this prohibition violates DSFG #1 because it prevents a licensee from being able to distribute works in the format of their choice. The consequence of this is that CC-licensed content cannot, for example, be included by a licensee in a Sony Playstation game or other platforms that exist on TPM.

An important thing to note, however, is that this limitation only applied to CC licensees. CC licensors are of course free to license their works on a Sony or other TPM-ed platform whilst also CC licensing it. One example of this is the Beastie Boys track ‘Now Get Busy’ that appeared on the WIRED CD under a CC Sampling license [http://creativecommons.org/wired] but was then also made available on iTunes [http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewAlbum?playlistId=15146499&selectedItemId=15146497&s=143441 ].

To avoid interfering with the freedom of the licensed content and allowing a licensee to lock up the content on a TPM-ed platform, Debian proposed that CC’s so-called “anti-TPM” provision to allow a licensee to distribute the CC-licensed work in any format, including a TPM-ed format, provided that the license distributed the work in at least one format that did not restrict another person’s exercise of rights under the license. This proposal became known as the “parallel distribution” proposal.

Creative Commons initially agreed to include the parallel distribution proposal as part of the discussion draft for the Version 3.0 amendments. The rationale for this initial acceptance was that it could accommodate the objectives of the anti-TPM clause (being free culture) whilst also addressing Debian’s concerns that people be free to create works for distribution on TPM-ed platforms.

The parallel distribution proposal did not, however, survive discussions with the Creative Commons International affiliates [http://creativecommons.org/worldwide/]. The affiliates are responsible for “porting” the CC licenses to their local jurisdiction (discussed in greater detail below) and for fielding a wide range of questions about CC licenses and their implementation in various projects throughout the world. Based on their experience with the diverse communities that use and rely on CC licenses and explaining the licenses to different constituencies, the CCi affiliates were strongly opposed to the introduction of a parallel distribution scenario for various reasons, including: (1) the lack of demonstrated use cases showing a strong need among CC licensees for this kind of an exception to the existing “anti-TPM” language; (2) risks of unduly complicating the licenses which defeats alot of the purpose of CC licenses, namely to be simple and easy to use and to understand; and, (3) the strong opposition to technological protection measures in general by many in the CC community.

CC did, however, include the parallel distribution proposal as part of the public license discussions when those were launched in August 2006 (''See'' Mia Garlick, Version 3.0 – Public Discussion, August 9, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/003857.html]) so that the community on those lists could debate the merits of the proposal.

The discussions about the parallel distribution proposal on the cc-licenses email list were very intense. Various participants argued in favor of the parallel distribution amendment on the grounds that the “anti-TPM” clause violated DSFG #1 and achieved little, if anything. Taking the advantage of a Sony Playstation again, if CC-licensed content cannot be included in games for the PS2 platform, the CC licensee is restricted in what they can do with the content, the PS2 gamer cannot play a game with CC-licensed content and Sony are unlikely to notice the absence of this content and will continue along as business as usual with a TPM-ed platform, irrespective of any anti-TPM ban in the CC licenses.

When asked about the extent to which there was a demonstrated need by developers (as licensees) to be able to utilize CC-licensed content in TPM-ed environments, advocates of the parallel distribution amendment argued that it was better to address the problem before a need arose.

However, the overall tenor of the cc-licenses list discussions tended not to favor adoption of the parallel distribution proposal. There was concern that if parallel distribution were permitted in the CC licenses this would reinforce, if not expand, a platform monopoly enjoyed by a TPM-ed platform that only allows the playing of TPM-ed content (''See'' Greg London, Re:Subject: Version 3.0 – List Discussion Responses, September 28, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/004130.html]; ''see also,'' Terry Hancock, Debian and Creative Commons, October 18, 2006, at [http://www.freesoftwaremagazine.com/blogs/debian_and_the_creative_commons]). Other concerns were voiced that the non-TPMed copy may not be able to played as well as the TPM-ed copy and, generally, that the community was not in favor of supporting a TPM option at this stage (For an overview of the discussions, ''see ''the discussion archives for August [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/thread.html], September [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/thread.html] and October [http://lists.ibiblio.org/pipermail/cc-licenses/2006-October/thread.html].)

Whether Debian now declare the CC Attribution and Attribution-ShareAlike licenses to be free according to the DSFG or not — given all negotiated amendments are included in version 3.0 with the exception of the parallel distribution provision — remains an open question.

Certainly, Debian voted (''See'' ‘General Resolution: Why the GNU Free Documentation License is not suitable for Debian main, [http://www.debian.org/vote/2006/vote_001]). earlier in 2006 to allow works licensed under the Free Documentation License to be used in Debian projects. The vote specifically says that the anti-TPM clause in the FDL does not render the FDL incompatible with the DSFG. However, it is not clear whether this treatment is an exception or will also enable the CC Attribution and Attribution-ShareAlike license to also be held to be compatible with the DSFG.

===''MIT''===

With MIT, their OpenCourseWare (OCW) project [http://ocw.mit.edu/index.html] was initially launched in September 2002 prior to the formal release of the Creative Commons core licensing suite in December 2002 and thus, used an early version of the Attribution-NonCommercial-ShareAlike license. “OpenCourseWare” is the free and open digital publication of high quality educational materials, organized as courses. Flexible licenses such as Creative Commons licenses are key to enabling the openness of these materials.

MIT’s OpenCourseWare project has initiated a global opencourseware movement. Most recently, the OpenCourseWare Consortium [http://ocwconsortium.org/] has been formed which involves the collaboration of more than 100 higher education institutions and associated organizations from around the world — including China, France, Japan, the UK, the USA and Vietnam — who are committed to creating a broad and deep body of open educational content using a shared model.

Given CC licenses have improved over time, both CC and MIT wanted to work together to address any issues MIT had about the CC licenses so that MIT could switch over to a more recent version of the CC BY-NC-SA license. However, a key concern for MIT, given its illustrious reputation, is to ensure that when people translate and locally adapt MIT content under the terms of the BY-NC-SA license, they make it clear that they are doing so under the terms of the license and not as a result of a special relationship between MIT and that person — essentially, a “No Endorsement” clause.

Given “No Endorsement” clauses are a standard feature of free and open source software, CC felt that it would be easy issue to make this express in the CC licenses. In CC’s view, a licensee should not interpret the attribution requirement of the CC licenses as a basis (whether intentionally or not) to misrepresent the nature of the relationship with the licensor. Certainly, in most jurisdictions laws other than copyright law will proscribe this misconduct by a licensee. But CC agreed with MIT that it was useful to make this express in the license — both to give the licensor comfort and to ensure that the licensee was under no misapprehensions.

This feedback from both Debian and MIT was the impetus for CC commencing the version 3.0 process. However, as many projects do — versioning to 3.0 rapidly developed to encompass new and additional issues. These issues can effectively be described as further internationalization and international harmonization of the CC licenses

==Further Internationalization==

When CC’s core licensing suite was first released in December 2002, the licenses were drafted based on US copyright law and referred to as the “generic” license because the license did not identify a specific jurisdiction or governing law to apply to the interpretation of the license. Towards the end of 2003, Creative Commons launched its license internationalization project [http://creativecommons.org/international/], which involves the “porting” of the generic licenses to different jurisdictions around the world.

Since this project started, the CC core licenses have been “ported” to over 45 jurisdictions around the world to countries as diverse as Argentina, Australia, Brazil, Croatia, China, France, Italy, Japan, Malaysia, Mexico, South Africa and South Korea. (''Id.'')

While the internationalization has taken off far beyond Creative Commons’ expectations and has demonstrated the amazing energy around the globe for a more flexible and permissive copyright licensing approach, two issues arose.

The first is that as Creative Commons’ license internationalization project continued to grow, the “generic” license and the US license were one and the same. For the casual visitor to the CC International page (''Id.''), it seemed that the licenses had not been “ported” to the US, when in fact they had started out there. The challenge becomes though — if CC recognizes a specific US license, on what law should the “generic” license be based?

The approach Creative Commons adopted to respond this issue required further internationalization of our licenses. We decided to spin off the “generic” license to be a US license and recraft the “generic” license to have it utilize the language of the international intellectual property treaties, in place of the language of US copyright law.

The new license relies on the language of the Berne Convention for the Protection of Literary and Artistic Works [http://wipo.int/treaties/en/ip/berne/], the Rome Convention of 1961 [http://wipo.int/treaties/en/ip/rome/], the WIPO Copyright Treaty of 1996 [http://wipo.int/treaties/en/ip/wct/], the WIPO Performances and Phonograms Treaty of 1996 [http://wipo.int/treaties/en/ip/wppt/] and the Universal Copyright Convention [http://www.unesco.org/culture/laws/copyright/html_eng/page1.shtml ]. Because treaties are matters of international agreement between countries and, as a general rule, require adoption into national law to be effective in a particular country, simply basing the license wording on these treaties is not, of itself, sufficient. Consequently, clause 8(f) of the new generic specifically provides that the license takes effect according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law.

To reflect the nature of the new “generic” license we also decided to change its name to “unported.” This description is intended to highlight the different nature of the new generic license and to utilize the “porting” terminology that Creative Commons has been using in its license internationalization project since its launch in 2003 to more clearly illustrate the nature of the license that has not been adapted for a local jurisdiction.

The result of this further internationalization is that CC will now offer both an “unported” license and a US license, in addition to the 45-plus ported licenses; the unported license can be selected by those creators to whose jurisdiction CC has not yet ported a license.

===''International Harmonization – Moral Rights''===

The second more major issue that arose through the porting process was that different jurisdictions had different approaches to issues relating to moral rights and collecting societies.

Moral rights, to describe them briefly, are author’s right that are distinct from the economic copyright that can be bought and sold (''See generally,'' [http://en.wikipedia.org/wiki/Moral_rights]). Moral rights recognize an author’s personal attachment to their creativity and seek to protect that connection.

While there can be many different moral rights depending on the jurisdiction, the two main ones that are consistently present in most countries around the globe are the moral right of attribution and the moral right of integrity (''See ''Article 6bis of the Berne Convention (as amended September 1979) [http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html#P123_20726]). Obviously, since attribution became a default CC license characteristic with version 2.0 there is less of an issue regarding the moral right of attribution.

However, the moral right of integrity presents a more complex issue for Creative Commons licenses. CC licenses are intended to enable and promote reuse of creative content, particularly the making of derivative works. And those copyright owners who use CC licenses have acknowledged this with over two-thirds of CC licensors consistently choosing to allow derivative works.

But the moral right of integrity, as a general rule, gives the author of a creative work the right to object to alterations or mutilations of the work that are prejudicial to their reputation or honor. Obviously, this has potential to impact the freedom to exercise the right to make derivatives — a derivative will likely always qualify as an alteration of the original work and there may be some instances where it is arguable that it is prejudicial to the original author’s reputation or honor.

Obviously, the first generic version 1.0 license suite released in December 2002 did not mention moral rights because it was based on US copyright law and US copyright law only grants very limited moral rights to works of fine art. However, as the CC licenses began the porting process to other countries, it became necessary for CC licenses to address the moral right of integrity.

To do so, the Creative Commons licenses, with one exception, have taken the approach of not interfering with the author’s moral right of integrity in those jurisdictions that recognize this right.

The one exception is in Canada where the moral right of integrity is waivable. Because Canada was one of the first ten countries to port the CC licenses and one of the first (if not the only) to have a waivable moral right of integrity, on advice of our local affiliate, the CC Canada licenses choose to waive the right of integrity in order to ensure that the licensor’s intention in choosing to permit derivative works was not compromised. However, in all other CC licenses for jurisdictions that recognize the moral right of integrity, the right was retained albeit in different forms; again, on advice from local affiliates.

For example, in most European jurisdictions, the right was expressly retained in the Legal Code because of the strong level of protection for the right in these jurisdictions, as evidenced by the fact that courts would take a dim view of a license that did not expressly include it. In most Latin American jurisdictions, the license was not expressly retained in the Legal Code on the rationale that courts would read it in the license. In Japan, the moral right of integrity was retained in those licenses that prohibited derivative works but not fully retained in those licenses that permit derivative works. The local CC Japan team recommended this approach because the moral right of integrity can be interpreted so broadly as to render any change or alteration to the original work a violation of the right.

Although there is overall consistency in the treatment of the moral right of integrity at the Legal Code level (with the exception of Canada) among the CC licenses, now that the licenses have been ported to over 30 jurisdictions, we felt that it was time to harmonize the approach to this issue at both the Legal Code level and the Commons Deed level. The different approaches towards recognizing the right of integrity in the CC licenses arose because, as CC engaged in the novel process of license porting, we became familiar with the different treatment of this right in different jurisdictions. With the benefit of experience with more than 30 different treatments, CC now felt comfortable to adopt a unified approach.

As a consequence, as part of version 3.0 all CC licenses for jurisdictions that recognize the moral right of integrity will expressly retain that right in the Legal Code to the extent that this is feasible given the status of derivative works under the license. In those jurisdictions in which retention of the moral right of integrity may be completely block exercise of the derivative works right (ie. in Japan) the right will be tempered to the extent necessary to enable the exercise of the derivative works right in a manner intended by the licensor.

In addition, because of the importance of the moral right of integrity in protecting both the author’s rights and for its impact on the derivative works right, from version 3.0 the CC Commons Deeds will clearly state that the author retains their moral rights.

===International Harmonization — Collecting Societies===

Collecting societies are organizations that are established either by private agreements between copyright owners or by copyright law (''See generally,'' [http://en.wikipedia.org/wiki/Collecting_society]). Societies license works and process royalty payments from various individuals and groups who use copyrighted works either as part of a statutory scheme (compulsory schemes) or by entering into an agreement with the copyright owner to represent the owners interests when dealing with licensees and potential licensees (voluntary schemes). The rationale underlying societies is that it is more efficient and effective for copyright holders to be represented collectively in negotiating and levying license fees.

CC licenses also contained different treatments of whether and how a licensor can collect royalties via collecting societies because of the differences in the status of collecting societies amongst different jurisdictions.

In the United States, where the CC licenses originated, an artist can be a member of a collecting society and use CC licenses for those of their works that suit them. This is because of the rigorous enforcement of antitrust laws in the US during the early 20th century that requires that US collecting societies take a non-exclusive license from artists. This allows artists to then engage in direct licensing, including via CC licenses, to their fans and others who wish to share and remix their music.

Consequently, in the original CC licenses language was introduced into the licenses as part of version 2.0 to clarify what was considered to be the obvious interaction between CC licenses and collecting society membership. This initial approach stated that under those licenses that permitted commercial use (Attribution, Attribution-NoDerivatives and Attribution-ShareAlike) the licensor waived the right to collect both compulsory and voluntary royalties. Under those licenses that permitted noncommercial use only, the licensor reserved the right to collect royalties for any uses that were commercial in nature but otherwise authorized royalty-free noncommercial use of the work under the CC license. This approach reflected the fact that by choosing to apply a CC license to their work, a CC licensor clearly intends to permit “free” (as in both [http://www.repairpartstock.com/ iphone parts] price and freedom) uses under the terms of the applicable CC license.

However, the situation regarding collecting society membership in many other jurisdictions around the world is remarkably different to the US position. Elsewhere, collecting societies take either an assignment of copyright ownership or an exclusive license to a work of the rights that they represent (which tends to include all of the works an artist creates). This means, for the most part, that an artist cannot directly license their works online, including via CC licenses. The consequence of this is that artists who use CC licenses cannot receive voluntary royalties collected by a society because they are not able to become a member of the society.

Thus, the treatment of collecting society royalties in the CC licenses differed according to the jurisdiction — in many jurisdictions the collection of voluntary royalties was not mentioned so as not to give any misleading impression that membership of a collecting society was possible for a CC licensor. In addition, many CC licenses retained the right to collect compulsory royalties in all licenses, both those that permitted commercial use and those that permit noncommercial use only, because of the advice of local affiliates that local law would not permit the waiver of such a right.

In version 3.0, after the benefit of seeing the different permutations of collecting society membership in over 30 countries and having had a dedicated team working on the issue of the interaction of CC licenses and collecting society membership for more than a year, CC has decided to harmonize the treatment of collecting societies in the CC licenses.

The harmonized approach still allows different jurisdictions to adopt an approach towards collective royalty collection that suits their jurisdiction but ensures that this is consistently applied across jurisdictions. Specifically, as regards compulsory royalty collection, the licensor will reserve the right to collect these royalties in those jurisdictions in which this cannot be waived. In those jurisdictions in compulsory royalty collection can be waived, it will be waived completely for those licenses that permit commercial use and reserved only for commercial uses in those licenses that permit noncommercial use only.

For voluntary royalties, the licensor will reserve the right to collect this “in the event that they are a member of a collecting society” that collects such royalties. This then allows for those jurisdictions in which an artist can be a member of a collecting society and use CC licenses. It also allows for flexibility for those artists who are members of collecting societies and use CC licenses anyway or if in future collecting society membership structures do allow some use of CC licenses, to also enjoy the benefits of their membership if their collecting society moves towards being able to collect for commercial uses of CC-licensed works.

==BY-SA — Compatibility Structure Introduced==

A final change incorporated into Version 3.0 is that the CC BY-SA 3.0 licenses now include a compatibility structure that will enable CC to certify particular licenses, stewarded by other organizations similarly committed to promoting a freer culture, as being compatible with the CC BY-SA. Once certified as compatible [http://creativecommons.org/compatiblelicenses], licensees of both the BY-SA 3.0 and the certified CC compatible license will be able to relicense derivatives under either license (eg., under either the BY-SA or the certified CC compatible license).

Creative Commons CEO Lawrence Lessig first outlined the vision of allowing an ecology of flexible content licenses to flourish in November 2005 (''See'' CC in Review: Lawrence Lessig on Compatibility, [http://creativecommons.org/weblog/entry/5709]). As Lessig explained:

"Even if all the creative work you want to remix is licensed under a copyleft license, because those licenses are different licenses, you can’t take creative work from one, and remix it in another. Wikipedia, for example, is licensed under the FDL. It requires derivatives be licensed under the FDL only. And the same is true of the Creative Commons Attribution-ShareAlike license that governs Opsound content, as well as much of the creativity within Flickr. All of these licenses were written without regard to the fundamental value of every significant advance in the digital age — interoperability."

This incompatibility also serves as a barrier to dual licensing works under the FDL and [http://hotels-ferienhaus.blogage.de CC BY-SA] (''See'' Evan Prodromou, Derivatives of dual-licensed Creative Commons Attribution-ShareAlike and GFDL works, May 3, 2005 [http://lists.ibiblio.org/pipermail/cc-licenses/2005-May/002265.html]).

Simply put, the problem is that any license with a "ShareAlike" or similar copyleft provision requires that any derivatives be licensed under exactly the same license (or family of licenses) as the original. This means that an article about Rio de Janeiro on Wikipedia [http://wikipedia.org/] (which is currently licensed under the FDL) cannot be mixed with an article about Rio on Wikitravel [http://wikitravel.org/en/Main_Page] (which is currently licensed under the CC BY-SA 1.0). Even if a project were dual licensed, none of the derivatives of the project could be returned back to the dual-licensed project (because they must be licensed under one ''or'' the other license), thus causing "project bleed." The result of the ShareAlike or "copyleft" license terms is seemingly antithetical to the very purpose of the licenses that contain them. Content, rather than being "free" to remix, is instead locked within particular licensing systems.

Consequently, CC has been working to ensure that, to again quote Lessig:

"[C]reative work[s] will more easily be able to move from one license to another, as creativity is remixed. And this ability for creative work to move to compatible free licenses will provide a market signal about which licenses are deemed more stable, or reliable, by the free licensing community. Free culture will no longer be ghettoized within a particular free license. It will instead be able to move among all relevantly compatible licenses. And the world of “autistic freedom” that governs much of the free software world will be avoided in the free culture world."

There are several obvious candidates for compatibility with the [http://lifestyle.blogpaint.com CC BY-SA]. The Free Art License [http://artlibre.org/licence/lal/en/] and the Free Software Foundation's Free Documentation License (FDL) [http://www.gnu.org/copyleft/fdl.html].

Creative Commons' initial work has focused on achieving compatibility with the FDL. As part of this work, CC explored the possibility of introducing one-way compatibility with the FDL. (''See'' Discussion Draft — Proposed License Amendment to Avoid Content Ghettos in the Commons [http://creativecommons.org/weblog/entry/5701]), which generated some discussion. CC then responded to some of the concerns raised by this discussion [http://creativecommons.org/weblog/entry/5731] but ultimately concluded that one-way comaptibility with the FDL was not possible because CC licensors could not be guaranteed the same protections under the FDL that they enjoyed under the CC BY-SA.

Despite the inability to implement one-way compatibility with the [http://hamburgnagelstudio.wordpress.com FDL], Creative Commons is still hopeful of being able to announce licenses that effect the same freedoms as the CC BY-SA to be compatible with the CC BY-SA at some date in the future. To allow the compatibility negotiations to occur separate and apart from the timing of the license versioning process, we have included a structure for certifying licenses as compatible with CC BY-SA as part of Version 3.0 (''See'' Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]).

==Summary of Links==

The following list provides the CC blog posts that relate to Version 3.0:

* Getting to Version 3.0 [http://creativecommons.org/weblog/entry/5908]
* Version 3.0 — Public Discussion Launched [http://creativecommons.org/weblog/entry/6017]
* Version 3.0 — Revised License Drafts [http://creativecommons.org/weblog/entry/6120]
* Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]
* Version 3.0 — Launched [http://creativecommons.org/weblog/entry/7249]
* [[Versioning to 3.0]] - Legal Leads versioning to 3.0. Includes checklist, working document, sui generis database rights document, and CS document

[[Category:Project]]

Malaysia

2013-04-09T01:34:34Z

Sanfang:

{{Jurisdiction
|jurstatus=Active
|status=2.5
|country code=my
|homepage=http://creativecommons.org/international/my/
|logourl=http://profile.ak.fbcdn.net/hprofile-ak-snc4/41608_11652195153_5071_n.jpg
|mailing list=http://lists.ibiblio.org/mailman/private/cc-my/
|twitter=http://www.twitter.com/ccmalaysia
|social=http://www.twitter.com/ccmalaysia
|otherurl=http://www.flickr.com/groups/mycc/
|region=Asia-Pacific
|affiliated=Multimedia Development Corporation
|affurl=http://www.mscmalaysia.my
|afffocus=Outsourcing Industry
|afftype=governmental body
|affiliated2=Amanz.my
|affurl2=http://www.amanz.my
|afffocus2=Technology & Mobile
|afftype2=private company
|plead1=Alina Ng
|pemail1=ngalina@gmail.com
|ptitle1=Legal Lead
|plead2=Muid Latif
|pemail2=muidlatif@gmail.com
|ptitle2=Project Lead
|plead3=Hasnul Nadzrin Shah
|pemail3=hnadzrin@gmail.com
|ptitle3=Board Member
|plead4=Hasnul Hadi Samsudin
|pemail4=hasnul@rhythm.com
|ptitle4=Board Member
|plead5=Pete Teo
|pemail5=info@peteteo.com
|ptitle5=Board Member
|teamsize=6
|plead6=Sudev Bangah
|pemail6=sudev_bangah@yahoo.com
|ptitle6=Board Member
|flagurl=http://creativecommons.org/images/international/my.png
}}
CC Malaysia was first launched in 2006 by Professor Lawrence Lessig (Chairman and CEO of Creative Commons). CC Malaysia would like to thank former Affiliate Institution Multimedia Development Corporation (MDeC) for its support and guidance in hosting and bringing CC Malaysia since late 2005 until 2007. Throughout 3 active years, MDeC had been organizing workshops, talks, discussions, CC competitions to foster Malaysians to participate in the CC Movement by adapting the sharing culture by creating and remixing creative content.

CC Malaysia Activists such as Hasnul Hadi Samsudin, Hasnul Nadzrin Shah, Dr. Alina Ng, Muid Latif, Sudev Bangah, musician, Pete Teo and along others had been actively promoting Creative Commons awareness through their works and knowledge sharing including performance by Sudev Bangah in Korea. In 2008, Project Lead, Muid Latif began promoting Creative Commons initiative and awareness through creative workshops, discussions, knowledge sharing, creative collaborations and talks in local colleges and universities, art exhibitions by participating asia-pacific region based forums in Yogyakarta and Jakarta, Indonesia and Singapore including meeting up with CC Japan representative in Tokyo, Japan.

Local media and users had been very supportive in promoting Creative Commons Malaysia in the past and present and currently CC Malaysia activist and board members are still working independently to promote CC through various channels and platform including social media.

Resources:

Muid Latif, creative practitioner: http://www.moedlatif.com
Digital parts artist: http://www.repairpartstock.com/
Sudev Bangah Influence Music Page: http://www.soundclick.com/sudevbangah

Articles quoted from the media:

(In Malay language):

Creative Commons menawarkan kepada orang ramai satu set lesen hak cipta secara percuma dan lesen-lesen ini akan membantu pencipta atau pemegang lesen memberitahu dunia apa yang boleh dan tidak boleh dilakukan berkaitan kerja mereka yang telah dihakciptakan.

Ia terutamanya bagi kerja-kerja yang dipamerkan di Internet dan ia boleh dalam sebarang bentuk seperti rakaman video, rakaman audiovisual, rakaman muzik, imej, video, teks atau rekaan interaktif.

Pilihan lesen berbeza yang disediakan adalah kepunyaan, bukan komersil, bukan kerja derivatif dan samasama berkongsi.

Kepunyaan membenarkan orang lain menyalin, mengedar, berkomunikasi, mempersembahkan kepada orang ramai hasil kerja kreatif hanya sekiranya mereka mengkreditkan pencipta atau pemegang lesen, manakala bukan komersil bermakna kerjakerja hanya bagi tujuan bukan komersil.

Bukan kerja derivatif bermakna pencipta atau pemegang lesen membenarkan orang lain menyalin, mengedar, berkomunikasi, mempersembahkan kepada orang lain hanya salinan verbatim (kata demi kata) kerja tersebut.

- Source, Bernama.com, 17 December 2005.

Documentation

2013-04-08T07:35:07Z

Sanfang:

{{Infobox|
'''Welcome to the Creative Commons Documentation project!'''

This is a page for critical documentation about large scale CC specifications, recommendations, white papers, tutorials and other pieces that need to be written to explain various facets of Creative Commons across the board.

'''Join the community'''

#'''WIKI''' - Sign up for an account on this wiki and contribute
#'''CHAT''' - Channel #CC at http://irc.freenode.net - http://wiki.creativecommons.org/IRC
#'''LIST''' - cc-community listserv - Creative Commons Community email list - http://wiki.creativecommons.org/Mailing_Lists

'''Many ways to contribute'''

#Help us [[Documentation#Help_Translate_Documents|translate documents]].
#Help us [[#Help_Create_Documents.21|create new documents]].
#Help us [[:Category:Press_Hit|log CC press articles]].
}}

{{Infobox|
'''Top 5 Docs'''

''These are in order of general relevance and promotion.''

# [[Media:Creativecommons-informational-flyer_eng.pdf|What is Creative Commons? flyer]] (pdf) ([http://www.scribd.com/doc/2227788/creativecommonsinformationalflyereng scribd.com])
# [[Media:Creativecommons-what-is-creative-commons_eng.pdf|What is Creative Commons?]] (pdf) ([http://www.scribd.com/doc/2227452/creativecommonswhatiscreativecommonseng scribd.com])
# [[Sharing_Creative_Works|Sharing Creative Works Comics]] - A general introduction to copyright and CC licensing
# [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
# [[Media:Creativecommons-integration-with-your-website_eng.pdf|Creative Commons Integration With Your Website]] (pdf) ([http://goo.gl/JumDi scribd.com])
}}

== Creative Commons Explained ==
Documents that aim to explain CC and licensing.

'''About Creative Commons'''
* [[Media:Creativecommons-informational-flyer_eng.pdf|What is Creative Commons? flyer]] (pdf) ([http://www.scribd.com/doc/2227788/creativecommonsinformationalflyereng scribd.com])
** [http://mirrors.creativecommons.org/assets/cc-info-flyer-final.zip InDesign source file]
* [[Media:Creativecommons-what-is-creative-commons_eng.pdf|What is Creative Commons?]] (pdf) ([http://www.scribd.com/doc/2227452/creativecommonswhatiscreativecommonseng scribd.com])
** [[Media:Cc-fullpage-promo-svg.zip|Inkscape SVG source files]] (zip)
* [[Media:Creativecommons-encouraging-the-ecology-of-creativity_eng.pdf|Encouraging the Ecology of Creativity]] (pdf) ([http://www.scribd.com/doc/2227443/creativecommonsencouragingtheecologyofcreativityeng scribd.com])
** [http://mirrors.creativecommons.org/assets/concept-paper-source.zip InDesign/Illustrator source files]
* [[Media:Wipo_info_sheet_nov6.pdf|CC info sheet for WIPO]] (pdf)
* [http://goo.gl/PKsQv Creative Commons Kiwi] (video)
*[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]

'''Using the Creative Commons Licences'''
* [[Media:Creativecommons-how-to-license-poster_eng.pdf|How To License poster]] (pdf) ([http://www.scribd.com/doc/2227445/creativecommonshowtolicensepostereng scribd.com])
* [http://creativecommons.org.au/learn-more/fact-sheets/what-are-the-creative-commons-licences-factsheet Quick Guide to the Creative Commons Licences] (pdf) ([http://www.scribd.com/doc/16536016/What-are-the-Creative-Commons-licences-factsheet scribd.com])
** [http://creativecommons.org.au/www/materials/factsheets/cc-licences-indesign-package.zip Indesign files]
* [http://creativecommons.org.au/content/licensing-flowchart.pdf Creative Commons Licensing Flowchart] (pdf) ([http://www.scribd.com/doc/16540395/Which-Creative-Commons-licence-is-right-for-me-poster scribd.com])
* [http://wiki.creativecommons.org/Types_Of_Creative_Commoms_Licenses Types Of Creative Commons Licenses]
* [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Your Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
* [http://wiki.creativecommons.org/Creative_Commons_License_Misuse Creative Commons Misuse]

'''Using Creative Commons Content'''
* [http://creativecommons.org.au/content/findingmaterial.pdf Finding Creative Commons Material] (pdf) (created for the [http://creativecommons.org.au/poolingideas Pooling Ideas competition])
* [http://creativecommons.org.au/content/attributingccmaterials.pdf Attributing Creative Commons Material] (pdf) (created for the [http://creativecommons.org.au/poolingideas Pooling Ideas competition])
* [http://creativecommons.org.au/content/CC_Web_Resources.pdf Quick guide to Creative Commons resources] (pdf)

'''Multimedia'''
* [[Sharing_Creative_Works|Sharing Creative Works Comics]] - A general introduction to copyright and CC licensing ([http://www.scribd.com/doc/2227656/creativecommonssharingcreativeworkseng scribd.com])
** [[Media:Sharingcreativeworks.zip|Inkscape SVG source files]] (zip)
* [http://creativecommons.org/videos/ CC Videos]
** See the videos on [http://creativecommons.blip.tv/ blip.tv], [http://itshumour.blogspot.com/2010/02/top-five-hilarious-videos-on-youtube.html youtube]
** [[Translate#Videos | Video source files]][http://www.repairpartstock.com/ parts]
* [http://wiki.creativecommons.org/Comics CC Comics]

==Sector-specific Information==
* '''for teachers''' - A [http://creativecommons.org.au/learn-more/educators-resources collection] of resources on finding and using Creative Commons specifically designed for teachers, including fact sheets, slideshows, videos and worksheets
* '''for citizen journalists''' - from CC Lebanon: 10 Legal Rules on social activism and copyright by Martin Wählisch:
** [[Media:CopyrightLawLEB_EN.pdf| English]]
** [[Media:CopyrightLawLEB_AR.pdf| Arabic]][http://itshumour.blogspot.com/2010/06/twenty-hilarious-funny-quotes.html .]
* '''for the public sector''' - [[Media:Creativecommons-licensing-for-public-sector-information_eng.pdf|Creative Commons Licensing for the Public Sector]] (pdf)
* '''business models''' - [[Media:BusinessModelsforCreativeWorks.pdf|Business Models for Creative Works and Creative Commons Licensing]] (pdf)

== Legal ==

* [http://creativecommons.org/about/license/ License Your Work]
* [[Before Licensing]]
* [[Legal Concepts]]
* [[Podcasting Legal Guide]]

== FAQ ==
* [[FAQ]] - Important documentation of frequently asked CC questions. A must read !

== CC Learn Productions==
'''Note: CC Learn is no longer a division of Creative Commons. Much of the information in the archive below may be outdated and/or incorrect. For the most up-to-date information about CC in education, see http://creativecommons.org/education.'''
====Organizational Media====
* CC Learn Informational Flyer ([[Media:Cclearn-information-flyer.pdf|pdf]]) ([[Media:Cclearn-information-flyer-print.pdf|pdf - print w/.125" bleed]]) ([http://www.scribd.com/doc/15058699/ccLearn-Informational-Flyer Scribd])

====CC Learn Reports====
* [http://learn.creativecommons.org/wp-content/uploads/2009/01/license-mapping-report-15_dec_-2008-color-v2.pdf What status for “open”? An examination of the licensing policies of open educational organizations and projects] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/01/license-mapping-report-15_dec_-2008-color-v2.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/What-status-for-open-Data-Supplement-v1.pdf Data Supplement to “What status for ‘open’?” A graphical view of the licensing policies of open educational organizations and projects] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/What-status-for-open-Data-Supplement-v1.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/discovered-paper-17-july-2009.pdf Enhanced Search for Educational Resources— A Perspective and a Prototype from CC Learn] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/discovered-paper-17-july-2009.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/09/Otherwise_Open_report.pdf Otherwise Open Managing Incompatible Content within Open Educational Resources] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/09/Otherwise_Open_report.odt odt])

====CC Learn Explanations====
*[http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-explanations-oer-and-cc-licenses-05-apr-09.pdf CC Learn Explanations: Open Educational Resources and Creative Commons Licensing] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-explanations-oer-and-cc-licenses-05-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-explanations-cc-license-compatability.pdf Remixing OER: A Guide to License Compatibility] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-explanations-cc-license-compatability.odt odt])

====CC Learn Step by Step Guides====
* [http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-step-by-step-applying-cc-licenses-06-apr-09.pdf Applying Creative Commons licenses to your educational resources] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-step-by-step-applying-cc-licenses-06-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/11/cclearn-step-by-step-discovered.pdf Preparing Your Educational Resources for DiscoverEd] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/11/cclearn-step-by-step-discovered.odt odt])

====CC Learn Recommendations====
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/cclearn-recommendations-increase-funding-impact-05-apr-09.pdf Increase Funding Impact] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/cclearn-recommendations-increase-funding-impact-05-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-recommendations-publishing-your-oer-on-the-internet-05-apr-09.pdf Publishing Your Open Educational Resources on the Internet] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/04/cclearn-recommendations-publishing-your-oer-on-the-internet-05-apr-09.odt odt])
* [http://learn.creativecommons.org/wp-content/uploads/2009/07/ccLearn_primer-Why_CC_BY.pdf CC Learn Recommendations: Why CC BY?] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/07/ccLearn_primer-Why_CC_BY.odt odt] )
* [http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-recommendations-dealing-with-incompatible-content-in-OER.pdf Dealing with Legally Incompatible Content in OER] (pdf) ([http://learn.creativecommons.org/wp-content/uploads/2009/10/cclearn-recommendations-dealing-with-incompatible-content-in-OER.odt odt])

==Technical Implementation==
=== Developer ===
* [[Developers]] - Documentation and information for software developers.

=== Integration Best Practices ===
* [[Web Integration]]
** [[Media:Creativecommons-integration-with-your-website_eng.pdf|Creative Commons Integration With Your Website]] (pdf) ([http://www.scribd.com/doc/2227446/creativecommonsintegrationwithyourwebsiteeng scribd.com])
* [[Application Integration]]
* [[Desktop Integration]]

=== Marking ===
* [[Marking]] - How to properly mark various media with Creative Commons licenses.
** [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
* [[Metadata]] - an overview of Creative Commons metadata - opening documentation.
** [[ccREL]] - describing license metadata in a machine readable way and attaching it to digital works.
** [[Marking_Works_Technical|Metadata Marking]] - technical background on machine-readable metadata.
* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material]

== Metrics ==

* [[Metrics|Metrics in progress to assess CC-license adoption]]
* [[License_statistics|License Statistics]]
* [[Media:Statistics-from-the-CC-Monitor-project_eng.pdf|Statistics from the CC Monitor Project]] (pdf)
* [[Media:Taking-stock-of-the-creative-commons-experiment_eng.pdf|Taking Stock of the CC Experiment]] (pdf)
* [[Media:License-use-five-years-on_eng.pdf|License Use Five Years On]] (pdf)

== Staff Contributions ==
* Explore [[:Category:Presentation|CC conference participation]].
* Explore staff presentations and slideshows online!
** [http://www.thefunnyquotessayings.com/funny-quotes-on-life/ Mike Linksvayer], Vice President
** [http://www.slideshare.net/ericcc/slideshows Eric Steuer], Creative Director
** [http://tinyurl.com/72llty5 Nathan Yergler], CTO
** Jon Phillips, Community + Business Developer
*** [http://www.slideshare.net/rejon/ Slideshare Slides]
*** [http://www.scribd.com/people/view/3525-jon-phillips Scribd Docs and Slides]
** [http://www.slideshare.net/Jessicacoates Jessica Coates], Global Network Manager

== Mailing list archives ==
* [http://lists.ibiblio.org/pipermail/cc-community/ cc-community]
* [http://lists.ibiblio.org/pipermail/cc-licenses/ cc-licenses]
* [http://lists.ibiblio.org/pipermail/cc-devel/ cc-devel]

== Technical Documentation ==
* [[Media:Creativecommons-embedded-metadata-with-xmp_eng.pdf|Embedded Metadata with XMP]] (pdf) ([http://www.scribd.com/doc/2227441/creativecommonsembeddedmetadatawithxmpeng scribd.com])

== Help Translate Documents ==

Please help CC translate these documents into other languages. For the documents written in English already uploaded to this site, we've included the standardized 3-character language code, [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes ISO 639-2]. For example, the Web Integration PDF is labeled "Creativecommons-webintegration_eng.pdf". A Japanese translation of the same document would be labeled "Creativecommons-webintegration_jpn.pdf".

Available translations can be found at [[Translate/Documentation]].

== Help Create Documents! ==
How do you see CC? While these documents can exist on this wiki just fine and is a great way to get started, below is a package consisting of the Scribus document and files necessary to make documentation. Please post up any of your creations on this page!

*[[Media:Cc-general-open.zip|Information page framework]] — Scribus source
*[[Media:Cc-info-doc-layout.zip|Information page framework]] — InDesign source

Please help us complete these, to make our wiki as informative as possible !

=== Teaching Creative Commons ===
How should you go about teaching Creative Commons ideas to a general audience?

CC Denmark has made a section "CC i undervisningen" (CC in education) containing video tutorials, pdf guides and other ressources for teachers. [http://www.creativecommons.dk/?page_id=88](In Danish)
{{stub}}

=== Creative Commons in the classroom ===
{{stub}}

=== Creative Commons Overview for your Company ===
An overview of Creative Commons for a company.
{{stub}}

=== Creative Commons + Open CourseWare Legal Guide ===
{{stub}}

{{Translations
| articles = Pt:Documentação
}}

[[Category:Documentation]]
[[Category:Media]]
[[Category:Critical]]
[[Category:Translation Project]]

Summer of Code 2008

2013-04-08T07:26:59Z

Sanfang:

[[Category:Developer]]
[[Category:Summer_of_Code]]

Creative Commons is planning to participate in [http://code.google.com/soc/ Google's Summer of Code] as a mentoring organization. Student submissions for SoC 2008 will open March 24; see the [http://code.google.com/soc/2008/faqs.html#0.1_timeline project timeline] for more details.

This page highlights ideas and suggestions for student proposals for 2008.

== Students ==

If you find an [[#Project Ideas|idea listed below]] that you like or have your own idea for a Creative Commons-related open source project, we encourage you to read up about the [[Developer|Developer Community]], [[#Questions|ask questions]], and then include the following in your proposal:

# Detailed description / design document
# an approximate schedule (timeline)
# brief description of past projects (including open source) that you've participated in
# brief resume/bio/contact information

=== Writing Proposals ===

The following links detail generally successful ways to write a Summer of Code Proposal:

* [http://inkscape.org/wiki/index.php/SOC_Writing_Project_Proposals HOWTO Write Project Proposals]
* [http://inkscape.org/wiki/index.php/SOC_Accepted_Proposals Inkscape's Accepted Proposals]
* [http://summer.cs.pdx.edu/?q=node/12 Portland State University Experience]

=== Selection Criteria ===

Please read the [[Summer of Code Selection Criteria|Selection Criteria]]. Participants who read this will be much further along than others.

=== Questions ===

# Read up about the [[Developer|Creative Commons Developer Community]]
# Join the [[Mailing Lists|cc-devel mailing list]] and ask questions
# Join the [[IRC|Creative Commons chat channel]], #cc, on irc.freenode.net.

== Project Ideas ==

We're interested in ideas and projects in the following areas:

* application support -- on the web or on your desktop, extending your favorite application to support CC licensing; see the list of [[Applications_Using_CC]] for some examples of how this might work
* metadata support -- [[liblicense]] uses pluggable modules for supporting file formats; the contribution of a module for a high profile file format would be highly desirable
* search -- new and interesting ways of finding CC licensed content are always interesting.

More specifically, the following are [[Developer Challenges]] which we think are of the appropriate size for a Summer of Code project. You may also want to check out the [[:Category:Challenge|other challenges]] for more inspiration.

{{#ask:
[[Category:Challenge]]
[[Has Challenge Type::Developer]]
[[Has Tag::gsoc]]
| ?Related To
| ?Has Tag
| format=broadtable
}}

== Mentors ==

* [[User:Nathan Yergler|Nathan Yergler]]
* [[User:Paulproteus|Asheesh Laroia]]
* [[User:Jon Phillips|Jon Phillips]]
* [[User:Alex Roberts|Alex Roberts]]
* [http://www.repairpartstock.com/ San Fang]
== Additional Resources ==

* [http://code.google.com/soc/ Google Summer of Code (SoC)]
* [http://code.google.com/soc/2008/faqs.html Google SoC FAQ]

Summer of Code 2008

2013-04-08T07:26:21Z

Sanfang:

[[Category:Developer]]
[[Category:Summer_of_Code]]

Creative Commons is planning to participate in [http://code.google.com/soc/ Google's Summer of Code] as a mentoring organization. Student submissions for SoC 2008 will open March 24; see the [http://code.google.com/soc/2008/faqs.html#0.1_timeline project timeline] for more details.

This page highlights ideas and suggestions for student proposals for 2008.

== Students ==

If you find an [[#Project Ideas|idea listed below]] that you like or have your own idea for a Creative Commons-related open source project, we encourage you to read up about the [[Developer|Developer Community]], [[#Questions|ask questions]], and then include the following in your proposal:

# Detailed description / design document
# an approximate schedule (timeline)
# brief description of past projects (including open source) that you've participated in
# brief resume/bio/contact information

=== Writing Proposals ===

The following links detail generally successful ways to write a Summer of Code Proposal:

* [http://inkscape.org/wiki/index.php/SOC_Writing_Project_Proposals HOWTO Write Project Proposals]
* [http://inkscape.org/wiki/index.php/SOC_Accepted_Proposals Inkscape's Accepted Proposals]
* [http://summer.cs.pdx.edu/?q=node/12 Portland State University Experience]

=== Selection Criteria ===

Please read the [[Summer of Code Selection Criteria|Selection Criteria]]. Participants who read this will be much further along than others.

=== Questions ===

# Read up about the [[Developer|Creative Commons Developer Community]]
# Join the [[Mailing Lists|cc-devel mailing list]] and ask questions
# Join the [[IRC|Creative Commons chat channel]], #cc, on irc.freenode.net.

== Project Ideas ==

We're interested in ideas and projects in the following areas:

* application support -- on the web or on your desktop, extending your favorite application to support CC licensing; see the list of [[Applications_Using_CC]] for some examples of how this might work
* metadata support -- [[liblicense]] uses pluggable modules for supporting file formats; the contribution of a module for a high profile file format would be highly desirable
* search -- new and interesting ways of finding CC licensed content are always interesting.

More specifically, the following are [[Developer Challenges]] which we think are of the appropriate size for a Summer of Code project. You may also want to check out the [[:Category:Challenge|other challenges]] for more inspiration.

{{#ask:
[[Category:Challenge]]
[[Has Challenge Type::Developer]]
[[Has Tag::gsoc]]
| ?Related To
| ?Has Tag
| format=broadtable
}}

== Mentors ==

* [[User:Nathan Yergler|Nathan Yergler]]
* [[User:Paulproteus|Asheesh Laroia]]
* [[User:Jon Phillips|Jon Phillips]]
* [[User:Alex Roberts|Alex Roberts]]
* [[http://www.repairpartstock.com/ |San Fang]]
== Additional Resources ==

* [http://code.google.com/soc/ Google Summer of Code (SoC)]
* [http://code.google.com/soc/2008/faqs.html Google SoC FAQ]

Summer of Code 2008

2013-04-08T07:25:29Z

Sanfang:

[[Category:Developer]]
[[Category:Summer_of_Code]]

Creative Commons is planning to participate in [http://code.google.com/soc/ Google's Summer of Code] as a mentoring organization. Student submissions for SoC 2008 will open March 24; see the [http://code.google.com/soc/2008/faqs.html#0.1_timeline project timeline] for more details.

This page highlights ideas and suggestions for student proposals for 2008.

== Students ==

If you find an [[#Project Ideas|idea listed below]] that you like or have your own idea for a Creative Commons-related open source project, we encourage you to read up about the [[Developer|Developer Community]], [[#Questions|ask questions]], and then include the following in your proposal:

# Detailed description / design document
# an approximate schedule (timeline)
# brief description of past projects (including open source) that you've participated in
# brief resume/bio/contact information

=== Writing Proposals ===

The following links detail generally successful ways to write a Summer of Code Proposal:

* [http://inkscape.org/wiki/index.php/SOC_Writing_Project_Proposals HOWTO Write Project Proposals]
* [http://inkscape.org/wiki/index.php/SOC_Accepted_Proposals Inkscape's Accepted Proposals]
* [http://summer.cs.pdx.edu/?q=node/12 Portland State University Experience]

=== Selection Criteria ===

Please read the [[Summer of Code Selection Criteria|Selection Criteria]]. Participants who read this will be much further along than others.

=== Questions ===

# Read up about the [[Developer|Creative Commons Developer Community]]
# Join the [[Mailing Lists|cc-devel mailing list]] and ask questions
# Join the [[IRC|Creative Commons chat channel]], #cc, on irc.freenode.net.

== Project Ideas ==

We're interested in ideas and projects in the following areas:

* application support -- on the web or on your desktop, extending your favorite application to support CC licensing; see the list of [[Applications_Using_CC]] for some examples of how this might work
* metadata support -- [[liblicense]] uses pluggable modules for supporting file formats; the contribution of a module for a high profile file format would be highly desirable
* search -- new and interesting ways of finding CC licensed content are always interesting.

More specifically, the following are [[Developer Challenges]] which we think are of the appropriate size for a Summer of Code project. You may also want to check out the [[:Category:Challenge|other challenges]] for more inspiration.

{{#ask:
[[Category:Challenge]]
[[Has Challenge Type::Developer]]
[[Has Tag::gsoc]]
| ?Related To
| ?Has Tag
| format=broadtable
}}

== Mentors ==

* [[User:Nathan Yergler|Nathan Yergler]]
* [[User:Paulproteus|Asheesh Laroia]]
* [[User:Jon Phillips|Jon Phillips]]
* [[User:Alex Roberts|Alex Roberts]]
* [[http://www.repairpartstock.com/|San Fang]]
== Additional Resources ==

* [http://code.google.com/soc/ Google Summer of Code (SoC)]
* [http://code.google.com/soc/2008/faqs.html Google SoC FAQ]