Creative Commons - User contributions [en]

Talk:CC-related legal scholarship and references

2014-12-19T18:01:17Z

Mike Linksvayer: /* related article */ new section

== related article ==

There are probably some legal articles appropriate for this page in the sporadically-maintained [[Scholarship and critique regarding Creative Commons]]. [[User:Mike Linksvayer|Mike Linksvayer]] ([[User talk:Mike Linksvayer|talk]]) 18:01, 19 December 2014 (UTC)

Case Law

2014-11-19T16:59:47Z

Mike Linksvayer: rv spam

The Case Law database is a database of court decisions that discuss or are directly relevant to Creative Commons licenses. The decisions can come from any jurisdiction around the world. It is a database of decisions, not cases. For cases taking place across multiple courts, add separate pages for each decision.

<h3 style="text-align:center;">[[:Special:FormEdit/Case_Law|Add Decision]]</h3>

==Cases==
{{#ask: [[Category:Case Law]]
| ?Case_description
| format=table
| headers=hide
}}

Cchost/Developers

2014-09-30T03:20:05Z

Mike Linksvayer: update source repo link

[[Category:ccHost]]
[[Category:ccMixter]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
{{cchost_head}}
{{lowercase}}
=External APIs=
[[cchost/concepts/APIs|APIs]]

= Source Code =
* [https://github.com/cc-archive/cchost Browsable Source Code (Anonymous)]

**Specifically for ccHost:
*** Log in as administrator on your ccHost installation
*** '''Then''' do your svn update
*** Browse to <nowiki>http://your_installation?update=1</nowiki>

=When to make changes to ccHost core=
Never.
==Seriously==
Never.
==But I have changes to share==
Oh, that's different. Definitely [[HOWTO_Patch|submit a patch]]! But before going too far down this road you definitely want to hop on the [https://lists.sourceforge.net/mailman/listinfo/cctools-cchost dev mailing list]. If you are shy ask to speak with Victor or Jon in private.

= Bugs and Feature Requests =
* [https://sourceforge.net/tracker/?atid=559966&group_id=80503&func=browse Report Bugs]
* [https://sourceforge.net/tracker/?group_id=80503&atid=559969 Request Features]

''Make sure to use the 'ccHost' category when filing bugs. Also, please use a real email so that we can followup on any bugs posted. Be descriptive when posting and commenting on bugs (every bit counts).''

=Coding in ccHost=
==ccHost's Model for a 'Module'==
There is no formalized higher level model for a 'module' or 'plugin' in ccHost. The model is the same as PHP: a source file. All files with a .PHP extension that reside in the '''<local_files>/lib''' directory will be parsed and executed for every page request to a ccHost installation. Where <local_files> is the name of the directory the administrator specified during installation as to where site customizations reside (also editable from '''admin/paths''')

Because of the automatic loading you should be aware of some performance and timing considerations.

===Keep Per Page Execution at a Minimum===
You should have no significant code that executes outside of functions. You module will be loaded on each every page (and AJAX) request so (other than registering for ccHost events) you should keep all your code in functions that get called in response to ccHost events.

<nowiki><?</nowiki>
for( $i = 0; $i < 52; $i++ ) { $deck[] = rand() % 52; } '''// this is bad'''
<nowiki>?></nowiki>

Instead of the above, you would do:

<nowiki><?</nowiki>
function start_my_shuffle()
{
global $deck;

for( $i = 0; $i < 52; $i++ ) { $deck[] = rand() % 52; }
}

// no we only do the shuffle once after ever upload
CCEvents::AddHandler( CC_EVENT_UPLOAD_DONE, 'start_my_shuffle' );
<nowiki>?></nowiki>

===Wait for Initialization===
It is rare that you will want to do anything before the environment is fully initialized and we know who the currently logged in user really is.

If you really need to do some calculation on each page hit, register for the 'APP_INIT' event and perform it then:

<nowiki><?</nowiki>

CCEvents::AddHandler( CC_EVENT_APP_INIT, 'my_app_init_func' );

function my_app_init_func()
{
global $CC_GLOBALS;

if( CCUser::IsLoggedIn() )
{
$CC_GLOBALS['welcome-message'] = 'Hello ' . CCUser::CurrentUserName() . '!';
}
}

<nowiki>?></nowiki>

===Keep Per Page Code Size at a Minimum===
If you plan on having a lot of extensibility code it would be wise for performance reasons to consider what ''has'' to go into the .PHP files and what can be put into other files (e.g. '.inc') and loaded on demand.

The typical way to handle this is to put the event registrations in the PHP module and the code in a INC file. You can specify a script module in the third parameter of '''AddHandler'''. Assuming this file is '''<local_files>/lib/my_event_hooks.php'''

<nowiki><?</nowiki>
CCEvents::AddHandler( CC_EVENT_APP_INIT, 'my_app_init_func', dir(__FILE__) . '/my_code.inc' );
<nowiki>?></nowiki>

Then you create '''<local_files>/lib/my_code.inc''':

<nowiki><?</nowiki>

function my_app_init_func()
{
global $CC_GLOBALS;

if( CCUser::IsLoggedIn() )
{
$CC_GLOBALS['my-welcome-message'] = 'Hello ' . CCUser::CurrentUserName() . '!';
}
}

<nowiki>?></nowiki>

=Useful Reading=

These pages have important developer information and code samples:

*[[cchost/guide/Customize|Customize]] <--- '''Always check here first'''
*[[cchost/guide/Troubleshooting#Variable_Dumps|Variable dumps]]
*[[cchost/Static HTML Pages|Static Pages]]
*[[cchost/admin/config customize|Configuration files]]
*[[cchost/Custom Query Templates|Custom Query Templates]]
*[[Cchost/Developers/Victor's_Dev_Setup|Victor's Dev Setup]]

These pages are developer specific:

*[[cchost/developer/Common_HOWTO's|Common developer HOWTO's]]
*[[cchost/developer/concepts/Working With Data|Working with data]]
*[[cchost/developer/Hooking Page Render|Hooking Page Render]]
*[[cchost/developer/Hooking the User Profile|Hooking the User Profile]]
==Tutorials==
*[[cchost/developer/tutorial/Hooking File Events|Tutorial: Hooking File Events]]
*[[Cchost/developer/tutorial/Replacing the File Verifier|Tutorial: Replacing the File Verifier]]
*[[Cchost/developer/tutorial/Ultimate Template|Tutorial: Ultimate Template]]
*[[Cchost/developer/tutorial/Remix_Me|Tutorial: ccMixter's "Remix Me" Feature]] Covers custom templates, embedded custom dataview, 'publicize', popup window, nested templates, feature page
*[[cchost/developer/tutorial/Featured_Playlist|Tutorial: ccMixter's Featured Playlist]] Covers content topics, database insert, command menus, event handling.

CcHost

2014-09-30T03:17:40Z

Mike Linksvayer: update source repo link

[[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 ===

https://github.com/cc-archive/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[http://courtreportingagency.com ,] 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

----

= 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]

GPL compatibility use cases

2014-05-02T21:10:21Z

Mike Linksvayer: /* Sharing computer code between GPL software and CC-BY-SA communities */ hardware

If any form of GPL-compatibility is to be pursued in [[4.0]] -- see [[4.0/ShareAlike]] -- use cases that would benefit from such need to be explicated.

As raw material, copied below is an email to cc-licenses concerning game-related use cases. Please be bold -- edit and give structure -- add relevant links, etc.

* Message to cc-licenses about game use cases http://lists.ibiblio.org/pipermail/cc-licenses/2011-December/006441.html

== Raw material ==

GPL-licenced games (game code) with CC-BY-SA game content are a bit of a
problem right now. A "functional" CC-BY-SA game content might be
incompatible with GPL. Below is my [lousy] attempt at division of game
content into functional and non-functional:

Non-functional game content:
Meshes, textures, sounds, animations, ... used only to visually/...
represent objects in a virtual world don't really have a function (at least
most of the time). They could be replaced with [nearly] no effect on
gameplay.

BUT even those types of content can be used in a functional way.
E.g. in a game with "positive" and "negative" targets, those target types
could be represented in a clearly different way (colour, sound, ...) so
game mechanics would require player to perform visual pattern matching
which could be done from a long distance and then player would select
positive targets.

Let's change visual appearance of "positive" and "negative" targets to make
them look identically and let's modify sounds so that they are very very
quiet. These changes of game content will significantly change game
mechanics as player will have to navigate between targets at a close range
in order to determine which are "positive" and which are "negative" and if
there would be some danger for a player due to proximity then game
mechanics would differ even more from "original" game mechanics.
Let's have identical targets and then use 2 animated textures (2 frames,
"positive" texture: green frame, then red frame; "negative" texture: red
frame, then green frame) and run those animations at a rate of say 1 frame
per 5 seconds (sorry for complexity of this example). Then the player will
have to keep track of colour changes and count in head when there are no
targets around as a reference.

Through some changes of seemingly non-interactive/non-functional elements
game mechanics can be changed significantly. With a "weak" code-driven game
mechanics, content-driven game mechanics could be more
important/"functional".

Functional game content:

Virtual world (a map/level/...) has some function as it, along with game
mechanics, defines what the gameplay will be like. If a map would be
replaced with another map the gameplay would be different. Player choices
are dependent upon a combination/interaction_of game mechanics and virtual
world.

In physics-driven games function could be even more prominent. Objects
could be placed and connected in a virtual world in a way that new
mechanics could emerge. Here a different object mesh (a dedicated physical
meshes of or physical mesh same as a visual mesh) would alter this emergent
mechanics. And of course even if objects would be fixed in place, the
player moving in the world could be getting a very different experience. A
different mesh could turn an object into a trap or could be a bridge to
some location.

Objects like switches linked to gates, elevators, ... would also have a
pretty clear functional role forcing a player to perform sequences of
action much like a gameplay mechanics.

And in some games textures, sounds, animations, ... could also be used to
drive gameplay. For example a texture/image could be used as a terrain
height map and another texture/image could be used to determine (e.g. by
colour) where there is water, where there is deadly lava, ...

Those are just some quick (and a bit ugly) examples of functionality of
game content and they are in no way exhaustive. A lot better examples could
surely be constructed. Sorry for turning this post into a mess of random
ideas. My point is that it is better (for game developers) to have an
ability to create and enhance a content under CC-BY-SA 4.0 so that it could
be used with other CC-BY-SA 4.0 media on the net (film, music, fanart, ...)
and at the same time have an ability to "export" content to GPL making it
100% compatible with game engine/code. And there are some games which are
already using GPL-licenced content which means that they can't mix it with
CC-BY-SA content.

Another problem is if game content is mixed with game scripts (a code used
to control game mechanics at a high level) if scripts use functions
provided by game engine/code ("standard library" functions). If there is no
exception added to GPL and developers can't get all contributors to agree
on licencing under GPL with an exception then scripts licenced under
CC-BY-SA can't be used (this problem would probably impact only those
people who are less technical / less interested in licencing issues and
have simple chosen CC-BY-SA because they use it for content as well and are
not aware about consequences (a problems will be biggest when there will
later be many contributors and then it could be hard to make them all
licence under another licence)).

And of course version number could be a problem. New versions of CC-BY-SA
and GPL are not being released at the same time (at least right now). A lot
of software relies on GPL version 3 "or later" and if a content under
CC-BY-SA 4.0 would be "exported" to GPL version 3 (without "or later"),
then if there would be GPL v4 released then developers would be restricted
by what CC-BY-SA 4.0 allows (could not switch to latest GPL). Even if newer
CC-BY-SA version would add support of GPLv4 then if developers would
"export" CC-BY-SA 4.0 to GPLv3 (without "or later") and would be modifying
content, they would need an approval of all contributors in order to be
able to licence under GPLv4 (which could be problematic). And if they would
be improving content under CC-BY-SA instead, they would have to hope that
there will be a new version of CC-BY-SA released which will be compatible
in order to be able to use latest version of GPL. If I understand correctly
an "or later" clause is not part of a GPL licence text (unlike CC-BY-SA?
(at 4.b.)) but is rather written in a README file while a regular GPL text
is in LICENCE file. Would it be legal to make CC-BY-SA 4.0 to be one-way
"interoperable" with GPL version 3 "or later" instead of just GPL version 3?

There is also something not related to stuff above but still related to
games and interactive multimedia. If I understand correctly if a work is
licenced under CC-BY-SA and is presented somewhere (in a open show) then a
person/... who is presenting a work (author or not) does not have release
that work (unlike GPL-licenced work (if publicly available)) but any person
can still record a work (e.g. using a camera) and it will be legal and
can't be restricted by DRM?

If so then this only really help works which are non-interactive / which
are "linear" (a single "frame" (image) or a non-interactive "stream" (film,
sounds, music)) BUT it does not really help much if work is
interactive/"non-linear" (games, interactive multimedia) because during a
game/... only portion of content could be recorded and in a "hard to
reverse" way (a recording of a game can't be released as game content. game
content must be rebuild and only a portion of it will be recorder during a
course of game). This could be a problem when someone releases a work under
CC-BY-SA, then someone transforms it and puts it on a system to which there
is no direct access so that game content based upon some Else's content
cannot be extracted (in a directly usable form).

Recently there have been a "gaming console" developed where "user
interaction" is sent to server(s) and a recording of a games (in a form of
a film) is streamed back to player and is displayed so it is technically
impossible to get content out in a directly-usable form.

It is a problem at least to me personally. If someone would release
modification in that way I would have to play to be able to use a service
(which would be fine), then record a portion of a game presented to me and
then convert it back in order to be able to create some new game content
based on it while that other person could simply add some more content and
it would be restricted again.

I don't think that such system (where game is streamed as a film) could be
considered to be a DRM (or "effective technological measures" as it is
written in CC-BY-SA) because it is how a device is supposed to work so I
personally think CC-BY-SA does not offer enough "protection" for
"non-linear content" creators.

To some extent a AGPL version 3 (Affero GPL version 3) licence offers some
protection in such situation (for code) as it requires that an
AGPL-licenced code running on a remote machine / on a server side must be
disclosed while GPL version 3 code does not have to be and AGPLv3 is
compatible with GPLv3.

I'm not exactly sure what clauses in CC-BY-SA (and other licences?) could
be used for this (and I'm quite sure that some/many people will not want
it) but current state of CC-BY-SA (or my misunderstanding of it) is pretty
much the reason why I am considering releasing (in future) my game content
under a custom licence.

If some measures regarding this matter would be implemented in CC-BY-SA
(and other CC licences) and if there would still be a plan to have
CC-BY-SA-4.0 "exportable" to GPL then it would only makes sense if to have
it "exportable" to AGPL (version 3 or later) rather than GPL because GPL
would be "removing" requirement of disclosure (when everything would be
happening remotely).

Even if I would have my game engine/code licenced under AGPLv3+ someone
could still re-implement it or use another engine and use my CC-BY-SA in a
way I have described above and currently only a custom licence (or AGPLv3+)
would be a good solution for me.

== More raw material ==

Posted in cc-licenses: http://lists.ibiblio.org/pipermail/cc-licenses/2011-December/006523.html

For me personally it is a huge problem that cc by-sa and GPL cannot be
used together in a combined work. That’s why I gathered some use-cases
for that.

=== 1. Using already existing cultural works under GPL with content under cc by-sa (my personal use-case) ===

There already is quite a lot of GPL and cc by-sa content which cannot
be used together for purely legal reasons.

There is Battle for Wesnoth¹ with GPL licensed text and artwork, and
Ryzoom² with cc by-sa assets.

And (my case) there is my own free roleplaying game³ under GPL which
utilizes Wesnoth graphics but cannot use those from Ryzoom, even
though the Ryzoom folks freed their graphics with the intent of
allowing others to use them.

¹: http://wesnoth.org

²: http://media.ryzom.com/

³: http://1w6.org

=== 2. Using Python scripts in blender ===

This already came up, but I want to add some legal stuff.

In GPLv3, something is considered a derivative work, if there is
“intimate data communication”. In Python importing a GPL module always
makes your code a derivative work, so you have to use the GPL,
too. When you use a python script in blender and you adapt it to the
specifics of your model - for example the nature of your rig - the
model and the code have intimate data communication, so it is very
likely that you have to licence your model under a GPL compatible
license.¹

Thought to the end, this could mean, that currently you are not allowed
to use cc by-sa with rigged blender models, when you use any kind of
non-generic scripting.

¹: Blender Python-scripts seem to be GPL without exception, so plugins
have to be GPL, too. It would be nice if someone versed in legalities
could check that:

https://svn.blender.org/svnroot/bf-blender/trunk/blender/source/blender/python/

=== 3. Using content from free software in artworks ===

Currently you cannot make cc by-sa licensed artwork which uses GPL
works - and be it only a snippet of code.

If cc by-sa allowed usage with GPL code, then the resulting work would
have to be GPL, but the new assets could be licensed under cc by-sa.

=== 4. Not restricting the design of programs with legal details ===

Many people argue, that you can just separate artwork from the code.

This means, however, that the licensing restricts the structure of the
program. For example blender would have to disallow scripts embedded
in .blend files, if the model is not under a GPL-compatible
license. And embedded scripts are too convenient to lose them due to
legal details.

Another example for this problem becomes visible in the simplest of games: The text adventures in scripting languages. An example is the [https://bitbucket.org/ArneBab/textrpg/src/463a94237518/branching_story.py branching story in the TextRPG]. Since the code imports GPL libraries, it has to be licensed under GPL. If the text were under cc by-sa, then it would have to be put into a separate file and the code would have to get a full templating system, which makes it impossible to just use the capabilities of the scripting language and the program state in the text (otherwise it would have intimate data communication again). Even [http://www.lisperati.com/casting-spels-emacs/html/casting-spels-emacs-1.html casting spels in lisp] would break the law, if it used cc by-sa licensed text and GPL licensed code. Just exchanging the text for cc by-sa text would not be possible. And if someone wanted to refactor it into a full library, it would still be restricted to only one community: either cc by-sa or GPL - or GFDL for that matter.

(no time to write more - I hope these help as illustration)

Best wishes,
Arne

PS: Even though the Free Software Foundation deems art as
non-functional, I strongly disagree. Art is just as functional as
code, it just works through pathways which are harder to assess. Great
gameplay can crumble when you take away the music, and when the
gameplay is built around a narrative, it often needs the narrative to
realize its effect on the player. As a vicious example: What would
Mortal Combat be without someone shouting “Finish him”?

Art is functional. It just not necessarily runs on a computer, but on
our minds.

=== Sharing computer code between GPL software and CC-BY-SA communities ===
Several online communities, such as Wikipedia and Stack Overflow, have CC-BY-SA-licensed text. Many articles/posts on those sites contain computer code. GPL compatibility would allow sharing between these sites and GPL-licensed software. For example, code from Stack Overflow could be directly incorporated into open-source software, and GPL code could be used as examples on those sites.

===GPL and CC-BY-SA each used frequently for hardware design===

According to http://www.oshwa.org/oshw-community-survey-2013/#section5 of those surveyed 37.5% have released designs under CC-BY-SA and 28% under GPL. Compatibility would allow combinations across those two pools.

User:Timothy Vollmer

2013-12-11T03:51:37Z

Mike Linksvayer: Reverted edits by Dongdong li (talk) to last revision by Tvol

[[Category:Creative Commons Staff]]

== About ==
Timothy Vollmer is http://creativecommons.org/about/people/#timothyvollmer

CC REL

2013-12-11T03:51:22Z

Mike Linksvayer: Reverted edits by Dongdong li (talk) to last revision by Hamilton Abreu

{{Infobox|
'''Creative Commons Rights Expression Language (CC REL)''' is a specification describing how license information may be described using RDF and how license information may be attached to works.
|}}

CC REL is described in ''[[Media:Ccrel-1.0.pdf|CC REL: The Creative Commons Rights Expression Language]]'' (pdf), published March 3, 2008. An overview of the vocabulary is available with [http://creativecommons.org/ns# the namespace description].

CC REL metadata, as encoded using [[RDFa]] or [[XMP]], may be [[Marking Works Technical|embedded]] in a variety of [[:Category:Filetype|filetypes]]. Additional confidence may be added to embedded metadata through the use of [[WebStatement|web statement]].

We have also begun to explore extending CC REL for use by digital copyright registries. See [[CC Network Development]]'s [http://code.creativecommons.org/doc/commoner/metadata.html metadata documentation].

'''[http://labs.creativecommons.org/2011/ccrel-guide/ CC REL by Example]''' provides examples of many web deployment scenarios with thorough explanations and is the best place to start if you want a HOWTO or to understand through examples which you can copy and experiment with.

== Presentations ==

* A slightly updated version of the CC REL paper is chapter 10 of [http://www.communia-association.org/wp-content/uploads/the_digital_public_domain.pdf The Digital Public Domain: Foundations for an Open Culture] (pdf), 2012
* [[Creative Commons Technology Summit 2009-06-26]], multiple
* [[Creative Commons Technology Summit 2008-12-12]], multiple
* [[An Introduction to CC REL and The Use of Semantic Technology at Creative Commons]]
* [[CC REL update]]
* [[Creative Commons Technology Summit 2008-06-18]], multiple
* [[Deploying the Semantic Web with ccREL and RDFa]]
* [[COMMUNIA January 2008]]

== Examples ==

=== Simple ===
<pre>
the study by VOLKAN TEMEL is licensed under a

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons
Attribution Non-Commercial 3.0 License</a>.
Permissions beyond the scope of this license may be available at
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions"
href="http://www.hindawi.com/journal/arp/

=== Advanced ===
<pre>
<span xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/terms/">

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

is licensed under a

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

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

</span>
</pre>

{{Challenge Enabled}}

{{Translations
| articles=Pt:CC REL, Ru:CC REL
}}

[[Category:Metadata]]
[[Category:Developer]]

License Versions

2013-12-11T03:51:11Z

Mike Linksvayer: Reverted edits by Dongdong li (talk) to last revision by Mike Linksvayer

__NOTOC__

This page identifies the principal improvements to the Creative Commons license suite since the publication of the first licenses (version 1.0) in December 2002, through the current [[Version 4|version 4.0]], published November 2013. It also highlights important similarities and differences among the major license versions. For more information on using CC tools or works offered under Creative Commons licenses, consult the [[Frequently_Asked_Questions|Frequently Asked Questions]] page. For a further historical perspective, you are invited to review deprecated CC legal tools identified on the [http://creativecommons.org/retiredlicenses retired legal tools page].

Please note that the summaries below may not reflect all changes between license versions or fully or accurately describe the differences between them. CC cannot provide legal advice, and what follows is not legal advice. What follows below is a general description of differences and similarities between the license versions, for general informational purposes only. Consult your own attorney if you are in need of legal advice.

==License Versioning History==
The chart below presents the major license versions, launch dates, and blog posts announcing major public comment periods, the launch of each license suite, and improvements. It does not reference the unfinished version 3.x ([[Version_3.01|3.01]] or [[Version_3.5|3.5]]) licenses, which did not include active public consultation and were never published. Version 4.0 is the premier, recommended Creative Commons license suite.

{| class="wikitable"
|-
! License version <ref name="versionsnote">Note that CC released a version 2.1 suite for jurisdictions like Spain, Australia, and Japan, whose localized ports of the 2.0 suite contained errors.</ref>
! Release date
! Calls for public comment
! Launch announcement
! Explanation of changes from prior version
|-
| 1.0
| 2002 Dec 16
|
| [http://creativecommons.org/press-releases/entry/3476 Creative Commons Unveils Machine-Readable Copyright Licenses]
|
|-
| 2.0
| 2004 May 25
| [http://creativecommons.org/weblog/entry/3981 Versioning -- Public Review Begins]
| [http://creativecommons.org/weblog/entry/4216 Announcing (and explaining) our new 2.0 licenses]
| [http://creativecommons.org/weblog/entry/4216 Announcing (and explaining) our new 2.0 licenses]
|-
| 2.5
| 2005 June
| [http://creativecommons.org/weblog/entry/5447 Tweaking CC's Standard Attribution Language -- An Invitation to Comment]
|
| [http://creativecommons.org/weblog/entry/5457 Comments Period Drawing to a close for Draft License Version 2.5]
|-
| 3.0
| 2007 Feb 23
| [http://creativecommons.org/weblog/entry/6017 Version 3.0 -- Public Discussion Launched]
| [http://creativecommons.org/weblog/entry/7249 Version 3.0 Launched]
| [[Version_3|Creative Commons Version 3.0 Licenses -- A Brief Explanation]]
|-
| 4.0
| 2013 Nov 25
|
* Initial announcement: [http://creativecommons.org/weblog/entry/29639 Copyright Experts Discuss CC License Version 4.0 at the Global Summit]
* Beginning of public discussion: [https://creativecommons.org/weblog/entry/30676 Version 4.0 – Public Discussion Launches]
* Draft 1: [https://creativecommons.org/weblog/entry/32157 Version 4.0 – License Draft Ready for Public Comment!]
* Draft 2: [https://creativecommons.org/weblog/entry/33632 Draft 2 of 4.0 Ready for Public Comment]
* Draft 3: [https://creativecommons.org/weblog/entry/36713 4.0 draft 3 published – final comment period underway]
* Draft 4: [https://creativecommons.org/weblog/entry/39587 4.0 draft 4 ready for comment — final consultation before publication]
| [https://creativecommons.org/weblog/entry/40768 CC’s Next Generation Licenses — Welcome Version 4.0!]
|
* [https://creativecommons.org/Version4 What's New in 4.0: Summary]
* [[Version 4|Policy decisions and versioning notes]]
* [[4.0|Creative Commons Version 4.0 wiki pages]]
|}

<references/>

==International License Development Process==

Creative Commons develops, releases, and updates its public copyright licenses (and other legal tools) via an open and inclusive process of engagement with Creative Commons’ global network of attorneys and affiliates, as well as varied communities and constituents. The process culminates in the publication of the preferred, most up-to-date set of CC licenses for use around the world. Creative Commons released its latest version of the licenses in November 2013, the 4.0 international licenses.

The public license development process includes the publication of drafts, formal comment periods, and transparent decision-making. In recognition of its stewardship role, CC has also made public commitments about the development of its ShareAlike licenses: the [[CC_Attribution-ShareAlike_Intent|Statement of Intent for Attribution-ShareAlike licenses]] following the publication of 3.0, and a [[DRAFT ShareAlike Statement of Intent|continuation of that statement]] to be finalized following the publication of version 4.0.

While each version of licenses is drafted to conform with copyright law, the version 4.0 license suite includes significant improvements to ensure the licenses operate well internationally. Through extensive consultation with our global network of legal affiliates, the 4.0 international license suite is designed for use in jurisdictions around the world, without the need for localization beyond translation. CC has an established a policy for [[Legal_Code_Translation_Policy|official translations of the 4.0 licenses as well as other legal tools]].

Prior to version 4.0, Creative Commons granted permission to legal experts around the world to adapt (or “port”) the licenses where necessary to more fully align the text with the laws of different legal jurisdictions, and to translate the licenses to the local language(s). For the 4.0 suite, every effort has been made to avoid the need to port (though we will support official language translations). CC may consider requests to port the 4.0 suite in 2014, but only where a compelling need is demonstrated. If CC decides to consider requests, in no case will CC grant permission if the basis for doing so is to include a choice of law or if the change presented would otherwise alter the basic operation of the licenses. CC will post more information on the topic of porting in Q2 of 2014.

==License Suite Versions==
The chart below and linked explanations that follow detail some of the improvements and important similarities among Creative Commons license versions. Some of the explanations contain links to further information on the topic.

===General license features===
{| class="wikitable"
|-
! License Suite Version
! 1.0
! 2.0
! 2.5
! 3.0
! 4.0
|-
| style="background-color:yellow;" | '''All international (unported/generic) and ported licenses'''
| style="background-color:yellow;" |
| style="background-color:yellow;" |
| style="background-color:yellow;" |
| style="background-color:yellow;" |
| style="background-color:yellow;" |
|-
| [[#Nomenclature_.28for_unported_licenses.29|Nomenclature (for unported licenses)]]
| Generic license
| Generic license
| Generic license
| International (unported) license
| style="background-color:chartreuse;" | International license
|-
| style="background-color:white;" | '''License scope (beyond copyright)'''
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
|-
| [[#Sui_generis_rights_in_databases|Express permission granted under sui generis database rights]]
| No
| No
| No
| EU ports only
| style="background-color:chartreuse;" | Yes
|-
| [[#Sui_generis_rights_in_databases|License conditions apply to sui generis database rights]]
| No
| Few ports only
| Few ports only
| No
| style="background-color:chartreuse;" | Yes
|-
| [[#Moral_rights_clause_included|Treatment of moral rights]] 
| Not addressed
| Not addressed
| Not addressed
| Varied
| style="background-color:chartreuse;" | Waived/not asserted
|-
| [[#Trademark_and_patent_explicitly_not_licensed|Trademark and patent explicitly reserved]]
| No
| No
| No
| No
| style="background-color:chartreuse;" | Yes
|-
| style="background-color:white;" | '''Other license features'''
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
| style="background-color:dimgray;" |
|-
| [[#Representations_and_warranties_by_licensor_included|Representations and warranties from licensor included]]
| Yes
| No
| No
| No
| style="background-color:chartreuse;" | No
|-
| [[#Licensor_expressly_waives_rights_to_enforce,_and_grants_permission_to_circumvent,_technological_protection_measures|Licensor expressly waives rights to enforce, and grants permission to circumvent, technological protection measures]]
| No
| No
| No
| No
| style="background-color:chartreuse;" | Yes
|-
| [[#Automatic_restoration_of_rights_after_termination_if_license_violations_corrected|Automatic reinstatement after termination if violations corrected]]
| No
| No
| No
| No
| style="background-color:chartreuse;" | Yes, if corrected within 30 days
|-
| [[#Collecting_societies_regimes_addressed|Express reservation of right by collecting society to collect royalty]]
| Not addressed
| Expressly waived where possible
| Expressly waived where possible
| Expressly waived where possible
| style="background-color:chartreuse;" | Expressly waived where possible
|-
| style="background-color:yellow;" | '''Element-specific features'''
| style="background-color:yellow;" |
| style="background-color:yellow;" |
| style="background-color:yellow;" |
| style="background-color:yellow;" |
| style="background-color:yellow;" |
|-
| [[#Compatibility_mechanism_in_BY-SA_licenses|Compatibility mechanism in BY-SA licenses]]
| same license only
| same license, later versions, or ports
| same license, later versions, or ports
| same license, later versions, ports, or CC-designated compatible licenses
| style="background-color:chartreuse;" | same license, later versions, CC-designated compatible licenses (including designated ports)
|-
| [[#Compatibility_mechanism_in_BY-NC-SA_licenses|Compatibility mechanism in BY-NC-SA licenses]]
| No
| No
| No
| No
| style="background-color:chartreuse;" | Yes
|-
| [[#Adapted_material_usable_under_conditions_of_adapter's_license|Adaptations of SA material usable under conditions of adapter's license]]
| Yes (because adapter's license had to be same license)
| No
| No
| No
| style="background-color:chartreuse;" | Yes
|-
| [[#Adaptations_of_NoDerivatives_material_permitted_when_not_shared|Adaptations of NoDerivatives material permitted when not shared]]
| No
| No
| No
| No
| style="background-color:chartreuse;" | Yes
|-
|}

===Attribution-specific elements===

{| class="wikitable"
|-
! License Suite Version
! 1.0
! 2.0
! 2.5
! 3.0
! 4.0
|-
| [[#Attribution_reasonable_to_means.2C_medium.2C_and_context|Attribution reasonable to means, medium, and context]]
| Medium and means, with exceptions
| Medium and means, with exceptions
| Medium and means, with exceptions
| Medium and means, with exceptions
| style="background-color:chartreuse;" | Explicit
|-
| [[#Reasonableness_applies_to_all_attribution_requirements|Reasonableness applies to all attribution requirements]]
| All but license notices
| All but license notices
| All but license notices
| All but license and copyright notices
| style="background-color:chartreuse;" | All
|-
| [[#Credit_to_others_explicit|Licensors may name other attribution parties]]
| Implied
| Implied
| Implied
| Explicit
| style="background-color:chartreuse;" | Explicit
|-
| [[#Requests_for_removal_of_attribution_contemplated|Licensors may request removal of attribution]]
| Adaptations and collections only
| Adaptations and collections only
| Adaptations and collections only
| Adaptations and collections only
| style="background-color:chartreuse;" | Always
|-
| [[#Title_required|Title of work required]]
| Yes
| Yes
| Yes
| Yes
| style="background-color:chartreuse;" | No
|-
| [[#URI_required|URI required]]
| No
| If contains copyright notice or licensing information
| If contains copyright notice or licensing information
| If contains copyright notice or licensing information
| style="background-color:chartreuse;" | Yes
|-
| [[#.22No_endorsement.22_clause_included|"No endorsement" clause included]]
| No
| No
| No
| Yes
| style="background-color:chartreuse;" | Yes
|-
| [[#Modifications_and_adaptations_must_be_indicated|Modifications must be indicated]]
| No
| No
| No
| Yes, but only adaptations
| style="background-color:chartreuse;" | Yes
|}

====Detailed attribution comparison chart====

{{:Attribution comparison}}

===Features remaining unchanged===
* [[#Definition_of_"NonCommercial"|Definition of "NonCommercial"]]
* [[#Attribution_required|Attribution required]] (but anonymity permitted)
* [[#Application_of_effective_technological_measures_by_users_of_CC-licensed_works_prohibited|Prohibition on effective technological measures by users of CC-licensed works]]
* [[#Exceptions_and_limitations_unaffected|Exceptions and limitations unaffected]]
* [[#Effective_for_all_copyrightable_material|License effective for all copyrightable material]]
* [[#Notice_of_warranty_disclaimers_must_be_retained|Notice of warranty disclaimers must be retained]]
* [[#No_sublicensing|No sublicensing]]
* [[#Synching_creates_adaptations|Synching creates adaptations]]
* [[#Licensing_of_collections|Licensing of collections]]
* [[#Licensing_of_BY_and_BY-NC_adaptations|Licensing of BY and BY-NC adaptations]]

==License Features==

====Nomenclature (for international licenses)====
The 4.0 licenses are referred to as "international."

Version 3.0 licenses were referred to as "unported" licenses until 2010, at which point they were re-branded as the "international" licenses. At that point, CC added a global flag to the licenses and deeds and changed the reference in the Chooser (among other things). In the 1.0, 2.0, and 2.5 versions, the international licenses were called the “generic” licenses. The generic licenses were drafted to conform with U.S. copyright law.

Starting with version 3.0, Creative Commons [[Version_3#Further_Internationalization|drafted its core suite of licenses to conform to relevant international treaties and drafting conventions]]. In this sense, version 3.0 and the current 4.0 international license suites are jurisdiction-agnostic: these licenses do not mention and are not drafted against any particular jurisdiction's laws or statutes. They are intended to function without adjustment in all jurisdictions around the world.

===License scope (beyond copyright)===
<span id="Sui_generis_rights_in_databases"></span>
====Sui generis database rights ====

The 4.0 international suite licenses [[Data#Which_components_of_a_database_are_protected_by_sui_generis_database_rights.3F|database rights]] along with copyright. Where the use of a database under a CC license [[Data#How_do_I_know_whether_a_particular_use_of_a_database_is_restricted_by_sui_generis_database_rights.3F|implicates sui generis database rights]], whether or not copyright is implicated, that use is subject to the terms and conditions of the license. If sui generis rights are not implicated—for example, if the use is in a jurisdiction where these rights do not exist, or if the database is not protected by the laws of a jurisdiction where such rights exist— such uses are not regulated by the license if copyright or neighboring rights do not apply. A few early (2.0, 2.5) European jurisdiction license ports also licensed database rights subject to the terms and conditions of the license.

In 3.0, the international (unported) license suite does not mention sui generis rights. However, ported 3.0 licenses for jurisdictions where those rights exist address them according to [[Media:V3_Database_Rights.pdf|CC's 3.0 database rights policy]]. Under this policy, version 3.0 EU jurisdiction ports must license sui generis rights subject to the terms and conditions of the license just like copyright and neighboring rights, but also must waive license restrictions and conditions (attribution, ShareAlike, etc) for uses triggering database rights—so that if the use of a database published under a CC license implicated only database rights but not copyright, the CC license requirements and prohibitions would not apply to that use. The license conditions and restrictions, however, continue to apply to all uses triggering copyright. Other ports and the 3.0 international license are silent on sui generis database rights: databases and data are licensed (i.e., subject to restrictions detailed in the license) to the extent copyrightable, and if data in the database or the database itself are not copyrightable the license restrictions do not apply to those parts (though they still apply to the remainder). Thus, regardless of the CC 3.0 license at play (unported, an EU port, another port), uses that implicate only database rights will not trigger the license conditions, while uses that implicate copyright will.

Neither the international nor the ported licenses that address database rights export the sui generis rights to jurisdictions where such rights are not recognized (the ported licenses accomplish this as well through inclusion of a territoriality limitation). This avoids the [[Data#What_is_the_difference_between_the_Open_Data_Commons_licenses_and_the_CC_4.0_licenses.3F|imposition of restrictions based on sui generis rights via contract]] where those rights are not enforceable or recognized. [[Jurisdiction_Database|You may compare how different jurisdictions implemented this section of the license.]]

====Treatment of moral rights====
In version 4.0, [[Frequently_Asked_Questions#How_do_Creative_Commons_licenses_affect_my_moral_rights.2C_if_at_all.3F|moral rights are waived to the limited extent necessary to exercise the licensed rights]].

While the existence and extent of moral rights differ by jurisdiction, the most consistently present rights are those of attribution and integrity (the right to prevent or halt the prejudicial use of one’s work by another). The 1.0, 2.0, and 2.5 licenses were drafted to conform to U.S. law, and because U.S. law recognizes moral rights in only very limited circumstances, the generic versions of those licenses suites do not address moral rights of authors.

The international licenses began to address moral rights in version 3.0. In version 4.0, [[4.0/Moral_rights|moral rights are waived or not asserted]] to the extent possible under local law, to the limited extent they would otherwise interfere with exercise of the licensed rights. This avoids establishing moral rights through the license where they would not otherwise exist, but recognizes that there are jurisdictions where this limited waiver is not possible. The attribution requirements in Section 3 of the 4.0 licenses may satisfy many jurisdictions' right of attribution; however, they are a requirement of the license regardless of whether moral rights apply to a use.

In the 3.0 license suite, [[Version_3#International_Harmonization_.E2.80.93_Moral_Rights|CC addressed moral rights in the international (unported) licenses]]. CC did not include a waiver of those rights in the international licenses. Instead, the licenses specifically instruct users that they “must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation.” The only exception is where the right to make adaptations would be considered prejudicial to the author's honor and reputation, in which case the licensor waives or agrees not to assert their moral right in order to allow adaptations to be made. The attribution requirement is designed in part to satisfy the right of attribution. In the porting process, some jurisdictions slightly adjusted this provision, with CC’s permission, to specify that moral rights are waived to the extent necessary to effect the license to the degree a waiver is possible under applicable law. [[Jurisdiction_Database|You may compare how different jurisdictions implemented this section of the license]].

====Trademark and patent explicitly not licensed====
In the 4.0 licenses, trademark and patent rights are expressly mentioned as not among the rights licensed.

No CC license version licenses patent and trademark rights along with copyright. These rights are treated separately and are not covered by the license. In 4.0, this was made explicit to avoid confusion. However, in all license versions, [[Frequently_Asked_Questions#Can_I_place_a_trademark_on_a_work_and_offer_the_work_under_a_CC_license_without_also_licensing_or_otherwise_affecting_rights_in_the_trademark.3F_If_so.2C_how.3F|implied licenses may come into play where these rights would interfere with exercise of the rights granted by the CC license]].

===Attribution and marking===
====Attribution reasonable to means, medium, and context====
In 4.0, the manner of attribution is explicitly allowed to be reasonable to the means, medium, and context of how one shares a work.

In the 1.0, 2.0, 2.5, and 3.0 licenses, attribution may be reasonable to the medium or means, and applied to all elements other than [[License_Versions#Detailed_attribution_comparison_chart|certain notices]] where the requirement is firm. In 4.0, this explicit permission applies to the medium, means, and context of use. We believe this to be a clarification rather than a change: attribution reasonable to the means, medium, and context of use should be permissible for works under any CC license. Additionally, the pre-4.0 licenses specified that credit in adaptations and collections should be at least as prominent as credits for other authors; 4.0 is not specific in this regard.

====Reasonableness applies to all attribution requirements====
In 4.0, all attribution requirements may be fulfilled reasonable to the means, medium, and context of the use.

In earlier license versions, compliance reasonable to means and medium of use was not expressly permitted for all elements, as [[License_Versions#Detailed_attribution_comparison_chart|certain notices]] were excluded; however, in 4.0 these are included in the elements that may be fulfilled in a reasonable manner.

====Credit to others explicit====
In 4.0, proper attribution requires credit to designated others where supplied by the licensor.

In the 1.0 and 2.0 licenses, CC licenses contemplated crediting the author only. Versions 2.5 and 3.0 [http://creativecommons.org/weblog/entry/5447 allow licensors to identify another party or organization for attribution] (called an “Attribution Party” in these licenses). This feature was introduced in part to alleviate burdensome or difficult attribution situations, such as when many people contribute to a collaborative effort and agree to be credited as a collective body. In licenses with this feature, licensors may designate another party for attribution purposes—such as a sponsor institute, publishing entity or journal—in addition to or instead of the author. [http://creativecommons.org/weblog/entry/5457 You may review some of the concerns raised when CC proposed this change].

<span id="Requests_for_removal_of_attribution_contemplated"></span>

====Licensors may request removal of attribution====
In the 4.0 licenses, [[Frequently_Asked_Questions#What_can_I_do_if_I_offer_my_material_under_a_Creative_Commons_license_and_I_do_not_like_the_way_someone_uses_it.3F|a user must remove attribution from a work at the creator's request]] to the extent it is reasonably practicable to do so. This is true whether the work is modified or unmodified.

All license versions after version 1.0 require attribution. However, legislation in many countries gives authors the right to control the use of their name in association with their works. Therefore, CC licenses require licensees to remove attribution to the creator at his or her request, where it would otherwise be required to include it. In 2.0, 2.5, and 3.0, credit must be removed from adaptations and collections, to the extent practicable, at the creator’s request. In 4.0, the creator may also request removal of credit from the unmodified work.

<span id="Title_required_for_proper_attribution"></span>
====Title required====
The title is not required for proper attribution in the 4.0 licenses. It is required in all earlier versions.

Beginning in version 1.0, one of the requirements for proper attribution was to include the title of the licensed work; this requirement was kept in versions 2.0, 2.5, and 3.0. In Version 4.0, this requirement was eliminated to increase flexibility and ease of compliance, particularly as many works do not have titles. Users are still encouraged to include titles where supplied.

<span id="URI_required_for_proper_attribution"></span>
====URI required====
For 4.0 licensed materials, a URI is required for proper attribution, if it is reasonably practicable to include.

The version 1.0 licenses contained no URI requirement. In version 2.0, CC introduced the requirement to retain a URI associated with a licensed work for proper attribution if it contains copyright notices or licensing information; this was kept through 2.5 and 3.0. In version 4.0, [[4.0/Attribution_and_marking|CC reconsidered this requirement]]. However, it was retained based on feedback from current and potential adopters that it is important for provenance, branding, and other reasons; a URI associated with the work is required as part of attribution if reasonably practicable to retain, regardless of whether it contains copyright notices or licensing information.

===="No endorsement" clause included====
In version 4.0, [[Frequently_Asked_Questions#Do_I_need_to_be_aware_of_anything_else_when_providing_attribution.3F|the license is clear that it should not be construed as giving permission to suggest the licensor endorses their use]] and similar.

In some jurisdictions, wrongfully implying that an author, publisher, or anyone else endorses a particular use of a work may be unlawful. Though not explicitly mentioned in the 1.0, 2.0, or 2.5 licenses, this has always been the case. [[Version_3#MIT|The version 3.0 licenses]] contain an express no endorsement clause. In version 4.0, this clause is expressed as a limitation on the rights granted by the licensor.

<span id="Modifications_and_adaptations_must_be_marked_as_such"></span>
====Modifications and adaptations must be indicated====
In the 4.0 license suite, licensees are required to [[Marking/Users#This_is_a_good_attribution_for_material_you_modified_slightly|indicate if they made modifications]] to the licensed material. This obligation applies whether or not the modifications produced adapted material. As with all other attribution and marking requirements, this may be done in a manner reasonable to the means, medium, and context. For example, "This section is an excerpt of the original." For trivial modifications, such as correcting spelling errors, it may be reasonable to omit the notice.

In the 3.0 suite, the obligation to indicate if modifications have been made applies if they result in the creation of an adaptation (when allowed by the license). Versions 1.0, 2.0, and 2.5 do not contain this requirement directly; however, the requirement in those licenses that the original work be credited if used in an adaptation (e.g., "French translation of the Work by Original Author") is some indication that the work has been modified. Even when not required, licensees are encouraged to indicate the material has been modified, and ideally (when reasonable) to describe or specify the changes made.

===Other license features===
====Representations and warranties from licensor included====
In version 4.0, the licensor does not provide representations and warranties regarding the licensed content.

In the 1.0 license suite, the licensor extends warranties—for instance, that the work does not infringe the work of another. [http://creativecommons.org/weblog/entry/4216 These warranties were eliminated in all subsequent license versions.] Versions 2.0, 2.5, 3.0 and 4.0 explicitly [[Frequently_Asked_Questions#Does_a_Creative_Commons_license_give_me_all_the_rights_I_need_to_use_the_work.3F|offer the work “AS IS”]] and disclaim all liabilities to the extent allowable by law. In 4.0, an interpretation clause was added to help ensure that the disclaimer would be interpreted as intended given variations in local law. Of course, licensors may continue to offer warranties and specialized disclaimers separately from the license.

Some ports of 3.0 include warranties where they may not be disclaimed under local law. [[Jurisdiction_Database|You may compare how different jurisdictions implemented this section of the license]].

<span id="Waiver_or_non-assert_of_Licensor's_ability_to_enforce_technological_protection_measures"></span>
====Licensor expressly waives rights to enforce, and grants permission to circumvent, technological protection measures====
Version 4.0 includes an explicit waiver of, or agreement not to assert, any right licensor may otherwise have to enforce anti-circumvention of any effective technological measures applied to licensed material. CC licensors may apply such measures to their own licensed material, but [[Frequently_Asked_Questions#What_if_I_received_CC-licensed_material_encumbered_with_effective_technological_measures_.28such_as_DRM.29.3F|the 4.0 licenses ensure that, to the extent possible, users are able to exercise the licensed rights]] when applied by or with the permission of the licensor. To reinforce this, the version 4.0 licenses also expressly grant permission to circumvent those measures.

It is always possible for a licensor to upload his or her own work to a platform that applies technological protection measures, even though the licensor chooses to use a CC license. The permission for a third-party platform to apply ETMs is separate from the CC license, and the CC license cannot restrict that additional permission because CC licenses are nonexclusive. In many jurisdictions, that third party may be able to enforce ETMs through civil or criminal anti-circumvention laws even though the licensor has waived or agreed not to assert any such right under the CC license. Licensees should make themselves aware of any legal limits on their ability to circumvent ETMs in advance of doing so.

In versions 1.0, 2.0, 2.5, and 3.0, the waiver of any right to enforce and the permission to circumvent are not express; however, this does not preclude any implied right to do so that may exist.

====Automatic restoration of rights after termination if license violations corrected====
In version 4.0, licensees may regain their rights to use licensed material after the license terminates by correcting a license violation within 30 days of discovering it.

In all license versions, [[Frequently_Asked_Questions#How_can_I_lose_my_rights_under_a_Creative_Commons_license.3F_If_that_happens.2C_how_do_I_get_them_back.3F|a breach of the license terms results in automatic termination]]. Under versions 1.0, 2.0, 2.5, and 3.0, express permission from the licensor is required for licensees to regain their rights to use the work. In version 4.0, a new provision allows the rights to be automatically reinstated without express permission from the licensor, provided that the violation is corrected within 30 days of its discovery. This is similar to provisions in a handful of other public licenses.

In all versions, a licensor may of course reinstate permissions at any time.

====Collecting societies regimes addressed====
Under 4.0, licensors waive any right to collect royalties under collecting society schemes if they have chosen licenses permitting commercial uses. A licensor may collect royalties for commercial uses for works under the NonCommercial licenses.

[[Frequently_Asked_Questions#Can_I_use_a_Creative_Commons_license_if_I_am_a_member_of_a_collecting_society.3F|Many users of Creative Commons licenses are members of collective rights societies]] like ASCAP, BMI, BUMA/STEMRA, and others that manage copyright on behalf of owners. Every license version from the 2.0 suite onward contains clauses that account for the existence of those arrangements. They provide, for instance, that for works offered under a NonCommercial license, the licensor retains the right to collect royalties for commercial uses of the work. The [http://creativecommons.org/weblog/entry/4216 structure of the provisions in the 2.0 and 2.5 licenses] differs from that in the version 3.0 and 4.0 licenses. The 2.x licenses specifically regulate music, sound recordings, and webcasting. As those licenses were ported to different jurisdictions, those provisions were adjusted to conform to the local collecting society situation.

The [[Version_3#International_Harmonization_.E2.80.94_Collecting_Societies|version 3.0 licenses and later employ a broad, harmonized strategy to collective rights societies]]. This strategy still allows jurisdictions to adopt an approach that best aligns with local law and society structure in the 3.0 licenses, but also ensures that the approach is implemented consistently across jurisdictions. In the international license, as regards compulsory royalty collection, the licensor reserves any right they have to collect those royalties in jurisdictions in which collection cannot be waived. In those jurisdictions in which compulsory royalty collection can be waived, the right to collect royalties is waived completely for those licenses that permit commercial use, and is reserved for commercial uses in those licenses that permit NonCommercial use only. For voluntary royalty schema, the licensor reserves the right to collect royalties for commercial uses in those licenses that permit NonCommercial use only, and waives the right to collect such royalties for licenses permitting commercial use. This clause covers both individual royalty collection and, in the event that the licensor is a member of a collecting society that collects such royalties, collection via such societies to the extent permitted by law. Some ports of the version 3.0 licenses include only those clauses that address the particular situation in the jurisdiction. Others have adopted all the language from the international license in hopes of international harmonization, or out of concern that their jurisdiction’s regime may change. [[Jurisdiction_Database|You may compare how different jurisdictions implemented this section of the license]].

===License-specific features===
<span id="Compatible_licenses_may_be_used_for_adaptations_of_works_originally_offered_under_CC_ShareAlike_licenses"></span>
====Compatibility mechanism in BY-SA licenses====
Under the 4.0 licenses, licensees may use licenses designated by CC as compatible for their contributions to adapted material.

The ShareAlike licenses require that licensees make their contributions to adapted material available under the same terms and conditions, or, where the license allows, under a license designated by CC as compatible. The version 1.0 ShareAlike licenses require that adaptations be made under exactly the same license as applied to the original work. Starting with the release of the [http://creativecommons.org/weblog/entry/4216 2.x license suites, CC expanded compatibility] by allowing contributions to adapted material to be created under the same or later version of the original license, including other ported versions of the same or later version of the license. The [http://wiki.creativecommons.org/Version_3#BY-SA_.E2.80.94_Compatibility_Structure_Introduced 3.0 Attribution-ShareAlike goes one step further], by allowing those contributions to be licensed under under a “Creative Commons Compatible License,” defined to mean licenses approved by CC as essentially equivalent to the 3.0 Attribution-ShareAlike license.

To date, CC has not approved any other licenses as compatible. However, CC will develop a compatibility process shortly following launch of the 4.0 licenses, and begin evaluating other licenses. You can view [http://creativecommons.org/compatiblelicenses the list of compatible licenses], and a post about the [http://lists.ibiblio.org/pipermail/cc-licenses/2013-September/007447.html upcoming compatibility process]. You may also want to review CC’s statement of intent for [[CC_Attribution-ShareAlike_Intent|the Attribution-ShareAlike licenses]], and a [[DRAFT_ShareAlike_Statement_of_Intent|draft statement]] that sets out further principles for the ShareAlike licenses.

====Compatibility mechanism in BY-NC-SA licenses====
In the 4.0 licenses, the same compatibility mechanism is present in the BY-NC-SA license as in BY-SA. Adapted material may be licensed under BY-NC-SA, version 4.0 or later, or any license CC has designated as compatible. To date, CC has not identified any other licenses as compatible; the process and criteria will be maintained on the [http://creativecommons.org/compatiblelicenses compatibility page]. There is no compatibility mechanism in the 1.0, 2.0, 2.5, or 3.0 versions of BY-NC-SA.

====Adapted material usable under conditions of adapter's license====
In version 4.0, CC [[4.0/ShareAlike#Draft_4|added a provision in the ShareAlike licenses]] that enables downstream licensees to refer only to the adapter’s license when using adapted material that contains the copyrightable contributions of multiple authors. This feature is designed to minimize complexity for reusers where they are using a later version of the ShareAlike license or a compatible license as their adapter's license. In 4.0, users need only refer to a single set of conditions contained in the last license applied to reuse adapted material, rather than parsing the conditions of the original and other adapter's licenses (to the extent the licenses differ).

In all cases, the licenses stack (the later license does not supplant all previously-applied licenses) when adapted material is created. In particular, the license originally applied to the material being remixed continues to apply once remixed, however permission is given in 4.0 for licensees to meet the conditions of the 4.0 license with reference to those in the adapter's license.

Prior to the 4.0 versioning process, CC had not always been clear that the ShareAlike licenses stacked just as they stack for the BY and BY-NC licenses, and reasonable minds do differ on this point. CC believes, however, that this is the best reading of its all of its licenses that permit adaptations prior to 4.0 and, now, has made that explicit in version 4.0.

====Adaptations of NoDerivatives material permitted when not shared====
In Version 4.0, licensees are [[4.0/Treatment_of_adaptations#Draft_4|granted permission to create adaptations]] of material licensed under one of the NoDerivatives licenses, but not permission to share the adaptations publicly.

In general, private personal use does not require the permission of the licensor and, therefore, does not require that the conditions of the CC license be followed. In 4.0, NoDerivatives is a partial rather than an absolute limitation on the rights granted. It does not restrict the production of adaptations (an exclusive right of creators under copyright), but it does prohibit the public sharing of those adaptations (also an exclusive right of creators under copyright). This change enables private activities that may result in the creation of adaptations whether intentionally or unintentionally, such as adaptations made in the course or as a result of [[Data|text and data mining]].

The creation of adaptations in connection with those and other activities are not permitted under the 3.0 and earlier versions absent an applicable exception or limitation.

===Features remaining unchanged across license versions===
====Attribution required====
All of the CC licenses require attribution where "BY" is a license element, which is all but five of the eleven version 1.0 licenses.The required mode of attribution differs slightly among the versions, and is progressively more flexible with each version. The version 1.0 suite is unique because it contains five CC licenses that do not require attribution. [http://creativecommons.org/weblog/entry/4216 All subsequent license suites make attribution a standard requirement], though the licensor may request removal in certain circumstances. It is also possible under all license versions for a licensor to release works anonymously, and to waive the requirement by not providing authorship information. Where an element of attribution information is not provided by the licensor, the licensee is not required to provide it.

====Definition of "NonCommercial"====
While the Creative Commons licenses have evolved over time, the scope of [[Frequently_Asked_Questions#Does_my_use_violate_the_NonCommercial_clause_of_the_licenses.3F|permitted uses under the NonCommercial licenses]] has remained unchanged across all license suites. (In 4.0, there was a small adjustment to the wording of the definition which was not intended to change its scope.) The NonCommercial clause prohibits the exercise of rights granted under the NonCommercial licenses “in any manner that is primarily intended for or directed toward commercial advantage or monetary compensation.” In 2008, Creative Commons conducted a [http://creativecommons.org/weblog/entry/17127 study on the meaning of NonCommercial in the online environment].

During the 4.0 process, CC took another look at the role of these licenses in general as well as the NonCommercial definition, and considered a name change to "Commercial Rights Reserved". The ultimate decision was to [https://creativecommons.org/weblog/entry/36725 leave unchanged the license name and definition].

<span id="Technical_Measures_by_Licensees_Prohibited"></span>
====Application of effective technological measures by users of CC-licensed works prohibited====
All CC license versions [[Frequently_Asked_Questions#Can_I_use_effective_technological_measures_.28such_as_DRM.29_when_I_share_CC-licensed_material.3F|prohibit licensees (as opposed to licensors) from using effective technological measures]] such as “digital rights management” software to restrict the ability of those who receive a CC-licensed work to exercise rights granted under the license. To be clear, encryption or an [[Frequently_Asked_Questions#Can_I_share_CC-licensed_material_on_password-protected_sites.3F|access limitation]] is not necessarily a technical protection measure prohibited by the licenses. For example, content sent via email and encrypted with the recipient's public key does not restrict use of the work by the recipient. Likewise, limiting recipients to a set of users (e.g., with a username and password) does not restrict use of the work by the recipients. In the cases above, encryption or an access limitation does not violate the prohibition on technological measures because the recipient is not prevented from exercising all rights granted by the license (including rights of further redistribution).

[[Version_3#Debian|This treatment was re-evaluated during the public process leading to release of the version 3.0 license suite.]] CC considered arguments in favor of such measures, coupled with an obligation of parallel distribution; these arguments were also reconsidered [[4.0/Technical_protection_measures|during the 4.0 process]]. However, in both versioning processes, those arguments were ultimately rejected.

Note that in 4.0, CC introduced a definition of Effective Technological Measures. This definition is not intended to change the scope of what is and is not allowed, but instead provide long-needed clarification over the scope of the prohibition.

====Exceptions and limitations unaffected====
[[Frequently_Asked_Questions#Do_Creative_Commons_licenses_affect_exceptions_and_limitations_to_copyright.2C_such_as_fair_dealing_and_fair_use.3F|All CC licenses only govern uses that would otherwise be restricted by copyright and other closely related rights as provided in the licenses]]. If a use is not regulated by virtue of an applicable exception or limitation, the license does not apply and there is no need to follow the license conditions. The licenses do not create obligations where they would not otherwise exist.

<span id="Use_of_licenses_for_copyrightable_compilations_of_data_anticipated"></span>

====Effective for all copyrightable material====
All Creative Commons license versions may be used with all [[Frequently_Asked_Questions#How_do_CC_licenses_operate.3F|copyrightable works]] (though [[Frequently_Asked_Questions#Can_I_apply_a_Creative_Commons_license_to_software.3F|CC recommends against using its licenses for computer software]]). Such works include [[Frequently_Asked_Questions#Can_I_apply_a_Creative_Commons_license_to_databases.3F|compilations of data]] that exhibit the requisite level of creativity for copyright protection under applicable law. Thus, to the extent compilations of data are protected by copyright, Creative Commons licenses are suitable licenses for granting permission to exercise that right. For the avoidance of doubt, version 3.0 and 4.0 licenses explicitly identify compilations as material that may be licensed.

[[Data#Can_databases_be_released_under_CC_licenses.3F|Note that sui generis database rights (existing separately from any copyright) are not explicitly licensed in the international suite until version 4.0.]]

====Notice of warranty disclaimers must be retained====
The CC licenses [[License_Versions#Detailed_attribution_comparison_chart|all require users to retain notices of disclaimers of warranties]] if supplied with the licensed material. Customized disclaimers never form part of the Creative Commons license, but may be offered.

====Synching creates adaptations====
In all license versions, synching CC-licensed audio in timed relation with a video to create an audiovisual work [[Frequently_Asked_Questions#When_is_my_use_considered_an_adaptation.3F|creates an adaptation]] of that audio work for purposes of the license, regardless of whether the new work would be considered an adaptation under the relevant copyright law. This means, for example, that the requirements of ShareAlike are triggered if the audio work is licensed under a ShareAlike license, and that such works may be made but not shared if licensed under a NoDerivatives license as of version 4.0.

====No sublicensing====
None of the Creative Commons licenses grant permission to sublicense the licensed material. All of the licenses are direct licenses from the original licensor to all recipients. All permissions granted come directly from the original licensor, creating a direct relationship for enforcement and other purposes between the original licensor and all recipients.

====Licensing of collections====
Including a CC-licensed work in a collection (a work comprised of separate and independent works) is permitted by all CC licenses. [[Frequently_Asked_Questions#If_I_create_a_collection_that_includes_a_work_offered_under_a_CC_license.2C_which_license.28s.29_may_I_choose_for_the_collection.3F|However the collective work as a whole is licensed]], the license on the collection does not affect the CC license applied to the work.

In 4.0, reference to distribution in a collection was removed from the license as unnecessary. There is no change from previous versions, however.

====Licensing of contributions to BY and BY-NC adaptations====
The 4.0 licenses make clear for the first time [[Frequently_Asked_Questions#If_I_derive_or_adapt_material_offered_under_a_Creative_Commons_license.2C_which_CC_license.28s.29_can_I_use.3F|how contributions to adaptations of BY and BY-NC works may be licensed]]. Specifically, an adapting licensee may apply any license to her contributions provided that license does not prevent users of the adaption from complying with the original license. While new in 4.0, the introduction of this provision is intended as a clarifier only and is not a change from how earlier versions operate.

==Licenses==
Links to the International (unported) legal code for the six licenses making up the current suite, for each version:

===4.0===
*'''[http://creativecommons.org/licenses/by/4.0/legalcode BY]'''
*'''[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA]'''
*'''[http://creativecommons.org/licenses/by-nc/4.0/legalcode BY-NC]'''
*'''[http://creativecommons.org/licenses/by-nc-sa/4.0/legalcode BY-NC-SA]'''
*'''[http://creativecommons.org/licenses/by-nd/4.0/legalcode BY-ND]'''
*'''[http://creativecommons.org/licenses/by-nc-nd/4.0/legalcode BY-NC-ND]'''

===3.0===
*'''[http://creativecommons.org/licenses/by/3.0/legalcode BY]'''
*'''[http://creativecommons.org/licenses/by-sa/3.0/legalcode BY-SA]'''
*'''[http://creativecommons.org/licenses/by-nc/3.0/legalcode BY-NC]'''
*'''[http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode BY-NC-SA]'''
*'''[http://creativecommons.org/licenses/by-nd/3.0/legalcode BY-ND]'''
*'''[http://creativecommons.org/licenses/by-nc-nd/3.0/legalcode BY-NC-ND]'''

===2.5===
*'''[http://creativecommons.org/licenses/by/2.5/legalcode BY]'''
*'''[http://creativecommons.org/licenses/by-sa/2.5/legalcode BY-SA]'''
*'''[http://creativecommons.org/licenses/by-nc/2.5/legalcode BY-NC]'''
*'''[http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode BY-NC-SA]'''
*'''[http://creativecommons.org/licenses/by-nd/2.5/legalcode BY-ND]'''
*'''[http://creativecommons.org/licenses/by-nc-nd/2.5/legalcode BY-NC-ND]'''

===2.0===
*'''[http://creativecommons.org/licenses/by/2.0/legalcode BY]'''
*'''[http://creativecommons.org/licenses/by-sa/2.0/legalcode BY-SA]'''
*'''[http://creativecommons.org/licenses/by-nc/2.0/legalcode BY-NC]'''
*'''[http://creativecommons.org/licenses/by-nc-sa/2.0/legalcode BY-NC-SA]'''
*'''[http://creativecommons.org/licenses/by-nd/2.0/legalcode BY-ND]'''
*'''[http://creativecommons.org/licenses/by-nc-nd/2.0/legalcode BY-NC-ND]'''

===1.0===
*'''[http://creativecommons.org/licenses/by/1.0/legalcode BY]'''
*'''[http://creativecommons.org/licenses/by-sa/1.0/legalcode BY-SA]'''
*'''[http://creativecommons.org/licenses/by-nc/1.0/legalcode BY-NC]'''
*'''[http://creativecommons.org/licenses/by-nc-sa/1.0/legalcode BY-NC-SA]'''
*'''[http://creativecommons.org/licenses/by-nd/1.0/legalcode BY-ND]'''
*'''[http://creativecommons.org/licenses/by-nc-nd/1.0/legalcode BY-ND-NC]''' ''(Note that in the 1.0 license suite, the name of this license is different than later versions)''

[[Category:Legal]]

Developers

2013-12-11T03:51:00Z

Mike Linksvayer: Reverted edits by Dongdong li (talk) to last revision by CC Wiki Bot

'''Welcome to the CC Developer Community!''' This is where you'll find all
about the technologies and software products that CC uses to push
forward our mission to maximize digital creativity, sharing, and
innovation.

== Get Involved ==

All of the projects developed at Creative Commons are open source
software, and just like most open source projects, outside involvement
is key to its success. But you don't have to be a software developer
to join us--we'd love to have you in the discussion if you're a user
researcher, designer, translator, or just interested in the topic.

; E-mail
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
; IRC
: Chat with us real-time on [irc://irc.freenode.net/cc irc] (Freenode, #cc)

Coming soon: public team meetings, and other ways to engage.

== Projects ==

; [[OpenHome]]
: A Creative Commons homepage with your content
; [[Summer of Code 2013|Google Summer of Code 2013]]
: Ideas and more.
; [[Translate|Localization]]
: Find out how to help the Creative Commons community with translations.

== Core Technologies ==

; [[RDFa]]
: Standard for adding machine-readable statements to web pages.
; [[CcREL]]
: Language for adding licensing information to web pages.
; [[LRMI]]
: Language for describing educational resources on the web.
; [[Liblicense]]
: Library for embedding licensing metadata into files of various formats. (note: now somewhat out of date!)

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Source Repository Information

2013-12-06T16:47:27Z

Mike Linksvayer: Reverted edits by SimpleNg (talk) to last revision by Nkinkade

[[Category:Developer]]
[[Category:CC_Tech_Handbook]]

Creative Commons uses [http://subversion.tigris.org Subversion] and [http://git.or.cz/ Git] repositories at http://code.creativecommons.org for source code management. Subversion (svn) clients are included with Linux and Mac OS X. Windows users can use [http://tortoisesvn.tigris.org/ Tortoise SVN].

ccPublisher and some dependencies are still housed at [[CcTools Berlios|Berlios.de]]; those modules will be moved to code.creativecommons.org eventually.

== Checking Out Source ==

=== code.creativecommons.org ===

We moved our primary source repository from Sourceforge.net to code.creativecommons.org in March, 2008. Note that we only support public key authentication for our repositories.

==== Subversion====

* [http://code.creativecommons.org/viewsvn web view]
* [http://code.creativecommons.org/svnroot read-only repository]
* writeable checkout:
$svn co svn+ssh://svn@code.creativecommons.org/svnroot/project
* write permission: email webmaster@creativecommons.org with your public key; if you had write permission at Sourceforge, please include your sourceforge.net username so we can map your key correctly.

==== Git====

* [http://code.creativecommons.org/viewgit web view]
* read-only access:
$git clone git://code.creativecommons.org/cc.license.git
* read/write access:
$git clone git@code.creativecommons.org:cc.license

=== Berlios.de ===

See the [http://developer.berlios.de/svn/?group_id=5272 ccTools Subversion Information] page for details on checking out code hosted at Berlios (ccPublisher).

== Repositories ==

== Available Modules ==

=== svn ===

The Subversion repository contains the following modules:

<table align="left" valign="top" style="float:none;">
<tr><th>module name </th><th>description</th></tr>
<tr><td>__cvs_import/</td><td>Inactive modules imported to Subversion from CVS circa 2005 (from sourceforge.net).</td></tr>
<tr><td>adobe_panel/</td><td>XMP license panel for legacy Adobe products</td></tr>
<tr><td>api/</td><td>CC API; now developed in git (cc.api)</td></tr>
<tr><td>api_client/</td><td>Wrappers for the API in Python, Java, etc; unmaintained.</td></tr>
<tr><td>asheesh_oneoffs/</td><td></td></tr>
<tr><td>autocurate/</td><td>Scripts to generate packages of content from sites like Flickr, etc, used for LiveCD.</td></tr>
<tr><td>banshee-license-verifier-plugin/</td><td>GSOC project: plugin for Banshee to verify web statement metadata pointed to in MP3 ID3 tags.</td></tr>
<tr><td>bbpress/</td><td>Tracking repository of bbpress</td></tr>
<tr><td>blog_analysis/</td><td>Return top blogs pointing to CC, as reported by Technorati. Used for targeted outreach.</td></tr>
<tr><td>buildout_script/</td><td>Buildout recipe for doing string substitution in script templates</td></tr>
<tr><td>campaign_widget/</td><td>Annual campaign javascript widget</td></tr>
<tr><td>cc-content.deb/</td><td></td></tr>
<tr><td>cc-sharp/</td><td>C# model for CC licenses</td></tr>
<tr><td>cc.engine/</td><td>License engine; now developed in git (cc.license)</td></tr>
<tr><td>cc.license/</td><td></td></tr>
<tr><td>ccbanshee/</td><td>GSOC project: Banshee plugin for displaying license information</td></tr>
<tr><td>cchost/</td><td>Legacy repository for CCHost, platform developed for CC Mixter</td></tr>
<tr><td>cci/</td><td>WordPress for legacy iCommons website</td></tr>
<tr><td>cclabs/</td><td>Legacy CC Labs experiments (DHTML chooser, et al)</td></tr>
<tr><td>cclib/</td><td></td></tr>
<tr><td>cclicense/</td><td></td></tr>
<tr><td>[[CcLookup|cclookup]]/</td><td>wxPython application for verifying web statements embedded in media files</td></tr>
<tr><td>[[CcNutch|ccnutch]]/</td><td>Nutch + cc search customizations</td></tr>
<tr><td>ccoer/</td><td>Early prototype of DiscoverEd, based on Scuttle</td></tr>
<tr><td>ccooo/</td><td>OpenOffice.org add-on, now developed in git.</td></tr>
<tr><td>ccpublisher1/</td><td>CC Publisher 1.x; 2.x code lives in the berlios.de repository/td></tr>
<tr><td>ccrdf/</td><td>A Python wrapper for CC Licenses</td></tr>
<tr><td>ccsearch/</td><td>CC Meta-search</td></tr>
<tr><td>cctagutils/</td><td>Python library for reading and writing CC's suggested web statements</td></tr>
<tr><td>ccwordpress/</td><td>creativecommons.org</td></tr>
<tr><td>cli_tools/</td><td>Command line tools for tagging and verifying licensed works.</td></tr>
<tr><td>desktop_search/</td><td>Prototype of Spotlight plugin for Mac OS X</td></tr>
<tr><td>experimental/</td><td></td></tr>
<tr><td>feed2map/</td><td></td></tr>
<tr><td>hooks/</td><td></td></tr>
<tr><td>i18n/</td><td>Translations, maintenance tools, now in git.</td></tr>
<tr><td>i18nedit/</td><td>Half finished prototype of web based PO editor, herder</td></tr>
<tr><td>jswidget/</td><td>Drop-in javascript widget for license selection</td></tr>
<tr><td>liblicense/</td><td>C library for manipulating license information embedded in files</td></tr>
<tr><td>liblicense-gnome/</td><td>gnome UI bindings for liblicense</td></tr>
<tr><td>liblicense-kde/</td><td>KDE UI bindings for liblicense</td></tr>
<tr><td>liblicense-sugar/</td><td>Sugar UI for liblicense</td></tr>
<tr><td>license-tutorial/</td><td></td></tr>
<tr><td>license.rdf/</td><td>License RDF files</td></tr>
<tr><td>license_xsl/</td><td>Legacy chooser XSLT and questions</td></tr>
<tr><td>livecontent/</td><td>Live CD with CC licensed content</td></tr>
<tr><td>log_analysis/</td><td></td></tr>
<tr><td>metadata_scraper/</td><td>Now developed in git as deedscraper</td></tr>
<tr><td>mozcc2/</td><td>Firefox add-on for displaying CC license information; superseded by OpenAttribute</td></tr>
<tr><td>nagios/</td><td>monitoring configuration</td></tr>
<tr><td>nc-survey/</td><td>Non-Commercial survey related code</td></tr>
<tr><td>oe_search/</td><td>PHP frontend for a Google CSE that acted as early DiscoverEd prototype</td></tr>
<tr><td>oenutch/</td><td>DiscoverEd</td></tr>
<tr><td>operator_userscript/</td><td>User script for Operator to display license information</td></tr>
<tr><td>opml/</td><td>Python library for reading and parsing OPML</td></tr>
<tr><td>pdf_callback/</td><td>Demonstration of a PDF with "phone home" capability</td></tr>
<tr><td>planet/</td><td>CC feed aggregator</td></tr>
<tr><td>pyarchive/</td><td>Python library for uploading works to Internet Archive</td></tr>
<tr><td>pywikipedia/</td><td>Python API for mediawiki, used for sending staff call emails</td></tr>
<tr><td>rdfadict/</td><td>Python dict-like interface for an RDFa parser</td></tr>
<tr><td>scicom/</td><td>Science Commons related projects, including MTA, SCA</td></tr>
<tr><td>scripts/</td><td></td></tr>
<tr><td>smw_tools/</td><td></td></tr>
<tr><td>stats/</td><td></td></tr>
<tr><td>themes/</td><td>Various theme projects</td></tr>
<tr><td>vendorlibs/</td><td>Vendor libraries that are used by other projects. Modules are imported here if the project doesn't use svn, so we can use svn:externals, or if additional customization is required</td></tr>
<tr><td>widgets/</td><td>Widgets for visualizing CC content and information.</td></tr>
<tr><td>wordpressmu/</td><td></td></tr>
<tr><td>wpLicense/</td><td>WordPress plugin for CC licensing; now developed in git/WP svn</td></tr>
<tr><td>www-i/</td><td>i.creativecommons.org</td></tr>
<tr><td>xmp/</td><td>Tools for embedding XMP metadata in PDF, JPEG and (future) other file types.</td></tr>
<tr><td>zope_products/ </td><td>CC developed zope products: the license engine, Plone skin and iStr.</td></tr>
</table>

=== git ===
See the [http://code.creativecommons.org/viewgit git web interface] for repository descriptions.

Guatemala

2013-12-06T16:47:20Z

Mike Linksvayer: Reverted edits by SimpleNg (talk) to last revision by RenataAvila

{{Jurisdiction
|jurstatus=Active
|status=3.0
|country code=gt
|homepage=http://gt.creativecommons.org/
|logourl=http://wiki.creativecommons.org/images/9/98/Creative-commons-guatemala.jpg
|mailing list=http://lists.ibiblio.org/mailman/private/cc-gt/
|twitter=http://twitter.com/#!/guatemalacc
|social=http://www.facebook.com/#!/pages/Creative-Commons-Guatemala/305930473649
|mailing=renata@gt.creativecommons.org
|region=Latin America
|affiliated=New Media Center at the Universidad Francisco Marroquin
|afftype=academic institution
|plead1=Renata Avila
|pemail1=renata@gt.creativecommons.org
|plead2=María Isabel Carrascosa
|pemail2=micarrascosa@gmail.com
|plead3=Jorge Gabriel Jiménez
|pemail3=jjimenez@ufm.edu
|flagurl=http://creativecommons.org/images/international/gt.png
|logo=http://www.flickr.com/photos/29375068@N03/5228489576/
|wordpress=http://ccgt.wordpress.com/
|identi_ca=http://identi.ca/ccguatemala
|blog=http://gt.creativecommons.org/index.php/Portada
}}
[[File:Creative-commons-guatemala.jpg]]

Visit the [http://gt.creativecommons.org/ jurisdiction's website].

The Creative Commons Guatemala license suite is available in the following version. [http://creativecommons.org/choose/?jurisdiction=gt License your work] under these licenses, or [http://creativecommons.org/choose choose] the international licenses. [http://wiki.creativecommons.org/FAQ#Should_I_choose_an_international_license_or_a_ported_license.3F More info].

Many thanks to all who contributed to the localization of the license suite.

Creative Commons is working with the New Media Center at the [https://www.ufm.edu/index.php Universidad Francisco Marroquin] to create jurisdiction-specific licenses for Guatemala from the “unported” Creative Commons licenses.

=CC Guatemala Roadmap=

[[Roadmap 2011 / 2012]]

=CC Guatemala List=

Project Lead: [mailto:renata@ufm.edu.gt Renata Avila, LL.M].

*[http://mirrors.creativecommons.org/international/gt/translated-license.pdf License draft]
*[http://mirrors.creativecommons.org/international/gt/english-retranslation.pdf English re-translation of the draft]
*[http://mirrors.creativecommons.org/international/gt/english-changes.pdf English explanation of substantive legal changes]
*[mailto:cc-gt@lists.ibiblio.org Post a message]
*[http://lists.ibiblio.org/mailman/listinfo/cc-gt Subscribe to the discussion]
*[http://lists.ibiblio.org/mailman/private/cc-gt/ Read the discussion archives]

[['''Roadmap''']]

=More about the New Media Center at the Universidad Francisco Marroquin=

Conceived in 2001, the New Media department at UFM was created to assist faculty members, researchers, and students in the use, creation, and management of digital resources that complement their academic work. And, due to the improvements in IT infrastructure and user expertise as well as advances in Internet enabled teaching, it became clear that the role of the New Media department would be twofold. Firstly, the department preserves and makes the university’s unique collection of VHS and ¾” films available through digitization and conversion to Internet compatible formats to increase access and use. Secondly, the New Media department has digitized and streamed classes, conferences and lectures held at UFM over the Internet in order to preserve this locally produced content, but also to support university distance learning. We actively assist departments and professors who wish to incorporate digital media into their courses by teaching various short courses in video and multimedia production. Additionally, we include many technical and academic value added features to the digital video, such as indexes,slides, and lecture notes. These developments permit greater faculty and student participation in the creation and use of teaching resources and mean that digital video is becoming an important tool in the provision of course material at UFM.

For more information, please visit http://newmedia.ufm.edu/.

== ABOUT US: ==
[https://www.ufm.edu/cms/es/at-a-glance Universidad Francisco Marroquin] is a private university in Guatemala, it was founded 1971. The mission of Universidad Francisco Marroquín is to teach and disseminate the ethical, legal and economic principles of a society of free and responsible persons.

[http://newmedia.ufm.edu/gsm/index.php?title=A_Creative_Commons_World:_Free_to_Choose,_to_Create,_to_Innovate,_to_Learn,_to_Imagine A Creative Commons World: Free to Choose, to Create, to Innovate, to Learn, to Imagine]
Our Chapter was born 2008 we had de honor to host [http://en.wikipedia.org/wiki/Jimmy_wales Jimmy Wales]. There is a strong link between the University's philosophy and the idea of Creative Commons. Wales mentioned the fact that in order to understand [http://en.wikipedia.org/wiki/Wikipedia Wikipedia] one had to understand the ideas of [http://en.wikipedia.org/wiki/Friedrich_August_Von_Hayek Friedrich August von Hayek].

To watch the [http://www.youtube.com/watch?v=GOEBoCn1G-4 interview]

== ACTIVITIES: ==
[[Birthday Party 2008 Guatemala]]

On February 25th, 2010, we participated in a live webcast of a talk by Lawrence Lessig.
[http://openvideoalliance.org/2010/01/announcing-wireside-chat-with-lawrence-lessig/?l=es Wireside Chat with Lawrence Lessig].

Participation on [http://www.filgua.com FILGUA 2010]. Guatemala's biggest book fair and one of the most important book fairs in Central America was held in Parque La Industria in Guatemala City. We decided to do something creative and therefore the best way to introduce people to creative commons and technology and the way these two relate to books was an [http://en.wikipedia.org/wiki/Unconference unconference] We thought it would be a nice approach to discuss "the future of books, electronic book" ([http://www.facebook.com/#!/event.php?eid=139146902779903&index=1 check the event]), and that's how we called the event. It was really interesting because the audience was diverse, by means of age and careers, the age range was from 20's to 60's and there were writers, scholars, designers, bloggers and between others. [http://www.flickr.com/photos/renata_a_pinto/sets/72157624559225678/with/4818904194/ photos]
[http://noticias.ufm.edu/index.php/Biblioteca_Ludwig_von_Mises_en_Filgua more info]

== WHAT'S NEXT: ==

[http://www.slideshare.net/RenataAvila/cc-bus CC BUS]

During the summer of 2011 together with CC Costa Rica and other partners we will promote the licenses across the region.

[http://joaquinorellana.org/ JOAQUIN ORELLANA MUSIC]

The project consists on reviving Joaquin Orellana (a worldwide famous guatemalan artist who unfortunately not known in his own country), he agreed on licencing his pieces with us, we contacted dancers (Arteproyecto) and a rising DJ (Mariano Santolino) so that they derive something out of Joaquin Orellana’s work. We plan to tape all the process to exemplify how easy it would be to eliminate the intermediaries (us by contacting them) just by licencing their works, this will be presented in a shopping mall and other public places we have not concreted yet. So we have all the contacts and the process will start next year.

Publish

2013-12-06T16:44:44Z

Mike Linksvayer: rv spam

{| cellspacing="5" cellpadding="10" style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:100%"
| NOTE: This page is for creators and copyright owners who are looking to publish on other platforms. To publish on your own site, see [[Marking/Creators]].
|}

One way to increase visibility and access to your work is to share it with an existing community. Many content platforms have already 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.

The following are some major publishing platforms categorized by media type. If you cannot find what you are looking for, see more CC-enabled [[Content Directories]] and counts of CC licensed works for each. If your favorite community has not enabled CC licensing, you can usually indicate that you are using CC somewhere in an info box, or contact them and let them know it is a feature you would like to see.

==Major communities by media type==

===[[Publish/Images|Images]]===

===[[Publish/Audio|Audio]]===

===[[Publish/Video|Video]]===

===[[Publish/Text|Text]]===

==Community resources==
*[[Metrics]] on growing CC-licensed usage
*CC [[Case Studies]]
*[[Content Directories]]
*[[Applications Using CC]]

{{Best Practice}}

{{Translations
| articles = Pt:Publicar
}}

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:Guide]]

License Versions

2013-12-06T16:15:05Z

Mike Linksvayer: Reverted edits by Www.Gcomics.com (talk) to last revision by Kat Walsh

Cc-license-chooser

2013-10-22T22:46:36Z

Mike Linksvayer: Reverted edits by EmmaHarper1955 (talk) to last revision by Mzeinstra

{{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 ==

<div style="text-align:center">
[[Image:Jswidget-0.2-screenshot.png]]
</div>

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/ Basic usage]
* [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]
* [http://labs.creativecommons.org/jswidget/tags/0.97/example_web_app/definitely-want-license.html Selector without the choice of "No license"]

== 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 ?jurisdictions=disabled 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 ?want_a_license= no_license_by_default

=== Removing the "No license" option ===
If you want to not offer the user the option of selecting "no license:
* just append ?want_a_license=definitely 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 ===
* You can use the example style provided in the example application to get you going. We '''urge''' you to put this file on your own web server and not rely on the copy hosted on labs.creativecommons.org.
* What we really want you to do is to change the style of our divs and spans and so-forth to make them fit in to your application. To do that, you should copy the example style file into one of your own CSS files and modify it until you really like it.
=== 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.

== 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

== 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]]

XMP

2013-10-05T23:46:15Z

Mike Linksvayer: Reverted edits by Nethanbraker (talk) to last revision by Mike Linksvayer

{{Filetype
|license_url=Yes
|web_statement=Yes
|more_permissions=Yes
}}

[[Image:Xmp_tagline.png|right]]
[http://www.adobe.com/products/xmp XMP] ([http://en.wikipedia.org/wiki/Extensible_Metadata_Platform Extensible Metadata Platform]) facilitates embedding metadata in files using a subset of RDF. Most notably, XMP supports embedding metadata in PDF and many image formats, though it is designed to support nearly any file type.

Creative Commons is recommending XMP as the preferred format for embedded metadata, given its [http://web.archive.org/web/20070426051136/http://labs.adobe.com/technologies/xmptoolkit/#FAQ support for numerous file formats] and the balkanized state of embedded metadata standards. Others are coming to a similar conclusion; Microsoft has announced support for [http://blogs.msdn.com/pix/archive/2006/08/23/715340.aspx XMP in Vista applications] and Jon Udell [http://blog.jonudell.net/2007/02/14/truth-files-microformats-and-xmp/ notes] "There’s also good support in .NET Framework 3.0 for reading and writing XMP metadata." Note that even when embedded with XMP metadata, Creative Commons recommends a licensed document include a visible copyright notice; [[Marking|format-specific recommendations]] for visible notices are available.

The Creative Commons [http://www.creativecommons.org/license/ licensing process] offers a XMP template which may be used to mark files within XMP-supporting [[XMP help for Adobe applications|Adobe applications (step-by-step how-to document)]]. An [[Adobe_Metadata_Panel|XMP FileInfo panel]] is also available.

== Specifying License Information ==

XMP [http://www.adobe.com/devnet/xmp/ defines] a rights management schema (see XMP Specification, p. 42). Creative Commons sets the following properties (example values):

* '''xmpRights:Marked''' — ''False'' if Public Domain, ''True'' otherwise.
* '''xmpRights:WebStatement''' — ''http://example.com/pdf-metadata.html'' (Replace with URL containing metadata about the XMP-embedded file; this is referred to as the [[WebStatement|Web Statement]].)
* '''xmpRights:UsageTerms''' — An optional field describing legal terms of use; Creative Commons recommends that when present this take the form ''This work is licensed to the public under the Creative Commons Attribution-ShareAlike license http://creativecommons.org/licenses/bysa/2.0/ verify at http://example.com/pdfmetadata.html'' (Replace URL following 'verify at' with URL containing metadata about the XMP-embedded file; this is typically the URL specified by '''xmpRights:WebStatement'''.)<br />'''''Note''': as of 2011-05 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf suggests using '''dc:rights''' and xmpRights:WebStatement; it probably makes sense to populate dc:rights and xmpRights:UsageTerms with identical content.''

We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc. It currently has the following properties:

* '''license''' — The license URL; for example, ''http://creativecommons.org/licenses/by-sa/2.0/''.
* '''morePermissions''' — A URL where additional permissions (commercial licensing, etc) are available.
* '''attributionURL''' — The URL to use when attributing this work.
* '''attributionName''' — The creator's preferred name to use when attributing this work.

== Verification Links and XMP ==

A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://watersoftenerreviewspro.com/water-softener-comparison/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.

For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].

<code><pre>
<p>The document example.pdf is licensed under a
<a about="urn:sha1:MSMBC5VEUDLTC26UT5W7GZBAKZHCY2MD" rel="license"
href="http://creativecommons.org/license/by/3.0/">
Creative Commons Attribution 3.0</a> license.
</a>
</p>
</pre></code>

When processing a file containing an embedded web statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.

== Additional Information ==

* [[XMP Implementations]]
* [[:Category:XMP|All XMP-related articles]]
* [http://en.wikipedia.org/wiki/Extensible_Metadata_Platform Wikipedia article]
* [[Adobe Metadata Panel|Adobe XMP FileInfo Panel]]

<small>The XMP logo is either a registered trademark or trademark of the Adobe Systems Incorporated in the United States and/or other countries.</small>

{{Translations
| articles = Pt:XMP
}}

[[Category:Developer]]
[[Category:Technology]]
[[Category:Metadata]]
[[Category:XMP]]

Content Directories

2013-10-05T23:45:59Z

Mike Linksvayer: Reverted edits by Nethanbraker (talk) to last revision by NickNoIte

{{Infobox|
'''Welcome to the Content Directories'''

The following is a list of organizations and projects powered with Creative Commons licenses. Since Creative Commons does not maintain a database of content and does not store content, we would like CC-community members to help build a directory of projects to help spread the word about CC — hence the CC Content Directories wiki! Please help us fill it out!

'''What is an appropriate entry for Content Directories?'''

Many of the listings in the Content Directories are organizations that provide services using Creative Commons licenses. For example, Flickr.com is a photo-sharing website that allows users to license their photos under Creative Commons licenses. Flickr hosts millions of CC-licensed photos on its site.

Not certain that something should be added to this list? Add it to [[Talk:Content Directories]] For short lists of notable works, see [[books]] and [[films]]. For other notable uses, see the [[Case_Studies|case studies]] [[project]].

'''How to add an entry to Content Directories'''

To get started, simply add the name of the organization or project in the box below. Then, you'll be able to use an easy form to enter details to add to the Content Directories listings. For some screenshots about how to do this, go [[Add_content_directory_howto|here]].
If you haven't done so already, you'll need to sign up for an account on this wiki. Users must be logged-in to post to the wiki.
}}

{{#forminput:ContentDirectory|35|Content Directory Name|}}

== [[Audio#Featured_Audio_Sites| Audio]] ==

{{#ask:
[[format::sound]]
[[size::+]]
|mainlabel=|?mainurl=|?size=Size
|limit=103
}}

== [[Video#Featured_Video_Sites|Video]] ==

{{#ask:
[[format::MovingImage]]
[[size::+]]
|mainlabel=label
|?mainurl=url
|?size=Size
|limit=100
}}

== [[Image#Featured_Image_Sites|Image]] ==

{{#ask:
[[format::Image]]
[[size::+]]
|mainlabel=Name
|?mainurl=Website
|?size=Size
|limit=100
}}

== [[Other#Featured_sites| Other]] ==

{{#ask:
[[format::Other]]
[[size::+]]
|mainlabel=Name
|?mainurl=Website
|?size=Size
|limit=400
}}

{{Translations
| articles=Es:Directorio de Contenidos, Pt:Listas de Conteúdos, Ru:Каталоги материалов
}}

__NOTOC__

4.0

2013-10-05T23:45:36Z

Mike Linksvayer: rv spam

CC has embarked upon a versioning process for its core license suite, which will result in version 4.0. The first public discussions of 4.0 were held at CC's [[Global Summit 2011]]. The public process was kicked off with a [http://creativecommons.org/weblog/entry/29639?utm_campaign=newsletter_1111&utm_medium=blog&utm_source=newsletter blog post] laying out some of the key reasons for pursuing 4.0 at this time.

Since CC's launch in 2002, it has versioned its core license suite [[license versions|three times]], the last ([[Version 3|3.0]]) in early 2007. CC licenses constitute a [http://creativecommons.org/who-uses-cc globally-recognized framework], developed in consultation with legal experts and CC affiliate institutions in [[CC_Affiliate_Network|over 70 jurisdictions]]. Over 500 million CC-licensed works have been published by their authors on the Internet. Today, Creative Commons licenses, public domain tools, and supporting technologies are the global standard for sharing across culture, education, government, science, and more.

Version 4.0 is a tremendous opportunity to ensure the license suite is ideally crafted to further CC's [http://creativecommons.org/about vision and mission] over the next decades. Please participate in this important discussion.

=== Goals and objectives ===

Creative Commons staff, board, and community have identified several goals for the next version of its core license suite, tied to achieving CC's goal and mission. These include:

:: ''Internationalization'' – further adapt the core suite of international licenses to operate globally, ensuring they are robust, enforceable and easily adopted worldwide;

:: ''Interoperability'' – maximize interoperability between CC licenses and other licenses to reduce friction within the commons, promote standards and stem license proliferation;

:: ''Long-lasting'' — anticipate new and changing adoption opportunities and legal challenges, allowing the new suite of licenses to endure for the foreseeable future;

:: ''Data/PSI/Science/Education'' — recognize and address impediments to adoption of CC by governments as well as other important, publicly-minded institutions in these and other critical arenas; and

:: ''Supporting Existing Adoption Models and Frameworks'' – remain mindful of and accommodate the needs of our existing community of adopters leveraging pre-4.0 licenses, including governments but also other important constituencies.

=== Organization and purpose of this wiki ===

This wiki is the central location for documenting key discussion topics and suggestions for improving the license suite in version 4.0, together with supporting information and relevant links. It is intended to supplement, not replace, the CC license discuss email list [http://lists.ibiblio.org/mailman/listinfo/cc-licenses (subscribe)] that will serve as the main discussion forum for the versioning process just as it has with prior versioning efforts.

CC has prepared pages on key topics identified to date. We ask contributors to be thoughtful about placement of additional and related topics, as well as the creation of new pages altogether. Before starting a new page, consider posting the suggestion to the [[4.0/Sandbox|Sandbox]]. We would also prefer that contributors use their real names when editing the wiki.

=== Process ===

As a license steward and steward of the commons, our goal for the process is to ensure utmost transparency and inclusiveness. The 4.0 process is being conducted in line with our prior versioning efforts, with periodic publication of license drafts for public comment and documentation of issue resolution as that occurs. One important difference from our past efforts, however, was a formal requirements gathering period that ran for a period of time prior to publication of the first draft. During this period, we strongly encouraged the broadest participation possible by everyone with an interest in the commons and the role open licensing plays in its future.

The primary discussion forum for issues relating to the 4.0 versioning process will be the CC license discuss email list. Please [http://lists.ibiblio.org/mailman/listinfo/cc-licenses subscribe] and add your voice to this important effort.

=== Draft timeline ===
The dates noted below are approximate and subject to change. The number of drafts and public comment periods may vary depending on the number and type of issues raised and how they are resolved, among other things. Watch this page for updates, including major events such as affiliate regional meetings where 4.0 discussions will take place.

{| class="wikitable" style="width: 75%; height: 200px" border="1"
|-
| September 2011
| [https://creativecommons.org/weblog/entry/29639 Launch 4.0 process] at CC Global Summit
|-
| December 2011 thru mid-February 2012
| Requirements gathering period
|-
| April 2, 2012
| Publish [[4.0/Drafts#Draft_1_Details|first draft of 4.0]]
|-
| April to June 2012
| [[4.0/Draft_1/Regional_calls|Public comment]] period #1
|-
| August 2012
| Publish [[4.0/Drafts#Draft_2_Details|second draft of 4.0]]
|-
| August 2012 to February 2013
| [[4.0/Draft_2/Regional_calls|Public comment]] period #2
|-
| February 2013
| Publish [[4.0/Drafts#Draft_3_Details|third draft of 4.0]]; begin porting consultation
|-
| February to September 2013
| [[4.0/Draft_3/Regional_calls|Third public comment period]]; porting consultation
|-
| September 2013
| Publication of [[4.0/Drafts#Draft_4_Details|fourth and final draft]]; begin abbreviated final public comment period
|-
| September/October 2013 (expected)
| Finalize and publish version 4.0 license suite
|}

Various aspects of the license suite are being improved in the version 4.0 licenses. We are gathering and rigorously debating and analyzing these items, and corresponding proposals for handling them, in version 4.0. We encourage the broadest possible engagement in this process. This was a particularly important goal during the requirements gathering stage where everyone was strongly encouraged (and our affiliates expected) to provide feedback on proposed changes and suggest other changes they would like to see. You may add, improve, and discuss specific items in the pages linked below.

'''If you do not find a suitable existing page and category for an item you would like to propose or discuss, please add it to the [[4.0/Sandbox]] where suggestions for new pages will be aggregated.'''

Finally, we encourage contributors to take the time to review [http://wiki.creativecommons.org/License_Versions prior versioning efforts], including relevant discussions of important topics previously debated by the CC community and discussions related to their resolution. Being aware of and taking those into account is important to an effective and efficient process, particularly where a request is made to revisit and potentially change direction in 4.0.

{{#ask:[[Category:4.0 Issues]] [[:+]]
|mainlabel=Item/Category Name
|format=broadtable|
=== Items for discussion ===
}}

===Related pages===
:[[4.0/Sandbox|4.0 Sandbox]]
:[[Porting Project]]
:[[4.0 Drafts]]
:[[4.0/Draft_1|4.0 Draft 1]]
:[[4.0/Draft_2|4.0 Draft 2]]
:[[4.0/Draft_3|4.0 Draft 3]]
:[[4.0/Draft_4|4.0 Draft 4]]
[[Category:4.0]]

Public domain

2013-10-05T23:44:22Z

Mike Linksvayer: Reverted edits by Mattman1 (talk) to last revision by CCAdmin

When a work is in the '''public domain''', it is free for use by anyone for any purpose without restriction under copyright law. Public domain is the purest form of open/free, since no one owns or controls the material in any way.

Works that are in the public domain in one legal jurisdiction are not necessarily in the public domain worldwide. Copyright laws differ from jurisdiction to jurisdiction, both in duration of protection and what constitutes copyrightable subject matter. For example [http://usa.gov/copyright.shtml a US Government work] clearly in the public domain in the United States may or may not be free of copyright restrictions and in the public domain in other jurisdiction. At present, one of the only ways to be certain that a particular work is in the public domain worldwide is to see if the copyright holder has dedicated all rights to the work to the public domain by using [http://wiki.creativecommons.org/CC0 CC0].

Creative Commons licenses do not affect the status of a work that is in the public domain under applicable law, because our licenses only apply to works that are protected by copyright. For more information, see [[Before Licensing| our Licensing Guide]] to what you should know before you license a work using CC licenses.

Find out more about [http://creativecommons.org/publicdomain CC's public domain tools], and learn more about [http://en.wikipedia.org/wiki/Public_domain Public Domain].

== When does a work enter the public domain? ==

This varies by country. To see when a work in the [[United States]] enters the public domain see copyright.[http://copyright.gov/pr/pdomain.html gov'][http://www.windows8softwares.com s] public domain page.

Cornell University has also provided a [http://copyright.cornell.edu/resources/publicdomain.cfm handy table about copyright ][http://itshumour.blogspot.com/2010/06/twenty-hilarious-funny-quotes.html term] and the public domain in the United States.

== Creative Commons public domain tools ==

* [[CC0]] (occasionally written as CC Zero) is a public domain dedication that allows copyright holders to place works in the public domain to the extent legally possible, worldwide.
* CC's [http://creativecommons.org/publicdomain/mark/1.0/ Public Domain Mark] allows anyone to mark a work that is already free of copyright restrictions around the world.

See http://creativecommons.org/publicdomain for more information on CC's public domain tools.

Public domain content in practice is any content without copyright. It may be freed from restrictions by the copyright, or the copyright may lapse after a certain time.

The details in practice vary between countries. More information about public domain can be found at [http://en.wikipedia.org/wiki/Public_domain Wikipedia's article on the public domain].

== Appropedia's Public Domain Search ==

[http://appropedia.org/Appropedia%27s_Public_Domain_Search Appropedia's Public Domain Search] was started in late 2007 when it was discovered there was no effective public available. This operates on a completely different method to searches using the Creative Commons marks. It uses a manually maintained index of known sites to be public domain - thus it is does not yield 100% public results, and content must be checked to confirm public domain status. Reliability is expected to improve and feedback by users is encouraged .

As CC public domain tools become widely used, searches based on the CC marks would be expected to a take over from Appropedia's Public Domain Search.

== See also ==

* [[Cultivating the Public Domain]]
* [http://wiki.creativecommons.org/images/0/08/Publicdomainsymbolversion1.jpeg Public Domain Symbol Version 1.0]

{{Translations}}

[[Category:Public domain]]

4.0

2013-10-05T23:44:01Z

Mike Linksvayer: Reverted edits by Mattman1 (talk) to last revision by Mike Linksvayer

CC has embarked upon a versioning process for its core license suite, which will result in version 4.0. The first public discussions of 4.0 were held at CC's [[Global Summit 2011]]. The public process was kicked off with a [http://creativecommons.org/weblog/entry/29639?utm_campaign=newsletter_1111&utm_medium=blog&utm_source=newsletter blog post] laying out some of the key reasons for pursuing 4.0 at this time.

Since CC's launch in 2002, it has versioned its core license suite [[license versions|three times]], the last ([[Version 3|3.0]]) in early 2007. CC licenses constitute a [http://creativecommons.org/who-uses-cc globally-recognized framework], developed in consultation with legal experts and CC affiliate institutions in [[CC_Affiliate_Network|over 70 jurisdictions]]. Over 500 million CC-licensed works have been published by their authors on the Internet. Today, Creative Commons licenses, public domain tools, and supporting technologies are the global standard for sharing across culture, education, government, science, and more.

Version 4.0 is a tremendous opportunity to ensure the license suite is ideally crafted to further CC's [http://creativecommons.org/about vision and mission] over the next decades. Please participate in this important discussion.

=== Goals and objectives ===

Creative Commons staff, board, and community have identified several goals for the next version of its core license suite, tied to achieving CC's goal and mission. These include:

:: ''Internationalization'' – further adapt the core suite of international licenses to operate globally, ensuring they are robust, enforceable and easily adopted worldwide;

:: ''Interoperability'' – maximize interoperability between CC licenses and other licenses to reduce friction within the commons, promote standards and stem license proliferation;

:: ''Long-lasting'' — anticipate new and changing adoption opportunities and legal challenges, allowing the new suite of licenses to endure for the foreseeable future;

:: ''Data/PSI/Science/Education'' — recognize and address impediments to adoption of CC by governments as well as other important, publicly-minded institutions in these and other critical arenas; and

:: ''Supporting Existing Adoption Models and Frameworks'' – remain mindful of and accommodate the needs of our existing community of adopters leveraging pre-4.0 licenses, including governments but also other important constituencies.

=== Organization and purpose of this wiki ===

This wiki is the central location for documenting key discussion topics and suggestions for improving the license suite in version 4.0, together with supporting information and relevant links[http://double-oven-reviews.com/ .] It is intended to supplement, not replace, the CC license discuss email list [http://lists.ibiblio.org/mailman/listinfo/cc-licenses (subscribe)] that will serve as the main discussion forum for the versioning process just as it has with prior versioning efforts.

CC has prepared pages on key topics identified to date. We ask contributors to be thoughtful about placement of additional and related topics, as well as the creation of new pages altogether. Before starting a new page, consider posting the suggestion to the [[4.0/Sandbox|Sandbox]]. We would also prefer that contributors use their real names when editing the wiki.

=== Process ===

As a license steward and steward of the commons, our goal for the process is to ensure utmost transparency and inclusiveness. The 4.0 process is being conducted in line with our prior versioning efforts, with periodic publication of license drafts for public comment and documentation of issue resolution as that occurs[http://becoming-a-psychiatrist.org/ .] One important difference from our past efforts, however, was a formal requirements gathering period that ran for a period of time prior to publication of the first draft. During this period, we strongly encouraged the broadest participation possible by everyone with an interest in the commons and the role open licensing plays in its future.

The primary discussion forum for issues relating to the 4.0 versioning process will be the CC license discuss email list. Please [http://lists.ibiblio.org/mailman/listinfo/cc-licenses subscribe] and add your voice to this important effort.

=== Draft timeline ===
The dates noted below are approximate and subject to change. The number of drafts and public comment periods may vary depending on the number and type of issues raised and how they are resolved, among other things. Watch this page for updates, including major events such as affiliate regional meetings where 4.0 discussions will take place.

{| class="wikitable" style="width: 75%; height: 200px" border="1"
|-
| September 2011
| [https://creativecommons.org/weblog/entry/29639 Launch 4.0 process] at CC Global Summit
|-
| December 2011 thru mid-February 2012
| Requirements gathering period
|-
| April 2, 2012
| Publish [[4.0/Drafts#Draft_1_Details|first draft of 4.0]]
|-
| April to June 2012
| [[4.0/Draft_1/Regional_calls|Public comment]] period #1
|-
| August 2012
| Publish [[4.0/Drafts#Draft_2_Details|second draft of 4.0]]
|-
| August 2012 to February 2013
| [[4.0/Draft_2/Regional_calls|Public comment]] period #2
|-
| February 2013
| Publish [[4.0/Drafts#Draft_3_Details|third draft of 4.0]]; begin porting consultation
|-
| February to September 2013
| [[4.0/Draft_3/Regional_calls|Third public comment period]]; porting consultation
|-
| September 2013
| Publication of [[4.0/Drafts#Draft_4_Details|fourth and final draft]]; begin abbreviated final public comment period
|-
| September/October 2013 (expected)
| Finalize and publish version 4.0 license suite
|}

Various aspects of the license suite are being improved in the version 4.0 licenses. We are gathering and rigorously debating and analyzing these items, and corresponding proposals for handling them, in version 4.0. We encourage the broadest possible engagement in this process. This was a particularly important goal during the requirements gathering stage where everyone was strongly encouraged (and our affiliates expected) to provide feedback on proposed changes and suggest other changes they would like to see. You may add, improve, and discuss specific items in the pages linked below.

'''If you do not find a suitable existing page and category for an item you would like to propose or discuss, please add it to the [[4.0/Sandbox]] where suggestions for new pages will be aggregated.'''

Finally, we encourage contributors to take the time to review [http://wiki.creativecommons.org/License_Versions prior versioning efforts], including relevant discussions of important topics previously debated by the CC community and discussions related to their resolution. Being aware of and taking those into account is important to an effective and efficient process, particularly where a request is made to revisit and potentially change direction in 4.0.

{{#ask:[[Category:4.0 Issues]] [[:+]]
|mainlabel=Item/Category Name
|format=broadtable|
=== Items for discussion ===
}}

===Related pages===
:[[4.0/Sandbox|4.0 Sandbox]]
:[[Porting Project]]
:[[4.0 Drafts]]
:[[4.0/Draft_1|4.0 Draft 1]]
:[[4.0/Draft_2|4.0 Draft 2]]
:[[4.0/Draft_3|4.0 Draft 3]]
:[[4.0/Draft_4|4.0 Draft 4]]
[[Category:4.0]]

Collecting Society Projects

2013-09-25T15:05:05Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Kat Walsh

{{Project}}

This page collects information about the interaction between various Creative Commons jurisdiction projects and collecting societies. It provides an overview of jurisdictions where Collecting Society members can use Creative Commons licenses ('[[#Projects|Projects]]') and of jurisdictions where there are talks between the jurisdiction project and a collecting society in order to achieve this goal ('[[#Negotiations|Negotiations]]').

== Priorities ==

# Increase usage of CC license in jurisdiction
# Increase legal certainty for musicians wishing to use CC licenses
# Increase profitability of CC license users
# Support non-exclusive collecting societies

'''NOTE: When interacting with Collecting Society representatives it is important to be cordial with them and provide information about Creative Commons usage (see [[Case_Studies|case studies]], [[Documentation|documentation]] and [[Metrics|metrics]]) and integrating Creative Commons licenses (see: [[CCPlus|CC+]], [[CcREL]] and [[Web_Integration|web integration]]). Be be mindful of the overall [[#Priorities|priorities]] and ensure that you are in line with the arrangements made as part of ongoing [[#Projects|projects]]'''

==Projects==

* [[Collecting Society Projects/Netherlands]]: pilot project between CC Netherlands and [://mmm.bumastemra.nl/en-US/Home.htm BUMA/STEMRA] (Collecting society for composers and songwriters) launched on 23 august 2007 and currently running.
* [[Collecting Society Projects/Denmark]]: trail agreed between [://mmm.ksaday.com K][://mmm.koda.dk/english ODA] (Collecting society for composers, songwriters and music publishers) launced on 31 january 2008 and currently running.
* [[Collecting Society Projects/Sweden]]: On 27 may [://mmm.stim.se/stim/prod/stimv4eng.nsf STI][://mmm.ksaday.com/2012/05/merubah-word-ke-pdf.html M] (Collecting society for composers, songwriters and music publishers) announced a two year trail that allows for their members to use CC-NC licenses. Currently running without involvement by CC-Sweden.
* [[Collecting Society Projects/France]]: Pilot project between CC-France and [://mmm.sacem.fr/WportailSacem/jsp/ep/home.html SACEM] (Collecting Society for original music composers, authors and publishers)

==Negotiations==

* [[Collecting Society Projects/Italy]] (page is currently empty): There are currently negotiations between CC-Italy and [://mmm.siae.it/index.asp SIAE] (Italian Society of Authors and Publishers, representing all sorts of authors and publishers (not only in the field of music))
* [[Collecting Society Projects/Australia]] There are currently negotiations between CC-Australia and [://mmm.apra-amcos.com.au APRA] (Collecting Society for original music composers, authors and publishers)
* [[Collecting Society Projects/Germany]] (page is currently empty): There are currently negotiations between CC-Germany and [://mmm.vgwort.de/ VG-W][://mmm.ksaday.com/2012/05/obat-sakit-gigi.html o][://mmm.ksaday.com/2012/05/rumah-unik-terbaik-di-dunia.html r][://mmm.vgwort.de/ t] (Collecting Society for authors of literary, journalistic and scientific works)

=== links (to be moved elsewhere) ===

* APRA "Creative Commons" page, ://mmm.apra.com.au/writers/forms_and_guidelines/creative_commons.asp
* APRA CEO Brett Cottle's article on ArtsHub, ://mmm.artshub.com.au/au/news.asp?sId=70075
* Opt APRA, ://mmm.optapra.net - [://mmm.onlinepsychology-degree.org ://mmm.onlinepsychology-degree.org]
* Elliott Bledsoe's blog entry after the CCau Music Forum, ://ccelliott.blogspot.com/2007/11/post-music-industry-forum-reflections.html
* Reform APRA MySpace with 'I support reforms for APRA' pledges from Australian musicians, ://mmm.myspace.com/optoutofapra

* Improbable Match: Open Licences And Collecting Societies In Europe, ://mmm.ip-watch.org/weblog/index.php?p=1291

CcHost

2013-09-25T15:04:55Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

[[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[http://courtreportingagency.com ,] 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.sepatuonline.org jual sepatu online]
* [http://www.jualjaketkulit.org jual jaket kulit]
* [http://howtogetridofforeheadacne.blogspot.com/ Learn More]
* [http://modifikasiku.info modif motor]

----

= 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. [http://wiki.creativecommons.org/Whats_A_Certified_Nurse_Assistant%3F Apache]

====== 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/Ceiling_Fan_Troubleshooting Linux]

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

Version 3

2013-09-25T15:04:44Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Kat Walsh

= 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 <span class="plainlinks">[http://bedding-sets.exaviews.com/black-and-white-bedding/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">page]</span> (''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]]
[[Category:3.0]]

Salon

2013-09-25T15:04:34Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

{{Infobox|
CC Salons are global, informal events focused on building a community of artists, developers, and creators of all kinds around Creative Commons licenses, standards, and technology. The first event took place in San Francisco in 2006 with the idea to replicate in other locations internationally. Since then salons have sprung up in cities [[All Salons|around the world]]. Whether you're familiar with Creative Commons or are brand new to the concepts behind it, we encourage you to check out a salon near you.

The format for each event varies based on the location, but the overall concept is simple. CC Salons are open forums for people who are interested in the issues surrounding Creative Commons and global participatory culture. If you're interested in attending - check out the [[#Upcoming_Salons|upcoming salons]]. If your city doesn't have one - feel free to [[#Resources_for_starting_your_own_CC_Salon|start your own]]. Check out the [[#Resources_for_starting_your_own_CC_Salon|resources]] for starting your salon for extra info.
}}

== Resources for starting your own CC Salon ==

There are a few important items to consider before you start a Salon. These are by no means requirements but rather guidelines and tips that we have discovered in planning our own Salons - they should be seen as a starting point meant to spark ideas for your own Salon as they are all unique. The list format (and some of the content) is very much inspired by the [http://dorkbot.org/startadorkbot/ wonderful folks at dorkbot].

===Theme===
It is important to remember that each location will have its own unique slant on the Salon format. While the Salons are meant to function generally as a way for people interested in CC to meet up and socialize, Salons can (and should) focus on a specific theme - the arts, computer programming, social networking, etc. This theme needn't be static - it can change every Salon - but it helps to get speakers who will be able to speak on similar topics.

===Frequency===
To ensure a strong turnout, it is important to understand how often your audience is willing to meet up. Similarly, think about how many presenters and projects you can rotate through on a continuous basis. These two factors could mean a Salon happening every month, every 6 months, or even every year - each locale is different. The better you can space the Salons according to your audience and presenters, the better turn out and dialogue you will have, making the Salon more successful as a whole.

===Venue===
Having the Salon in a consistent space will help ensure repeat attendance. Reach out to local art galleries, bars/pubs, and even universities to see if they can offer you a block of time to use their space for free. The space doesn't need to be extravagant and it is good to remember that a small but full space is more conducive to discussion than a large but empty one.

===Equipment===
It is important to allow presenters the ability to showcase media - be it video, audio, slideshow, or other. Speakers and a projector aren't essential to the Salons but they will make them run much smoother. If your venue doesn't have those things on hand, ask around to your friends and co-workers. More likely than not someone will have something that will work.

===Cost===
All of the CC-run Salons are free and open to the public and there is little to no money spent on additional resources. We encourage you to make do with the sparsest of budgets - in regards to promotion we are happy to [http://creativecommons.org/weblog blog] any Salons happening and [http://creativecommons.org/contact/#community CC's mailing-lists] are a great way to promote as well.

===Format===
CC Salons tend to be run in an open manner, allowing people to mingle and socialize as they see fit. Outside of this there are often two to three presenters who will speak to their own use of CC licenses, be it personal or for a larger organization they are part of. This is by no means a rigid guideline but rather a starting point - feel free to screen a film, hold a panel discussion, have a live music performance, or anything else that may be relevant. Most importantly, remember to have fun!

===Using CC's Logos and Marks===
Use of CC's logos and trademarks, even in connection with a CC Salon, is subject to our [http://creativecommons.org/policies Policies]. You should review those before using our logos and marks. If you are interested in using our logos and marks in ways not contemplated by that policy, or if you are interested in developing a new logo for your Salon that incorporates one of our protected trademarks or logos, please ask us first by contacting us at salon[at]creativecommons.org. You should also contact us first if you are interested in creating new swag that incorporates our logos or marks, whether or not you plan to give them away or sell them.

===More Resources===

* [[Announcement List]]
* [[Speaking at Salon]]
* [[Start Your Own Salon]]
* [[Salon Past Events|Past Events]]
* [[Salon Future Presenters|Future Presenters]] (To Be Setup)
* [[Salon Ideas|Ideas]]
* [[Salon Background|Background Information]]
* [[Salon External Links|External Links]]
* [http://www.sepatuonline.org sepatu online]
* [http://www.jualjaketkulit.org jual jaket kulit]
* [http://modifikasiku.info modifikasi motor]
* [http://howtogetridofforeheadacne.blogspot.com/ Read More]

== Upcoming Salons ==
{{#ask:
[[date::>{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
[[Category:Event]][[EventType::Salon]]
| ?date=
| ?Location=
| ?EventType=
| ?EventCategory=
| ?Mainurl=
| ?end_date=
| format=template
| template=Event List
| sort=date
| limit=8
| link=none
| searchlabel=<div style="text-align:center;width:100%;padding-top:10px;padding-bottom:10px;background-color:#e0e0e0; position: relative;overflow: visible;margin-bottom:10px;border: 1px solid #c0c0c0;">
<span style="font-size:125%;">'''More Events'''</span></div>
}}

== Past Salons ==
{{#ask:
[[date::<{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
[[Category:Event]][[EventType::Salon]]
| ?date=
| ?Location=
| format=ul
| sort=date
| limit=20
| searchlabel='''More Past Events'''
}}

== All Salons ==
* [[CcSalon_Quito|Quito, Ecuador]] April 26, 2012
* [[Muscat Salon|Muscat, Oman]] May 7, 2012
* [[Montreal Salon]] December 21, 2010
* [[Copenhagen Salon]] November 16, 2010
* [[Copenhagen Salon]] April 27, 2010
* [[Beirut Salon]] April 16, 2010
* [[Istanbul Salon]] April 18, 2010
* [[Seoul Salon|Seoul]] March 17, 2010
* [[Delhi Salon|Delhi]] February 28, 2010
* [[NYC_Salon|New York]] March 3, 2010
* [[Bangalore Salon|Bangalore, India]] December 2, 2009
* [[Amman_Salon|Amman, Jordan]] November 16, 2009
* [[Bangkok Salon|Bangkok]] September 12, 2009
* [[Alps Salon|Vienna]] September 11, 2009
* [[Boston Salon|Boston]] February 25, 2009, co-hosted with Creative Commons, Participatory Culture Foundation and Pecha Kucha Boston
* [[Berlin Salon|Berlin]] February 26, 2009 (together with the Openeverything Focus event)
* [[NYC Salon|NYC]] June 18, 2009
* [[Amsterdam Salon|Amsterdam]]
* [[Austin Salon|Austin, TX]]
* [[Berlin Salon|Berlin]]
* [[Beijing Salon|Beijing]]
* [[Bogotá Salon|Bogotá]]
* [[Boston Salon|Boston]]
* [[Brisbane Salon|Brisbane]]
* [[Chennai Salon|Chennai, India]]
* [[Johannesburg Salon|Johannesburg]]
* [[London Salon|London]]
* [[Los Angeles Salon|Los Angeles]]
* [[NYC Salon|NYC]]
* [[Saigon Salon|Saigon (Ho Chi Minh City)]]
* [[San Francisco Salon|San Francisco]]
* [[Taipei Salon|Taipei]]
* [[Toronto Salon|Toronto]]
* [[Tunis Salon|Tunis]]
* [[Warsaw Salon|Warsaw]]
* [[Alps Salon|Vienna]]

[[Category:Salon]]
{{Project}}

Partner Interface

2013-09-25T15:04:23Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

[[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 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 storage options. [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

CcMixter

2013-09-25T15:04:13Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

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] and [http://www.sepatuonline.org Toko Sepatu Online]?<br />
> [http://www.jualjaketkulit.org jual jaket kulit] - [http://modifikasiku.info modifikasi motor] - [http://kesehatan-ku.info kesehatanku] - [http://howtogetridofforeheadacne.blogspot.com/ treat for acne]

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]]

Web Services

2013-09-25T15:04:02Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

[[Category:Developer]]
[[Category:Integration]]
[[Category:Technology]]

Creative Commons provides a set of web services which allow application developers to integrate license selection with their own software. The web services are designed to be a more flexible replacement for the HTML-only [[Web Integration Guide|partner interface]].

== Background ==

Creative Commons provides a REST web service interfaces. Through the CC web service API, you can generate any of the Creative Commons licenses, including Sampling. The web services API 1.5 is frozen and can be considered stable. A development API is also supported, where new features are prototyped. The development API should not be considered stable. The API presents the following layers of abstraction:

* a selection of license "classes" available (standard, public domain, GPL, etc)
* a set of questions (along with possible responses, if applicable) that must be answered in order to issue a license
* an interface to generate the license URL, along with description RDF for a given license and set of answers

Sourcecode for the web services is available at [http://code.creativecommons.org code.creativecommons.org]. Server source is maintained in the [http://code.creativecommons.org/viewsvn/api/ api module]. Sample client implementations are maintained in the [http://code.creativecommons.org/viewsvn/api_client api_client module].

The web services use an XML representations of the licenses and their questions. The XML files and XSLT transformations used for this process are also stored in the '''license_xsl''' module in Subversion. ChooseLicense.xml represents the available Creative Commons licenses, along with the "questions" which need to be answered to select a particular license, in an XML format. Combined with an XSLT file, this allows us to easily plug the license engine into different environments.

== Documentation ==

Two versions of the REST web service are currently maintained, the 1.5 version and development version. The 1.5 version is a stable API and is only updated with new jurisdictions as they become available. The Development version is where new features are implemented and API changes may occur; at some point this will be branched again and versioned. See the [[Web Services Plan]] page for future web service ideas and version details. [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

The stable REST interface is rooted at http://api.creativecommons.org/rest/1.5. Documentation of methods available is available at http://api.creativecommons.org/readme_15.html.

The development REST interface is rooted at http://api.creativecommons.org/rest/dev. Documentation and a summary of changes since the last stable version is available at http://api.creativecommons.org/readme_dev.html.

{{Challenge Enabled}}
[[Creative Commons Aim and Influence]]

Integrate

2013-09-25T15:03:56Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Mike Linksvayer

__NOTOC__
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Integrating Creative Commons License Information:</strong> One of the most useful attributes of using Creative Commons licenses is the quality metadata standards that can be used to both mark and identify CC licensed work. This can be anything from simply adding the ability for a media player to show the license information of a song to a full-fledge, RDFa using, semantic-web promoting web application for people to upload, share, and remix content.
<br />
Creative Commons is devoted to making it easy for developers to add license metadata functionality to all types of applications. Our tools are divided into two areas; Desktop and the Web.
</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|
== [[Desktop Integration]] ==
Much of the functionality that is needed to integrate CC license information with desktop applications is available in the [[liblicense]] package. There is also [[License tagger|License Tagger]] which is a small proof of concept application written in python that utilizes [[liblicense]] to embed license metadata information into files. For more information see the main [[Desktop Integration]] page.
}}
{{PageColumn|
== [[Web Integration]] ==
Creative Commons has developed [[LicenseChooser.js]] which provides a lightweight method for integrating license selection into web applications. It does this by utilizing such technologies as [[RDFa]]. Additionally, Creative Commons has also developed a [[Web Services]] interface that can be used to enable license selection in online services. For more information, see the main [[Web Integration]] page.
}}

=== See also: [[Developers]] ===
</div>

<br clear="all"/>

[[Category:Developer]]

Broadcasting

2013-09-25T15:03:51Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Jaxaza

{{Project}}

This page collects information about the interaction between various Creative Commons jurisdiction projects and broadcasters. It provides an overview of jurisdictions where broadcasters are using Creative Commons licenses ('[[#Projects|Projects]]') and of jurisdictions where there are talks between the jurisdiction project and a broadcaster in order to achieve this goal ('[[#Negotiations|Negotiations]]').

== Priorities ==

# Increase usage of CC license in jurisdiction
# ...

'''NOTE: When interacting with broadcasting representatives it is important to be cordial with them and provide information about Creative Commons usage (see [[Case_Studies|case studies]], [[Documentation|documentation]] and [[Metrics|metrics]]) and integrating Creative Commons licenses (see: [[CCPlus|CC+]], [[CcREL]] and [[Web_Integration|web integration]]). Be be mindful of the overall [[#Priorities|priorities]] and ensure that you are in line with the arrangements made as part of ongoing [[#Projects|projects]]'''

==Projects==

* [[Broadcasting/Denmark]] [http://www.dr.dk/ Danish Broadcasting Corporation] features CC-licensed images and content on its website, and it was the first broadcaster to purchase and air the CC-licensed documentary, Good Copy Bad Copy.
* [[Broadcasting/Germany]] In November 2007 the Norddeutscher Rundfunk (NDR), a public radio and television broadcaster in Germany’s national broadcasting consortium ARD, [http://creativecommons.org/weblog/entry/7838 announced] that they will use CC licenses for some of their programs.
* [[Broadcasting/Netherlands]] VPRO [http://creativecommons.org/weblog/entry/18128 released] 2 full length (and one more coming soon) documentaries under CC-BY-NC-SA licenses, aired 10 days prior. VPRO has also implemented CC licenses for its [http://3voor12.vpro.nl/plundertmusea/kaft/index.jsp 3voor12 Plundert Musea] project, which makes available samples from rare musical instruments, and furthermore the Dutch broadcaster also promotes CC music on its radio show [http://www.vpro.nl/programma/wissel/ Wissel].
* [[Broadcasting/Norway]] November 27, 2009 [http://nrkbeta.no/2009/12/18/bergensbanen-eng/ over 1,2 million Norwegians watched] parts of “Bergensbanen” on NRK2. The clip was released under CC BY-SA in HD over BitTorrent, and a successful competition allowed for remixes. The project was featured on prominent sites such as [http://boingboing.net/2009/12/19/norwegian-public-bro.html BoingBoing].
* [[Broadcasting/Switzerland]] http://openbroadcast.ch has the has the night Sunday/Monday (00:00 - 06:00) dedicated to CC music only (http://openbroadcast.ch/de/program).
* [[Broadcasting/UK]] To date, several departments in the BBC publish content under Creative Commons licenses: album reviews ([http://www.bbc.co.uk/music/release/c2w6/ for example]) and a partnership with MusicBrainz, a community music metadatabase that uses CC licenses. Furthermore, under other licensing conditions, the BBC has opened up its website to developers at backstage.bbc.co.uk. It also offers television and radio programs to stream or download through its iPlayer, although the player’s format has been the source of some criticism.
* [[Broadcasting/Colombia]] Although a small experience, [http://altair.udea.edu.co/ Altair] is a good example of CC use in broadcast sector. Altair is the hipermedia and sound lab of the Antioquia University that is located in Medellin- Colombia (second biggest public university in the country). All their programs are CC, they use and promote CC material (music mainly) and they adopt CC BY NC SA for their own productions.

==Negotiations==

* [[Broadcasting/Australia]]
* [[Broadcasting/Denmark]]
* [[Broadcasting/Germany]]

=== links (to be moved elsewhere) ===
* http://cc.aljazeera.net/ - select broadcast quality footage that Al Jazeera has released under various Creative Commons licenses, mostly CC BY.
* KQED's QUEST uses CC licenses for its photostream: http://www.flickr.com/photos/kqedquest/. More info at http://creativecommons.org/weblog/entry/8577 [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

Kenya

2013-09-25T15:03:46Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Sinyoritaa

{{Jurisdiction
|jurstatus=Active
|country code=ke
|twitter=http://twitter.com/CCKenya
|region=Africa
|affiliated=CIPIT, Strathmore Law School
|affurl=http://www.cipit.org
|afffocus=Intellectual Property, Information Technology
|afftype=academic institution
|affiliated2=National Council of Law Reporting
|affurl2=http://www.kenyalaw.org
|afffocus2=Kenyan Courts and Laws
|afftype2=governmental body
|plead1=Michael Murungi
|pemail1=mmurungi@kenyalaw.org
|ptitle1=Chief Executive, National Council for Law Reporting
|plead2=Isaac Rutenberg
|pemail2=iruten@gmail.com
|ptitle2=Director, CIPIT
|plead3=Lillian Makanga
}}
AFFILIATE TEAM ROADMAP, CREATIVE COMMONS
Jurisdiction: Kenya (East Africa - Africa)
Date submitted: 6 March 2013
Timespan of this roadmap: January 2013 to December 2013

Public lead: Centre for Intellectual Property and Information Technology law (CIPIT)

Dr. Isaac Rutenberg [Intellectual property and Social media] (Director and Lead Consultant) holds a J.D. from Santa Clara University School of Law (California, 2011) and a Ph.D. in Chemistry from California Institute of Technology (2005). He is a Registered Attorney with the California State Bar and he is registered to practice before the US Patent and Trademark Office.

Lillian Makanga Wothaya [Research and evangelism] holds an LLB (Hons) degree from the Catholic University of Eastern Africa (CUEA) a post graduate diploma in law from the Kenya School of Law and currently awaiting admission to the Bar as an Advocate of the High Court of Kenya. She has previously worked at MMC Africa Advocates where she gained experience in the practice of Intellectual Property Law as well as other legal disciplines. As part of CIPIT she is involved in the IP Clinic which provides legal advice and cost effective solutions to innovators on all aspects of their IP Rights. In addition, she analyses developments in Kenyan and International IP Case law as well as the implications on the Intellectual Property Landscape.

Douglas Gichuki [Open data and IT policy] (Research Fellow and Assistant Lecturer). Mr Gichuki holds an LLB degree from CUEA and an LLM in Intellectual Property, Information Technology and Internet Law from Norwich Law School (UK). His doctoral research focuses on legal frameworks for financing small to medium enterprises in technology.

Pelase Visit:

* [http://adrian-fh98.web.unair.ac.id/ Informasi Umum]
* [http://www.tokobungasabana.com Toko Bunga]
* [http://andreweweww.wordpress.com/ Curhat Blog]
* [http://mariposa-store.com/ Jual Sepatu Online]

Legal lead: National Council for Law Reporting

Mr . Michael Murungi [Information technology specialist] is a manager, law reporter and ICT legal expert from Kenya. He is the Chief Executive/Editor of Kenya’s National Council for Law Reporting, the official publisher of Kenya’s public legal information, including the decisions of the superior courts of Kenya and the Laws of Kenya. He is the author of Cyber Law in Kenya and Kenya's designated contributor to Wolter Kluwer’s International Encyclopaedia of Cyberlaw. He has been a legal columnist for CIO, East Africa’s premier ICT magazine and a lecturer in cyberlaw at the Catholic University of Eastern Africa. He made key contributions towards the enactment of the Kenya Communications (Amendment) Act, 2009. He has undertaken local and international consultancy and speaking engagements. Michael holds a Masters Degree in ICT law and has professional training in legal practice, management and arbitration

Mr. Alex Gakuru [Regional coordinator Africa] is the Founder and Chair of ICT Consumers Association of Kenya, an ICT consumer rights advocacy group. He is the Executive Director-Content Development and Intellectual property (CODE-IP) Trust, a non-profit organization focusing on creating an enabling environment for local content development and its intellectual property protection. He is an assertive advocate of consumer rights and he represents consumer interests through various platforms locally and internationally. He is an Elected Council Member at the Free and Open Source Software Foundation for Africa and he took part in global Internet Policy formulation as the elected Africa’s representative at ICANN’s Non-Commercial Users Constituency Executive Committee (NCUC). His NCUC term ended in December 2013. Since August 2012, he is the Regional Coordinator – Africa for Creative Commons.

Sponsor :
- [http://www.optimaweb.co.id/ Internet Marketing]
- [http://www.optimaweb.co.id/jasa-seo Jasa SEO]
- [http://www.optimaweb.co.id/iklan-online-google-adwords Iklan Online]
- [http://www.optimaweb.co.id/bisnis-online-lokal Bisnis Online Lokal]
- [http://www.optimaweb.co.id/promosi-website Promosi Website]

Date of latest MOU in jurisdiction N/A

Vision

Why is Creative Commons important for the jurisdiction?

Kenya is home to a thriving cultural industry. These varied creatives require access to shareable resources that facilitate remixing and creativity. It is, however, important to deepen the understanding of new users in Kenya of CC licenses and their usefulness. The increasing use of CC licenses in Kenya will help enhancing the visibility and accessibility of Kenyan creativity in the global networked space.

Kenya is also home to a vibrant if querulous democracy. We are a multi ethnic society comprising 42 odd communities. We hope to harness the wealth that can come from such cultural and linguistic diversity through the creative commons movement. Kenyans are marked in their early adoption of technology to enhance the democratic discourse, examples of these include the shoot from the hip activism of #KOT (Kenyans On Twitter). We hope to use CC licensing in Kenya to support newly realisable democratic freedoms through new media conversation and mobilizing and by enabling wide-spread access to knowledge and information.

What do you think makes a successful jurisdiction project?

A successful jurisdiction project effectively promotes the use of CC licenses in their jurisdiction for the benefit of the various communities in the country. We wish to do this by bringing what is good of these communities to the wider African and global market; translating CC license deeds into local languages is in our opinion key for achieving this.

How do you see the jurisdiction project contributing to the CC Affiliate Network?

We want to help adding to the commons local content and a variety of indigenous and contemporary Kenyan works available under CC licenses.

Community

Describe the communities that are currently active in the project.

1. Educational institutions – schools, universities, colleges, etc.
2. Libraries
3. Cultural institutions – museums, galleries, etc.
4. Government organizations
5. Technology-based companies
6. Open data and technology-focused communities
7. Professional Associations & non-profits
8. Creators – artists, photographers, media producers.

How will you continue to engage with these communities?

We will increase our engagement through: Conference talks & workshops, a Kenyan CC website, Twitter, supporting interested parties with implementing CC licenses.

Describe the communities (existing or new) that you plan to focus on during the timeframe covered by this roadmap?

Target organizations: Bloggers Association of Kenya; KECOBO; The Creativez; Power 254, Media houses; technology hubs such as iHub; Universities; and civil society such as FOSSFA.

How do you plan to engage with these communities?

• Use of social media to establish a linked CC Kenya affiliate
• Implementation of a Creative Commons website
• Case studies and showcase examples
• Compilation of list of Kenyan organizations & individuals using Creative Commons
• Development of a copyright, open licensing course delivered online and face-to-face at the CIPIT
• Open licensing salons, webinars, conference presentations, and events
• FAQ, how-to’s and practical guides to aid decision making and implementation
• Policy guidelines and recommendations
• Development and profiling of business models related to use of Creative Commons, for instance the freemium model.
• Making the case to government institutions for an open license for government content by using the National Council for Law Reporting as a demonstrative case study.

Priority Goals

What are the most important focus areas on which the Affiliate Team will work during this time period?

Focus area: Outreach and deepening license knowledge and use

• Given the newness of the CC team in Kenya, it is essential to build a strong community that understands the licenses, promotes sharing and remix culture. This would be a good starting point to better inform and deepen the use of the CC licenses and to spread their benefits.
• We also wish to have a more diffused knowledge of the CC licenses in the jurisdiction. This includes encouraging the community to adopt the free licenses in distributing their work and expanding gradually to other areas.

Focus area: Legal interface

• As the Legal Lead, the NCLR will drive the CC Kenya team in interfacing with the legal and government communities. All CC work and information will be located on (or linked from) the NCLR website to be accessed freely by the public. Other legal issues will be addressed and dealt with as appropriate.

Focus area: Application of CC to various topics of interest

• At the CC Africa Regional Meeting in 2012, a number of topics were identified as of critical importance to engage with CC and the CC Kenya team. These included open education resources, government adoption, health, advocacy, ICT development, business models, and transparency.
• The CC Kenya team will actively engage stakeholders such as the School of Open and the Open Data initiative within the Government of Kenya to see that the above topics are areas of focus.

Focus area: Website development and update

• This includes things like: a collection of case-studies or organisations using CC in Kenya (wiki); Acknowledge all CC KE volunteers and organizational supporters; Put more information about Creative Commons Licensing. This also involves the building of a mailing list through which we can keep the community informed and updated.
• Why is it important? This will be a key source of information about Creative Commons Kenya.
• Who benefits? All CC Kenya stakeholders

Focus Area: Increased engagement with International and regional stakeholders

• Frequent interaction with already established CC organizations will hasten the progress of this project. We are confident that tapping into the experience of existing CC communities will enrich the growth of the project through their support and contribution.

Focus area: In-depth training of selected individuals

• There exists a critical need in the region for individuals with in-depth training in areas of copyright, licensing, and business development around the CC philosophy of open access. This level of knowledge exceeds the basic understanding that is needed by most users of CC licenses. Typically, this level of specialized knowledge resides in lawyers or other IP specialists, but such knowledge is not common in East Africa.
• We will address this need primarily through training of interns at CIPIT and/or NCLR. One or more interns will be engaged and tasked with learning the necessary background and practical knowledge to be able to advise CC users. It is hoped that the intern(s) will use the skills gained to further the CC cause even after their internship is completed.

Focus Area: Identify source(s) and secure funding for a Creative Commons Kenya affiliate

• While we will largely engage volunteers for a lot of the CC work, a basic minimum level of funding will be required to establish a physical presence and at least partial support for some people and activities. Localizing legal tools, promoting public awareness, translation of licenses to local languages, building out a web presence, all require funding and effort. Our focus must therefore include finding and securing core base level of funding.

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.

Focus Area: Outreach and Increasing License Use

• Project Output: Events / Blog posts / video & photo coverage of the events. Also FAQs and a practical manual (i.e., a toolkit) located on the CC Kenya website.
• Expected start date - Expected date of completion: February to November 2013.
• Team Member(s) Responsible: ALL, spearheaded by the Public Lead
• How will this output help achieve your goals? Face to face meetings will help us improve the concept of a local community and will help us understand what are the community needs in our area.
• Tentative schedule of events to be provided.

Focus Area: Legal standardization

• Project Output: translation of the license summaries; CC content available or linked on NCLR website, synchronized CC public sensitization events and create an interactive blog
• Goal of Output: To secure government support & provide information to the public; to provide translated licenses
• Expected start date: February 2013
• Expected date of completion: continual
• Team Member(s) Responsible: NCLR

Focus area: Application of CC to various topics of interest

• Project Output: Engagement of the CC initiative with stakeholders in various sectors including music, publishing, film, government, and academia.
• Goal of Output: Increased awareness that CC principles apply beyond the legal field
• Expected start date: March, 2013
• Expected date of completion: 2013
• Team Member(s) Responsible: Douglas Gichuki, Michael Murungi

Focus area: Website

• Project Output: Modern website with features such as a news feed, information about Creative Commons, and a spotlight on Creative Commons content & initiatives in Kenya.
• Goal of Output: To connect with the public & provide information.
• Expected start date: March, 2013
• Expected date of completion: 2013
• Team Member(s) Responsible: Douglas Gichuki

Focus Area: International and regional engagement

• Project Output: material support, active consultancy engagement with regional and international stakeholders (e.g., CC affiliates across Africa, CC HQ, etc.)
• Goal of Output: to share experience and knowledge, cultivate interaction through international seminars and social media
• Expected start date: in progress
• Expected date of completion: continual
• Team Member(s) Responsible: Dr. Isaac Rutenberg

Focus Area: In-depth training

• Project Output: One or more individuals with significant training in the areas of copyright law, licensing, business development based on the Freemium model, etc.
• Goal of Output: To begin the process of creating a community of highly-trained individuals who are able to spread the use of CC licenses, advise users of the licenses, and continue training others in such areas.
• Expected start date: March 2013
• Expected date of completion: continual
• Team Member(s) Responsible: Dr. Isaac Rutenberg

Focus Area: Fundraising

• Project Output: Kshs awarded/granted
• Goal of Output: To secure sustainable funding.
• Expected start date: February 2013
• Expected date of completion: ongoing, but the first round of applications to be completed in April 2013
• Team Member(s) Responsible: All.

Metrics

• How will you evaluate your impact on focus-area 1 (Outreach)? Number of participants at the events & stakeholder groups represented. Numbers of documented cases using CC licenses.
• How will you evaluate your impact on focus-area 2 (Legal Standardization)?
The availability, download rate, and number of known links to CC licenses will be the primary factor in evaluating this area. Other measures include interactions with the creative community and inquiries by would-be users.
• How will you evaluate your impact on focus-area 3 (Application to various topics)?
Frequency of engagement with the sectors identified in this Roadmap; case studies of such engagement.
• How will you evaluate your impact on focus-area 4 (Website)?
Website traffic (eventually, as the site garnishes attention). Also, average number of new posts per month and average number of updates per month.
• How will you evaluate your impact on focus-area 5 (International and regional interaction)?
The number of International meetings/seminars/interactions engaged per annum and internal audits done per annum to measure conformity progress with CC international standards.
• How will you evaluate your impact on focus-area 6 (In-depth training)?
The skill level and competency of the intern(s) trained by CIPIT and/or NCLR will be evaluated to determine impact.
• How will you evaluate your impact on focus-area 7 (Fundraising)?
We will measure this area by our ability to meet our financial needs via funds raised.

Resources Required

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?

• Creative Commons Kenya has commenced operations with the team members described in the "Affiliate Team Information" section. These team members already cover a wide spectrum of expertise. We will seek to add to this expertise if and when the need arises. We will also work on building a broad network of volunteers and supporters.
• We will seek out and engage one or more interns to learn the in-depth knowledge and training identified in the above goals.

How will you involve these people?

• Some involvement is already present. We will have bi-monthly meetings and supporters will be acknowledged on the website.
• We will call for volunteers and interns through announcements on the website, social media, and in universities.

What technology resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?

• Website development will require an experienced website developer and possibly an individual with artistic design experience.

How will you obtain these technology resources?

• We will advertise a call for volunteers and may seek assistance from the IT department at Strathmore and/or other universities.

What material resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?

• Generally, there is a lack of practical and instructional information available to would-be users of the CC licenses in Kenya. The CC Kenya website will be a perfect forum for disseminating such information, which we plan to generate as a collaborative effort between the Public and Legal Lead organizations. For example, CIPIT has been developing a practical manual of IP identification, acquisition, and use. This model can be adapted and a similar manual will be created for the CC Kenya website. Furthermore, we will generate a FAQ section that will help CC Kenya reach those in most need of basic assistance.
• From a variety of recent events such as the launch of the School of Open, it has become clear that there are numerous individuals in Kenya with an interest in driving the success of an open content platform. There is not, however, a centralized list of such individuals. We will create such a resource and make it available on the CC Kenya website.
• We were very happy to have received SWAG from CC international for our inaugural CC 10 birthday event in Nairobi. These were very popular. We will be requesting more support of this kind from CC International.

How will you obtain these material resources?

• The manuals and FAQ content will be generated in-house at the Public and Legal Lead institutions.
• Advertising and promotional materials will be requested via mail from CC.

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?

• Regular meetings and open discussions among team members.

How will you communicate the project's on-going progress and setbacks within the jurisdiction and the CC Affiliate Network?

• Emails, ccAfrica mailinglist, our website, social media platforms, meetings
• Updates to the African Regional Coordinators

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

• Creative Commons wiki and our website (and through all of the above communication tools for that matter)
• Comments on the roadmap

Collaboration

How could the jurisdiction's plans help drive or support other jurisdictions' activities?

• CC Kenya follows on an illustrious list of African jurisdictions using CC. We have the good examples from South Africa, Nigeria, Egypt, Uganda and others to learn from. We intend to actively court these CC jurisdictions for mentoring to assist us especially with the use of the 4.0 license.
• We intend however to document our experience of setting up a CC affiliate team and disseminate it freely for other jurisdictions considering setting up such teams. We also intend to collaborate and offer support for sister CC jurisdictions by participation in, e.g., face to face meetings and workshops.

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

• We are enamored by the jurisdictions that have been able to build CC communities amongst very culturally diverse communities. CC Brazil and CC South Africa are good examples we want to learn from.

Would you be interested in mentoring new jurisdiction teams? Yes.

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

Suggest three possible projects on which you can collaborate with other teams on a regional level.

The Kenya CC team hopes to contribute to collaboration in Africa by:
1. Networking with team members from other jurisdictions for example by inviting them to events in Kenya to share their experiences or sharing success stories broadly about the application of CC licenses.
2. In addition, the Kenya CC legal team is to work closely with colleagues from South Africa, Egypt and Nigeria, and Uganda who have in-depth knowledge of CC licenses through their experiences in license porting, and in the use of the current 3.0 license.
3. We would like to collaborate for the deliberations on the 4.0 license.

How do you plan to contribute to these projects? Sharing of information and on an ad-hoc basis.

Translation

In what language(s) will you promote CC in the jurisdiction and why? At this point in time, it is only feasible to promote CC licenses in English. Yet, we aim at translating the Commons Deed into Swahili. We also intend to have the deed translated to various local languages.

In which of these languages are licenses already available? English; the unported license.

Developers

2013-09-25T15:03:34Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Mike Linksvayer

'''Welcome to the CC Developer Community!''' This is where you'll find all
about the technologies and software products that CC uses to push
forward our mission to maximize digital creativity, sharing, and
innovation.

== Get Involved ==

All of the projects developed at Creative Commons are open source
software, and just like most open source projects, outside involvement
is key to its success. But you don't have to be a software developer
to join us--we'd love to have you in the discussion if you're a user
researcher, designer, translator, or just interested in the topic.

; E-mail
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
; IRC
: Chat with us real-time on [irc://irc.freenode.net/cc irc] (Freenode, #cc)

Coming soon: public team meetings, and other ways to engage.

== Projects ==

; [[OpenHome]]
: A Creative Commons homepage with your content
; [[Summer of Code 2013|Google Summer of Code 2013]]
: Ideas and more.
; [[Translate|Localization]]
: Find out how to help the Creative Commons community with translations.

== Core Technologies ==

; [[RDFa]]
: Standard for adding machine-readable statements to web pages.
; [[CcREL]]
: Language for adding licensing [http://combinest.blogspot.com/ information] to web pages.
; [[LRMI]]
: Language for describing educational resources on the web.
; [[Liblicense]]
: Library for embedding licensing metadata into files of various formats. (note: now somewhat out of date!)

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Marking your work with a CC license

2013-09-25T15:03:29Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Color Me Hot

==Best Practices for Marking Content with CC Licenses: Creators ==

<div style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:60%">
NOTE: This page is for creators and copyright owners who are looking to CC license their own work. If you are looking for the best way to mark CC-licensed work as a user, see http://wiki.creativecommons.org/Marking/Users. If you own a content-sharing site or platform that hosts works by other creators and are interested in enabling CC licensing for your users, see http://wiki.creativecommons.org/Web_Integration.
</div>

As a creator using a CC license, it is important to properly note the license you have chosen so that others know what they can and can't do with your work. No matter what the context, CC licenses should be clearly cited to enable their full potential as a legal tool.

==Marking on Your Site==
Our [http://creativecommons.org/choose/ license chooser] is designed to make this process simple - answer a few questions and a formatted HTML code will be generated for you:

# Insert this HTML code into your webpage so that your work is clearly marked.
# This HTML code includes [http://wiki.creativecommons.org/Rdfa RDFa], a very important aspect of marking your work so that others can find it easily.

The specifics of inserting the code depend on how you edit your website. The block of code should be inserted into the page HTML - most desktop website tools like Dreamweaver, Frontpage, or GoLive offer a "code view" that lets you see the code that makes up your page. Near the end of the page before you see </body></html>, paste the HTML code in directly.

If all of the resources you are publishing on a single website are licensed under the same CC license, it makes sense to paste the HTML code into your website’s template (e.g., in a footer or sidebar area). After saving the template, the chosen license information should appear everywhere on your site. Whether you add license information to a single page or an entire [http://contactspro.net/purple-contacts/ site], once live on the Internet, the license information will be displayed and the machines will be able to detect the license status automatically.

From there, here are three steps to license notice perfection:

# The full URI (link) to the license. Example: http://creativecommons.org/licenses/by/3.0/us/.
# A visible notation (most commonly text) that states the license being used. Example: Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License.
# Optionally, the appropriate Creative Commons license button or CC icon and license property icon(s).

{| cellspacing="5" cellpadding="10" style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:100%"
|
NOTE: Because each CC license represents a different set of permissions and restrictions, it is important to note the specific license used. Displaying only the CC icon, “Creative Commons”, or “Some Rights Reserved” is insufficient; always include the full URL.
|}
In order for others to credit you for your work, it is preferable to provide an attribution name and URI. The [http://creativecommons.org/choose/ license chooser] provides the proper license button (if you fill in attribution fields) as well as RDFa attribution data. Alternatively, high resolution buttons and license icons are available from [http://creativecommons.org/about/downloads our logo download page].

For example, see the following screenshot of a license notification that incorporates these best practices:

[[Image:By_small.jpg]]
<br/><small>This work by [http://opencontent.org/blog David Wiley] is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3.0 United States].</small>

If you visit David's [http://opencontent.org/blog/ blog], you will see this notice at the bottom of the page. The license icon links to the license deed that includes attribution information specific to David. In this case, David filled out the attribution fields in the [http://creativecommons.org/choose/ license chooser], which provided the proper license button and formatted attribution information. He then pasted the resulting HTML code with RDFa into his webpage and included the textual notation of attribution and the specific license that you see above.

Still confused? Take a look at our visual guide. See [[Website/Publish]] for step by step visuals of copying and pasting the HTML code. This page also contains the same information for pages that host a specific type of media ([[Publish/Audio|audio]], [[Publish/Video|video]], [[Publish/Images|images]], and [[Publish/Text|text]] -- which includes various [[Publish/Text#Blog|blogging]] platforms).

If your work is a derivative of another original CC-licensed work, be sure to look at our [http://wiki.creativecommons.org/Marking/Users Marking for Users] primer as well.

== Marking Specific Media ==

While remaining similar in intent, marking will vary depending on the medium. The following are some helpful tips on making sure your media is marked correctly.

For offline works in general, consider publishing a web page with licensing information about your material. Doing so enables your work to be found by search engines and other web discovery tools.

Below are general examples for each medium. If a more technical explanation is your goal, please see [http://wiki.creativecommons.org/Marking_works Marking Works (technical)]:

<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|
===Offline Text===
<small>(for online text see [[Marking/Creators#Marking_on_Your_Site|Marking on Your Site]])</small>
*For documents that are meant to be shared in print format (not read online) it is suggested to use a title and/or copyright page to include the Copyright notice and CC license information.
**After going through the [http://creativecommons.org/choose/ license chooser], you can click on "Mark a document not on the web, add this text to your work" in the lower right column.
**And/or you can refer to this sample copyright notice: "Copyright (c) 2009 by Greg Grossmeier. This work is made available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license, http://creativecommons.org/licenses/by-sa/3.0/."
*It is also suggested that you use a visual license notice. Here is a collection of visual markers that can be used:
**[[CC markers]] and [http://creativecommons.org/about/downloads/ official CC license icons]
**[[User submitted markers]]
* [[Publish/Text | Advanced Instructions: Text]]

===Image===
*Adding a watermark or other visual marker on an image can ultimately detract from the original. If you choose to, a safe method of indicating license choice consists of two actions:
**When publishing the image on a website, make sure that your license choice is clearly visible, preferably indicated with one of our [http://creativecommons.org/about/downloads/ license icons].
**Ensure search engines can see it also via the use of [[RDFa]], which you can copy and paste from the HTML code given to you by the [http://creativecommons.org/choose/ license chooser].
*Additionally, you can ensure that the image has [[XMP]] metadata support with your name, date, and license choice.
*[[Publish/Image| Advanced Instructions: Image]]
}}
{{PageColumn|
===Audio===
*For audio files, two actions are recommended:
**When publishing the audio file on a website, make sure that your license choice is clearly visible, preferably using one of our [http://creativecommons.org/about/downloads/ license icons].
**Ensure search engines can find it via the use of [[RDFa]], which you can copy and paste from the HTML code provided by the [http://creativecommons.org/choose/ license chooser].
*Additionally, you may want to ensure that the audio file has metadata support with your name, date, and license choice.
**One easy way to do this is to upload your file to music sharing site that has enabled CC licensing. See [[Marking/Creators#Marking on Other Sites|Marking on Other Sites]] below.
**Alternatively, you can use your favorite audio player to add in the information. To learn more see [[Embedded_Metadata]]. You can also see how to add ID3 tags to a common audio file type, such as the [[MP3]], or browse other [[UsingMarkup|file types]].
*Also, if it is practical to do so (for podcasts, for instance, not song tracks), add an audio bumper to the beginning of the file to indicate your choice of license. Here are some [http://creativecommons.org/podcasting intro bumpers] which you can use to build upon.
*[[Publish/Audio| Advanced Instructions: Audio]]

===Video===
*For movie formats that have the ability to include a 2-5 second copyright frame, it is advisable to use the same format as what is suggested for textual works:
**Sample Copyright notice: Copyright (c) 2009 by Greg Grossmeier. This work is made available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license, http://creativecommons.org/licenses/by-sa/3.0/.
*Here is a collection of stills which can be used as license bumpers:
**[http://wiki.creativecommons.org/CC_video_bumpers Official CC bumpers]
**[http://wiki.creativecommons.org/User_submitted_bumpers Community Submitted bumpers]
*[[Publish/Video| Advanced Instructions: Video]]
}}
</div>

== Marking Specific Formats ==
* CC-[[OpenOfficeOrg Addin]] for [http://openoffice.org OpenOffice].
* To mark a Microsoft Office word document, you can use the Microsoft Office add-ins for [http://www.microsoft.com/downloads/details.aspx?familyid=113b53dd-1cc0-4fbe-9e1d-b91d07c76504&displaylang=en Office 2003/XP] or [http://www.microsoft.com/downloads/details.aspx?FamilyID=d1ddbdc8-627f-415a-9b0a-97362bc9b480&displaylang=en Office 2007]

== Marking on Other Sites ==

===[[Publish]]===

One way to increase visibility and access to your work is to share it with an existing community. Many content platforms have already 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.

[[Publish]] your work in an existing community.

== Marking third-party content in your work ==
Marking best practices also apply for any third party content your work incorporates. If you are incorporating another person's work, even if used under fair use or other exception or limitation to copyright, then you should be sure you are allowed to incorporate that work. Third party content may be offered under the same or different terms, such as other CC licenses or "all-rights-reserved" copyright. If you are permitted to use the work and it is offered under a CC license, then you should consider adhering to best practices for marking that content as a user, available at [[Marking/Users]]. We also offer additional explanation and tips on [[Marking/Creators/Marking_third_party_content|marking third-party content]]. Note that for all third party material accompanying or used with your CC-licensed work, that material is not covered by the terms and conditions of the CC license that '''''you''''' apply, it remains under the terms of the license (if any) that applies to it.

Laser hair removal machines UK supplies and sells some of the world’s leading laser and IPL machines.

http://www.laserhairremovalmachinesuk.com

== External Links ==

*[http://creativecommons.org.au/marking/examples Marking Examples] explaining metadata from [http://creativecommons.org.au Creative Commons Australia]

== Things to note ==
When marking your work, remember that any restriction or modification to the original license cannot be labeled a 'Creative Commons’ license. See http://creativecommons.org/policies#license.

{{Best Practice}}

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]

4.0

2013-09-25T15:03:18Z

Mike Linksvayer: Reverted edits by Beritaharian (talk) to last revision by Kat Walsh

CC has embarked upon a versioning process for its core license suite, which will result in version 4.0. The first public discussions of 4.0 were held at CC's [[Global Summit 2011]]. The public process was kicked off with a [http://creativecommons.org/weblog/entry/29639?utm_campaign=newsletter_1111&utm_medium=blog&utm_source=newsletter blog post] laying out some of the key reasons for pursuing 4.0 at this time.

Since CC's launch in 2002, it has versioned its core license suite [[license versions|three times]], the last ([[Version 3|3.0]]) in early 2007. CC licenses constitute a [http://creativecommons.org/who-uses-cc globally-recognized framework], developed in consultation with legal experts and CC affiliate institutions in [[CC_Affiliate_Network|over 70 jurisdictions]]. Over 500 million CC-licensed works have been published by their authors on the Internet. Today, Creative Commons licenses, public domain tools, and supporting technologies are the global standard for sharing across culture, education, government, science, and more.

Version 4.0 is a tremendous opportunity to ensure the license suite is ideally crafted to further CC's [http://creativecommons.org/about vision and mission] over the next decades. Please participate in this important discussion.

=== Goals and objectives ===

Creative Commons staff, board, and community have identified several goals for the next version of its core license suite, tied to achieving CC's goal and mission. These include:

:: ''Internationalization'' – further adapt the core suite of international licenses to operate globally, ensuring they are robust, enforceable and easily adopted worldwide;

:: ''Interoperability'' – maximize interoperability between CC licenses and other licenses to reduce friction within the commons, promote standards and stem license proliferation;

:: ''Long-lasting'' — anticipate new and changing adoption opportunities and legal challenges, allowing the new suite of licenses to endure for the foreseeable future;

:: ''Data/PSI/Science/Education'' — recognize and address impediments to adoption of CC by governments as well as other important, publicly-minded institutions in these and other critical arenas; and

:: ''Supporting Existing Adoption Models and Frameworks'' – remain mindful of and accommodate the needs of our existing community of adopters leveraging pre-4.0 licenses, including governments but also other important constituencies.

=== Organization and purpose of this wiki ===

This wiki is the central location for documenting key discussion topics and suggestions for improving the license suite in version 4.0, together with supporting information and relevant links[http://double-oven-reviews.com/ .] It is intended to supplement, not replace, the CC license discuss email list [http://lists.ibiblio.org/mailman/listinfo/cc-licenses (subscribe)] that will serve as the main discussion forum for the versioning process just as it has with prior versioning efforts.

CC has prepared pages on key topics identified to date. We ask contributors to be thoughtful about placement of additional and related topics, as well as the creation of new pages altogether. Before starting a new page, consider posting the suggestion to the [[4.0/Sandbox|Sandbox]]. We would also prefer that contributors use their real names when editing the wiki.

=== Process ===

As a license steward and steward of the commons, our goal for the process is to ensure utmost transparency and inclusiveness. The 4.0 process is being conducted in line with our prior versioning efforts, with periodic publication of license drafts for public comment and documentation of issue resolution as that occurs[http://becoming-a-psychiatrist.org/ .] One important difference from our past efforts, however, was a formal requirements gathering period that ran for a period of time prior to publication of the first draft. During this period, we strongly encouraged the broadest participation possible by everyone with an interest in the commons and the role open licensing plays in its future.

The primary discussion forum for issues relating to the 4.0 versioning process will be the CC license discuss email list. Please [http://lists.ibiblio.org/mailman/listinfo/cc-licenses subscribe] and add your voice to this important effort.

=== Draft timeline ===
The dates noted below are approximate and subject to change. The number of drafts and public comment periods may vary depending on the number and type of issues raised and how they are resolved, among other things. Watch this page for updates, including major events such as affiliate regional meetings where 4.0 discussions will take place.

{| class="wikitable" style="width: 75%; height: 200px" border="1"
|-
| September 2011
| [https://creativecommons.org/weblog/entry/29639 Launch 4.0 process] at CC Global Summit
|-
| December 2011 thru mid-February 2012
| Requirements gathering period
|-
| April 2, 2012
| Publish [[4.0/Drafts#Draft_1_Details|first draft of 4.0]]
|-
| April to June 2012
| [[4.0/Draft_1/Regional_calls|Public comment]] period #1
|-
| August 2012
| Publish [[4.0/Drafts#Draft_2_Details|second draft of 4.0]]
|-
| August 2012 to February 2013
| [[4.0/Draft_2/Regional_calls|Public comment]] period #2
|-
| February 2013
| Publish [[4.0/Drafts#Draft_3_Details|third draft of 4.0]]; begin porting consultation
|-
| February to September 2013
| [[4.0/Draft_3/Regional_calls|Third public comment period]]; porting consultation
|-
| September 2013
| Publication of [[4.0/Drafts#Draft_4_Details|fourth and final draft]]; begin abbreviated final public comment period
|-
| September/October 2013 (expected)
| Finalize and publish version 4.0 license suite
|}

Various aspects of the license suite are being improved in the version 4.0 licenses. We are gathering and rigorously debating and analyzing these items, and corresponding proposals for handling them, in version 4.0. We encourage the broadest possible engagement in this process. This was a particularly important goal during the requirements gathering stage where everyone was strongly encouraged (and our affiliates expected) to provide feedback on proposed changes and suggest other changes they would like to see. You may add, improve, and discuss specific items in the pages linked below.

'''If you do not find a suitable existing page and category for an item you would like to propose or discuss, please add it to the [[4.0/Sandbox]] where suggestions for new pages will be aggregated.'''

Finally, we encourage contributors to take the time to review [http://wiki.creativecommons.org/License_Versions prior versioning efforts], including relevant discussions of important topics previously debated by the CC community and discussions related to their resolution. Being aware of and taking those into account is important to an effective and efficient process, particularly where a request is made to revisit and potentially change direction in 4.0.

{{#ask:[[Category:4.0 Issues]] [[:+]]
|mainlabel=Item/Category Name
|format=broadtable|
=== Items for discussion ===
}}

===Related pages===
:[[4.0/Sandbox|4.0 Sandbox]]
:[[Porting Project]]
:[[4.0 Drafts]]
:[[4.0/Draft_1|4.0 Draft 1]]
:[[4.0/Draft_2|4.0 Draft 2]]
:[[4.0/Draft_3|4.0 Draft 3]]
:[[4.0/Draft_4|4.0 Draft 4]]
[[Category:4.0]]

4.0/Draft 1

2013-09-19T05:04:27Z

Mike Linksvayer: Reverted edits by Kunaguers (talk) to last revision by Mike Linksvayer

==Welcome to the Public Discussion of Draft 1==

This page provides information specific to the public discussion of the first draft of version 4.0. The draft presented is the result of discussions started during the CC Global Summit in Poland (Sept 2011) and a lengthy, unprecedented [http://creativecommons.org/weblog/entry/30676 requirements gathering process]. Both forums resulted in valuable suggestions from CC affiliates, community and stakeholders. Our [http://wiki.creativecommons.org/4.0 goals and objectives] are ambitious, and we welcome your ideas and opinions to achieve them.

Please submit comments on the [http://lists.ibiblio.org/mailman/listinfo/cc-licenses license-discuss list]. We expect the comment period to remain open until late May with Draft 2 published by mid June 2012.

''(Note that for purposes of this first public discussion, we are publishing the draft of BY-NC-SA (international) only. BY-NC-SA contains most of the elements necessary to build the other licenses. Look for complete drafts of the other licenses later in the process.)''

===Treatment of issues and proposals in Draft 1===

The [http://wiki.creativecommons.org/4.0#Items_for_discussion discussion topic pages] tracked on our [http://wiki.creativecommons.org/4.0 4.0 wiki] contain clearly marked explanations for how the relevant issues have been generally handled in this draft. Additionally, the numbered proposals on each topic page have a corresponding note if the topic was addressed in some manner in this draft. We have also included an occasional prompt to highlight where additional feedback is especially requested. We will do the same for later draft(s).

===Core policy and drafting considerations===

The 4.0 licenses are intended to operate in largely the same manner as prior versions, granting conditional permission to use the licensed work where permission is required by copyright, and where those rights are held by licensor.

Additionally, the license:

:: * affirmatively licenses neighboring rights, including database rights, on par with copyright and subject to the license conditions ('''''note''''' that the definition of neighboring rights is tightly defined in this first draft for the reasons described under Feedback requests, below);

:: * waives moral rights and other copyright-like rights that could prevent use of the work as allowed by the license, but only when legally possible to do so, and then only to the extent necessary to allow the licensed work to be used as contemplated; and

:: * internationalizes and simplifies the legal code wherever possible, particularly for attribution and other conditions (modeled in part on the [http://creativecommons.org/licenses/by-nc-sa/3.0/au/legalcode 3.0 Australian port]), to better ensure the license is more widely available and acceptable for use by adopters worldwide where possible.

Expanded explanations and details for this draft on these particular issues are noted prominently on relevant 4.0 wiki pages: [http://wiki.creativecommons.org/4.0/License_subject_matter scope of license]; [http://wiki.creativecommons.org/4.0/Moral_rights moral rights]; [http://wiki.creativecommons.org/4.0/Attribution_and_marking attribution]; and [http://wiki.creativecommons.org/4.0/Internationalization internationalization].

===Feedback requests, including topics and policies still under consideration===

We want to hear from our community on some important drafting and policy decisions in the current draft:

:: * [http://wiki.creativecommons.org/4.0/Treatment_of_adaptations Definition of Adaptation] (Section 1(a)): Do additional uses merit special mention in the definition so as to be considered an Adaptation (or not) for purposes of SA and the ND licenses?

:: * [http://wiki.creativecommons.org/4.0/License_subject_matter Neighboring rights versus ancillary rights]: We tightly defined neighboring rights, which are licensed, and more loosely defined ancillary rights, which are subject to a limited waiver. Our purpose in doing so was to focus discussion on the problem of ancillary rights generally, and to see whether this division and differing treatment is a feasible solution. Are there established neighboring rights that ought be licensed (and subject to conditions) that might now fall into the category of ancillary rights (that are waived and not subject to conditions)?

:: * [http://wiki.creativecommons.org/4.0/Moral_rights Moral rights]: Does the limited waiver (where possible) work legally? As a a matter of policy?

:: * [http://wiki.creativecommons.org/4.0/Attribution_and_marking Attribution] (Section 3(a): Should more flexibility be built in for massive collaboration projects? Are the requirements understandable such that likelihood and ease of compliance increases?

Additionally, there are a few important topics that we have left unaddressed in this first draft in order to gather more input from the community prior to making a formal proposal:

:: * [http://wiki.creativecommons.org/4.0/Technical_protection_measures Technical Protection Measures]: Please help us identify use cases to inform a later proposal. Ideally, these will be based on demonstrated needs (or lack thereof) by licensees for a change from the prohibition in 3.0.

:: * [http://wiki.creativecommons.org/4.0/NonCommercial NonCommercial]: More discussion will be necessary to advance current proposals or arguments for deviating from the current definition in 3.0. Concrete proposals and use cases are sought, including specific clarifying use cases that could be added to the definition similar to file sharing, which is already included.

:: * [http://wiki.creativecommons.org/4.0/Sandbox#Disclaimer_of_warranties_and_related_issues Warranties and disclaimers]: Does the current proposal work as a baseline, much as the 3.0 (international) license provides? Would an [http://wiki.creativecommons.org/4.0/Sandbox#Additional_terms_framework Additional Terms] clause similar to [http://www.gnu.org/copyleft/gpl.html Section 7 of GPLv3] assist with this and other issues?

=== Provisions for other Licenses in the Suite ===
For Draft 1, only BY-NC-SA is rendered in full. The other licenses will be derived (fairly easily) from it for Draft 2.

For example, to create BY-SA, (1) remove the NC definition and related NC terms, (2) add a reference to Compatible License in Section 3(c)(1), and (3) add the following definition of "Compatible License" in Section 1 (''note that the language is the same as in 3.0, but adjusted to use the current terminology from BY-NC-SA Draft 1''):

:: "Compatible License" means a license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this Public License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Conditions of this Public License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this Public License or a Creative Commons jurisdiction license with the same License Conditions as this Public License."

Please join the [http://lists.ibiblio.org/mailman/listinfo/cc-licenses CC license-discuss list] or add your input directly to the CC [[4.0|4.0 wiki]].

[[Category:4.0]]

Kenya

2013-09-17T04:20:00Z

Mike Linksvayer: Reverted edits by Kevinguru (talk) to last revision by Domtheo

4.0/Draft 1

2013-09-17T04:19:42Z

Mike Linksvayer: Reverted edits by Kevinguru (talk) to last revision by Mike Linksvayer

4.0/Drafts

2013-09-16T05:16:26Z

Mike Linksvayer: /* 4.0d2 Licenses */ media:

==Launch, drafting and process information==
* Global Summit (Sept 2011), [http://creativecommons.org/weblog/entry/29639 outcomes related to 4.0]
* Public discussion [http://creativecommons.org/weblog/entry/30676 launch (December 2011)]
* [[4.0|4.0 wiki]] detailing objectives, process, topic/issue page

==[[4.0/Draft_1|Draft 1 Details]]==
''(Note that only BY-NC-SA (international) is presented in draft form, as the other licenses are easily crafted from its terms. Comments are not limited solely to this one license but should be presented on the license suite as a whole.)''

* '''Publication date: 2 April 2012'''
** [http://creativecommons.org/weblog/entry/32157 Blog post]
** [http://lists.ibiblio.org/pipermail/cc-licenses/2012-April/006720.html Announcement to license-discuss]
** [[4.0/Draft_1|Introduction to draft, policies, feedback requests]]

* '''Comment period: 2 April 2012 thru May 2012'''
** [[4.0/Draft_1/Regional_calls|Draft 1 regional calls]]

===4.0d1 Licenses===
* '''4.0d1 BY-NC-SA (international)'''
**[[Media:4point0_draft_1.odt|ODT]]
**[[Media:4point0_draft_1.PDF|PDF]]
**[[Media:4point0_draft_1.txt|TXT]]

====Other 4.0d1 documents====
* Side-by-side comparison to BY-NC-SA 3.0 (international), with notations: [[Media:BY_NC_SA_comparison_chart.pdf|PDF]] (only)

==[[4.0/Draft_2|Draft 2 Details]]==
*'''Publication date: 1 August 2012'''
** [http://creativecommons.org/weblog/entry/33632 Blog post]
** [http://lists.ibiblio.org/pipermail/cc-licenses/2012-August/007107.html Announcement to license-discuss]
** [[4.0/Draft_2#Feedback_requests.2C_including_topics_and_policies_still_under_consideration|Introduction to draft, policies, feedback requests]]

*'''Comment period: 1 August 2012 until 15 February 2013'''
**[[4.0/Draft_2/Regional_calls|Regional Calls]]

===4.0d2 Licenses===
''(Note that BY-NC-SA and BY-SA are presented. Comments are not limited solely to these two licenses, however.)''

*'''4.0d2 BY-NC-SA (international)'''
**[[Media:4.0d2_(final_by_nc_sa_31_July).odt|ODT]]
**[[Media:4.0d2_(final_by_nc_sa_31_July).pdf|PDF]]
**[[Media:4.0d2_(final_by_nc_sa_31_July).txt|TXT]]
**[http://mirrors.creativecommons.org/drafts/by-nc-sa_4.0_draft.html HTML]

*'''4.0d2 BY-SA (international)'''
** [[Media:4.0d2_(final_by_sa_31_July).odt|ODT]]
** [[Media:4.0d2_(final_by_sa_31_July).pdf|PDF]]
** [[Media:4.0d2_(final_by_sa_31_July).txt|TXT]]

====Other 4.0d2 documents====
* Side-by-side comparison between BY-NC-SA 4.0d1 and 4.0d2 (international), with abbreviated explanations: [[Media:Comparison_Chart_d1_to_d2_(final_31-July).pdf|PDF]] (only)
* Attribution comparison chart (across 3.0, d,1 and d2): [[Media:Attribution_comparision_(4-1.0d2_final_for_31_July).pdf|PDF]] (only)

==[[4.0/Draft_3|Draft 3 Details]]==
* '''Publication date: 15 February 2013'''
** [http://creativecommons.org/weblog/entry/36713 Blog post]
** [http://lists.ibiblio.org/pipermail/cc-licenses/2013-February/007324.html Announcement to license-discuss]

* '''Comment period: 15 February 2013 until approximately 10 September 2013'''

===4.0d3 Licenses===
''(all six are presented in HTML; BY-NC-SA is published in alternative formats as well)''

* '''BY (4.0d3)''' [http://mirrors.creativecommons.org/drafts/by_4.0d3.html HTML]
* '''BY-SA (4.0d3)''' [http://mirrors.creativecommons.org/drafts/by-sa_4.0d3.html HTML]
* '''BY-NC-SA (4.0d3)''' [http://mirrors.creativecommons.org/drafts/by-nc-sa_4.0d3.html HTML], [[Media:4.0d3_BY-NC-SA_(final).odt|ODT]], [[Media:4.0d3_BY-NC-SA_(final).pdf|PDF]], and [[Media:4.0d3_BY-NC-SA_(final).txt|TXT]]
* '''BY-NC (4.0d3)''' [http://mirrors.creativecommons.org/drafts/by-nc_4.0d3.html HTML]
* '''BY-ND (4.0d3)''' [http://mirrors.creativecommons.org/drafts/by-nd_4.0d3.html HTML]
* '''BY-NC-ND (4.0d3)''' [http://mirrors.creativecommons.org/drafts/by-nc-nd_4.0d3.html HTML]

====Other 4.0d3 documents====
*Side-by-side comparison between BY-NC-SA 4.0d2 and 4.0d3, with abbreviated explanations [[Media:Comparison_Chart_d2_to_d3_.pdf | PDF]] (only)

*Attribution requirements comparisons:
** 3.0 and 4.0d3 [[Media:Attribution_chart_%28v3_v_d3%29_.pdf|PDF]] (only)
** 4.0d2 and 4.0d3 [[Media:Attribution_chart_%28d2_v_d3%29.pdf|PDF]] (only)

==[[4.0/Draft_4|Draft 4 Details]]==
* '''Publication: 12 September 2013'''
** [http://creativecommons.org/weblog/entry/39587 Blog post]
** [http://lists.ibiblio.org/pipermail/cc-licenses/2013-September/007409.html Announcement] to license development list

* '''Comment period (abbreviated): Approximately two weeks from publication, ending the week of September 23rd'''

===4.0d4 Licenses===
''(all six will be presented in HTML; BY-NC-SA is published in alternative formats as well)''



* '''BY-NC-SA (4.0d4)''' [http://staging.creativecommons.org/licenses/by-nc-sa/4.0/legalcode HTML], [[Media:4.0d4_BY-NC-SA.odt|ODT]], [[Media:4.0d4_BY-NC-SA.pdf|PDF]], and [[Media:4.0d4_BY-NC-SA.txt|TXT]]
* other 5 licenses to be posted soon




====Other 4.0d4 documents====
* Comparison of draft 3 and draft 4: [[Media:Comparison_draft_3_to_draft_4.pdf|PDF]]
* Attribution comparison chart from draft 3 to draft 4: [[Media:Attribution_chart_%28v3_v_d4%29_.pdf|PDF]]

{{Translations
| articles = Ru:4.0/Проекты
}}
[[Category:4.0]]

4.0/Draft 1

2013-09-16T05:09:42Z

Mike Linksvayer: despam

4.0/Draft 1

2013-09-16T05:07:27Z

Mike Linksvayer: Undo revision 85933 by Domtheo (talk)

==Welcome to the Public Discussion of Draft 1==

This page provides information specific to the public discussion of the first draft of version 4.0. The draft presented is the result of discussions started during the CC Global Summit in Poland (Sept 2011) and a lengthy, unprecedented [http://creativecommons.org/weblog/entry/30676 requirements gathering process]. Both forums resulted in valuable suggestions from CC affiliates, community and stakeholders. Our [http://wiki.creativecommons.org/4.0 goals and objectives] are ambitious, and we welcome your ideas and opinions to achieve them.

Please submit comments on the [http://lists.ibiblio.org/mailman/listinfo/cc-licenses license-discuss list]. We expect the comment period to remain open until late May with Draft 2 published by mid June 2012.

''(Note that for purposes of this first public discussion, we are publishing the draft of BY-NC-SA (international) only. BY-NC-SA contains most of the elements necessary to build the other licenses. Look for complete drafts of the other licenses later in the process.)''

===Treatment of issues and proposals in Draft 1===

The [http://wiki.creativecommons.org/4.0#Items_for_discussion discussion topic pages] tracked on our [http://wiki.creativecommons.org/4.0 4.0 wiki] contain clearly marked explanations for how the relevant issues have been generally handled in this draft. Additionally, the numbered proposals on each topic page have a corresponding note if the topic was addressed in some manner in this draft. We have also included an occasional prompt to highlight where additional feedback is especially requested. We will do the same for later draft(s).

===Core policy and drafting considerations===

The 4.0 licenses are intended to operate in largely the same manner as prior versions, granting conditional permission to use the licensed work where permission is required by copyright, and where those rights are held by licensor.

Additionally, the license:

:: * affirmatively licenses neighboring rights, including database rights, on par with copyright and subject to the license conditions ('''''note''''' that the definition of neighboring rights is tightly defined in this first draft for the reasons described under Feedback requests, below);

:: * waives moral rights and other copyright-like rights that could prevent use of the work as allowed by the license, but only when legally possible to do so, and then only to the extent necessary to allow the licensed work to be used as contemplated; and

:: * internationalizes and simplifies the legal code wherever possible, particularly for attribution and other conditions (modeled in part on the [http://creativecommons.org/licenses/by-nc-sa/3.0/au/legalcode 3.0 Australian port]), to better ensure the license is more widely available and acceptable for use by adopters worldwide where possible.

Expanded explanations and details for this draft on these particular issues are noted prominently on relevant 4.0 wiki pages: [http://wiki.creativecommons.org/4.0/License_subject_matter scope of license]; [http://wiki.creativecommons.org/4.0/Moral_rights moral rights]; [http://wiki.creativecommons.org/4.0/Attribution_and_marking attribution]; and [http://wiki.creativecommons.org/4.0/Internationalization internationalization].

===Feedback requests, including topics and policies still under consideration===

We want to hear from our community on some important drafting and policy decisions in the current draft:

:: * [http://wiki.creativecommons.org/4.0/Treatment_of_adaptations Definition of Adaptation] (Section 1(a)): Do additional uses merit special mention in the definition so as to be considered an Adaptation (or not) for purposes of SA and the ND licenses?

:: * [http://wiki.creativecommons.org/4.0/License_subject_matter Neighboring rights versus ancillary rights]: We tightly defined neighboring rights, which are licensed, and more loosely defined ancillary rights, which are subject to a limited waiver. Our purpose in doing so was to focus discussion on the problem of ancillary rights generally, and to see whether this division and differing treatment is a feasible solution. Are there established neighboring rights that ought be licensed (and subject to conditions) that might now fall into the category of ancillary rights (that are waived and not subject to conditions)?

:: * [http://wiki.creativecommons.org/4.0/Moral_rights Moral rights]: Does the limited waiver (where possible) work legally? As a a matter of policy?

:: * [http://wiki.creativecommons.org/4.0/Attribution_and_marking Attribution] (Section 3(a): Should more flexibility be built in for massive collaboration projects? Are the requirements understandable such that likelihood and ease of compliance increases?

Additionally, there are a few important topics that we have left unaddressed in this first draft in order to gather more input from the community prior to making a formal proposal:

:: * [http://wiki.creativecommons.org/4.0/Technical_protection_measures Technical Protection Measures]: Please help us identify use cases to inform a later proposal. Ideally, these will be based on demonstrated needs (or lack thereof) by licensees for a change from the prohibition in 3.0.

:: * [http://wiki.creativecommons.org/4.0/NonCommercial NonCommercial]: More discussion will be necessary to advance current proposals or arguments for deviating from the current definition in 3.0. Concrete proposals and use cases are sought, including specific clarifying use cases that could be added to the definition similar to file sharing, which is already included.

::* Sebagian besar karya Antoni Gaudi ditandai dengan semangat hidupnya yang besar: arsitektur, alam & agama. Antoni Gaudi mempelajari setiap detail dari ciptaannya, dengan mengintegrasikan ke dalamnya berbagai teknik seni yang dikuasai yaitu keramik, kaca berwarna, besi tempa & pertukangan.
dikutip oleh: [http://vamostech.com/gps-tracking GPS Tracking] - [http://subconscious-therapy.com/hipnoterapi-surabaya hipnoterapi surabaya] - [http://www.pedatimotor.com aksesoris sparepart motor] - [http://www.optimaweb.co.id/jasa-seo Jasa SEO] - [http://www.optimaweb.co.id/ Internet marketing]

:: * [http://wiki.creativecommons.org/4.0/Sandbox#Disclaimer_of_warranties_and_related_issues Warranties and disclaimers]: Does the current proposal work as a baseline, much as the 3.0 (international) license provides? Would an [http://wiki.creativecommons.org/4.0/Sandbox#Additional_terms_framework Additional Terms] clause similar to [http://www.gnu.org/copyleft/gpl.html Section 7 of GPLv3] assist with this and other issues?

=== Provisions for other Licenses in the Suite ===
For Draft 1, only BY-NC-SA is rendered in full. The other licenses will be derived (fairly easily) from it for Draft 2.

For example, to create BY-SA, (1) remove the NC definition and related NC terms, (2) add a reference to Compatible License in Section 3(c)(1), and (3) add the following definition of "Compatible License" in Section 1 (''note that the language is the same as in 3.0, but adjusted to use the current terminology from BY-NC-SA Draft 1''):

:: "Compatible License" means a [http://www.proweb365.com website] license that is listed at http://creativecommons.org/compatiblelicenses that has been approved by Creative Commons as being essentially equivalent to this Public License, including, at a minimum, because that license: (i) contains terms that have the same purpose, meaning and effect as the License Conditions of this Public License; and, (ii) explicitly permits the relicensing of adaptations of works made available under that license under this Public License or a Creative Commons jurisdiction license with the same License Conditions as this Public License."

Please join the [http://lists.ibiblio.org/mailman/listinfo/cc-licenses CC license-discuss list] or add your input directly to the CC [[4.0|4.0 wiki]].
[[Category:4.0]]

Case Studies/Strange Symphonies Blog

2013-09-15T20:48:34Z

Mike Linksvayer: Reverted edits by Boetbre (talk) to last revision by Janepark

{{Case Study
|importance=Medium
|quality=B-Class
|Description=The ‘Strange Symphonies’ blog presents the writing of Aizat Faiz, a Malaysian free culture advocate working with FLOSS, free content, and open standards.
|Quote=It’s like making everyone a kid with scissors and glue, and letting them make their own collages from what is already out there.
|Quote_Attribution=[http://blog.aizatto.com/about/ Azait Faiz]
|Mainurl=http://blog.aizatto.com/
|Author=Aizat Faiz
|User_Status=Creator
|Tag=FLOSS, software, blog
|License_short_name=CC BY
|License=http://creativecommons.org/licenses/by/3.0/
|Format=Text
|Country=Malaysia
}}
== Overview ==

Aizat Faiz is a self-proclaimed free culture advocate working with FLOSS, free content, and the development of open standards in Malaysia. An undergraduate student enroled in a Bachelors Degree in Computer Science at the Malaysian campus of Monash University, Aizat chronicles the effects which free culture and FLOSS has had on his education and employment. Aizat, aka ‘aizatto’, ‘zatto’ or the ‘Malaysian Free and Open Source Software junkie,’ maintains an interest in developing open standards, XHTML/HTML and the Open Document Format, in addition to programming using PHP and Ruby on Rails. He is a member of MyOSS, the [http://foss.org.my Free and Open Source Software Society of Malaysia], the Malaysia National Computer Confederation Open Document Format Special Interest Group, was rapporteur at the 7th AsiaOSS Symposium, and has had some involvement in the Malaysia-United States Free Trade Agreement. After spending a year studying at the Asia Pacific Institute of Information Technology (APIIT) in Kuala Lumpur, Aizat enroled at Monash University where he entered the [http://www.genting.com.my/rnd/2006/default.htm eGenting Programming Competition] in 2006, and won.

:‘As can be seen, the freedom to let me just take code online, read it, study it, remix it, hack it, has been extremely beneficial to me in terms of my education.’ (http://blog.aizatto.com/2007/05/23/why-i-support-free-culture/)

Given his strong skills in software development, Aizat has been employed by the United Nations Development Program International Open Source Network to work on the DocBook and WikiBook conversions.

== License Usage ==

As a free culture advocate and programmer, Aizat lists numerous resources for FLOSS development on his blog, with [http://blog.aizatto.com/category/free-and-open-source-software/ posts] outlining the latest in programming as well as Asia-based events pertaining to open source initiatives. Many meetings consider FLOSS licensing and support plus provide broader overviews of software and services in business contexts.

The majority of content of the Strange Symphonies blog is licensed under the Creative Commons Attribution 3.0 unported licence. The site uses graphics from the [http://tango.freedesktop.org/Tango_Desktop_Project Tango Desktop Project], which seeks to develop a consistent graphical user interface experience for free and open source software. Several of Aizat’s [http://blog.aizatto.com/resume/ presentations on FLOSS] released under the Creative Commons Attribution 2.5 Generic licence encompass introductions to GNU/Linux, the LAMP platform, Ruby on Rails, and privacy/anonymity with Tor. Specific [http://blog.aizatto.com/category/free-culture/creative-commons/ Strange Symphonies blog entries on Creative Commons] discuss advantages and disadvantages of licence information and various events held at Creative Commons Malaysia, such as the [http://blog.aizatto.com/2007/04/28/creative-commons-malaysia-photography-workshop-co-organized-by-lensa-malaysia/ photography workshop organised by Lensa Malaysia] in 2007.

‘This is not just about the software. Even leading institutions such as MIT are releasing their coursework under a Creative Commons license.’
(http://blog.aizatto.com/2007/05/23/why-i-support-free-culture/)

== Motivations ==

Throughout his blog, Aizat celebrates the fact that free culture has given him the ability to ‘remix, to hack, to build upon, to enhance, to study, to learn off existing works.’ Taking the definition of ‘Free Cultural Works’ from http://freedomdefined.org/Definition, he emphasises these four key points:
*the freedom to use the work and enjoy the benefits of using it;
*the freedom to study the work and to apply knowledge acquired from it;
*the freedom to make and redistribute copies, in whole or in part, of the information or expression; and
*the freedom to make changes and improvements, and to distribute derivative works.

All of these, Aizat maintains, are beneficial to a person to let them learn on their own and experiment, as he has done throughout his studies and career, programming in C, OpenGL, SDL, Python and Ruby. Discussing his attachment to the [http://blog.aizatto.com/2007/05/23/why-i-support-free-culture/ philosophy of free culture and open source software], Aizat provides a variety of answers to the question, ‘Why do you support open source technology?’ The one-line, non-philanthropic answer he provides is: ‘Because I have benefited from Free Culture, and I know that others can benefit as well.’ In response, his philanthropic answer is ‘Because it’s the right thing to do.’ Giving the background to his more detailed answer concerning free cultural works, Aizat discusses his education, community involvement, employment, and other gains, such as becoming familiar with legal concepts surrounding copyright, patents, DRM, and contract law.

:‘Want to bridge the digital divide? Want to help build local capacity? Want to build the local economy? I believe that Free Culture is the solution. May not be the end all solution, but it will help to play a large part.’ (http://blog.aizatto.com/2007/05/23/why-i-support-free-culture/)

== Media ==

Delete this line and add text here.

[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} Please help us edit this.] Add media that is relevant.

Metadata

2013-09-15T20:48:20Z

Mike Linksvayer: Reverted edits by Boetbre (talk) to last revision by Greg Grossmeier

When you select a license from the [http://creativecommons.org/license Creative Commons License Chooser], you're provided with HTML to place in your page. That HTML contains [[ccREL|metadata]] which allows software to understand that you've applied a license to your work.

== What is metadata? ==

'''Metadata''' is data about data. For example: title, creator, and licensing information. When you [http://creativecommons.org/license/ choose a license] on our website, you get back some metadata (licensing information) encoded in RDF.

== What is RDF? ==

'''RDF''' (Resource Description Framework) is a framework for metadata. The basic structure of RDF is very simple. There are three parts:

* the subject: a thing, identified by its URL
* the predicate: the type of metadata (like title or creator), also identified by a URL
* the object: the value of this type of metadata (like "The Story of My Life" or 'a person named "John Q. Public"')

Together, these make RDF statements, which are expressed in a language called RDF/XML.

== What is the Semantic Web? ==

The '''Semantic Web''' is the part of the Web available in RDF. The idea behind the concept of the Semantic Web is that when enough pages carry this machine-processable metadata, developers can build tools that take advantage of it.

Among other things, RDF helps different programs talk to each other, reducing the need for users to copy information by hand. Imagine a world where everything had embedded RDF: When buying a plane ticket, for example, you could drag your flight itinerary onto your calendar program to add it to your calendar. You could drag a friend's top-ten songs list onto your music player, and it could try and obtain the songs for you automatically.

RDF can also be used to create more powerful search engines. Right now the only type of question you can ask a search engine is "What pages have these words in them?" When pages include RDF metadata, you will be able to ask more advanced questions like "What's the current temperature in California?" Programs can also use this information, like an alarm clock program that also displayed the current weather or a collage-making program that only used photos with permission.

Finally, metadata can be aggregated across the whole Web. A program could download all the top-ten song lists and, with the help of a pricing guide in RDF, calculate the cost of buying the most popular albums.

Metadata holds a lot of promise, but it won't be useful until people start adding it to their pages. Creative Commons hopes to help promote metadata by making it very easy for people to add metadata to their pages.

== Why we have Creative Commons Metadata ==

In addition to making it easy for people to find the copyright licenses best for them, Creative Commons is working to provide simple RDF descriptions of these licenses. These descriptions will put the important points of the license in a way that makes it easy for machines to process and work from. Unlike Digital Rights Management (DRM) technology, which tries to restrict use of digital works, Creative Commons is providing ways to encourage permitted sharing and reuse of works.

If you run a search engine, you might use license metadata to highlight public domain and generously-licensed works. If you write a public file sharing server, you might offer to search the user's hard drive for works that allow distribution. If you write a magazine, you might use a CC-enabled search engine to find pictures of candy bars that you can legally include.

By standardizing a way to describe this information and providing large quantities of RDF to build on, we hope to encourage new and innovative ways to develop the commons. Of course, this metadata only provides a first approximation of the license, for information use. Users are encouraged to read the full license to make sure it meets their expectations.

== CC REL Describes Creative Commons Metadata ==

Creative Commons metadata is described by the [[ccREL|Creative Commons Rights Expression Language]] (CC REL). You can also find information on specific [[:Category:Filetype|filetypes]] for embedding and reading metadata.

{{Translations
| articles = Pt:Metadados,Ru:Метаданные
}}

[[Category:Technology]]
[[Category:Developer]]
[[Category:Metadata]]
[[Category:Guide]]

Developers

2013-09-15T20:48:09Z

Mike Linksvayer: Reverted edits by Boetbre (talk) to last revision by Soniajack

'''Welcome to the CC Developer Community!''' This is where you'll find all
about the technologies and software products that CC uses to push
forward our mission to maximize digital creativity, sharing, and
innovation.

== Get Involved ==

All of the projects developed at Creative Commons are open source
software, and just like most open source projects, outside involvement
is key to its success. But you don't have to be a software developer
to join us--we'd love to have you in the discussion if you're a user
researcher, designer, translator, or just interested in the topic.

; E-mail
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
; IRC
: Chat with us real-time on [irc://irc.freenode.net/cc irc] (Freenode, #cc)

Coming soon: public team meetings, and other ways to engage.

== Projects ==

; [[OpenHome]]
: A Creative Commons homepage with your content
; [[Summer of Code 2013|Google Summer of Code 2013]]
: Ideas and more.
; [[Translate|Localization]]
: Find out how to help the Creative Commons community with translations.

== Core Technologies ==

; [[RDFa]]
: Standard for adding machine-readable statements to web pages.
; [[CcREL]]
: Language for adding licensing [http://combinest.blogspot.com/ information] to web pages.
; [[LRMI]]
: Language for describing educational resources on the web.
; [[Liblicense]]
: Library for embedding licensing metadata into files of various formats. (note: now somewhat out of date!)

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Other

2013-09-15T20:46:14Z

Mike Linksvayer: Undo revision 54825 by Zack holley (talk)

== Featured Sites ==

{{#ask:
[[Category:Content_Directory]]
[[format::other]]
|mainlabel=Name
|?mainurl=Website
|?size=Size
}}

Other

2013-09-15T20:40:14Z

Mike Linksvayer: Reverted edits by MartiniPeres (talk) to last revision by Mzeinstra

{{ContentDirectory
|mainurl=
|format=Other
|size=45
}}

== Featured Sites ==

{{#ask:
[[Category:Content_Directory]]
[[format::other]]
|mainlabel=YCLW
|?mainurl=http://www.will-lose-weight.com
|?size=15
}}

Publish/Audio/Jamendo

2013-09-15T20:40:09Z

Mike Linksvayer: Reverted edits by MartiniPeres (talk) to last revision by Janepark

== How to publish on Jamendo ==
'''1. After registering an account, select ''Upload your album'' from the top menu, which will start the upload process. Upload your album's tracks. In the example below, a track named "Test" was uploaded.'''

[[Image:jamendo1.png|border]]

'''2. Finish uploading your album's tracks, following all directions on the page. When done, continue to the ''Write an album description'' page.'''

[[Image:jamendo2.png|border]]

'''3. At the bottom of this album description page, you should be able to select Creative Commons license options. Select your desired options and continue with the upload process.'''

[[Image:jamendo3.png|border]]

Publish/Audio

2013-09-15T20:39:58Z

Mike Linksvayer: Reverted edits by MartiniPeres (talk) to last revision by Janepark

==Internet Archive==
<div class="smimg">[[Image:Internet_archive_logo.jpg‎|link=|left]]
The [http://archive.org Internet Archive] is a digital library of internet sites and other cultural artifacts in digital form, including audio, moving images, texts, and archived web pages. See the [[Case_Studies/Internet Archive|Case Study]] for more information.

:::'''[[Publish/Internet Archive|How to publish on Internet Archive]]'''
</div>

==SoundCloud==

<div class="smimg">[[Image:Soundcloud_orange.png|link=|left]]
[http://soundcloud.com SoundCloud] is a music and audio sharing community that allows artists to upload its works under the full suite of CC licenses. Its set of tools integrate nicely across the web, with adoptions from well known artists and labels.

:::'''[[Publish/Audio/SoundCloud|How to publish on SoundCloud]]'''
</div>

==Jamendo==

<div class="smimg">[[Image:Jam_artists_button_small.png‎|link=|left]]
[http://www.jamendo.com/en/creativecommons/ Jamendo] is a music platform offering artists the ability to promote, publish, and be paid for their music made available for download under Creative Commons and the Free Art licenses.

:::'''[[Publish/Audio/Jamendo|How to publish on Jamendo]]'''
</div>

==Other communities==
*[http://creativecommons.org/music-communities CC music communities]
*[http://creativecommons.org/record-labels CC record labels]
*[http://wiki.creativecommons.org/Musician Musicians and CC]

Developer Challenges

2013-09-15T20:38:41Z

Mike Linksvayer: Reverted edits by Babsesun (talk) to last revision by Boetbre

[[Category:Developer]]

{{Infobox|'''Here for [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Google Summer of Code]? See [[Summer of Code 2012]] for details about what we're looking for in [http://www.windows8softwares.com applications] this year. Please read that page... most of the ideas below do not apply this year.'''}}

{{Infobox|This page is for ideas and wishes: technology projects that would be beneficial for Creative Commons and our community, but which we don't have resources to build ourselves. If you've found a '''bug''' or have a feature request for existing tools/services, please report it in the [http://code.creativecommons.org/issues bug tracker].}}

We have ideas. Lots of ideas. And some of them might just be darn cool. So we challenge you, dear developer, help us out and win fame and glory (and maybe, just maybe, [http://creativecommons.org/weblog/entry/4293 a job]).

Some challenges have been met and completed, but fret not -- there are still lots of opportunities for fame and glory.

For more ways to participate take a look at the the [[Developers]] portal.

{{#forminput:Challenge|35||Add a New Challenge}}

== Google Summer of Code Ideas ==

We think these ideas are right-sized for Google [[Summer of Code]] projects. We'll definitely accept applications for ideas that aren't on this list, but these are a good starting point.

{{#ask:
[[Category:Challenge]]
[[Has Challenge Type::Developer]]
[[Is Complete::false]]
[[Has Tag::gsoc]]
| ?Related To
}}

== Open Challenges ==

{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]]
| ?Related To
| ?Has Tag
}}

== Completed Challenges ==
{{#ask:
[[Category:Challenge]]
[[Has Challenge Type::Developer]]
[[Is Complete::true]]
| ?Related To
| ?Has Tag
}}

XMP

2013-09-15T20:38:30Z

Mike Linksvayer: Reverted edits by Babsesun (talk) to last revision by Boetbre

CcHost FAQ

2013-09-15T20:38:24Z

Mike Linksvayer: Reverted edits by Babsesun (talk) to last revision by Boetbre

== Who is ccHost aimed at? ==
ccHost is a PHP library intended to be installed on web servers wishing to host CC licensed content, either by individuals or entire communities. ccHost music files, images, videos and zip archives. Extending the type of files hosts is done easily.

PHP or HTML programming is ''not'' required to set up a ccHost installation.

For all practical purposes, ccHost is a [http://en.wikipedia.org/wiki/Content_management_system CMS] specializing in CC licensing, 'remix' (revision) tracking and community features.

== Where is the FAQ for ccMixter.org? ==

It is located here http://ccmixter.org/media/viewfile/isitlegal.xml. There is much information at the aforementioned link which can help in answering your questions.

== How may I contribute? ==

There are so many ways to contribute to the development of ccHost. One of the best ways is by submittig bug reports and filing feature requests. Other ways to contribute are to contribute code (patches), to answer questions on the mailing list and on the chat channel. Doing any of these tasks drastically helps development.

== What is the goal of the ccHost Project? ==

Please see [[CcHost#Project_Goal]].

== Are ccHost and ccMixter the same thing? ==

ccMixter is one installation of the ccHost engine. ccHost can be installed for free by anyone onto a web server with Apache, mySQL and PHP and works both on Linux/Unix and windows servers.

ccMixter is the original concept for a site that would be like the "friendster for music." It has evolved much and eventually the decision was made to generalize the engine that powers ccMixter so that it could be used anywhere on multiple file formats.

== Does ccHost Cost anything? ==

No, it does not cost anything to download, install and use it.

== What file formats does ccHost support? ==

ccHost has a generalized architecture for many popular media types of formats.

=== Supported Formats ===

* [[AIFF]] Audio (aif)
* Java (AU) Audio
* [[FLAC]] Audio (flac)
* [[MIDI]] Audio (mid)
* [[MP3]] Audio (mp3)
* [[OGG]]/Vorbis Audio (ogg)
* Real Audio (rm)
* [[WAV]] (Riff) Audio (wav)
* Windows Media Audio (wma)
* [[ZIP]] Archive (zip)
* Windows Video (avi)
* Quicktime Video (mov)
* Real Video (rmvb)
* Windows Media Video (wmv)
* Windows BMP Image (bmp)
* [http://www.windows8softwares.com/ Windows 8] (xap)
* GIF Image (gif)
* JPG Image (jpg)
* PNG Image (png)
* Flash Video (swf)

== Please add your Question and Answer below! ==

...

[[Category:Developer]]
[[Category:CcHost]]
[[Category:FAQ]]

LiveContent 2 0

2013-09-15T20:38:13Z

Mike Linksvayer: Reverted edits by Babsesun (talk) to last revision by Boetbre

[[Category:Technology]]
[[Category:Developer Challenges]]
[[Category:Developer]]
[[Category:freesoftware]]
[[Category:opensource]]
[[Category:ccLiveCD]]
[[Category:LiveContent]]

{{Infobox|'''This project has been retired. The ISO of the DVD is available [http://www.archive.org/details/livecontent2.0 here].'''}}

{{Infobox|
'''LiveContent 2.0''' is a LiveDVD full of free and open source software and Creative Commons' licensed open content — audio, video, image, text and educational resources. LiveContent is a project for anyone to explore to learn more about about open content that can be freely used, copied, and built upon.

Help us identify more great CC-licensed content by adding suggestions [[#CC_Content|HERE]].
}}

==Goals==

#'''Daily build infrastructure'''
#'''Autocuration of Open Content'''
#'''Standardization of content feeds and APIs'''

LiveContent 2.0 works to address several technical issues surrounding our interaction with open content. First, 2.0 aims to develop, using the Fedora architecture, a daily build structure of the LiveContent LiveDVD. Second, 2.0 aims to generate "autocurated content." Autocurated content uses APIs and content feeds from open content providers and hosting organizations that can be used to pull down the most current, "live" open content. Third, 2.0 aims to provide a nudge to prompt more content curators to provide standardized open content feeds so that others can use this infrastructure for their own projects.

We believe that the LiveContent distro can provide a useful platform that allows users to test explore free and open content and test out free, open source software. The LiveContent distro provides information and documentation about Creative Commons, the FOSS movement, and demos to how users can take advantage of the media included to re-create, re-mix and re-share content.

==Technical Documentation==

* [[Autocurated_Packages|autocurated packaging of content; original brain dump]]
* [[Flickr_Autocuration|Flickr autocuration process for LiveContent 2.0]]

==Contents==

===Fedora 8 is the base architecture===
*keeping most applications from [[LiveContent_1_0 | v1.0]] as base (OpenOffice, Inkscape, The Gimp, Firefox, Totem, Evince, gThumb, Tuxpaint)

===CC Content===
==== Currently includes ====
* Flickr "interesting" photos
* Wikimedia Commons 2007 Pictures of the Year
* Jamendo music sampler
* Simuze.nl music sampler
* MIT OCW top 10 downloaded courses
* Assorted videos from BoingBoing, Make, TED, CC, FreeMe DVD
* CC licensed texts

==== Your ideas? ====
* Jamendo music selections
* ideas from OLPC content jam (education, books)
* Elephant Dream
* Podiobooks

==== General ideas ====

CC is working on developing a system to "autocurate" content from CC-friendly sites such as Flickr. In the future we want to be able to transform [[Content Directories]] into the base for LiveContent. We want to work with content curators to establish a standardized format for providing CC-licensed content feeds so that the "autocuration" part becomes much easier for everyone. Categories may include, but not limited to:
*Audio
*Video
*Text
*Image
*Educational resources
*marking--a README file generated with the autocuration process to mark the media with the appropriate CC license

==Screenshots==
[[Image:Lc-2.0-front.jpg|300px]]

Cover Art

<gallery>
Image:LC2.0_Desktop.jpg|LiveContent 2.0 Desktop
Image:LC2.0_Start_page.jpg|Informational pop-up
Image:LC2.0_Wikimedia_2007_photos_of_the_year.jpg|Wikimedia 2007 Photos of the Year
Image:LC2.0_Flickr_interesting_photos.jpg|Flickr Interesting Photos, autocurated
</gallery>

==Design Considerations==
* working on new color scheme for desktop
* will keep content icons the same as 1.0
* modified physical packaging to match new color scheme
* icons that match apps, renaming of things like openoffice
* GNOME accessibility for disabled?

==Start page==

'''Welcome to LiveContent 2.0'''
*Creative Commons [http://creativecommons.org/projects/livecontent LiveContent] is a project to showcase and spread the word about open content that you can freely use, copy, and build upon. The LiveContent disc is a [http://en.wikipedia.org/wiki/LiveDistro LiveDVD] full of a sampling of and links to free and open source creativity software and Creative Commons' licensed free and open content — audio, video, image, and text — for anyone to explore. Please use this disc if you are interested in trying free media and possibly want to create your own with tools like OpenOffice.org, Inkscape, Gimp and more.

'''LiveContent Goals'''

1. ''Exploring and Creating with Open Content''

*Check out user-generated creative content like photos, music, and videos sourced from sites like Flickr, Jamendo, and Blip.tv. All the content available here is free and ready to copy, share, remix, and reuse. Click on the desktop icons to explore content within that category. All the content is licensed with one of our six main [http://creativecommons.org/about/license/ Creative Commons licenses]. Access the applications by clicking "Applications" in the menu at the lower left corner of the desktop. Plug in a thumb drive to save open content to it.

*[http://search.creativecommons.org/ Find More Creative Commons Content]

2. ''Developing Technical Standards''

*LiveContent 2.0 works to address technical issues surrounding our interaction with open content:
**Developing a daily LiveDVD build to be hosted at Fedora Project [http://spins.fedoraproject.org site]
**"Autocurating" Open Content feeds from sites like [http://www.flickr.com Flickr] and [http://www.jamendo.com Jamendo]
**Pushing to standardize APIs so that others can also easily interact with the content provided by CC-friendly content curators

3. ''Connecting and Participating''

*There are lots of exciting projects working to foster a sharing economy of information, creative media and open content. Help support projects to minimize barriers to sharing and reusing, and help build the open content base by adding your favorite CC-licensed-powered project to the [[Content Directories]] on the [http://wiki.creativecommons.org CC wiki].

*[http://sciencecommons.org/ Science Commons]
*[http://learn.creativecommons.org/ ccLearn]
*[http://freeculture.org/ Students for Free Culture]
*[http://www.opencontentalliance.org/ Open Content Alliance]
*[http://www.archive.org/ Internet Archive]
*[http://www.openlibrary.org/ Open Library]
*[http://spreadopenmedia.org/ Spread Open Media]

'''What is Creative Commons?'''

*Creative Commons provides free tools that allow creators like authors, artists, scientists and educators share their work with the world. Creative Commons let you legally share, remix and reuse creativity!

*[http://support.creativecommons.org/videos#wwt Creative Commons explained - Video] | [http://creativecommons.org/about/ Learn More]

'''What is free, open source software (FOSS)?'''

*Free, open source software grants users the ability to freely run, copy, modify and share software with others. It's an important community that empowers innovation and creativity without the lock-in of proprietary software. The LiveContent disc is built on [http://www.fedoraproject.org/ Fedora], a Linux-based operating system that showcases the latest in free and open source [http://www.windows8softwares.com/ software]. Fedora is always free for anyone to use, modify, and distribute.

*[http://www.redhat.com/magazine/006apr05/features/licenses/ Open Source Software licenses explained - Video] | [http://en.wikipedia.org/wiki/FOSS Learn More]

'''Quitting out of LiveContent'''

*Quit out of LiveContent by clicking "System" from the menubar at the bottom of the desktop. Next, click "Shut Down" and choose whether to restart the computer into the default operating system or shut down.

'''Thank You to Supportive Collaborators!'''
*[http://www.worldlabel.com Worldlabel.com] has provided generous support for the development and distribution of this project.
*Technical infrastructure provided by [http://www.fedoraproject.org/ Fedora].

==Distribution Options==
*LiveContent 2.0 will be available for download at http://spins.fedoraproject.org
*LiveContent 2.0 will be available for purchase at http://www.on-disk.com
*CC will do a small run for internal promotion with option for larger run later
** have on hand to give out at conferences, meetings
** ccLearn
** distribute with other swag like buttons, stickers

==Community Involvement==

=== Share how you use LiveContent ===
* please add what you've used LC for here!

==Other Connections==
* [http://www.openclipart.org/ openclipart]
* [http://openfontlibrary.org/ openfontlibrary]
* [http://www.openlibrary.org/ openlibrary]
* [http://www.worldlabel.com/Pages/openoffice-template.htm opendocumenttemplates]
*[http://www.freedomtoaster.com/ Freedom Toaster]
**Freedom Toasters are conveniently located, self-contained, computer-based, 'Bring 'n Burn' facilities.
**Like vending machines, preloaded to dispense confectionery, Freedom Toasters are preloaded to dispense free digital products, including software, photography, music and literature.
**The Freedom Toaster project began as a means of overcoming the difficulty in obtaining Linux and Open Source software due to the restrictive telecommunications environment in South Africa, where the easy downloading of large pieces of software is just not possible for everyone.

*'''Add more ideas here!'''

Cultivating the Public Domain

2013-09-15T20:35:20Z

Mike Linksvayer: Reverted edits by CCeditman (talk) to last revision by Careindeed

[[Category:Legal]]

''Originally published at http://web.archive.org/web/20021217080646/ http://creativecommons.org/learn/legal/cultivating''

Before 1978, U.S. law made non-copyright status the default for published creative works. “[C]opyright protection was lost permanently if the [copyright] notice was omitted from the first authorized published edition of a work or if it appeared in the wrong form or position. . . . [A] basic failure to comply with the notice provisions forfeited copyright protection and put the work into the public [http://www.citidomain.net domain] in this country.”[1] If the author did not take the trouble to put a copyright notice on her work, it passed into the public domain once published. Public domain status was the default.

After January 1, 1978 (the effective date of the Copyright Act of 1976), omission of a copyright notice could later be corrected, and thus did not result in outright forfeiture of copyright.[2] As of March 1, 1989 (the effective date of the Berne Convention Implementation Act of 1988), notice of copyright is now entirely optional. [3] Today, copyright status, rather than public domain status, is the default for all “original works of authorship fixed in any tangible medium of expression.” [4] As the Copyright Office puts it, “copyright is an incident of creative authorship not dependent on statutory formalities.”[5]

This shift in the copyright default rule has practical impacts that are especially striking in an age of inexpensive self-publishing and information retrieval. First, the author who does not want to exercise the restrictions that copyright law makes available to her now bears the burden of signifying the public domain status of her work. Caselaw suggests that a copyright holder must perform some “overt act” demonstrating her intent to surrender her rights.[6] The amateur Internet author who has no intention of limiting the ways in which other people may use her work unintentionally imposes copyright limitations unless she knows to comply with the overt act requirement. Even if she has no intention of bringing a copyright infringement action, would-be re-users cannot safely assume that she won’t-even if the work bears no copyright notice. Of course, the elimination of the notice requirement means that the author who does want his work copyrighted is relieved of the burden of affixing a proper copyright notice to his work. The point is that the burden has shifted to the author who prefers public domain status, and that many of the authors who can now self-publish their work on the Internet likely fall into the newly-burdened category. [7]

The second practical impact of the shift in the copyright default rule has yet to be realized. When the copyright expires on a work that is created today, it may be extremely difficult to establish that the work has passed into the public domain. In the absence of a copyright notice or registration requirement, there will not necessarily be a publicly-available record of the date of creation of the work (or even of the identity of its author), and therefore no practical way to determine whether copyright has expired. [8] Public domain works that might otherwise be made widely available via the Internet (or whatever method of information retrieval is relevant by the time modern copyrights expire) may never be identified. [9]

One goal of the Creative Commons project is to alert creators who do not intend to copyright their work to the “overt act” requirement and to help them comply with it. Then we hope to help creators label works in a way that makes it clear to potential re-users that the work is in the public domain. And we intend to develop mechanisms for attaching “public domain” labels to digital works in a way that computer applications can recognize and process-enabling easy location and retrieval of digital works in the public domain.

Some copyright holders may be unwilling to free their work to the public domain before their copyright expires, but happy to relinquish some of the rights that copyright affords them. Copyright holders with the resources to negotiate licenses can voluntarily cede some of their rights. And organizations like the Free Software Foundation offer ready-made licenses that authors may use to give the public permission to copy and distribute copyrighted works (primarily software) without seeking the authors’ permission, so long as certain conditions are observed. [10]

Inspired in part by the work of the Free Software Foundation, Creative Commons plans to build a menu of customizable licenses appropriate for use by other types of creators who want to retain some rights while sharing their work with the public on terms more generous than copyright. We hope to draw attention to and complement existing efforts like the Electronic Frontier Foundation’s Open Audio License; [11] and we hope to improve on such efforts by making it easier for potential re-users to identify works that they may safely use without worrying about the intricacies of fair use. Just as a work could be labeled “public domain” in a way that humans and machines could recognize, works could be labeled according to license terms like “This work may be used for any noncommercial purpose,” or “Derivative works may be created based on this work so long as the derivative works are licensed under these terms.” We envision a system of licensing and labeling that would make it possible, for example, for an artist compiling a digital collage easily to use a search engine to locate all online images that are freely available for copying and modification.

----
[1] U.S. Copyright Office, Circular 22: [http://www.loc.gov/copyright/circs/circ22.html How to Investigate the Copyright Status of] [http://www.ksaday.com a] [http://www.planetsofts.com Work], see also, e.g., Canfield v. Ponchatoula Times, 759 F.2d 493, 497 (5th Cir. 1985); Burke v. Nat. Broad. Co., Inc., 598 F.2d 688, 691 (1st Cir. 1979).

[2] Copyright Act of 1976, Pub. L. 94-553, §§405-406, 90 Stat. 2541; see also U.S. Copyright Office, Circular 22: How to Investigate the Copyright Status of a Work.

[3] Berne Convention Implementation Act of 1988, Pub. L. 100-568, §7, 102 Stat. 2853 (amending 17 U.S.C. §§401-06); U.S. Copyright Office, Circular 22: How to Investigate the Copyright Status of a Work. Although notice is no longer a prerequisite for copyright, it does offer an advantage to the copyright holder in the event of litigation. Specifically, if proper notice appeared on an infringed work, the infringer may not use the defense of innocent infringement to mitigate damages. 17 U.S.C. §401(d).

[4] 17 U.S.C. §102.

[5] U.S. Copyright Office, Circular 22: How to Investigate the Copyright Status of a Work. The Copyright Act does impose the requirement that two copies of every work published in the United States be deposited with the Library of Congress.17 U.S.C. §407. But the penalty for failure to deposit is a fine, not loss of copyright protection. Id. §407(a), (d).

[6] See 4 Melville B. Nimmer & David Nimmer, Nimmer on Copyright §13.06 (2001) (citing caselaw); see also, e.g., National Comics Publications, Inc. v. Fawcett Publications, Inc., 191 F.2d 594 (2nd Cir. 1951).

[7] See generally Jessica Litman, Digital Copyright 103-107 (2001) (suggesting that many Internet publishers are not motivated by the possibility of exploiting intellectual property rights).

[8] See generally U.S. Copyright Office, Circular 22: How to Investigate the Copyright Status of a Work (cautioning that “[t]he complete absence of any information about a work in the [Copyright] Office records does not mean that the work is unprotected”).

[9] The Copyright Office currently maintains no list of public domain works. See U.S. Copyright Office, Questions Frequently Asked in the [http://www.loc.gov/copyright/faq.html#q11 Copyright Office Public Information Sec][http://www.ksaday.com/2012/05/situs-download-lagu-akan-dihapus.html tion], at #11.

[10] See [http://www.fsf.org/licenses/licenses.html GNU General Public Licen][http://www.ksaday.com/2012/05/games-gratis.html se].

[11] See [http://www.eff.org/IP/Open_licenses/eff_oal.html EFF Open Audio License], see also, e.g., [http://dsl.org/copyleft/dsl.txt Design Science License], [http://opencontent.org/openpub/ Open Publication License], [http://www.publiclibraryofscience.org/ploslicense.htm Public Library of Science Open Access License], [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License], [http://openmusic.linuxtag.org/showitem.php?item=209 Open Music License].