Creative Commons - User contributions [en]

Philippines

2012-07-05T03:44:57Z

Sawyer Lee:

{{Jurisdiction
|jurstatus=Active
|status=3.0
|country code=ph
|homepage=http://creativecommons.org/international/ph/
|mailing list=http://lists.ibiblio.org/pipermail/cc-ph/
|region=Asia-Pacific
|affiliated=Arellano University School of Law
|affurl=http://www.arellanolaw.edu/
|afftype=academic institution
|plead1=Michael Vernon Guerrero
|pemail1=berneguerrero@gmail.com
|flagurl=http://creativecommons.org/images/international/ph.png
|blog=http://creativecommons.org/international/ph/
}}
The Creative Commons Philippines license suite is available in the following version. [http://creativecommons.org/choose/?jurisdiction=ph 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 e-Law Center of the [http://www.arellanolaw.edu/ Arellano University School of Law] to create Philippines jurisdiction-specific licenses from the generic Creative Commons licenses.

=CC Philippines List=

Project Lead: [mailto:berneguerrero@gmail.com Michael Vernon Guerrero], Acting Executive Director of the [http://www.lawphil.net/ e-Law Center] of the [http://www.arellanolaw.edu/ Arellano University School of Law].

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

=More about AUSL=

Named after the [http://www.supremecourt.gov.ph/elibrary/biodata/arellano_cayetano.htm First Chief Justice of the Philippine Supreme Court], [http://www.arellanolaw.edu/cayetano.html Cayetano S. Arellano], the school, a non-stock non-profit institution, was established in 1938 and boasts of more than six decades of providing quality legal education.

Foremost of the school objective is to create global lawyers, practitioners who are deeply educated in the law, practice-ready, and devoted to service not only in the local but also the international community. Arellano Law prides itself for being one of the most populous law schools in the Philippines with faculty members who have distinguished themselves in law practice, the judiciary, government service, and the academe. The law school revels in being one of the few schools in the Philippines that produce the most number of lawyers in the annual bar examinations administered by the Supreme Court. The school has likewise included technology law as [http://www.repairpartstock.com/ part] of its curriculum and utilizes cutting-edge technology in law instructions.

For more information about AUS-Law, please visit our webpage at http://www.arellanolaw.edu/.

=About the e-Law Center=

The Center was founded in November 2002 under the auspices of the [http://www.arellanolaw.edu/ Arellano University School of Law], following the launching of the school’s [http://www.lawphil.net/ LAWPHiL Project], considered as one of the most popular on-line and electronic databank of Philippine law and jurisprudence accessible for free to the general public.

The Center is pursuing projects in research, publication, policy initiatives and advocacy, capability building, academic support, and linkages in the field of information and communication technology as it affects the Philippine legal system.

Among the significant activities of the Center is the publication of the first quarterly IT Law Journal in the Philippines and the formation of the first law student-based [http://www.arellanolaw.net/ IT Law Society] in 2004.

Germany

2012-07-05T03:39:59Z

Sawyer Lee:

{{Jurisdiction
|jurstatus=Active
|status=3.0
|country code=de
|homepage=http://de.creativecommons.org/
|logourl=http://de.creativecommons.org/wp-content/uploads/2010/12/logo_cc-de.jpg
|mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-de/
|twitter=http://twitter.com/cc_de
|social=http://www.linkedin.com/groups?mostPopular=&gid=164152
|otherurl=http://identi.ca/ccde
|mailing=c/o newthinking communications
Schönhauser Allee 6-7
10119 Berlin
|region=Europe
|affiliated=European Academy of Law and Computing (EEAR)
|affurl=http://www.eear.eu/
|afffocus=IT and law
|afftype=academic institution
|affiliated2=newthinking communications
|affurl2=http://newthinking.de/
|afffocus2=IT, media, and politics
|afftype2=private company
|affiliated3=institute of Law and Informatics (Institut für Rechtsinformatik) at Saarland University
|affurl3=http://rechtsinformatik.jura.uni-sb.de/
|afffocus3=IT and law
|afftype3=academic institution
|plead1=John Hendrik Weitzmann
|pemail1=john@creativecommons.de
|ptitle1=Legal Project Lead
|plead2=Markus Beckedahl
|pemail2=markus@creativecommons.de
|ptitle2=Public Project Lead
|teamsize=13
|flagurl=http://creativecommons.org/images/international/de.png
|leads=Legal Project Lead: John Hendrik Weitzmann; Public Project Lead: Markus Beckedahl;
|blog=http://de.creativecommons.org/
}}
Visit the [http://de.creativecommons.org/ jurisdiction's website].

The Creative Commons Germany license suite is available in the following version. [http://creativecommons.org/choose/?jurisdiction=de 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 [http://www.eear.eu/ European Academy of Law and Computing] and the [http://www.rechtsinformatik.de/pages/home.php?lang=EN Institute of Law and Informatics] at [http://www.uni-saarland.de/en Saarland University] to create Germany jurisdiction-specific licenses from the generic Creative Commons licenses.

=CC Germany List=

Legal Project Lead: [http://www.rechtsinformatik.de/pages/institut/mitarbeiter.php?lang=DE John Hendrik Weitzmann]

Public Project Lead: Markus Beckedahl

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

=More about the European Academy of Law and Computing (EEAR), Merzig and Saarbrücken=

The [http://www.eear.eu/ European Academy of Law and Computing] was established in the year 2005 as a non-profit corporation situated in Merzig and Saarbrücken, near the borders to France and Luxemburg in south-western Germany. The Academy wants to build bridges between the IT sector and the world of legal professionals. Its mission therefore is threefold, combining research activities, educational courses and development of software and services.

In the area of research the Academy offers various workshops, conducts EU funded studies and hosts the Merzig Legal Database Forum [http://www.eear.eu/index.php?id=3 (Merziger Datenbankenforum Recht)], to name a few. In regard to education and additional qualification for lawyers a fully equipped test environment is on offer as well as a wide range of courses, covering topics like XML, Digital Data Management and Legal Web Services. The development activities include the German Database of Higher Education Law [http://www.eear.eu/kmk-hochschulrecht/ (KMK Hochschulrecht)], the Caveat Registry Service, applications for implementing the XJustiz standard, and other projects.

=More about Institute of Law and Informatics (Institut für Rechtsinformatik) at Saarland University, Saarbrücken=

The ‘Saarbrücker Rechtsinformatik’ (Law and Informatics in Saarbrücken) was founded in 1988 along with the establishment of the department of law and informatics, which was originally funded by the Stifterverband für die Deutsche Wissenschaft (Donors’ Association for the Promotion of Sciences and Humanities in Germany) and headed by Prof. Dr. Herberger. Today the Institute of Law and Informatics at Saarland University (Universität des Saarlandes in Saarbrücken, Germany) is maintained by the [http://herberger.jura.uni-sb.de/ Chair for Civil Law, Legal Theory and Legal Informatics Prof. Dr. Maximilian Herberger] and the [http://ruessmann.jura.uni-sb.de/ Chair for Civil Law, Civil Procedure and Philosophy of Law Prof. Dr. Helmut Rüßmann].

The [http://www.rechtsinformatik.de/pages/home.php?lang=EN Institute of Law and Informatics] concerns itself with the question of how legal professionals can improve their ways of working with the aid of new technology. Law and informatics is part of applied information technology just like business information systems and medical informatics are. In this context the Institute of Law and Informatics feels that it is its duty to make legal information electronically available, therefore deviating from the traditional printed format, and to support the electronic exchange of legal documents. Examples include online legal databases as well as the technical maintenance of the decision databases of the Courts, for example the [http://www.bundesverfassungsgericht.de/ websites of the Federal Constitutional Court], the Social, Labour and Fiscal Courts of the Saarland as well as the Administrative Court in Frankfurt am Main.

Furthermore, the Institute of Law and Informatics deals with Information Law and legal problems of new media, especially Internet Law. The Internet poses many legal questions, which concern current and future legislation of almost all areas of law and numerous regulations. In relation to the named issues the Institute concentrates mainly on questions of civil law.

=Acknowledgements=

Creative Commons would like to thank the former project leads,
Professor Dr. Thomas Dreier, Ellen Euler, and Oliver Meyer , and Dr. Till Jaeger, who in a shared effort adapted the CC licenses to German copyright law; the

[http://www.zar.uni-karlsruhe.de/iirdreier/ Institute for Information Law at the University of Karlsruhe] and the

[http://www.ifross.de/ Institut für Rechtsfragen der Freien und Open Source Software], for the extensive work done so far and their continuing support.

Jurisdiction: Creative Commons Germany

Date submitted: December 2010

=Roadmap=

==Description==

The German CC Jurisdiction Project aims at supporting a better way of sharing online. It does so by making the CCPL work under German law and by bridging gaps between the world in which Creative Commons was invented and everyday online reality in Germany, that exist in terms of both history of law as well as discourse of creativity.

The project has two Leads, both located mainly in Berlin. John Weitzmann as Legal Project Lead is supported by the [http://eear.eu/index.php?id=47 European Academy of Law and Computing (EEAR)], Markus Beckedahl as Public Project Lead is supported by [http://newthinking-communications.de/ newthinking communications].

==Priorities for 2011==

- Run one or more contests online to let fans do new designs for schwag (both graphics only and with text) and have the best produced also as parts of flyers, brochures and other new CC info material. Of course any new designs will be CC licensed and as such re-usable for others.

- Make progress on the issues of porting gaps and plain language reform, in cooperation with the Communia Network and CC Portugal, who have agreed to work on this as a CC Europe task force. The goal is to have a paper ready for the CC meeting in the 3rd quarter.

- Act as cooperation partner for re:publica 2010 and put CC-relevant topics on the agenda of the conference. One way to go forward on this one will be to individually invite possible adopters to learn more about the CCPL and its application at re:publica. Another part of this item is to establish re:publica as a background for regular CC Europe meetings..

- Build the basic structure and introductory texts for the CC Commentary and build a group of volunteers to work on the first set of content. Some positive replies have already been received on the latter, but more needs to be done.

- Boost social media integration and donation functions on our website [http://www.ksaday.com Berita Terbaru]

==Project Composition==

'''Legal Lead'''

John H. Weitzmann supported by EEAR

'''Public Lead'''

Markus Beckedahl supported by newthinking communications

'''Affiliate Team (all part-time only)'''

Tim Baumann, Filmmaker (Team Speaker Film/Video)

Ulrike Elteste, Lawyer

Ralph Hecksteden, Jurmatix GbR (Sysadmin)

Professor Dr. Maximilian Herberger, Law Professor, Saarland University

Ronen Kadushin, Designer (Team Speaker Design)

Sarah Leiendecker, Institute for Law and Informatics, Saarland University

Sabine Micka, EEAR (Accounting/Donations)

Hans-Martin Schmidt, Lawyer (Team Speaker Open Data)

Klaas Schmidt, Lawyer

Wolfgang Senges, Media Consultant

Michael Weller, Lawyer, EEAR

'''Helpers and Interns'''

From time to time we have additional volunteers (and regular interns at newthinking communications) helping with everyday work or special projects.

==Web resources==

''Jurisdiction website''

Our [http://de.creativecommons.org/ website] runs on Wordpress, with a theme modified from one of the previous themes of creativecommons.org. Next items on the agenda for the site are a better integration of our social media channels (identi.ca and twitter), an easy web-based donation scheme (using either PayPal or Sofortüberweisung.de), a remodeling of our FAQ section and integration of a module to aggregate CC news on the site.

''CC Category within netzpolitik.org Weblog''

Markus Beckedahl is a very sought-after evangelist for freedom of the internet, open government and – as CC Germany Public Lead – also for CC licensing. He runs one of the top ten weblogs in Germany, [http://www.netzpolitik.org netzpolitik.org], which contains a separate [http://www.netzpolitik.org/category/creative-commons/ category] for CC-related topics with hundreds of articles.

''Internal ATeam Wiki''

For internal coordination of the Affiliate Team and for material collection and other purposes the EEAR maintains a moinmoin wiki that all team members can access.

==Metrics==

We see the numbers of CC licenses or CC licensed content as a rather arbitrary factor, because the sheer numbers themselves do in no way reflect quality and relevance of the so lincensed content. They also tend to distort debates about the benefits and downsides of alternative licensing away from the aspect of individual creators making licensing decisions. We see more value in highlighting certain projects, groups or individuals that in our opinion are possible role models for CC licensing.

==Competitions==

''CC DE Schwag Competition''

In cooperation with Wikimedia Germany we want to run an online competition to make new designs for CC schwag and merchandising material. This is meant to raise awareness of how diverse the group of CC licensors and re-users is and to also benefit the project in terms of material to promote CC's cause. The winners will be announced at one of the larger gatherings of net-minded people in Berlin (28C3, re:pubica, Linuxtag, …).

==Workshops, Presentations and Strategic Talks==

People from the CC DE Affiliate Team (ATeam) and the two project leads are frequently invited to talk about CC and alternative licensing and write [http://lewisseo.com/ articles] and papers on the topic. There have also been individual consultations and strategic talks on the CCPL and their application with several stake holder institutions, one of the most prominent being the CC-GEMA dialogue, an exchange with the leading German collecting society for musical works. Other such consultantions have been held with public broadcasters, political and philathropic foundations and media companies.

==Institutional and Project Cooperations==

CC Germany is always open to cooperate with other groups and institutions if this apprears to be beneficial to our common(s) cause. In the past, such cooperations have existed f. e. with the German Film Museum Deutsche Kinemathek, the Board of Open Youth Education of the State of Baden-Württemberg and others. At the moment and in the coming year we will especially cooperate with Google Germany's policy group and their Co://aboratory and also with the activists of the C3S project that explored the pros and cons of setting up a collecting society for CC content.

==Regional Collaboration==

Since 2009 there is a regional collaboration on European CC Projects under the name CC Europe. It is not formalized and has developed out of the Communia Project, a EU-funded Thematic Network on the digital public domain to which many European CC Projects are members. CC Germany hat built and runs the CC Europe website at http://europe.creativecommons.org as a central entry point for anyone interested in CC licensing and related topics at the European level. In addition to that we maintain the CC Europe mailinglist and coordinate regional meetings and more.

CcHost

2012-07-05T03:32:01Z

Sawyer Lee:

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

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

= Download =

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

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

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

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

= Documentation =

[[cchost/Documentation|ccHost 5 Documentation]]

=Communication=

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

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

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

=== Usage Examples ===

* [http://ccmixter.org ccMixter] - Primary usage of ccHost is the Creative Commons remix site, ccMixter.
* [http://www.openclipart.org/ Open Clip Art Library ccHost in testing]
* [http://www.openfontlibrary.org Open Font Library]
* [http://freemusic.freeculture.org Freemusic Project]
* [http://lewisseo.com/ free article directory]
* [http://www.opensourcecinema.com/cchost Open Source Cinema]
* [http://rayne.hellawack.net/ Matrix Rayne Online]
* [http://remix.machinehasnoagenda.com/ remix.linux]
* [http://www.ccmixter.co.za/ ccmixter South Africa]
* [http://fourstones.net fourstones.net] Victor's personal website
* [http://www.esolpc.com/teacherhost/ TeacherHost] - for Instructors to share instructional materials.
* [http://adrenalinicsound.com/ Adrenalinic Sound]
* [http://creativecommons.org.tw/formoz ccMixter from CC Taiwan]
* [http://www.overmundo.com.br/overmixter Overmixter - Brazil]
* [http://www.iamacc.org/ Iamacc.org]
* [http://www.enciclopediacecilia.org/remix/ Remix Cecilia] at the Enciclopedia Cecilia project (Spanish).
* [http://audio.ibeat.org/ iBeat]

----

= 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

Documentation

2012-07-05T03:28:40Z

Sawyer Lee:

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

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

'''Join the community'''

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

'''Many ways to contribute'''

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

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

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

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

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

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

'''Using the Creative Commons Licences'''
* [[Media:Creativecommons-how-to-license-poster_eng.pdf|How To License poster]] (pdf) ([http://www.scribd.com/doc/2227445/creativecommonshowtolicensepostereng scribd.com])
* [http://creativecommons.org.au/materials/licencesexplainedcontentcreatorsinfopack.pdf Creative Commons Licences Explained] (pdf)
* [http://creativecommons.org.au/learn-more/fact-sheets/what-are-the-creative-commons-licences-factsheet Quick Guide to the Creative Commons Licences] (pdf) ([http://www.scribd.com/doc/16536016/What-are-the-Creative-Commons-licences-factsheet scribd.com])
** [http://creativecommons.org.au/www/materials/factsheets/cc-licences-indesign-package.zip Indesign files]
* [http://creativecommons.org.au/content/licensing-flowchart.pdf Creative Commons Licensing Flowchart] (pdf) ([http://www.scribd.com/doc/16540395/Which-Creative-Commons-licence-is-right-for-me-poster scribd.com])
* [[Media:Creativecommons-licensing-and-marking-your-content_eng.pdf|Licensing and Marking Your Content]] (pdf) ([http://www.scribd.com/doc/2227448/creativecommonslicensingandmarkingyourcontenteng scribd.com])
* CC For Citizen Journalism in Lebanon. 10 Legal Rules on social activism and copyright by Martin Wählisch:
** [[Media:CopyrightLawLEB_EN.pdf| English]]
** [[Media:CopyrightLawLEB_AR.pdf| Arabic]].

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

'''Multimedia'''
* [[Sharing_Creative_Works|Sharing Creative Works Comics]] - A general introduction to copyright and CC licensing ([http://www.scribd.com/doc/2227656/creativecommonssharingcreativeworkseng scribd.com])
** [[Media:Sharingcreativeworks.zip|Inkscape SVG source files]] (zip)
* [http://creativecommons.org/videos/ CC Videos]
** See the videos on [http://creativecommons.blip.tv/ blip.tv], [http://itshumour.blogspot.com/2010/02/top-five-hilarious-videos-on-youtube.html youtube] [http://dotsub.com/view/search/?q=creative%20commons dotsub], [http://revver.com/u/ccommons/ revver], or [http://youtube.com/user/commonscreative youtube] [http://lewisseo.com/ free article directory].
** [[Translate#Videos | Video source files]]
* [http://wiki.creativecommons.org/Comics CC Comics]

'''For Teachers'''
* A [http://creativecommons.org.au/learn-more/educators-resources collection] of resources on finding and using Creative Commons specifically designed for teachers, including fact sheets, slideshows, videos and worksheets

== CC Learn Productions==
====Organizational Media====
* CC Learn Informational Flyer ([[Media:Cclearn-information-flyer.pdf|pdf]]) ([[Media:Cclearn-information-flyer-print.pdf|pdf - print w/.125" bleed]]) ([http://www.scribd.com/doc/15058699/ccLearn-Informational-Flyer Scribd])

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

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

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

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

== Developer ==
* [[Developers]] - Documentation for software developers.

== FAQ ==
* [[FAQ]] - Important documentation of frequently asked CC questions.

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

== Legal ==

* [http://creativecommons.org/about/license/ License Your Work]
* [http://www.thefunnyquotessayings.com/cool-hilarious-funny-quotes-sayings/ Funny sayings]
* [[Before Licensing]]
* [[Legal Concepts]]
* [[Podcasting Legal Guide]]

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

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

== Metrics ==

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

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

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

== White Papers ==
* [[Media:Creativecommons-licensing-for-public-sector-information_eng.pdf|Creative Commons Licensing for the Public Sector]] (pdf)

== Help Translate Documents ==

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

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

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

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

Please help us complete these!

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

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

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

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

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

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

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

Brisbane Salon

2012-07-05T03:25:35Z

Sawyer Lee:

{{Event
|Event Name=Brisbane Salon
|Mainurl=http://wiki.creativecommons.org/Brisbane_Salon
|date=2006/11/29
|end_date=2006/11/29
|Location=Brisbane, Australia
|EventType=Salon
|EventCategory=Salon
}}
[[Category:Salon]] [[Category:Event]]

== Help start a Salon in Brisbane! ==

It is easy, just read [[Start Your Own Salon]]

== Past Salon ==

Who would have thought a Wednesday night could have so much excitement? On 29 November, Creative Commons Australia (CCau) (http://creativecommons.org.au), in conjunction with Queensland University of Technology (http://www.qut.edu.au), the Australian Research Centre of Excellence for Creative Industries and Innovation (CCi) (http://www.cci.edu.au) and the Institute for Creative Industries and Innovation (iCi) (http://www.ici.qut.edu.au), held the first Australian ccSalon, a live showcase of Creative Commons art, music, film and text in Australia.

In a ‘two birds/one stone’ move CCau decided to take full advantage of the relationship building opportunities of the Salon, and make sure that we had a diverse group of attendees, by tying the Salon to a series of industry meetings, which we held at the same venue in the afternoon leading up to the Salon. These meetings, which we dubbed the first CCau Industry Forum, were designed to act as both education and research tools, providing an opportunity to explore and explain the potential for Creative Commons across government, education and the creative industries both to generate awareness and help direct CCau’s focus from here.

The Forum proved surprisingly popular, with about 60 attendees from a range of private organisations, government departments, industry bodies, as well as individuals with an interest in the area. Asides from the fabulous crew at CCau (including Project Lead Professor Brian Fitzgerald, Project Manager, Jesscia Coates, Project Officer, Elliott Bledsoe and Research Officer, Nic Suzor), other Creative Commons licence users/advocates from Australia were given the opportunity to engage directly with the attendees, discussing their experiences of, motivations for, and results from using Creative Commons and other open content licensing models. Speakers included Tim Norton from A New Leaf Media (http://www.anewleaf.com.au), Anna Helme from Engage Media (http://www.engagemedia.org), Scott Kiel-Chisholm from the Open Access to Knowledge (OAK) Law Project (http://oak.qut.edu.au), Neale Hooper from the Queensland Government’s Whole of Government Information Licensing Project (http://www.qsic.qld.gov.au/qsic/QSIC.nsf/CPByUNID/6C31063F945CD93B4A257096000CBA1A) and Delia Browne from the Ministerial Council on Education, Employment, Training and Youth Affairs (MCEETYA) (http://www.mceetya.edu.au).

And as the warm Brisbane day cooled off into evening, the Salon heated things up with some smoking live performances by Brisbane/Sydney DJ artist collapsicon (http://www.collapsicon.net) and Brisbane hybrid arts ensemble collusion (http://www.collusion.com.au). Andrew Garton of Toysatellite (http://www.toysatellite.org) also provided a lavish audio/visual feast incorporating content from across the Australian Creative Commons(http://lewisseo.com/). Tasty tidbits included the work of photographers from a specially created group on Flickr (http://www.flickr.com/groups/ccSalon), the animation works of Blackbrow (http://www.blackbrow.com), photos from Brisbane photographer Frollop (http://www.frollop.com) and content from the Community Convergent Newsroom (http://www.ccnonline.org.au).

The event also included a very successful exhibition of the Flickr photographers curated by Rachel Cobcroft from iCi. Rachel’s idea of running a curated exhibition, complete with biographies of the artists and statements on why they use CC, was a particularly successful addition to the festivities, which we will definitely aim to reproduce at our future Salons. As an added bonus, a number of the contributing photographers managed to make it on the night with some even coming along from other parts of the country.

This coincided with a hands-on ‘share your wares’ table where attendees could look, touch and taste samples (eg books, magazines, websites) of the work produced by some of the featured commoners and a DVD compilation showcasing all the featured commoners, backed by ccMixter (http://ccmixter.org) music from CDK, Duncan Beattie and Minimal Art, played on loop across the day and night.

Overall the ccSalon was a very successful and enjoyable event. Tying it into a more formal industry event was a good way of publicising the whole event and exposing key industry people to the real-world uses of Creative Commons. Another really successful element was the integration of multiple areas of CC content, including the kinds of content that may not always be considered for showcasing in a performance, into one final, on-site, live event.

Our advice for other CC organisations thinking about running their very own ccSalons: make sure you have plenty of time to get it going (we could have done with at least another week); check that all the people involved are really clear about what will be happening on the evening; and don’t skimp on the catering. It is lots of effort but well worth it in the end.

Jswidget new

2012-07-05T03:18:28Z

Sawyer Lee:

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

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

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

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

== Sample Usage ==

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

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

== Availability ==

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

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

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

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

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

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

=== Styling ===
* Jswidget uses javascript magic to pull in a stylesheet, whether you want it to or not. Luckily, it puts the stylesheet at the very top of the header, so that you can easily override styles by including your own style sheet. We encourage you to write your own style sheet that builds on the one we've provided and personalized the look and feel of the widget to match your [http://lewisseo.com/ free article directory].

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

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

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

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

==== Examples: ====

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

==== Defaults ====

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

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

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

You might consider passing query string variables that assert settings that would be true due to default behavior anyway--this ensures that on the off chance that default behavior changes, your [http://www.topsheung.com/ psp lcd] widget's behavior does not.

== Goals ==

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

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

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

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

PDM FAQ

2012-07-05T03:13:27Z

Sawyer Lee: /* Am I required to attribute the author of the work, or the person who applied the PDM to the work? */

[[Category:FAQ]]
[[Category:PDM]]
[[Category:Public domain]]

These Public Domain Mark FAQs contain information that you should familiarize yourself with before applying the Public Domain Mark (“PDM”) to a work, or before using a work that is marked with the PDM. The information provided below is not exhaustive – it may not cover important issues that could affect you.
__TOC__
These FAQs are intended to supplement, not replace, our existing [http://wiki.creativecommons.org/FAQ FAQ] and our [http://wiki.creativecommons.org/CC0_FAQ CC0 FAQ]. You are encouraged to review those FAQs before using the PDM or any of our other legal tools or licenses. You should also read the PDM deed carefully, as well as the information linked to from the deed. The deed and supplemental information contain important information about the work that has been marked, and should be fully understood before you apply it to a work or use a PDM-marked work.

Please note: '''Creative Commons does not provide legal advice.''' The information provided below is not a substitute for legal advice and is not complete. Please consult your own legal advisor if you have any questions or concerns about the information provided below, about the Public Domain Mark or about Creative Commons licenses and tools generally.

=== Questions about the Public Domain Mark generally ===

==== What is the Public Domain Mark? ====

<div style="float: left; margin-right: 1em;">http://i.creativecommons.org/p/mark/1.0/88x31.png</div> The Public Domain Mark (“PDM”) is a tool that allows anyone to mark and tag a work that is free of known copyright restrictions worldwide, all in a way that clearly communicates that status to the public and allows it to be easily discoverable. The PDM is not a legal instrument like CC0 or our licenses; there is no accompanying legal code or agreement. It should only be used to label a work that is already free of known copyright restrictions around the world, typically very old works. It should not be used to attempt to change a work’s current status under copyright law, or affect any person’s rights in a work. Just like CC0 and our licenses, PDM has a metadata-supported deed and is machine readable, allowing works properly tagged to be readily discovered over the Internet.

==== How does it work? ====

Anyone can use the PDM to mark a work that is free of known copyright restrictions. Information about the work, its author(s), and the person marking the work is supplied through our [http://creativecommons.org/choose/mark PDM Chooser] and embedded in the HTML generated for the work. When supplied, this information may help users of the work evaluate the copyright status of the work for themselves, and learn more about the work. Again, please keep in mind that the PDM does not affect the legal status of the work or the legal rights of the author, the person identifying it or others. The PDM serves a marking and labeling function only.

====What is the difference between the PDM and CC0?====

PDM and CC0 differ in important respects and have distinct purposes. CC0 is intended for use only by authors or holders of copyright and related or neighboring rights (including sui generis database rights), in connection with '''works that are still subject to those rights''' in one or more jurisdictions. PDM, on the other hand, can be used by anyone, and is intended for use with''' works that are already free of known copyright restrictions throughout the world'''.

The tools also differ in terms of their effect when applied to a work. CC0 is legally operative in the sense that when it is applied, it changes the copyright status of the work, effectively relinquishing all copyright and related or neighboring rights worldwide. PDM is not legally operative in any respect – it is intended to function as a label, marking a work that is already free of known copyright restrictions worldwide.

Review a [http://wiki.creativecommons.org/CC0_PDM_comparison_chart chart comparing] the] [http://wiki.creativecommons.org/CC0_PDM_comparison_chart attributes of PDM and CC0], and learn more about [http://wiki.creativecommons.org/CC0_FAQ CC0].

====Can I use the PDM with data, such as metadata? What about databases?====

Yes, PDM can be applied to any work that is free of known copyright restrictions. This means, for example, that you can use PDM to mark [http://wiki.creativecommons.org/Metadata metadata], which is data about data, if the metadata is not copyrightable or otherwise free of copyright. For example, whether or not a photograph is still protected by copyright, metadata that describes the photograph may be unprotected by copyright. In that instance, PDM could be applied to the metadata itself.

PDM can also be applied to databases that are not protected by copyright, including databases containing metadata. The treatment of databases under copyright law varies from jurisdiction to jurisdiction, however, sometimes dramatically. Additionally, databases are also granted sui generis protection in some jurisdictions, which may limit the ability to extract and/or reuse information from the database even if the information itself in the public domain. If you are uncertain whether a database is protected by copyright around the world, then you should not mark the database itself with the PDM, but could use PDM to mark unprotected content in the database.

If you are the creator or maker of a database and want to ensure that anyone can freely extract and reuse content (subject, of course, to other rights that may apply to the contents of the database such as a photograph still under copyright), then you may wish to consider using CC0 to waive all of your copyright and sui generis database rights in the database itself. In all cases, clearly marking and labeling the works to which PDM and CC0 apply is important.

==== What about CC’s Public Domain Dedication and Certification? Can that tool still be used? ====

With the launch of the PDM, Creative Commons is officially deprecating its Public Domain Dedication and Certification (“PDDC”). CC no longer recommends the PDDC for use in any situation. The PDDC had served the dual purposes of allowing a copyright holder to dedicate a work to the public domain, and to mark and certify a work as being in the public domain. We discovered that having a single tool performing both functions was confusing, among other things. In early 2008, we published [http://creativecommons.org/about/cc0 CC0] to take on the dedication function the PDDC had been performing. We [http://creativecommons.org/weblog/entry/13304 announced] at that time that we would be working to improve the way people mark or “tag” a work with information relevant to a work’s public domain status. The PDM is that improved tool. The PDM now assumes the marking and tagging function previously served by PDDC, thereby replacing the PDDC as the recommended tool of choice for doing so.

For those who have used the PDDC to date, you can remain confident that CC will continue to support and serve the PDDC deed.

If you need to certify your public domain dedication, you may visit a service provider such as [http://www.registeredcommons.org RegisteredCommons].

=== Questions for those thinking about applying the PDM to a work ===

==== Who can apply the Public Domain Mark to a work? ====

Anyone who believes a work is free of known copyright restrictions may use the PDM. Keep in mind, however, that the PDM is recommended only for works that are free of known copyright restrictions around the world. You should not apply the PDM to works that you know are only in the public domain in a limited number of jurisdictions. We anticipate that most of the time, the PDM in its current form will only be applied to very old works.

==== If I apply the PDM to a work, am I warranting or promising that the work is free of copyright around the world? ====

No, not unless the law otherwise provides or you want to provide a separate warranty to that effect. Like all CC legal tools, the PDM deed includes express disclaimers of warranties and liabilities, to the extent those are enforceable under applicable laws. Additionally, the PDM deed puts users on notice that the work may not be free of copyright restrictions in all jurisdictions. That notice is intended to caution would-be users of the work that it can be difficult to account for all laws and all possible underlying factual circumstances that impact the copyright status of a particular work in every jurisdiction.

Notwithstanding the disclaimers and notice, if you know that a work you would like to mark is still in copyright in one or more jurisdictions, please do not apply the PDM. We are working on other means for marking works that are in the public domain in some jurisdictions while still restricted by copyright in others, and hope to publish that soon.

==== How do I apply the PDM to a work? ====

Our [http://creativecommons.org/choose/mark PDM Chooser] will lead you through process. When completed, you will be provided with HTML code that you can copy and paste into your website. Please be aware that it is up to you, the person identifying the work, to publish the work marked with the PDM to your website or elsewhere. Creative Commons does not publish any works and cannot accept responsibility for doing so.

==== What are the benefits of including the information requested by the PDM Chooser? ====

The information you provide when using the PDM Chooser will be included in the rendered PDM deed that is linked to the work, as well as included in the machine-readable code. Potential users of the work can then use that information to find out more about the work and its status. Although the information fields are optional, we encourage you to provide all of the information you can for the benefit of users.

==== Does the PDM require those using a work I have marked to give me credit? Or the author? ====

No, there is no credit or attribution requirement, either for the person marking the work or the original author of the work. However, this does not mean that you cannot ask others to give you credit for your effort digitizing and/or marking the work in accordance with community or professional norms and standards.

PDM makes it very easy for users to cite the work itself. If information about the author and work is supplied during the PDM Chooser stage, an HTML citation box will appear on the deed. Users of the work can easily copy the code contained in the box and paste it into the webpage where the work is being used, providing citation information. We encourage everyone identifying works using the PDM Chooser to supply that information; and whenever made available, we encourage users of PDM-marked works to use the ready-to-use citation information.

=== Questions for those thinking about using a PDM-marked work ===

==== Can anyone use a work that is marked using the PDM? ====

Yes, the PDM doesn’t restrict who may use a marked work. Generally, any work free of copyright restrictions can be used for any purpose, even commercial purposes, without asking anyone’s permission first. Note, however, that the PDM deed identifies some important caveats under '''Other Information''' that all would-be users of the work should understand. Among others, it’s possible that a work marked using PDM is not free of all copyright restrictions in all jurisdictions around the world, or that other laws outside of copyright restrict how the work may be used. Read more about these possibilities and others, below.

If you are in doubt about whether or how you can use a PDM-marked work, you should consult with your legal advisor.

==== Am I really free to use a work marked with the PDM anyway I want, anywhere in the world? ====

Like all works that are labeled “free of known copyright restrictions,” “in the public domain” or similar – including works published on the Flickr Commons, museum or library websites or elsewhere – the answer is simple: “It depends.” In this one respect, PDM is no different than any other public domain marking system. That said, one of the most important advantages PDM has over other systems is that the deed alerts would-be users of a work to '''some''' of the important, potential limitations on their ability to use the work.

These potential limitations and caveats are highlighted on the PDM deed under '''Other Information'''. Users are strongly encouraged to review and understand those in advance of using a PDM-marked work (or any other work characterized as part of the public domain, for that matter).

==== Why might a free of copyright restrictions in one jurisdiction not be free of copyright restrictions everywhere? ====

Copyright laws around the world vary; there is no harmonized or standardized copyright law that all jurisdictions follow for purposes of determining when a work is no longer restricted by copyright. Additionally, circumstances causing a work to become part of the public domain under the laws of one jurisdiction may not cause a similar result under others’ laws. Thus, the identical work may be restricted by copyright in some jurisdictions while free of copyright in others.

A work may have this limited or “hybrid” public domain status for a variety of reasons. Some jurisdictions have unusually long copyright [http://www.repairpartstock.com/ iphone parts wholesale] terms, which may mean that a work free from copyright restrictions most everywhere else in the world may still be protected by the copyright laws of that particular country. Sometimes a work is no longer restricted by copyright in a jurisdiction because the author or owner failed to comply with formalities such as renewal of registration or publication with notice, where those formalities apply. It could also be the case that certain categories of works are not protected by copyright by operation of law in a particular jurisdiction, but may be afforded protection under the copyright laws of other jurisdictions. This is the case, for example, with [http://www.usa.gov/copyright.shtml U.S. government works].

CC does not recommend the current version of PDM for works with are in public domain in some jurisdictions but known to be restricted by copyright in others. Even when this recommendation is followed, however, you should be aware that the possibility still exists. We choose to alert would-be users to that possibility up front, however remote it may be.

==== What practices do those who apply PDM to works use to arrive at a determination that a work is free of known copyright? ====

That will depend. CC has not established standards, expectations or even suggested practices for those choosing to apply the mark. Nor are we qualified to do so. Every institution and individual applying the mark must exercise their own judgment for marking works they wish to indicate are free of known copyright. Our hope is that those practices will be published widely and made transparent so that would-be users of PDM-marked works are able to understand the review that was undertaken. We also encourage potential users of PDM-marked works to inquire about those practices with the identifying institution or individual if they want to know more.

Unless otherwise stated to the contrary, however, the person applying the PDM to a work is not guaranteeing anything about it, including what processes or diligence they engaged in before applying the PDM to a work. Creative Commons does not verify the copyright status of works to which the Public Domain Mark has been applied.

==== Are there other laws I should be aware of that might restrict my ability to use a PDM-marked work? ====

Probably. PDM is focused exclusively on copyright law and related and [http://wiki.creativecommons.org/CC0_FAQ#What_are_neighboring_rights.3F neighboring rights]. It does not address the applicability (or inapplicability) of other laws, except to alert users that use of the work may be otherwise regulated or limited. For example, if the work contains an image or likeness of a person or their voice, privacy or [http://wiki.creativecommons.org/Faq#When_are_publicity_rights_relevant.3F publicity rights] may be implicated in some jurisdictions. Similarly, personal data protections laws could come into play depending on the nature of the work, its contents and the particular jurisdiction.

The freedom that comes with using a work in the public domain doesn’t extend to uses that may violate other applicable laws. Just as with works licensed under a CC license, you should be cognizant of other laws that may apply to your particular uses of a work.

==== Am I required to attribute the author of the work, or the person who applied the PDM to the work? ====

No, there is no legal requirement that you credit the author of the original work or the person who identified the work, only a request that you do so voluntarily if requested and the means are provided for doing so.

For purposes of author/work citation, the PDM deed provides HTML code that can be copy and pasted into a webpage to easily cite the author and the work if the person who marked the worked provided that information about [http://lewisseo.com/ free article directory]. We encourage you to take advantage of this copy/paste citation feature whenever possible.

==== How can I be sure that I can use the work as I would like? ====

The Public Domain Mark contains a disclaimer of warranties just like our licenses and CC0, so there is no assurance whatsoever that the work is free of all copyright restrictions in every jurisdiction around the world just because the mark is applied. You should also be aware of restrictions or limitations beyond copyright that may apply, such privacy, publicity, personal data laws and the like.

If you are in doubt, then we strongly recommend you not use the work until you have taken all the steps and precautions you feel you need to before doing so, which may include contacting the person who applied the PDM to the work and consulting legal counsel.
][

{{Translations
| articles = Zh-tw:PDM_常見問題
}}

PDM FAQ

2012-07-05T03:12:00Z

Sawyer Lee: /* Why might a free of copyright restrictions in one jurisdiction not be free of copyright restrictions everywhere? */

[[Category:FAQ]]
[[Category:PDM]]
[[Category:Public domain]]

These Public Domain Mark FAQs contain information that you should familiarize yourself with before applying the Public Domain Mark (“PDM”) to a work, or before using a work that is marked with the PDM. The information provided below is not exhaustive – it may not cover important issues that could affect you.
__TOC__
These FAQs are intended to supplement, not replace, our existing [http://wiki.creativecommons.org/FAQ FAQ] and our [http://wiki.creativecommons.org/CC0_FAQ CC0 FAQ]. You are encouraged to review those FAQs before using the PDM or any of our other legal tools or licenses. You should also read the PDM deed carefully, as well as the information linked to from the deed. The deed and supplemental information contain important information about the work that has been marked, and should be fully understood before you apply it to a work or use a PDM-marked work.

Please note: '''Creative Commons does not provide legal advice.''' The information provided below is not a substitute for legal advice and is not complete. Please consult your own legal advisor if you have any questions or concerns about the information provided below, about the Public Domain Mark or about Creative Commons licenses and tools generally.

=== Questions about the Public Domain Mark generally ===

==== What is the Public Domain Mark? ====

<div style="float: left; margin-right: 1em;">http://i.creativecommons.org/p/mark/1.0/88x31.png</div> The Public Domain Mark (“PDM”) is a tool that allows anyone to mark and tag a work that is free of known copyright restrictions worldwide, all in a way that clearly communicates that status to the public and allows it to be easily discoverable. The PDM is not a legal instrument like CC0 or our licenses; there is no accompanying legal code or agreement. It should only be used to label a work that is already free of known copyright restrictions around the world, typically very old works. It should not be used to attempt to change a work’s current status under copyright law, or affect any person’s rights in a work. Just like CC0 and our licenses, PDM has a metadata-supported deed and is machine readable, allowing works properly tagged to be readily discovered over the Internet.

==== How does it work? ====

Anyone can use the PDM to mark a work that is free of known copyright restrictions. Information about the work, its author(s), and the person marking the work is supplied through our [http://creativecommons.org/choose/mark PDM Chooser] and embedded in the HTML generated for the work. When supplied, this information may help users of the work evaluate the copyright status of the work for themselves, and learn more about the work. Again, please keep in mind that the PDM does not affect the legal status of the work or the legal rights of the author, the person identifying it or others. The PDM serves a marking and labeling function only.

====What is the difference between the PDM and CC0?====

PDM and CC0 differ in important respects and have distinct purposes. CC0 is intended for use only by authors or holders of copyright and related or neighboring rights (including sui generis database rights), in connection with '''works that are still subject to those rights''' in one or more jurisdictions. PDM, on the other hand, can be used by anyone, and is intended for use with''' works that are already free of known copyright restrictions throughout the world'''.

The tools also differ in terms of their effect when applied to a work. CC0 is legally operative in the sense that when it is applied, it changes the copyright status of the work, effectively relinquishing all copyright and related or neighboring rights worldwide. PDM is not legally operative in any respect – it is intended to function as a label, marking a work that is already free of known copyright restrictions worldwide.

Review a [http://wiki.creativecommons.org/CC0_PDM_comparison_chart chart comparing] the] [http://wiki.creativecommons.org/CC0_PDM_comparison_chart attributes of PDM and CC0], and learn more about [http://wiki.creativecommons.org/CC0_FAQ CC0].

====Can I use the PDM with data, such as metadata? What about databases?====

Yes, PDM can be applied to any work that is free of known copyright restrictions. This means, for example, that you can use PDM to mark [http://wiki.creativecommons.org/Metadata metadata], which is data about data, if the metadata is not copyrightable or otherwise free of copyright. For example, whether or not a photograph is still protected by copyright, metadata that describes the photograph may be unprotected by copyright. In that instance, PDM could be applied to the metadata itself.

PDM can also be applied to databases that are not protected by copyright, including databases containing metadata. The treatment of databases under copyright law varies from jurisdiction to jurisdiction, however, sometimes dramatically. Additionally, databases are also granted sui generis protection in some jurisdictions, which may limit the ability to extract and/or reuse information from the database even if the information itself in the public domain. If you are uncertain whether a database is protected by copyright around the world, then you should not mark the database itself with the PDM, but could use PDM to mark unprotected content in the database.

If you are the creator or maker of a database and want to ensure that anyone can freely extract and reuse content (subject, of course, to other rights that may apply to the contents of the database such as a photograph still under copyright), then you may wish to consider using CC0 to waive all of your copyright and sui generis database rights in the database itself. In all cases, clearly marking and labeling the works to which PDM and CC0 apply is important.

==== What about CC’s Public Domain Dedication and Certification? Can that tool still be used? ====

With the launch of the PDM, Creative Commons is officially deprecating its Public Domain Dedication and Certification (“PDDC”). CC no longer recommends the PDDC for use in any situation. The PDDC had served the dual purposes of allowing a copyright holder to dedicate a work to the public domain, and to mark and certify a work as being in the public domain. We discovered that having a single tool performing both functions was confusing, among other things. In early 2008, we published [http://creativecommons.org/about/cc0 CC0] to take on the dedication function the PDDC had been performing. We [http://creativecommons.org/weblog/entry/13304 announced] at that time that we would be working to improve the way people mark or “tag” a work with information relevant to a work’s public domain status. The PDM is that improved tool. The PDM now assumes the marking and tagging function previously served by PDDC, thereby replacing the PDDC as the recommended tool of choice for doing so.

For those who have used the PDDC to date, you can remain confident that CC will continue to support and serve the PDDC deed.

If you need to certify your public domain dedication, you may visit a service provider such as [http://www.registeredcommons.org RegisteredCommons].

=== Questions for those thinking about applying the PDM to a work ===

==== Who can apply the Public Domain Mark to a work? ====

Anyone who believes a work is free of known copyright restrictions may use the PDM. Keep in mind, however, that the PDM is recommended only for works that are free of known copyright restrictions around the world. You should not apply the PDM to works that you know are only in the public domain in a limited number of jurisdictions. We anticipate that most of the time, the PDM in its current form will only be applied to very old works.

==== If I apply the PDM to a work, am I warranting or promising that the work is free of copyright around the world? ====

No, not unless the law otherwise provides or you want to provide a separate warranty to that effect. Like all CC legal tools, the PDM deed includes express disclaimers of warranties and liabilities, to the extent those are enforceable under applicable laws. Additionally, the PDM deed puts users on notice that the work may not be free of copyright restrictions in all jurisdictions. That notice is intended to caution would-be users of the work that it can be difficult to account for all laws and all possible underlying factual circumstances that impact the copyright status of a particular work in every jurisdiction.

Notwithstanding the disclaimers and notice, if you know that a work you would like to mark is still in copyright in one or more jurisdictions, please do not apply the PDM. We are working on other means for marking works that are in the public domain in some jurisdictions while still restricted by copyright in others, and hope to publish that soon.

==== How do I apply the PDM to a work? ====

Our [http://creativecommons.org/choose/mark PDM Chooser] will lead you through process. When completed, you will be provided with HTML code that you can copy and paste into your website. Please be aware that it is up to you, the person identifying the work, to publish the work marked with the PDM to your website or elsewhere. Creative Commons does not publish any works and cannot accept responsibility for doing so.

==== What are the benefits of including the information requested by the PDM Chooser? ====

The information you provide when using the PDM Chooser will be included in the rendered PDM deed that is linked to the work, as well as included in the machine-readable code. Potential users of the work can then use that information to find out more about the work and its status. Although the information fields are optional, we encourage you to provide all of the information you can for the benefit of users.

==== Does the PDM require those using a work I have marked to give me credit? Or the author? ====

No, there is no credit or attribution requirement, either for the person marking the work or the original author of the work. However, this does not mean that you cannot ask others to give you credit for your effort digitizing and/or marking the work in accordance with community or professional norms and standards.

PDM makes it very easy for users to cite the work itself. If information about the author and work is supplied during the PDM Chooser stage, an HTML citation box will appear on the deed. Users of the work can easily copy the code contained in the box and paste it into the webpage where the work is being used, providing citation information. We encourage everyone identifying works using the PDM Chooser to supply that information; and whenever made available, we encourage users of PDM-marked works to use the ready-to-use citation information.

=== Questions for those thinking about using a PDM-marked work ===

==== Can anyone use a work that is marked using the PDM? ====

Yes, the PDM doesn’t restrict who may use a marked work. Generally, any work free of copyright restrictions can be used for any purpose, even commercial purposes, without asking anyone’s permission first. Note, however, that the PDM deed identifies some important caveats under '''Other Information''' that all would-be users of the work should understand. Among others, it’s possible that a work marked using PDM is not free of all copyright restrictions in all jurisdictions around the world, or that other laws outside of copyright restrict how the work may be used. Read more about these possibilities and others, below.

If you are in doubt about whether or how you can use a PDM-marked work, you should consult with your legal advisor.

==== Am I really free to use a work marked with the PDM anyway I want, anywhere in the world? ====

Like all works that are labeled “free of known copyright restrictions,” “in the public domain” or similar – including works published on the Flickr Commons, museum or library websites or elsewhere – the answer is simple: “It depends.” In this one respect, PDM is no different than any other public domain marking system. That said, one of the most important advantages PDM has over other systems is that the deed alerts would-be users of a work to '''some''' of the important, potential limitations on their ability to use the work.

These potential limitations and caveats are highlighted on the PDM deed under '''Other Information'''. Users are strongly encouraged to review and understand those in advance of using a PDM-marked work (or any other work characterized as part of the public domain, for that matter).

==== Why might a free of copyright restrictions in one jurisdiction not be free of copyright restrictions everywhere? ====

Copyright laws around the world vary; there is no harmonized or standardized copyright law that all jurisdictions follow for purposes of determining when a work is no longer restricted by copyright. Additionally, circumstances causing a work to become part of the public domain under the laws of one jurisdiction may not cause a similar result under others’ laws. Thus, the identical work may be restricted by copyright in some jurisdictions while free of copyright in others.

A work may have this limited or “hybrid” public domain status for a variety of reasons. Some jurisdictions have unusually long copyright [http://www.repairpartstock.com/ iphone parts wholesale] terms, which may mean that a work free from copyright restrictions most everywhere else in the world may still be protected by the copyright laws of that particular country. Sometimes a work is no longer restricted by copyright in a jurisdiction because the author or owner failed to comply with formalities such as renewal of registration or publication with notice, where those formalities apply. It could also be the case that certain categories of works are not protected by copyright by operation of law in a particular jurisdiction, but may be afforded protection under the copyright laws of other jurisdictions. This is the case, for example, with [http://www.usa.gov/copyright.shtml U.S. government works].

CC does not recommend the current version of PDM for works with are in public domain in some jurisdictions but known to be restricted by copyright in others. Even when this recommendation is followed, however, you should be aware that the possibility still exists. We choose to alert would-be users to that possibility up front, however remote it may be.

==== What practices do those who apply PDM to works use to arrive at a determination that a work is free of known copyright? ====

That will depend. CC has not established standards, expectations or even suggested practices for those choosing to apply the mark. Nor are we qualified to do so. Every institution and individual applying the mark must exercise their own judgment for marking works they wish to indicate are free of known copyright. Our hope is that those practices will be published widely and made transparent so that would-be users of PDM-marked works are able to understand the review that was undertaken. We also encourage potential users of PDM-marked works to inquire about those practices with the identifying institution or individual if they want to know more.

Unless otherwise stated to the contrary, however, the person applying the PDM to a work is not guaranteeing anything about it, including what processes or diligence they engaged in before applying the PDM to a work. Creative Commons does not verify the copyright status of works to which the Public Domain Mark has been applied.

==== Are there other laws I should be aware of that might restrict my ability to use a PDM-marked work? ====

Probably. PDM is focused exclusively on copyright law and related and [http://wiki.creativecommons.org/CC0_FAQ#What_are_neighboring_rights.3F neighboring rights]. It does not address the applicability (or inapplicability) of other laws, except to alert users that use of the work may be otherwise regulated or limited. For example, if the work contains an image or likeness of a person or their voice, privacy or [http://wiki.creativecommons.org/Faq#When_are_publicity_rights_relevant.3F publicity rights] may be implicated in some jurisdictions. Similarly, personal data protections laws could come into play depending on the nature of the work, its contents and the particular jurisdiction.

The freedom that comes with using a work in the public domain doesn’t extend to uses that may violate other applicable laws. Just as with works licensed under a CC license, you should be cognizant of other laws that may apply to your particular uses of a work.

==== Am I required to attribute the author of the work, or the person who applied the PDM to the work? ====

No, there is no legal requirement that you credit the author of the original work or the person who identified the work, only a request that you do so voluntarily if requested and the means are provided for doing so.

For purposes of author/work citation, the PDM deed provides HTML code that can be copy and pasted into a webpage to easily cite the author and the work if the person who marked the worked provided that information. We encourage you to take advantage of this copy/paste citation feature whenever possible.

==== How can I be sure that I can use the work as I would like? ====

The Public Domain Mark contains a disclaimer of warranties just like our licenses and CC0, so there is no assurance whatsoever that the work is free of all copyright restrictions in every jurisdiction around the world just because the mark is applied. You should also be aware of restrictions or limitations beyond copyright that may apply, such privacy, publicity, personal data laws and the like.

If you are in doubt, then we strongly recommend you not use the work until you have taken all the steps and precautions you feel you need to before doing so, which may include contacting the person who applied the PDM to the work and consulting legal counsel.
][

{{Translations
| articles = Zh-tw:PDM_常見問題
}}

CcMixter

2012-07-05T03:05:28Z

Sawyer Lee:

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://lewisseo.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 
>>http://ccmixter.org/contests/magnatune/loops and 
>>http://ccmixter.org/contests/magnatune 
>> 
>>Were these pretty much custom creations for the Magnatune contest? 
>> 

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 
> just pointed them to http://ccmixter.org/magnatune/view/contest/entries 
> or did you package them in a zip or something else like [http://www.repairpartstock.com/ laptop repair parts]? 

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.

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

Internet Services

2012-07-05T02:59:59Z

Sawyer Lee:

[[MOU and Policies Summary| Return to Summary page]]

To share your feedback on the Internet Services Policy, please go to the [http://wiki.creativecommons.org/index.php?title=Talk:Internet_Services&action=edit&redlink=1| Internet Services Policy discussion page] and type your comments there.

[[Media:isp.pdf | PDF Version]]

--Please do not edit any text below this line.--
----

== Creative Commons Internet Services Policy ==
'''Plain English Summary'''
The overarching purpose of this Internet Service Policy is to ensure that information provided via the Internet about Creative Commons by our Affiliates is consistent and in the best interests of all those dedicated to CC around the world.
* This Internet Services Policy outlines the requirements to which Creative Commons and CC Affiliates must adhere when operating a website, email account, Facebook page, Twitter account or other internet service for a Creative Commons jurisdiction project.
* Affiliates are ultimately responsible for all content on any internet service.
* Any use of internet services must comply with CC’s policies and memorandums of understanding.
* Licenses, license choosers, translated documents and legal tools should never be hosted anywhere other than the main Creative Commons website at http:creativecommons.org.

- - - - -

The Internet Services Policy (“Policy”) complements the Trademark Policy, Merchandising Policy and other policies available at http://creativecommons.org/policies, (collectively “CC Policies”) and the agreements signed by Creative Commons Corporation (“CC” or “Creative Commons”) and its Affiliate(s) (“Affiliate”), which may include a Memorandum of Understanding, Legal Lead Affiliate Agreement, Project Lead Affiliate Agreement or previous incarnations of such agreements (for purposes of this Policy, collectively “MOUs” and each an “MOU”).

'''PURPOSE'''

Creative Commons appreciates the time, energy and hard work that all Affiliates contribute to CC projects around the globe. In order to maximize the impact of those efforts, CC and Affiliates need to work together to ensure a uniform Creative Commons message and protect our most valuable assets, which include our collective goodwill and reputation. We all strive to reach the public and connect with our communities in many ways. The purpose of this Policy is to ensure that information provided via the internet to the public about Creative Commons by Creative Commons Headquarters our Affiliates is accurate and in the best interests of all those dedicated to CC around the world.

This Policy governs the creation, and use of, domain names, email addresses, websites and other internet-based contact points, including but not limited to Twitter accounts and Facebook pages, (collectively, “Internet Services”) used in connection with the Project (as described in the MOU). This includes but is not limited to Internet Services displaying or incorporating any of the Creative Commons Marks (as defined in the Creative Commons Trademark Policy [link]). Websites (as that term is used in this Policy) include both websites for the Project within Affiliate’s jurisdiction (“Project Website”) and websites for more than one jurisdiction, such as websites for a specific geographical or geopolitical region (“Regional Websites”).

'''TERMS OF POLICY'''

Creative Commons will consider deviations from this Policy on a case by case basis through conversations with Affiliate. As confirmed by the signing of the MOU, Creative Commons and Affiliate agree:

;I. Domain Names. If Affiliate chooses to operate a Project Website or Regional Website, the Website must operate at a domain name chosen in accordance with the following:

:(a) CC Sub-Domains. CC will make available to each jurisdiction, at Affiliate’s request, a sub-domain of the Creative Commons main website at http://creativecommons.org (“CC HQ Website”) for Affiliate to use in conjunction with the Project. The sub-domain will consist of xx.creativecommons.org, where xx is the ccTLD top level domain extension for the Project’s jurisdiction.

:(b) Subdomain Administration. If Affiliate requests that CC establish a sub-domain, CC will grant Affiliate administrator access privileges to the sub-domain for so long as Affiliate is in compliance with this Policy and officially connected with the Project through an MOU.

:(c) Acquiring a Domain Name. Affiliate acknowledges that CC’s general policy is not to pay to acquire domain names that incorporate the Marks for example a domain name creativecommons.org.xx or creativecommons.xx. Where CC has not acquired a domain name that incorporates the Marks in the Project’s jurisdiction, Affiliate may choose to acquire such a domain name at its own cost, provided that:

::(i) Affiliate notifies CC in advance (if possible) that it intends to acquire the domain name, and whether the domain name will be acquired according to the procedure described in clause I (e) or I (f); and,

::(ii) Within a reasonable time of acquisition of the domain name, Affiliate emails domains@creativecommons.org with the details of the domain name and the registration data.

:(d) Registering in CC’s Name. If Affiliate chooses to acquire a domain name that incorporates the Marks and the registration authority’s rules permit the domain name to be registered in CC’s name, Affiliate must register it in CC’s name. Up-to-date registration information can be obtained by emailing domains@creativecommons.org.

:(e) Registering in Affiliate’s Name. If Affiliate chooses to acquire a domain name that incorporates any of the Marks and the registration authority’s rules do not permit the domain name to be registered in CC’s name, then Affiliate may register the domain name in its own name provided that:

::(i) Affiliate agrees that it holds the domain name for and on behalf of CC in accordance with the Trademark Policy;

::(ii) Affiliate ensures that the administrative contact on the account will at all times be domains@creativecommons.org.;

::(iii) If the rules governing the registration of domain names in the Project’s jurisdiction change such that CC can hold the domain name in CC’s own name, Affiliate will notify Creative Commons within a reasonable time of becoming aware of this change and CC and Affiliate will decide together whether and when the domain name should be transferred to Creative Commons;

::(iv) If CC and Affiliate agree to transfer the domain name to Creative Commons, Affiliate will do all things reasonably requested by CC to effect the transfer to CC, at CC’s expense; and

::(v) Affiliate will only transfer the domain name to a third party with the prior written consent of CC.

:(f) Competing Domain Names. Affiliate should notify Creative Commons as soon as is reasonably practicable if Affiliate becomes aware of any domain name registrations in the Project jurisdiction that use any Marks or are similar to any Marks.

:(g) Unforeseen Circumstances. Affiliate and CC acknowledge that this policy cannot cover every situation and new circumstances may arise. Affiliate undertakes to do all things CC reasonably requests.

;II. Website(s) and Public Portal(s). If Affiliate chooses to operate a Project Website, Regional Website or other Internet Service that provides information about Creative Commons, such as a Facebook page or Twitter account (each a “Public Portal” for purposes of this Policy) in their Affiliate capacity for the purpose of undertaking activities in connection with the Project, then the following apply:

:(a) Purpose of Project Website. The Project Website (if any) is to serve as the principal public information portal about the Project, which should include educational, research and promotional programs that encourage and enable the sharing of work within the Project jurisdiction through the use of the six Creative Commons licenses: Attribution (BY), NoDerivs (BY-ND), NonCommercial (BY-NC), ShareAlike (BY-SA), NonCommercial NoDervis (BY-NC-ND), and NonCommercial ShareAlike (BY-NC-SA), (collectively “Licenses”); and other legal instruments, such as the CC0 waiver, patent licenses, patent non-assert tools, and other previous and forthcoming licenses and tools published by CC (collectively “Legal Tools”).

:(b) Purpose of Regional Website. Regional Websites are to serve as a collaboration point between jurisdictions in the region, and provide information about Creative Commons activities in the region as a whole.

:(c) Purpose of Public Portal(s). Each Public Portal (if any) is to serve as a secondary or supplemental portal to the Project Website or Regional Website for undertaking activities in connection with the Project or Region and/or providing information about Creative Commons. If there is no existing Project Website or Regional Website, the Public Portal will serve as the principal public information portal and will provide information as stated above in II (a).

:(d) Relationship of Public Portals with Website. All Public Portals must provide a link to the main Project Website or Regional Website when it exists, and to the CC HQ Website if no Project Website or Regional Website exists.

:(e) Quality. Affiliate will ensure the Website is of a high quality and value consistent with the CC HQ Website and other Creative Commons project websites, but should not be so confusingly similar that it misleads Website visitors into thinking that the Website is the CC HQ Website. CC agrees to provide reasonable assistance to ensure such quality. To this end, CC can facilitate hosting services for the Website with a third-party hosting platform.

:(f) Branding. The Project Website will be branded as “Creative Commons [Jurisdiction]”. Regional Websites will be branded as “Creative Commons [Region]”. The Website will clearly state that it is a collaboration between Creative Commons and Affiliate(s) and will include a list of all Affiliates with links to Affiliates’ websites. Affiliate may decide where on the Website to place this information.

:(g) Disclaimers. The Website will include at a minimum two disclaimers within the footer. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible. The disclaimers should be as follows:

::(i) The following agency disclaimer, in the primary language of the Website: “[Affiliate] and Creative Commons Corporation are independent and separate entities. Neither is a partner, agent or employee of the other. Neither party shall have the authority to make any statements, representations or commitments of any kind, or to take any action which shall be binding on the other party, except as may be authorized in writing.”; and

::(ii) A legal disclaimer in the primary language of the Website that clearly states that the Website does not provide legal advice and that using the website does not form any type of legal relationship between Affiliate and users. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible.

:(h) Policies. The Website will include a statement to the effect that “Except where otherwise noted [link to policies page], this site is licensed under a Creative Commons Attribution license.” In keeping with the legal disclaimer and policies page, Affiliate will ensure that nothing provided on the Website constitutes legal advice. Each Website will provide certain policies, as outlined in (i) or (ii) below, as applicable. The Website may not require users to adhere to any new or additional policies without CC’s written consent. Applicable policies are as follows:

::(i) For Websites hosted on CC servers or for which the domain is registered in CC’s name, the CC Policies will apply, and the Websites will include a link on each page to the Creative Commons policies page at http://creativecommons.org/policies and CC Terms of Use available at http://creativecommons.org/terms; and

::(ii) For Websites not hosted on CC servers and for which the domain is registered to someone other than CC, Affiliate will establish and maintain an appropriate privacy policy, terms of use and other policies that comply with applicable law and do not contradict anything in this Policy.

:(i) Content. Affiliate will ensure the Project Website and Public Portals contain proper content in the appropriate language(s) as chosen by Affiliate and/or English, and in line with the MOU and all applicable CC Policies. Proper content may include, but is not limited to, information about (i) Affiliate(s); (ii) the relevant jurisdiction, in a manner that promotes and encourages the adoption of Creative Commons Licenses and Legal Tools; (iii) a link to or translation of the content explaining Creative Commons’ philosophy, history and mission, available at http://creativecommons.org/about/history/; (iv) the local and international adoption of Creative Commons licenses, and (v) Creative Commons-related events.

:(j) Content Restrictions. Websites and Public Portals will only contain content that promotes the objectives of the collaboration between Affiliate and Creative Commons as described in the MOU. For the avoidance of doubt, this means Websites and Public Portals will not contain, link to or endorse any content that is defamatory, hateful or otherwise discriminatory, offensive or obscene, infringing, illegal or otherwise contrary to the law of the applicable jurisdiction.

:(k) Third-Party Contributions. Where Websites or a Public Portal allow third parties to contribute material, Affiliate will adopt a system of review that enables it to monitor this material for compliance with this Policy, the other CC Policies and the MOU, and will promptly remove material that does not comply.

:(l) Removal of Content. CC reserves the right to request the removal of any content that fails (in CC’s sole discretion) to conform to the requirements of this Policy, the MOU, or any other applicable CC Policies. Affiliate will respond promptly to such a request.

:(m) Infringing Material. If Affiliate receives a notice or becomes aware of any claim or information that a Website or a Public Portal contains content that violates the intellectual property rights of any person, and:

::(i) The content is on a Website that is hosted on a Creative Commons server or registered to Creative Commons, Affiliate agrees to send any such notice or claim immediately to dmca@creativecommons.org, with relevant information.

::(ii) The content is on a Website that is not hosted on a Creative Commons server and is registered to someone other than Creative Commons, Affiliate agrees to comply with all applicable laws governing its obligations and responsibilities with respect to such material.

::(iii) The content is on a Public Portal, Affiliate agrees to use reasonable efforts to remove the content.

:(n) Website License. Affiliate will ensure that to the greatest extent possible, all content on a Website or Public Portals is licensed under a Creative Commons Attribution license. Affiliate alone is responsible for ensuring that it has obtained all rights necessary to the content included on a Website and will use best efforts to enable it to be licensed under the CC Attribution license. All third-party content that appears on a Website that is not licensed under the CC BY license must be clearly marked with its copyright status and/or applicable license.

:(o) Content Syndication. Any content that appears on a Website or Public Portal may be syndicated on the websites of other CC project jurisdictions, Regional Websites and the CC HQ Website, unless expressly indicated otherwise by Affiliate in writing to CC or another Affiliate, as the case may be. Similarly, any and content on the CC HQ Website may be used on the Project Website or Regional Website, unless CC expressly indicates to the contrary.

:(p) Items that cannot be hosted. The following items will be hosted on the CC HQ Website only: License drafts, final Licenses, legal code, license deeds, License HTML, license buttons, Legal Tools (whether in human-readable, lawyer-readable or machine-readable formats, or any other formats whatsoever) and the license chooser engine. For the avoidance of doubt, this means that these items may not be hosted on a Project Website or Regional Website, but the Project Website or Regional Website may link to the items on the CC HQ Website.

:(q) Document Translation. If Affiliate or the Affiliate Team wish to translate documents from CC’s wiki (http://wiki.creativecommons.org), those documents must remain posted (as translated) on the wiki. Websites and Public Portals may link to the documents.

:(r) FAQs. The Project Website will include a link to CC’s “Frequently Asked Questions” page available at http://wiki.creativecommons.org/Frequently_Asked_Questions. The Project Website may also include a “Frequently Asked Questions” page with human readable information about CC topics, licensing and related legal issues customized to the Project’s jurisdiction and in the jurisdiction’s primary language(s). Regional Websites may include a link to the “Frequently Asked Questions” page.

:(s) Developers. Websites may contain a link to CC’s developers pages available at http://wiki.creativecommons.org/Developers.

:(t) Commercial Activity. Websites will not contain third party advertisements, banner ads or promotions by Affiliate for any products or services other than those permitted under the Merchandising Policy or anticipated by the scope of the Project as described by the MOU. Creative Commons Counsel and Affiliate can discuss other fund-raising or commercial activity to be conducted on [http://lewisseo.com/ free article directory] or through Project Portals.

:(u) Third-Party Hosting. To the extent that CC facilitates hosting services for a Website and a third party hosting platform, CC is not in any way responsible for the provision of the hosting services and Affiliate will contract separately with the third party hosting platform for the provision of these services.

;III. Email Addresses and Lists. If Affiliate wishes to create email addresses or email lists for the Project, each email address or list must be operated in accordance with the following:

:(a) Email Addresses. Email addresses may correspond to the domain name for the Project, provided that:

::(i) The email addresses are used only to send communications in accordance with the MOU and CC Polices;

::(ii) All emails sent from the email addresses include a footer that makes clear to the recipient that the sender does not work for Creative Commons (e.g. [sender’s name], CC [jurisdiction] [Title]) and that clearly states that CC, Affiliate and the contents of the email do not provide legal advice; and,

::(iii) Affiliate agrees to provide email addresses only to persons who are working with Affiliate on the Project in accordance with the MOU, and to terminate a person’s email account when that person is no longer working with Affiliate on the Project.

:(b) Set-Up of Lists. If Affiliate would like have a mailing list for the jurisdiction, it must be done on Ibiblio (unless otherwise approved by CC) and Affiliate must send the administrators names, administrative password and any updates or changes to administrators or administrative passwords to CC when the list is set-up. To create a new mailing list, send an email to help@ibiblio.org with desired list name and the name of a chosen administrator.

:(c) List Membership. Affiliate will not arbitrarily exclude anyone from membership in the list, and Affiliate will use its discretion when deciding to terminate a person’s membership and then only for appropriate reasons, such as disruptiveness or inappropriate comments.

:(d) Moderating Lists. Affiliate will moderate any email lists for the Project fairly and will moderate discussions when necessary to ensure that all list members are allowed to participate fully.

;IV. All Internet Services. The following provisions are applicable to all Internet Services maintained or operated by Affiliate in relation to the Project:

:(a) Number of Internet Services. There may only be one central Project Website for each Jurisdiction and one Regional Website for a given region. For the avoidance of doubt, this does not preclude the use of supporting sites such as wikis [http://www.repairpartstock.com/ xbox 360 parts]. Public Portals should be limited in number to a reasonable amount. Additional Project Websites or Regional Websites will only be allowed if authorized in writing by Creative Commons.

:(b) Costs. Affiliate will be responsible for all costs and expenses associated with administering all Internet Services.

:(c) Delegation. Affiliate may grant administrative access for the Internet Services to a reasonable number of people for the purpose of maintaining the Internet Services in accordance with this Policy and the MOU. Affiliate will use its best judgment in deciding who will be allowed administrative access to the Internet Services. Affiliate will at all times remain ultimately responsible for ensuring that all Internet Services comply with this Policy, the MOU, and other CC Policies. Affiliate will terminate access granted to others if instructed to do so by Creative Commons. For the avoidance of doubt, CC will only instruct Affiliate to terminate another’s administrative access privileges if CC decides, in its sole discretion, that the access privilege is not being used in accordance with this Policy and the MOU.

:(d) Conduct. Affiliate, the Affiliate Team (as defined in the MOU) and others authorized as administrators of a Project Website or Regional Website in accordance with this Policy will work together with the relevant jurisdiction community, the CC Affiliate Network (as defined in the MOU), and Creative Commons, adhering to a high standard of civility, fairness, ethics and general conduct with each other. Affiliate and the Affiliate Team will engage in consensus-based decision-making on matters relating to administration of the Internet Services, using reasonable efforts to maintain, improve and operate the Internet Services for the purposes contemplated in furtherance of CC’s mission. Everyone with administrative access to an Internet Service registered to Creative Commons or hosted on CC’s servers agrees to comply with the Creative Commons Terms of Use available at http://creativecommons.org/terms.

:(e) Transfer of Internet Services. If Affiliate discontinues its official relationship with Creative Commons, habitually fails to adhere to this Policy, or if CC reasonably determines that a transfer is in the best interests of the maintenance and control of the domain name and the Marks, Affiliate agrees that CC may direct Affiliate to transfer to Creative Commons or a third party (and Affiliate will cooperate with CC in doing so):

::(i) Any domain name registered to someone other than CC;

::(ii) The entire Website, intact (to the extent not otherwise prohibited by third-party license terms); and

::(iii) Administrative access to any Public Portal, including changing all login ids and passwords as directed by Creative Commons.