Creative Commons - User contributions [en]

Croatia

2012-07-16T09:42:05Z

BurnsideRinehart:

{{Jurisdiction
|jurstatus=Active
|status=3.0
|country code=hr
|homepage=http://creativecommons.org/international/hr/
|mailing list=http://lists.ibiblio.org/pipermail/cc-hr/
|region=Europe
|affiliated=ultimedia Institute [mi2]
|affurl=http://www.mi2.hr/
|afftype=NGO
|plead1=Tomislav Medak
|pemail1=to-me@mi2.hr
|ptitle1=Public Lead
|plead2=Marcell Mars
|ptitle2=Public Lead
|plead3=Tomislav Domes
|ptitle3=Community Co-ordinator
|plead4=Diana Kovačević Remenarić
|pemail4=diana@mi2.hr
|ptitle4=Legal Lead
|teamsize=4
|flagurl=http://creativecommons.org/images/international/hr.png
}}
=Affiliate Team Roadmap=

* Date submitted: Dec 20, 2010
* Timespan of this roadmap: Jan 01-Dec 31, 2011

== Team information ==
Croatian Creative Commons affiliate organization Multimedia Institute, a non-profit working in technologies, culture and activism. Legal and public activities are co-ordinated by members of the organization and with external legal expertise. The project team includes following people:
** Tomislav Medak, project lead (general co-ordination, evangelism, facilitation of porting and versioning-up, translation, public inquiries, fundraising)
** Marcell Mars, project lead (evangelism, outreach & community building, technological expertise)
** Tomislav Domes, community co-ordinator (evangelism, education, community building)
** Diana Kovačević Remenarić, legal lead (legal advisory and co-ordination of public discussion in the process of porting and versioning-up)

Date of earliest MOU in jurisdiction: June 10, 2003

Self-Identified Region(s): Europe

Geographically Croatia is a part of Europe, however one should note that Europe sometimes, particularly in issues of advocacy, gets equated with the political formation of European Union, which Croatia is not part of, but wil probably acceed in 2012 or 2013.

==Vision==

Initial Croatian localization of Creative Commons licenses back in 2005 was part of broader efforts of the emerging and burgeoning community of free culture creators who – inspired by [http://www.planetsofts.com free software] ethos – subscribed to and promoted the ideas of culture of sharing and remixing. It is only after that early period that web services, media and institutions that the ethos and the licenses emerged on the radar of web services and public institutions.

Nowadays when free culture and freely licensed content is no longer a mystery in the public's eye and creators are no longer ignorant, localized licenses provide Croatian content providers: cultural, educational and heritage institutions, media and web businesses with a legal framework for pursuing their mandate, commitment or interest to publish freely licensed or public domain content. Licenses in the Croatian jurisdiction have become a tool for free content publishing and a tool for free content advocacy.

CC Croatia brings a useful mix to catalyze this process: experience of free culture community building, grass-root hacktivism, digital freedom advocacy, cultural policy expertise. As the international network of CC affiliates increasingly focuses on addressing educational, research and heritage institutions and public domain, so will the the CC Croatia intensify its work with institutional actors and content providers. With the entry of Croatia into the EU, it will work with the rest of EU CC projects on advocating the extension of structural public domain beyond the national context.

===Community===

The CC Croatia has emerged out of the community of free culture creators. The project continues to receive the support of music and film artists, while collaborating with them in promoting free culture and helping them in adoption and enforcement of licenses.

The project and Multimedia Institute will continue to provide creators and individual adopters with critical and fresh perspective on developments in digital culture by organizing conferences, guest lectures and other events throughout the year. In 2011 we will particularly focus on computer games and gaming culture by organizing a small international conference and an exhibition, with one of the focuses on free games and inclusion of free content into games.

Also we'll engage next year more with the almost non-existent open education community, focusing our efforts on working with the institution of higher learning and librarians to start investigating ways of creating frameworks for publishing open education resources. A part of this effort will also focus on DYI free software/hardware solution for book scanning.

==Priority Goals==

1. Focus-area:
Translating CC0 deed, chooser, and FAQ. An overdue goal that will allow us to have an enlarged framework to talk to heritage and research institutions.

2. Focus-area:
Identifying and approaching Croatian web content providing services who could adopt CC licensing framework for their content. With a number of smaller and several big content providing services already offering CC licensing, this will increase the outreach, visibility and adoption of licenses with the greater number of end users of those services.

3. Focus-area:
Identifying and approaching potential partners in academia and education to develop together OER activities.

==Project Outputs==
The outputs we plan to complete are as follows:

#Focus-area 1
##Project Output: translations of CC0 deed, chooser and FAQ
##Expected start date - Expected date of completion: Jan 1 – April 1, 2011
##Team Member(s) Responsible: Tomislav Medak, Diana Kovačević Remenarić
##How will this output help achieve your goals? The translation is a goal in itself, but it will allow us to have a complete set of localized legal tools and FAQs
#Focus-area
##Project Output: five content providing web services identify and three with CC licensing implemented
##Expected start date - Expected date of completion: March 1 – Dec 31, 2011
##Team Member(s) Responsible: Tomislav Medak, Marcell Mars, Tomislav Domes
##How will this output help achieve your goals? Within the Croatian jurisdiction there is already of smaller and several large content providing services that have adopted the licenses and they generate the largest quantity of licensed content and largest visibility of licenses. New users of this kind will further drive the adoption and promote the licenses.
#Focus-area
##Project Output: Three rounds of consultations with the Croatian proponents of open access (e.g. Library of the National Research Institute Ruđer Bošković, member of Croatian Academy of Sciences Vlatko Silobrčić, Hrčak database), Ministry of Education, Science and Sport, and a university, all focusing on initiating smaller scale OER cases. Forming one or more smaller sclae joint projects with partners from education sector.
##Expected start date - Expected date of completion: July 1, 2011 – Dec 31, 2011
##Team Member(s) Responsible: Marcell Mars, Tomislav Medak
##How will this output help achieve your goals? OER is an untreaded territory for local institutions of learning. Being a non-profit, non-academic institution, our access to these institutions is limited. Given the increasing social divide and student unrests over commercialization of education in Croatia, OER will create an inroad into the local academic context for issues of open access, open licensing, open education and public domain.

==Metrics==

* How will you measure and evaluate your impact on focus-area 1? % of translated strings, completeness of respective web pages, coherence of language
* How will you measure and evaluate your impact on focus-area 2? # of services and # of linkbacks to licenses
* How will you measure and evaluate your impact on focus-area 3? developed small projects, access to drivers and decision-makers in institutions of higher education

==Resources Required==

We will potentially need software developers to help web services we aprroach integrate licenses into their interfaces. A great source of developer expertise we can draw from is the hacker community active around our organization.

We are short on OER and open access expertise and practical experience and will have to seek that from other CC affiliates.

==Sustainability and Scalability==

CC Croatia has organizational stability through Multimedia Institute. The organization dedicates its organizational resources towards CC Croatia activities and compounds their effect with its other activities. It has done so for a number of years. If activities take longer to complete the organization will continue supporting them for as long as they take. Given that three persons within the organization are working part time on CC activities, the organization always has capacity to dedicate more work towards completing them.

* 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)

Through Multimedia Institute's mailing lists, CC-Croatia mailing list, Croatia CC project page, cc-affiliate mailing list.

* How will you document the project so that others may replicate or learn from your efforts?

Through public outputs of the project and if more detailed needed, oral transfer of knowledge.

==Collaboration==

* Please have a look at other roadmaps.
** How could the jurisdiction's plans help drive or support other jurisdictions' activities?

We can provide experience with regards to community building and evangelizing free culture ethos.

** What are other jurisdictions doing that might support or contribute to the project?

We would like to hook-up with jurisdictions that have an experience with ways of gaining access to the academia from the outside and initiating OER activities. Other aspect that we would like to follow others in is open data.

* Would you be interested in mentoring new jurisdiction teams?

We probably don't have the capacity to do it on an ongoing basis, but could provide one-off insights and feedback, particularly relating to direct work with the creators and community building.

* Conversely, would you be interested in having a mentor from a more experienced jurisdiction team?

It probably wouldn't be feasible, consultations would be more useful. However, there's already a structure for that within CC Europe meetings, provided they can continue beyond the Communia project.

===Regional===

Very few jurisdictions have a roadmap, so it's hard hard to identify the projects we could collaborate on. We will probably continue discussing and working with CC Europe and particularly with CC Affiliates in the Balkans.

==Translation==

Croatian CC activities are promoted primarily in Croatian language, which is for all intents and purposes a shared language with Serbia, Bosnia and Herzegovina and Monte Negro, so we are open to contributions from and to all those shared language communities. CC0 is not yet available in Croatian, but will soon be.

Croatian CC translations are discussed with the free software localization communities and linguists.

==Timeline==
2nd Quarter (Dec / Feb / Mar)
1. translations of CC0 deed, chooser and FAQtranslations of CC0 deed, chooser and FAQ (Tomislav Medak, Diana Kovačević Remenarić)
2. expanding adoption to new web services (Tomislav Medak, Marcell Mars, Tomislav Domes, external software developer expertise)

3rd Quarter (Apr / May / Jun)
1. expanding adoption to new web services (Tomislav Medak, Marcell Mars, Tomislav Domes, external software developer expertise)
2. initiating OER activities (Tomislav Medak, Marcell Mars, external expertise on OER from CC Affiliates Network)

4th Quarter (Sep / Oct / Nov)
1. expanding adoption to new web services( Tomislav Medak, Marcell Mars, Tomislav Domes, external software developer expertise)
2. initiating OER activities (Tomislav Medak, Marcell Mars, external expertise on OER from CC Affiliates Network)

Croatia

2012-07-16T09:41:01Z

BurnsideRinehart:

{{Jurisdiction
|jurstatus=Active
|status=3.0
|country code=hr
|homepage=http://creativecommons.org/international/hr/
|mailing list=http://lists.ibiblio.org/pipermail/cc-hr/
|region=Europe
|affiliated=ultimedia Institute [mi2]
|affurl=http://www.mi2.hr/
|afftype=NGO
|plead1=Tomislav Medak
|pemail1=to-me@mi2.hr
|ptitle1=Public Lead
|plead2=Marcell Mars
|ptitle2=Public Lead
|plead3=Tomislav Domes
|ptitle3=Community Co-ordinator
|plead4=Diana Kovačević Remenarić
|pemail4=diana@mi2.hr
|ptitle4=Legal Lead
|teamsize=4
|flagurl=http://creativecommons.org/images/international/hr.png
}}
=Affiliate Team Roadmap=

* Date submitted: Dec 20, 2010
* Timespan of this roadmap: Jan 01-Dec 31, 2011

== Team information ==
Croatian Creative Commons affiliate organization Multimedia Institute, a non-profit working in technologies, culture and activism. Legal and public activities are co-ordinated by members of the organization and with external legal expertise. The project team includes following people:
** Tomislav Medak, project lead (general co-ordination, evangelism, facilitation of porting and versioning-up, translation, public inquiries, fundraising)
** Marcell Mars, project lead (evangelism, outreach & community building, technological expertise)
** Tomislav Domes, community co-ordinator (evangelism, education, community building)
** Diana Kovačević Remenarić, legal lead (legal advisory and co-ordination of public discussion in the process of porting and versioning-up)

Date of earliest MOU in jurisdiction: June 10, 2003

Self-Identified Region(s): Europe

Geographically Croatia is a part of Europe, however one should note that Europe sometimes, particularly in issues of advocacy, gets equated with the political formation of European Union, which Croatia is not part of, but wil probably acceed in 2012 or 2013.

==Vision==

Initial Croatian localization of Creative Commons licenses back in 2005 was part of broader efforts of the emerging and burgeoning community of free culture creators who – inspired by [http://www.planetsofts.com free software] ethos – subscribed to and promoted the ideas of culture of sharing and remixing. It is only after that early period that web services, media and institutions that the ethos and the licenses emerged on the radar of web services and public institutions.

Nowadays when free culture and freely licensed content is no longer a mystery in the public's eye and creators are no longer ignorant, localized licenses provide Croatian content providers: cultural, educational and heritage institutions, media and web businesses with a legal framework for pursuing their mandate, commitment or interest to publish freely licensed or public domain content. Licenses in the Croatian jurisdiction have become a tool for free content publishing and a tool for free content advocacy.

CC Croatia brings a useful mix to catalyze this process: experience of free culture community building, grass-root hacktivism, digital freedom advocacy, cultural policy expertise. As the international network of CC affiliates increasingly focuses on addressing educational, research and heritage institutions and public domain, so will the the CC Croatia intensify its work with institutional actors and content providers. With the entry of Croatia into the EU, it will work with the rest of EU CC projects on advocating the extension of structural public domain beyond the national context.

===Community===

The CC Croatia has emerged out of the community of free culture creators. The project continues to receive the support of music and film artists, while collaborating with them in promoting free culture and helping them in adoption and enforcement of licenses.

The project and Multimedia Institute will continue to provide creators and individual adopters with critical and fresh perspective on developments in digital culture by organizing conferences, guest lectures and other events throughout the year. In 2011 we will particularly focus on computer games and gaming culture by organizing a small international conference and an exhibition, with one of the focuses on free games and inclusion of free content into games.

Also we'll engage next year more with the almost non-existent open education community, focusing our efforts on working with the institution of higher learning and librarians to start investigating ways of creating frameworks for publishing open education resources. A part of this effort will also focus on DYI free software/hardware solution for book scanning.

==Priority Goals==

1. Focus-area:
Translating CC0 deed, chooser, and FAQ. An overdue goal that will allow us to have an enlarged framework to talk to heritage and research institutions.

2. Focus-area:
Identifying and approaching Croatian web content providing services who could adopt CC licensing framework for their content. With a number of smaller and several big content providing services already offering CC licensing, this will increase the outreach, visibility and adoption of licenses with the greater number of end users of those services.

3. Focus-area:
Identifying and approaching potential partners in academia and education to develop together OER activities.

==Project Outputs==
The outputs we plan to complete are as follows:

#Focus-area 1
##Project Output: translations of CC0 deed, chooser and FAQ
##Expected start date - Expected date of completion: Jan 1 – April 1, 2011
##Team Member(s) Responsible: Tomislav Medak, Diana Kovačević Remenarić
##How will this output help achieve your goals? The translation is a goal in itself, but it will allow us to have a complete set of localized legal tools and FAQs
#Focus-area
##Project Output: five content providing web services identify and three with CC licensing implemented
##Expected start date - Expected date of completion: March 1 – Dec 31, 2011
##Team Member(s) Responsible: Tomislav Medak, Marcell Mars, Tomislav Domes
##How will this output help achieve your goals? Within the Croatian jurisdiction there is already of smaller and several large content providing services that have adopted the licenses and they generate the largest quantity of licensed content and largest visibility of licenses. New users of this kind will further drive the adoption and promote the licenses.
#Focus-area
##Project Output: Three rounds of consultations with the Croatian proponents of open access (e.g. Library of the National Research Institute Ruđer Bošković, member of Croatian Academy of Sciences Vlatko Silobrčić, Hrčak database), Ministry of Education, Science and Sport, and a university, all focusing on initiating smaller scale OER cases. Forming one or more smaller sclae joint projects with partners from education sector.
##Expected start date - Expected date of completion: July 1, 2011 – Dec 31, 2011
##Team Member(s) Responsible: Marcell Mars, Tomislav Medak
##How will this output help achieve your goals? OER is an untreaded territory for local institutions of learning. Being a non-profit, non-academic institution, our access to these institutions is limited. Given the increasing social divide and student unrests over commercialization of education in Croatia, OER will create an inroad into the local academic context for issues of open access, open licensing, open education and public domain.

==Metrics==

* How will you measure and evaluate your impact on focus-area 1? % of translated strings, completeness of respective web pages, coherence of language
* How will you measure and evaluate your impact on focus-area 2? # of services and # of linkbacks to licenses
* How will you measure and evaluate your impact on focus-area 3? developed small projects, access to drivers and decision-makers in institutions of higher education

==Resources Required==

We will potentially need software developers to help web services we aprroach integrate licenses into their interfaces. A great source of developer expertise we can draw from is the hacker community active around our organization.

We are short on OER and open access expertise and practical experience and will have to seek that from other CC affiliates.

==Sustainability and Scalability==

CC Croatia has organizational stability through Multimedia Institute. The organization dedicates its organizational resources towards CC Croatia activities and compounds their effect with its other activities. It has done so for a number of years. If activities take longer to complete the organization will continue supporting them for as long as they take. Given that three persons within the organization are working part time on CC activities, the organization always has capacity to dedicate more work towards completing them.

* 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)

Through Multimedia Institute's mailing lists, CC-Croatia mailing list, Croatia CC project page, cc-affiliate mailing list.

* How will you document the project so that others may replicate or learn from your efforts?

Through public outputs of the project and if more detailed needed, oral transfer of knowledge.

==Collaboration==

* Please have a look at other roadmaps.
** How could the jurisdiction's plans help drive or support other jurisdictions' activities?

We can provide experience with regards to community building and evangelizing free culture ethos.

** What are other jurisdictions doing that might support or contribute to the project?

We would like to hook-up with jurisdictions that have an experience with ways of gaining access to the academia from the outside and initiating OER activities. Other aspect that we would like to follow others in is open data.

* Would you be interested in mentoring new jurisdiction teams?

We probably don't have the capacity to do it on an ongoing basis, but could provide one-off insights and feedback, particularly relating to direct work with the creators and community building.

* Conversely, would you be interested in having a mentor from a more experienced jurisdiction team?

It probably wouldn't be feasible, consultations would be more useful. However, there's already a structure for that within CC Europe meetings, provided they can continue beyond the Communia project.

===Regional===

Very few jurisdictions have a roadmap, so it's hard hard to identify the projects we could collaborate on. We will probably continue discussing and working with CC Europe and particularly with CC Affiliates in the Balkans.

==Translation==

Croatian CC activities are promoted primarily in Croatian language, which is for all intents and purposes a shared language with Serbia, Bosnia and Herzegovina and Monte Negro, so we are open to contributions from and to all those shared language communities. CC0 is not yet available in Croatian, but will soon be.

Croatian CC translations are discussed with the free software localization communities and linguists.

==Timeline==
2nd Quarter (Dec / Feb / Mar)
1. translations of CC0 deed, chooser and FAQtranslations of CC0 deed, chooser and FAQ (Tomislav Medak, Diana Kovačević Remenarić)
2. expanding adoption to new web services (Tomislav Medak, Marcell Mars, Tomislav Domes, external software developer expertise)

3rd Quarter (Apr / May / Jun)
1. expanding adoption to new web services (Tomislav Medak, Marcell Mars, Tomislav Domes, external software developer expertise)
2. initiating OER activities (Tomislav Medak, Marcell Mars, external expertise on OER from CC Affiliates Network)

4th Quarter (Sep / Oct / Nov)
1. expanding adoption to new web services([http://phoenixfurnishedapartments.net/?page_id=10| Tomislav Medak], Marcell Mars, Tomislav Domes, external software developer expertise)
2. initiating OER activities (Tomislav Medak, Marcell Mars, external expertise on OER from CC Affiliates Network)

Partner Interface

2012-07-16T09:37:05Z

BurnsideRinehart:

[[Category:Developer]][[Category:technology]][[Category:guide]][[Category:Integration]]
{{Infobox|See [[Web Integration]] for information on all Creative Commons' integration tools.}}

== Web Integration Developer's Guide ==

''Integrating Creative Commons licenses into your web application''

While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software. If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate.

This guide is generally split into three parts:

* [[#Part 1: Letting users select a license|Part 1: Letting users select a license]]
* [[#Part 2: Processing and Storage of license information|Part 2: Processing and Storage of license information]]
* [[#Part 3: Display of license information|Part 3: Display of license information]]

== Part 1: Letting users select a license ==

Whether your software is a website or a downloadable application, the first step to integrating Creative Commons licenses is letting users select a license directly from your software. The process involves loading a simplified Creative Commons license interface from within a popup window, embedded into your website, or launched from an HTML window control in your application. URL variables are read into the page and are appended when complete, allowing data to be extracted from the process and passed through it.

==== The remote license engine application ====

The heart of the process is running the remote license interface which is available at this URL:

http://creativecommons.org/license/?partner={partner}&exit_url={exit_url}&stylesheet={stylesheet}&partner_icon_url={partner_icon_url}

Note that the curly braces, i.e. {partner}, should be omitted. The full set of URL variables available are as follows:

<div class="code">

'''partner (required):''' The name of your application or site, used for tracking usage at Creative Commons. Any descriptive name can be added here.

'''exit_url (required):''' The return URL on your application that will load after a user selects a license and will contain appended variables in the URL that your [http://www.planetsofts.com/Windows software] will need to read.

'''additional requirement:'''

Your exit_url must include "license_url=[license_url]" and may optionally include the license_name=[license_name], license_button=[license_button], and deed_url=[deed_url] variables. Explanation of each:

'''license_url:''' URL for the selected license. Link to this URL in the licensed page. Example: http://creativecommons.org/licenses/by/2.0/

'''license_name:''' Pretty name for the selected license. Example: Attribution

'''license_button:''' URL for the image corresponding to the selected license, useful for displaying on a licensed page. Example: http://creativecommons.org/images/public/somerights20.gif

'''deed_url:''' URL for the deed corresponding to the selected license. Usually this will be identical to the value of license_url, unless a "branded" license is selected. Note that even if deed_url is different than license_url, is is still valid to use the URL specified by license_url, as both will point to the same legal code. If you want to support this feature, link to the deed_url in the licensed page. Example: http://creativecommons.org/licenses/by-nc-nd/2.0/deed-music

A sample exit URL would be:

http://example.com/return_from_cc?license_url=[license_url]%26license_name=[license_name]

The license engine will replace the license_url, license_name, license_button, and deed_url variables with proper variables once a user has chosen a license (more on this in Part 2). The square brackets must be included for the license engine to properly replace the values.

Note that your exit URL can carry your application's URL variables into and out of the license application by URL escaping within your exit URL, for example:

http://example.com/return_from_cc?license_url=[license_url]%26license_name=[license_name]%26userID=42%26user-work=foo.jpg

The above example will let your application know that a userID of 42 that submitted a user-work titled foo.jpg selected a specific license on exit of the license engine.

If you want to maintain state but do not wish to pass data through the URL (e.g., for reasons of privacy or data size), consider saving the data in a user cookie (which will only be sent to your site, not creativecommons.org), save the data in a file or database and save a lookup key in a cookie or pass the lookup key via the URL, or use the popup or iframe methods (see below), which do not require the user to "leave" your form.

'''stylesheet (optional):'''

URL of a Cascading Style Sheet (CSS) file to customize the layout, look, and feel of the license questions. View source on the license engine to see the ID and classes available to be styled.

'''partner_icon_url (optional):''' if you'd like a custom image displayed at the top of the license application, add the image's URL in this variable.

''The following enable choosing licenses ported to the copyright law of specific legal jurisdictions. See the [[http://creativecommons.org/international Creative Commons international page]] for more information.''

'''jurisdiction (optional):''' Choose licenses of specified jurisdiction. With jurisdiction_choose on, sets pre-selected jurisdiction. You may use any jurisdiction code supported by the license engine.

'''jurisdiction_choose (optional):''' If set to '1', user will be given a list of jurisdictions to choose from.

'''lang (optional):''' Allows an override of the language used to present the user interface. A list of available languages codes is available from the [http://api.creativecommons.org/docs/readme_dev.html#locales API].
</div>

=== Invoking the remote license engine from your application ===

Once you have figured out the appropriate variables that will be fed into and out of the remote license engine, you need to invoke it from your website or application.

There are a few basic ways to accomplish this task:

* Popup window launched from your website
* Redirect from your website to license engine
* IFRAME embedded within your website
* Launched via HTML control within your desktop application

=== Popup window launched from your website ===

The most popular method of invoking the remote license engine is via a popup window. A user clicks something on a page that launches a small window containing the questions. After answering them, users proceed, the window closes, and the original page is updated to reflect their choice. Sites using this method will usually change a hidden form variable dynamically (using javascript) when the user finishes the license selection process.

Screenshot of popup below. Implementation example: [[Movable Type]].

[[Image:Choose_license_popup.png]]

=== Redirect from your website to license page ===

This option does not use popup windows of any kind and instead you leave the site you originated from, pick your license, then return to the site with your selection info for the site to decifer. Sites using this method would need to parse the URL variables within the return URL.

=== IFRAME embedded within your website ===

For those that do not want to use popup windows, have an audience using version 5.0 web browsers and up, and would like to keep the license selection within their application, an IFRAME can be used much like the popup. Sites using this method would embed the question form into their page, and upon completion, pass variables between the IFRAME and surrounding page.

=== Launched via HTML control within your desktop application ===

For desktop applications this method would essentially mimic the popup window code, but instead use a native HTML control within your application. On Windows, visual basic and visual C++ applications have access to an Internet Explorer HTML control that can be launched from within your application. For Mac programmers, OS X offers webcore controls that use Safari as a native browser environment from within your application.

== Part 2: Processing and Storage of license information ==

Once users of your website and application have the ability to select a license, the next step is processing the results of their selection. As mentioned in the previous section, the exit_url is the place on your server that users will return to. Once loaded, the data in the URL will need to be parsed. A exit URL result is shown below:

http://example.com/return.cgi?license_url=http://creativecommons.org/licenses/by-nc/2.0/&license_name=Attribution-NonCommercial&license_button=http://creativecommons.org/images/public/somerights20.gif&deed_url=http://creativecommons.org/licenses/by-nc/2.0/

Depending on your web application's server technology, you'll have to parse data from the URL as needed. From the above url, the following data points can be found:

<div class="code">
'''license_url:''' http://creativecommons.org/licenses/by-nc/2.0/

'''license_name:''' Attribution-NonCommercial

'''license_button:''' http://creativecommons.org/images/public/somerights20.gif

'''deed_url:''' http://creativecommons.org/licenses/by-nc/2.0/
</div>

If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and [http://www.rentittoday.com/storage-units-rentals storage options].

Version 3

2012-07-16T09:29:16Z

BurnsideRinehart:

= 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 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 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 CC BY-SA. The Free Art License [http://artlibre.org/licence/lal/en/] and the [http://www.planetsofts.com 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 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]]

Developers

2012-07-16T09:10:10Z

BurnsideRinehart:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Developer Community!</strong> The CC Developer Community is the place to find all about the various software and technical projects that happen within Creative Commons, and the larger CC community. All of the projects developed at Creative Commons are open source [http://www.planetsofts.com software], and just like most open source projects, outside involvement is key to its success. Be sure to [[Special:Userlogin|create a wiki account]] [http://wiki.creativecommons.org/Special:OpenIDLogin login with OpenID] so you can add to this wiki and help it grow.
<br />
There are many ways of interacting with the CC Developer Community, pick your point of entry below:
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
=== Integrate CC license data into applications ===
[[Integrate|Integrating CC license data]] into desktop or web-based applications provides users huge benefits: they get to decide how their work is licensed from the start.
* I want to do this for '''[[Desktop Integration|desktop application]]'''
* I want to do this for '''[[Web Integration|web applications]]'''

=== Translate ===
There are many opportunities to help the Creative Commons community with translations. Check out the [[Translate]] page for an overview.

=== Join the Discussion ===
The Developer Community is more than the sum of software written, it is also the conversations that the community has; what is important, what to do next, how to improve the old.

* '''[[Mailing Lists|Mailing Lists]]'''
** [http://lists.ibiblio.org/mailman/listinfo/cc-devel cc-devel] is the primary developer mailing list.
* '''[[IRC]]'''
** #cc on the Freenode IRC network.
* '''[http://code.creativecommons.org/issues/ Issue Tracking]'''
** See what we're working on.
* '''[http://labs.creativecommons.org Blog]'''
** CC Labs, our technology blog.
}}
{{PageColumn|
=== Participate in Developer Challenges ===
[[Developer Challenges|Creative Commons Developer Challenges]] are a great way of joining the community and producing software that others have already expressed interest in using!

==== Developer Challenges currently open (first 15): ====
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]]
| ?Related To
| limit=15
}}

}}</div>
<br clear="all"/>

{{Translations
| articles = Pt:Programadores, Ru:Разработчикам, Vi:Phát Triển Viên
}}

[[Category:Developer]]

__NOTOC__

Developers

2012-07-16T09:09:26Z

BurnsideRinehart:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Developer Community!</strong> The CC Developer Community is the place to find all about the various software and technical projects that happen within Creative Commons, and the larger CC community. All of the projects developed at Creative Commons are open source [http://www.planetsofts.com software], and just like most open source projects, outside involvement is key to its success. Be sure to [[Special:Userlogin] create a wiki account] [http://wiki.creativecommons.org/Special:OpenIDLogin login with OpenID] so you can add to this wiki and help it grow.
<br />
There are many ways of interacting with the CC Developer Community, pick your point of entry below:
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
=== Integrate CC license data into applications ===
[[Integrate|Integrating CC license data]] into desktop or web-based applications provides users huge benefits: they get to decide how their work is licensed from the start.
* I want to do this for '''[[Desktop Integration|desktop application]]'''
* I want to do this for '''[[Web Integration|web applications]]'''

=== Translate ===
There are many opportunities to help the Creative Commons community with translations. Check out the [[Translate]] page for an overview.

=== Join the Discussion ===
The Developer Community is more than the sum of software written, it is also the conversations that the community has; what is important, what to do next, how to improve the old.

* '''[[Mailing Lists|Mailing Lists]]'''
** [http://lists.ibiblio.org/mailman/listinfo/cc-devel cc-devel] is the primary developer mailing list.
* '''[[IRC]]'''
** #cc on the Freenode IRC network.
* '''[http://code.creativecommons.org/issues/ Issue Tracking]'''
** See what we're working on.
* '''[http://labs.creativecommons.org Blog]'''
** CC Labs, our technology blog.
}}
{{PageColumn|
=== Participate in Developer Challenges ===
[[Developer Challenges|Creative Commons Developer Challenges]] are a great way of joining the community and producing software that others have already expressed interest in using!

==== Developer Challenges currently open (first 15): ====
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]]
| ?Related To
| limit=15
}}

}}</div>
<br clear="all"/>

{{Translations
| articles = Pt:Programadores, Ru:Разработчикам, Vi:Phát Triển Viên
}}

[[Category:Developer]]

__NOTOC__

Developers

2012-07-16T09:08:31Z

BurnsideRinehart:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Developer Community!</strong> The CC Developer Community is the place to find all about the various software and technical projects that happen within Creative Commons, and the larger CC community. All of the projects developed at Creative Commons are open source [http://www.planetsofts.com software], and just like most open source projects, outside involvement is key to its success. Be sure to [[Special:Userlogin create a wiki account]] [http://wiki.creativecommons.org/Special:OpenIDLogin login with OpenID] so you can add to this wiki and help it grow.
<br />
There are many ways of interacting with the CC Developer Community, pick your point of entry below:
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
=== Integrate CC license data into applications ===
[[Integrate|Integrating CC license data]] into desktop or web-based applications provides users huge benefits: they get to decide how their work is licensed from the start.
* I want to do this for '''[[Desktop Integration|desktop application]]'''
* I want to do this for '''[[Web Integration|web applications]]'''

=== Translate ===
There are many opportunities to help the Creative Commons community with translations. Check out the [[Translate]] page for an overview.

=== Join the Discussion ===
The Developer Community is more than the sum of software written, it is also the conversations that the community has; what is important, what to do next, how to improve the old.

* '''[[Mailing Lists|Mailing Lists]]'''
** [http://lists.ibiblio.org/mailman/listinfo/cc-devel cc-devel] is the primary developer mailing list.
* '''[[IRC]]'''
** #cc on the Freenode IRC network.
* '''[http://code.creativecommons.org/issues/ Issue Tracking]'''
** See what we're working on.
* '''[http://labs.creativecommons.org Blog]'''
** CC Labs, our technology blog.
}}
{{PageColumn|
=== Participate in Developer Challenges ===
[[Developer Challenges|Creative Commons Developer Challenges]] are a great way of joining the community and producing software that others have already expressed interest in using!

==== Developer Challenges currently open (first 15): ====
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]]
| ?Related To
| limit=15
}}

}}</div>
<br clear="all"/>

{{Translations
| articles = Pt:Programadores, Ru:Разработчикам, Vi:Phát Triển Viên
}}

[[Category:Developer]]

__NOTOC__

Developers

2012-07-16T09:06:29Z

BurnsideRinehart:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Developer Community!</strong> The CC Developer Community is the place to find all about the various software and technical projects that happen within Creative Commons, and the larger CC community. All of the projects developed at Creative Commons are open source [http://www.planetsofts.com software], and just like most open source projects, outside involvement is key to its success. Be sure to [[Special:Userlogin|create a wiki account] [http://wiki.creativecommons.org/Special:OpenIDLogin login with OpenID] so you can add to this wiki and help it grow.
<br />
There are many ways of interacting with the CC Developer Community, pick your point of entry below:
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
=== Integrate CC license data into applications ===
[[Integrate|Integrating CC license data]] into desktop or web-based applications provides users huge benefits: they get to decide how their work is licensed from the start.
* I want to do this for '''[[Desktop Integration|desktop application]]'''
* I want to do this for '''[[Web Integration|web applications]]'''

=== Translate ===
There are many opportunities to help the Creative Commons community with translations. Check out the [[Translate]] page for an overview.

=== Join the Discussion ===
The Developer Community is more than the sum of software written, it is also the conversations that the community has; what is important, what to do next, how to improve the old.

* '''[[Mailing Lists|Mailing Lists]]'''
** [http://lists.ibiblio.org/mailman/listinfo/cc-devel cc-devel] is the primary developer mailing list.
* '''[[IRC]]'''
** #cc on the Freenode IRC network.
* '''[http://code.creativecommons.org/issues/ Issue Tracking]'''
** See what we're working on.
* '''[http://labs.creativecommons.org Blog]'''
** CC Labs, our technology blog.
}}
{{PageColumn|
=== Participate in Developer Challenges ===
[[Developer Challenges|Creative Commons Developer Challenges]] are a great way of joining the community and producing software that others have already expressed interest in using!

==== Developer Challenges currently open (first 15): ====
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]]
| ?Related To
| limit=15
}}

}}</div>
<br clear="all"/>

{{Translations
| articles = Pt:Programadores, Ru:Разработчикам, Vi:Phát Triển Viên
}}

[[Category:Developer]]

__NOTOC__