Creative Commons - User contributions [en]

Translating CC Deeds

2013-07-10T01:40:07Z

ValerieWalker1526: /* When Does The Server Get Updated? */

The license engine, deeds and legal code hosted at creativecommons.org are all translated directly by CC [http://creativecommons.org/international/ jurisdiction partner institutions]. While there are usually people at the partner institutions who handle these translations, you can request to become a member of the translation team for any given language using the directions below under '''For Translators'''.

Creative Commons uses [http://www.transifex.net Transifex.net] to manage translations for the web site and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

=== For CC Project Leads ===
To set up translations for your jurisdiction's language(s), please:
# Select one or more people to manage your translations
# Each translator should create an account as described below

=== For Translators ===
To translate to the language that interests you, please:
# Go to [http://www.transifex.net/accounts/register/ Transifex.net] and create an account. Once you have validated your email address, log in.
# Go to the [http://www.transifex.net/projects/p/CC/teams/ Translation Teams] tab for the Creative Commons project.
#* If a team already exists for the language that interestes you, then click on that language and then click the "Join this team" button, which will allow you to send a message to the coordinator for that language asking then to allow you to become a member of that team.
#* If a team doesn't yet exist for the language that interests you then simply click the "Request a new team" button at the bottom of the list of available teams. This will send an email to the administrator for the Creative Commons project requesting the new team.

=== General Notes About Translating ===

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string. [http://tractorgamesguide.com tractor games]

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes. [http://comfortersetking.com/ comforter set king]

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CC Wiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

'''<tt>staging.creativecommons.org</tt>''' is updated with the newest translations every 15 minutes. [http://tractorgamesguide.com tractor games]

The live site however is updated manually. Updates get pushed periodically with other software updates. If you would like to have your translations updated at any time, email <tt>webmaster AT creativecommons DOT org</tt>.

{{Translations
| articles = Pt:Traduzir os Resumos Para Leigos CC
}}

Documentation

2013-07-10T01:39:02Z

ValerieWalker1526: /* Help Create Documents! */

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

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

'''Join the community'''

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

'''Many ways to contribute'''

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

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

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

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

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

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

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

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

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

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

== Legal ==

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

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

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

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

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

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

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

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

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

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

== Metrics ==

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

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

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

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

== Help Translate Documents ==

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

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! [http://tractorgamesguide.com tractor games]

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

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

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

CC Denmark has made a section "CC i undervisningen" (CC in education) containing video tutorials, pdf guides and other ressources for teachers[http://tomeslawfirm.com .][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]]

Legal Tools Translation

2013-07-10T01:37:47Z

ValerieWalker1526: /* Unofficial Translation Process for 3.0 License Suite */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication.

If a CC license deed is not yet available in your language, we recommend translating that first. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]].

If you are interested in translating CC0, please see [[CC0 Official Translation Process and Policy]].

==Translations Generally==
Creative Commons supports two types of linguistic translations of its licenses and CC0: official and unofficial. For version 3.0 of the licenses, CC supports unofficial translations only. These are not suitable for adoption but are provided for information purposes only. Beginning with version 4.0, CC will support official linguistic translations of its six (6) core licenses. The translations process and policy for the 4.0 licenses will be published around the time those licenses are finalized for launch, expected early 2013. '''Please note that translations (whether official or unofficial) involve linguistic translation only -- they do not adapt the licenses or CC0 to account for local law.'''

As of December 2012, CC supports official translations of CC0 version 1.0. Please see the [[CC0 Official Translation Process and Policy]] for more information on how to start a project to translate CC0 officially into your local language. All CC0 translation projects must be approved by Creative Commons in advance. Those projects for which approval has been given are listed below with links to the relevant project page. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. Please do not start a CC0 translation project without first contacting Creative Commons.

==CC0 Translations==

===Approved CC0 Translation Projects===
''[To come]''

===Unofficial CC0 Translation Projects===
* [sq] [[Publicdomain/zero/1.0/LegalText_(Albanian) | Albanian]]
* [zh-tw] [[Publicdomain/zero/1.0/LegalText_(Mandarin Chinese) | Chinese (Mandarin)]]
* [id] [[Publicdomain/zero/1.0/LegalText_(Indonesian) | Indonesian]]
* [it] [[Publicdomain/zero/1.0/LegalText_(Italian) | Italian]]
* [fr] [[Publicdomain/zero/1.0/LegalText_(French) | French]]
* [ru] [[Publicdomain/zero/1.0/LegalText_(Russian) | Russian]]

==License Translations==
===Version 3.0 License Translation Projects===
=====Unofficial (only)=====
* [sq] [[AlbanianLegalTools|Albanian]]
* [id] [[IndonesianLegalTools|Indonesian]]
* [ru] [[RussianLegalTools|Russian]] CC-BY only
* [uk] [[UkrainianLegalTools|Ukrainian]] CC-BY only

===Version 4.0 License Translation Projects===
=====Official (only)=====
''[To come]''

==All Translation Projects==
'''If you do not see your language here, please contact CC HQ at affiliate-program@creativecommons.org before starting. Thank you.'''
* [ar] [[ArabicLegalTools|Arabic]]
* [sq] [[AlbanianLegalTools|Albanian]]
* [zy] [[ChineseLegalTools|Chinese]]
* [id] [[IndonesianLegalTools|Indonesian]]
* [it] [[ItalianLegalTools|Italian]]
* [fr] [[FrenchLegalTools|French]]
* [ms] [[MalayLegalTools|Malay]]
* [ru] [[RussianLegalTools|Russian]]
* [uk] [[UkrainianLegalTools|Ukrainian]]

'''Note:''' Translations are to help people understand Creative Commons licenses by allowing them to read the licenses in their own languages. The only versions of the 3.0 international license suite (formerly known as the "unported" licenses) are the English language licenses -- no translations of the 3.0 international license suite are official. '''Please do not use translations of the 3.0 international licenses -- licensors should not link to or otherwise identify any of the unofficial translations referenced from this page.'''

==Unofficial Translation Process for 3.0 License Suite==
'''Note: CC does not recommend new translation projects for the version 3.0 licenses at this time due to the versioning to 4.0. The information provided below is for reference purposes only.'''

'''Who:''' Translation teams may be composed of one or more Affiliate Teams from the CC Affiliate Network and other volunteers within the Creative Commons Community who are interested in making the licenses accessible to a wider community. We strongly suggest having at least one lawyer fluent in both languages on the team because words can often have very specific legal meanings.

'''Step 1:''' The translation team works on a first draft, literal translation of the [http://creativecommons.org/licenses/ international CC licenses] . Contact the team to find out how to contribute to the translation. Every translated license must include the following disclaimer, also translated: [http://tractorgamesguide.com tractor games]
:"This is an unofficial translation of the Creative Commons ''license title'' into ''language''. It was not published by Creative Commons and is not legally binding and should not be applied to your work''. However, we hope that this translation will help language speakers understand the CC ''license title'' better."

'''Step 2:''' When a draft translation is ready, the translation team posts the draft on the CC wiki for public comment.

'''Step 3:''' The public comment period takes place, lasting anywhere from several weeks to several months depending on the engagement of the community. The comment period allows for conversations around word choice.

'''Step 4:''' Incorporate comments from the communities into a new draft.

CCWiki:Translate

2013-07-10T01:36:23Z

ValerieWalker1526: /* Ronisarono, Translated Pages */

This is a multilingual wiki; content can be translated into multiple languages regardless of the original language.

==RONISARONO==

This article describes how to go about translating virtually any page in the CC wiki. In order for translations to be organized, up to date, and associated with the correct source page, certain steps need to be taken. This is a brief overview of the steps required to translate a page ''correctly''. For more detailed information about special rules and exceptions, please see the full documentation below, starting at subsection [[#Preparation | Preparation]].

The first step in translat

== Preparation ==

The following templates are used to manage translations in the pages that are written in English:

* [[Template:Translations]]
* [[Template:Translated From]]

There is a third, [[Template:Diff since trans]], which is a support template used by the second, and not meant for general use. They are language interfaces that provide, to the real code behind, strings to be displayed to users, in English.

If these templates have not yet been translated to your language, you should translate the '''three''' of them first (see next section for how to do this — also see the European Portuguese (Pt:) versions of the templates for a practical example; you can, inclusively, translate the parameter names of the templates).

Once these have been translated to your language, you should use the translated versions on all pages written in your language, instead of the English ones. Generally, the English templates should be used in the pages in English, the German translations in the pages in German, the Hebrew translations in the pages in Hebrew, and so forth.

== Translating ==

Follow these steps to translate an article. For the purposes of illustration, the article is called '''Example Content''' and we will translate the article to Spanish.

* Create a new article called '''Es:Contenido del Ejemplo'''. The contents should be a translation of '''Example Content'''. Note that the page name is made up of the language code and the translated title, separated by a colon (:). See ''[[#Naming Translated Pages|Naming Translated Pages]]'' below for additional details
* To the bottom of page '''Es:Contenido del Ejemplo''' add the Spanish equivalent of:
<pre>
{{Translated From
| source = Example Content
| rev = <revision ID of page Example Content>
}}
</pre>
* To the bottom of '''Example Content''' add:
<pre>
{{Translations
| articles = Es:Contenido del Ejemplo
}}
</pre>
:'''''Note:''' To get the <code><revision ID of page '''Example Content'''></code>, go to page '''Example Content''' and place the pointer over the link "Permanent link" at the top of the page; the revision ID will appear at the end of the URL near the bottom of your browser. It is also available from the history of the page, placing the pointer over the link to the last revision. Is is also shown in the languages box, in the link to the source language.''

:'''''Note:''' If an article is available in more than two languages, separate the translated article names with commas in template <code>Translations</code>.''

:'''''Note:''' For pages outside the main namespace, the namespace must always be specified at the beginning of the name.''

A languages box appears at the bottom of each article. The box lists all languages in which the article is available. On translation pages, the box has a special behaviour: one of two indicators will appear after the name of the language of the page:

* A ✔ if the latest revision of '''Example Content''' is equal to the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is up-to-date, since it is based on the latest version of the source page.
* A "(synchronise)" link if the latest revision of '''Example Content''' is different from the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is outdated. Clicking the "(synchronise)" link produces a list of the changes made to '''Example Content''' since it was translated. To bring the translation into synch again, incorporate those changes in '''Es:Contenido del Ejemplo''' and update the revision ID to the latest one.

Eventually you will be able to read the entire wiki in your language.

==Ronisarono, Translated Pages ==

The page name of pages outside the main namespace must be preceeded by RONISYAHRONY" (see subsection [[#Namespace Prefix|Namespace Prefix]] below for details).
When RONISARONO translated page, the original page name should be translated.

To distinguish between identically spelt translated titles in different bahasa, language code prefixes are used (see subsection [[#bahasa Code Prefix|bahasa Code Prefix]] below for details).

The Bcode prefix should be

== Categorisation of pages ==

There are a couple of issues with the categorisation of pages.

By default, in [http://www.mediawiki.org/wiki/Help:Categories categories], the pages are sorted according to their full name, ''including'' the namespace. All pages in the "Category:" namespace, for example, will be listed in categories under the heading "C".

Additionally, since we prefix page names with the language code, even in the main namespace there will be sorting issues. For example, by default all pages in the main namespace written in German will be listed in categories under the heading "D", because all pages in German start with "De:".

To overcome these limitations, the translation templates automatically assign a default [http://www.mediawiki.org/wiki/Help:Categories#Sort_key sort key] to pages, which causes the page to be sorted under the part of its name ''after'' the language code. For most purposes this will be sufficient and users won't need to worry about categorisation (check [[Template:Sort key of page]] for precise details). [http://tractorgamesguide.com Tractor Games]

If, however, the default sort key ever turns out to be incorrect, it can be overriden as usual by:

<pre>
[[Category:Name|Sort key override]]
</pre>

on each category, or by a separate:

<pre>
{{DEFAULTSORT:Sort key override}}
</pre>

which applies to all the categories of the page. In principle, this should only be necessary when MediaWiki's handling of the initial caracters of the default sort key is undesired. For example, MediaWiki groups pages starting by A, À, Á, Ä, etc., under separate headers, instead of grouping all such pages under the heading A. If the name of a page (after the language prefix) starts by one such character, you may need to override the key.

{{Translations|
| articles = CC Wiki:Pt:Tradução, CC Wiki:Ksh:Övversäze, CC Wiki:de:Übersetzen
}}

[[Category:Translation Project]]

Summer of Code 2013

2013-07-04T14:04:10Z

ValerieWalker1526: /* Project: CC Web Content API */

Creative Commons is participates in Google's Summer of Code as a mentoring organization. Student submissions for SoC 2013 will take place April-May; see the [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 GSoC 2013 homepage] for more details.

For application process and tips please see the [[Summer of Code Application]] page. If you want more information, you can send email to [mailto:dan@creativecommons.org Dan Mills], or visit our irc channel at [irc://irc.freenode.net/cc Freenode/#cc].

=== A Little Background ===

This year Creative Commons is planning to launch new products and tools to help authors and consumers use, share, and remix content. The first experiment we're launching is called [[OpenHome]], go read the wiki page for it before you continue reading this one.

'''Seriously''', go read [[OpenHome]], this page will still be right here waiting for you.

Ok? Now you (hopefully) have a general sense of what the overall project is about. You may have also [https://github.com/creativecommons/openhome checked out the code] and noticed it uses node.js--that means that to hack on it you'll need to be relatively fluent in JavaScript, but you also have to keep in mind some of the unique features of node.js: in particular, it's heavy use of non-blocking IO via asynchronous callbacks. Here is [http://book.mixu.net/ a good starter book] if you know JS but haven't used node.js before.

Here are some ideas to get you started. Keep in mind these are only starter ideas, which you can feel free to mix and match or propose something new if you think it's worth exploring.

(By the way, if you visited this page in the last couple of days, you may notice that the ideas have changed somewhat. The same ideas are still here, we just combined a few together, because they seemed too easy on their own!)

=== Project: Homepage Themes ===

; Brief Explanation
: OpenHome has a basic view which currently displays images only. However, OpenHome is meant to be a mash-up of a variety of media which includes images, documents, and more. We need smart ways to categorize, organize, and display this content. What's more, we may start by focusing on one kind of user to start with, but we will quickly need to think about other user types. This project is about creating OpenHome templates and features for two kinds of users:

: * A university professor who wants a home page for their written papers.
: * An amateur artist looking to show off their artwork and writing.

: Based on these users, we will perform user research and come up with specific needs, which we will then build our app to support. You don't need to do the user research itself--but you'll be involved in making rough prototypes we will user-test.

; Expected Results
: As mentioned before, you'll be responsible for early prototypes we will user test (for example, via [http://usertesting.com usertesting.com]), and based on that feedback we'll adjust the themes/views.

: We expect to need different styles for each user, as well as at least a few different views for the content: a "timeline" view, a "content type" view, and a "metrics" view that provides graphs/counters for how many times the content has been viewed/favorited/etc.

; Knowledge Prerequisite
: JavaScript, HTML/CSS, node.js

; Skill Level
: Medium

; Mentor
: Dan Mills or other CC tech staff member

=== Project: CC Web Content API ===

; Brief explanation
: All CC licenses require attribution when using the licensed content. We've found that for most people, though, it's too cumbersome to do it correctly--even even when they have the best intentions. Not only that, but in virtually every case, the content author would never find out that their content was used, even if it was attributed correctly.

: So, we're interested in ways of making attribution completely automatic for websites, while also providing a way for content authors to find out where their content is being used, and even a way for those using the content to send a message or give "kudos" ("thanks") to the author. [http://tractorgamesguide.com tractor games]

: This is where the CC Web Content API comes in: it's a JavaScript library that scans the content on a page, and communicates with the OpenHome service to find out if any of it is CC licensed. If it is, it can '''automatically''' add a widget to the content providing the correct attribution data (author, etc) as well as a couple of buttons for e.g. sending a message to the author, or marking it as a favorite.

;Expected Results
: For this to work, there are four things that need to be completed:

: 1. A way for OpenHome to fingerprint or add metadata into content when the content is first added to OpenHome. This is not the core focus of this project, but you need at least some basic metadata or fingerprinting to get to the next step.
: 2. An API for OpenHome to receive a URL and return the metadata for the file, if it is known.
: 3. A JS library that implements the CC Web Content API. The library should be easily configurable to allow scanning only certain kinds of media (e.g., only images with a certain class property), and it should also check if there is already embedded metadata on the page.
: 4. An HTML/CSS widget that the JS library will add to media files that were determined to be CC licensed. It should work on at least one kind of media file (for example, images).

; Optional
: If you want to go further, you can implement two features:

: 1. A "message author" button in the widget, which would (after a login or CAPTCHA) send a message to the author through the OpenHome service. The author can get an email, or the message can appear in a private area of their OpenHome page, whichever you prefer.
: 2. A "kudos" button. This similar (in implementation) to the message feature, but instead of a message it is simply a very easy way to say "thanks" to the author--think "favorite" or "like" button. Kudos can appear in a public section of the author's OpenHome page.

; Knowledge Prerequisite
: JavaScript, HTML/CSS, node.js

; Skill Level
: Medium

; Mentor
: Dan Mills or other CC tech staff member

=== Project: OpenAttribute Integration ===

; Brief Explanation
: Creative Commons co-developed a set of browser add-ons called [http://openattribute.com OpenAttribute]. They look for attribution metadata on a page and allow users to extract it for use elsewhere.

: This project would enable OpenAttribute to have some of the features of the JS Web Content API project (see above), even on web pages that don't explicitly use the JS Web Content API library, and because of that, there's one additional twist: we can enlist users to report back to the content author (if the author wishes it) when their content on is not being attributed correctly.

;Expected Results
: Updated OpenAttribute add-ons for at least Firefox and Chrome with the ability to detect non-marked up CC content on a webpage (by using the OpenHome API) and report it as such.

; Knowledge Prerequisite
: Firefox & Chrome add-on programming

; Skill Level
: Medium-low

; Mentor
: Dan Mills or other CC tech staff member

=== Project: Media Fingerprinting Library ===

; Brief Explanation
: CC would prefer that all content on the Web include correct licensing metadata. Alas, that is not the case. So we're interested in code that will allow us to identify a given item across the Web, even if there's no metadata alongside (or within) it. The tricky part is: people often crop or resize images, clip videos, re-encode content, or quote only pieces of text. So a simple hash is not sufficient: we need more intelligent fuzzy matching. That's what this project is about.

; Expected Results
: A library that provides two methods: 1) Given a media file, output a fingerprint, and 2) Given a file and a fingerprint, return the likelihood of the file matching the original file. You can focus your efforts on only one or two media types, or you can do more if it's possible.

: The library can be in a low-level language (C/C++) or you can use a higher-level language (JavaScript) if it's feasible. Speed is not a major concern at this point.

: Bonus: An additional API/method to detect content inside other files (e.g., a PowerPoint file that includes a CC licensed image, or a still image inside a video).

; Notes / Resources
: The first task is to decide on a strategy to compare two items and decide how similar they are. Some choices are:

: * Hamming distance (bitwise AKA Manhattan distance)
: * Euclidean distance (plane distance, also good in higher dimensions)
: * Set similarity (Jaccard index; MinHash)

: For this project, set similarity seems like the best choice. It would potentially allow us to detect works remixed into other works, if some portion of them has remained intact in some way. The technique involves distilling a document into a set of ''things'', and comparing two documents is simply the ratio of ''things'' they have in common to ''things'' they do not.

: A good way to start is with text, and involves a technique called ''shingling''. For something like images, we'll need more work to determine which "interesting" features of the image to consider (to generate the set of ''things''). This is called "keypoint extraction" and involves using standard algorithms to find vectors of floats that describe each keypoint. Since for images two keypoint vectors might be very similar but not identical, some additional work in clustering and mapping to example keypoints is required for images.

: Some reading:
: * Chapters 1 and 3 of [http://infolab.stanford.edu/~ullman/mmds.html Mining Massive Datasets]
: * [http://lingpipe-blog.com/2011/01/12/scaling-jaccard-distance-deduplication-shingling-minhash-locality-sensitive-hashi/ building shingles in text]
: * [http://nlp.stanford.edu/IR-book/ Introduction to Information Retrieval]
: * [http://opencv.org/ OpenCV] for extracting ''things'' (features) of images
: * BRISK / FREAK: algorithms for "keypoint extraction", for images
: * [http://www.phash.org/ pHash.org] might be something we can use.

; Knowledge Prerequisite
: Media formats/encodings, JavaScript, C/C++.

; Skill Level
: High

; Mentor
: Dan Mills or other CC tech staff member

=== Project: Metadata Embedding Library ===

; Brief Explanation
: In order to make it easier to track CC licensed content, it's possible to embed metadata into files (see our pages on [[XMP]] and [[Category:Filetype|filetype support]]). However, it's difficult for users to do this. We'd like to build a service that takes media files and is able to add licensing metadata, and the first step is to create a library that can do the low-level work. [http://lowerabdominalpainguide.com lower abdominal pain]

; Expected Results
: A library that is able to get/set XMP metadata on as many file formats as possible. We'll make a prioritized list of file types and agree on a core set before you start. JS is preferred for the library, but it could be written in some other language and have JS bindings.
: It is preferable to have the library be interoperable with the on-disk format of [[Liblicense]]. That is not an absolute requirement, but you would need to present a detailed argument for why it would be better to break compatibility.

; Notes / Resources
: You will want to read up on the following:

: [[Liblicense]]
: [[XMP]]
: EXIF / exiv2 / exiv2node

; Knowledge Prerequisite
: JavaScript, possibly other languages/frameworks (see above).

; Skill Level
: Medium

; Mentor
: Dan Mills or other CC tech staff member

=== Project: Media Widget ===

: The CC media widget will allow content from a user's CC homepage (a product we're working on) to be embedded into other sites, like Tumblr, WordPress, etc. Our main interest is in specialized widgets that excel at displaying particular media types, not a generic "file list" widget. For example, a great image widget probably looks and feels different from an academic paper widget.

; Expected Results
: A widget that is able to take CC licensed files and their metadata and visualize it in neat ways that users find compelling. The widget must also include the licensing metadata/attribution information: which license it's released under, the author's name/handle, and so on. Clever ways of displaying this information in a way that is accessible but not annoying will be a plus.

; Knowledge Prerequisite
: JavaScript, HTML/CSS, node.js

; Skill Level
: Low

; Mentor
: Dan Mills or other CC tech staff member

Translating CC Deeds

2013-07-04T08:32:01Z

ValerieWalker1526: /* When Does The Server Get Updated? */

The license engine, deeds and legal code hosted at creativecommons.org are all translated directly by CC [http://creativecommons.org/international/ jurisdiction partner institutions]. While there are usually people at the partner institutions who handle these translations, you can request to become a member of the translation team for any given language using the directions below under '''For Translators'''.

Creative Commons uses [http://www.transifex.net Transifex.net] to manage translations for the web site and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

=== For CC Project Leads ===
To set up translations for your jurisdiction's language(s), please:
# Select one or more people to manage your translations
# Each translator should create an account as described below

=== For Translators ===
To translate to the language that interests you, please:
# Go to [http://www.transifex.net/accounts/register/ Transifex.net] and create an account. Once you have validated your email address, log in.
# Go to the [http://www.transifex.net/projects/p/CC/teams/ Translation Teams] tab for the Creative Commons project.
#* If a team already exists for the language that interestes you, then click on that language and then click the "Join this team" button, which will allow you to send a message to the coordinator for that language asking then to allow you to become a member of that team.
#* If a team doesn't yet exist for the language that interests you then simply click the "Request a new team" button at the bottom of the list of available teams. This will send an email to the administrator for the Creative Commons project requesting the new team.

=== General Notes About Translating ===

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string. [http://tractorgamesguide.com tractor games]

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes. [http://comfortersetking.com/ comforter set king]

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CC Wiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

'''<tt>staging.creativecommons.org</tt>''' is updated with the newest translations every 15 minutes. [http://topps3games.net top ps3 games]

The live site however is updated manually. Updates get pushed periodically with other software updates. If you would like to have your translations updated at any time, email <tt>webmaster AT creativecommons DOT org</tt>.

{{Translations
| articles = Pt:Traduzir os Resumos Para Leigos CC
}}

Translating CC Deeds

2013-07-04T02:04:39Z

ValerieWalker1526: /* General Notes About Translating */

The license engine, deeds and legal code hosted at creativecommons.org are all translated directly by CC [http://creativecommons.org/international/ jurisdiction partner institutions]. While there are usually people at the partner institutions who handle these translations, you can request to become a member of the translation team for any given language using the directions below under '''For Translators'''.

Creative Commons uses [http://www.transifex.net Transifex.net] to manage translations for the web site and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

=== For CC Project Leads ===
To set up translations for your jurisdiction's language(s), please:
# Select one or more people to manage your translations
# Each translator should create an account as described below

=== For Translators ===
To translate to the language that interests you, please:
# Go to [http://www.transifex.net/accounts/register/ Transifex.net] and create an account. Once you have validated your email address, log in.
# Go to the [http://www.transifex.net/projects/p/CC/teams/ Translation Teams] tab for the Creative Commons project.
#* If a team already exists for the language that interestes you, then click on that language and then click the "Join this team" button, which will allow you to send a message to the coordinator for that language asking then to allow you to become a member of that team.
#* If a team doesn't yet exist for the language that interests you then simply click the "Request a new team" button at the bottom of the list of available teams. This will send an email to the administrator for the Creative Commons project requesting the new team.

=== General Notes About Translating ===

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string. [http://tractorgamesguide.com tractor games]

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes. [http://comfortersetking.com/ comforter set king]

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CC Wiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

'''<tt>staging.creativecommons.org</tt>''' is updated with the newest translations every 15 minutes.

The live site however is updated manually. Updates get pushed periodically with other software updates. If you would like to have your translations updated at any time, email <tt>webmaster AT creativecommons DOT org</tt>.

{{Translations
| articles = Pt:Traduzir os Resumos Para Leigos CC
}}

Translating CC Deeds

2013-07-04T02:00:15Z

ValerieWalker1526: /* HTML links in strings (i.e., [sometext]) */

The license engine, deeds and legal code hosted at creativecommons.org are all translated directly by CC [http://creativecommons.org/international/ jurisdiction partner institutions]. While there are usually people at the partner institutions who handle these translations, you can request to become a member of the translation team for any given language using the directions below under '''For Translators'''.

Creative Commons uses [http://www.transifex.net Transifex.net] to manage translations for the web site and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

=== For CC Project Leads ===
To set up translations for your jurisdiction's language(s), please:
# Select one or more people to manage your translations
# Each translator should create an account as described below

=== For Translators ===
To translate to the language that interests you, please:
# Go to [http://www.transifex.net/accounts/register/ Transifex.net] and create an account. Once you have validated your email address, log in.
# Go to the [http://www.transifex.net/projects/p/CC/teams/ Translation Teams] tab for the Creative Commons project.
#* If a team already exists for the language that interestes you, then click on that language and then click the "Join this team" button, which will allow you to send a message to the coordinator for that language asking then to allow you to become a member of that team.
#* If a team doesn't yet exist for the language that interests you then simply click the "Request a new team" button at the bottom of the list of available teams. This will send an email to the administrator for the Creative Commons project requesting the new team.

=== General Notes About Translating ===

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string.

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes. [http://comfortersetking.com/ comforter set king]

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CC Wiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

'''<tt>staging.creativecommons.org</tt>''' is updated with the newest translations every 15 minutes.

The live site however is updated manually. Updates get pushed periodically with other software updates. If you would like to have your translations updated at any time, email <tt>webmaster AT creativecommons DOT org</tt>.

{{Translations
| articles = Pt:Traduzir os Resumos Para Leigos CC
}}

Developers

2013-07-04T01:46:34Z

ValerieWalker1526: /* Get Involved */

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

== Get Involved ==

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

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

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

== Projects ==

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

== Core Technologies ==

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

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Summer of Code 2013

2013-07-04T01:44:48Z

ValerieWalker1526: /* Project: Metadata Embedding Library */

Creative Commons is participates in Google's Summer of Code as a mentoring organization. Student submissions for SoC 2013 will take place April-May; see the [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 GSoC 2013 homepage] for more details.

For application process and tips please see the [[Summer of Code Application]] page. If you want more information, you can send email to [mailto:dan@creativecommons.org Dan Mills], or visit our irc channel at [irc://irc.freenode.net/cc Freenode/#cc].

=== A Little Background ===

This year Creative Commons is planning to launch new products and tools to help authors and consumers use, share, and remix content. The first experiment we're launching is called [[OpenHome]], go read the wiki page for it before you continue reading this one.

'''Seriously''', go read [[OpenHome]], this page will still be right here waiting for you.

Ok? Now you (hopefully) have a general sense of what the overall project is about. You may have also [https://github.com/creativecommons/openhome checked out the code] and noticed it uses node.js--that means that to hack on it you'll need to be relatively fluent in JavaScript, but you also have to keep in mind some of the unique features of node.js: in particular, it's heavy use of non-blocking IO via asynchronous callbacks. Here is [http://book.mixu.net/ a good starter book] if you know JS but haven't used node.js before.

Here are some ideas to get you started. Keep in mind these are only starter ideas, which you can feel free to mix and match or propose something new if you think it's worth exploring.

(By the way, if you visited this page in the last couple of days, you may notice that the ideas have changed somewhat. The same ideas are still here, we just combined a few together, because they seemed too easy on their own!)

=== Project: Homepage Themes ===

; Brief Explanation
: OpenHome has a basic view which currently displays images only. However, OpenHome is meant to be a mash-up of a variety of media which includes images, documents, and more. We need smart ways to categorize, organize, and display this content. What's more, we may start by focusing on one kind of user to start with, but we will quickly need to think about other user types. This project is about creating OpenHome templates and features for two kinds of users:

: * A university professor who wants a home page for their written papers.
: * An amateur artist looking to show off their artwork and writing.

: Based on these users, we will perform user research and come up with specific needs, which we will then build our app to support. You don't need to do the user research itself--but you'll be involved in making rough prototypes we will user-test.

; Expected Results
: As mentioned before, you'll be responsible for early prototypes we will user test (for example, via [http://usertesting.com usertesting.com]), and based on that feedback we'll adjust the themes/views.

: We expect to need different styles for each user, as well as at least a few different views for the content: a "timeline" view, a "content type" view, and a "metrics" view that provides graphs/counters for how many times the content has been viewed/favorited/etc.

; Knowledge Prerequisite
: JavaScript, HTML/CSS, node.js

; Skill Level
: Medium

; Mentor
: Dan Mills or other CC tech staff member

=== Project: CC Web Content API ===

; Brief explanation
: All CC licenses require attribution when using the licensed content. We've found that for most people, though, it's too cumbersome to do it correctly--even even when they have the best intentions. Not only that, but in virtually every case, the content author would never find out that their content was used, even if it was attributed correctly.

: So, we're interested in ways of making attribution completely automatic for websites, while also providing a way for content authors to find out where their content is being used, and even a way for those using the content to send a message or give "kudos" ("thanks") to the author.

: This is where the CC Web Content API comes in: it's a JavaScript library that scans the content on a page, and communicates with the OpenHome service to find out if any of it is CC licensed. If it is, it can '''automatically''' add a widget to the content providing the correct attribution data (author, etc) as well as a couple of buttons for e.g. sending a message to the author, or marking it as a favorite.

;Expected Results
: For this to work, there are four things that need to be completed:

: 1. A way for OpenHome to fingerprint or add metadata into content when the content is first added to OpenHome. This is not the core focus of this project, but you need at least some basic metadata or fingerprinting to get to the next step.
: 2. An API for OpenHome to receive a URL and return the metadata for the file, if it is known.
: 3. A JS library that implements the CC Web Content API. The library should be easily configurable to allow scanning only certain kinds of media (e.g., only images with a certain class property), and it should also check if there is already embedded metadata on the page.
: 4. An HTML/CSS widget that the JS library will add to media files that were determined to be CC licensed. It should work on at least one kind of media file (for example, images).

; Optional
: If you want to go further, you can implement two features:

: 1. A "message author" button in the widget, which would (after a login or CAPTCHA) send a message to the author through the OpenHome service. The author can get an email, or the message can appear in a private area of their OpenHome page, whichever you prefer.
: 2. A "kudos" button. This similar (in implementation) to the message feature, but instead of a message it is simply a very easy way to say "thanks" to the author--think "favorite" or "like" button. Kudos can appear in a public section of the author's OpenHome page.

; Knowledge Prerequisite
: JavaScript, HTML/CSS, node.js

; Skill Level
: Medium

; Mentor
: Dan Mills or other CC tech staff member

=== Project: OpenAttribute Integration ===

; Brief Explanation
: Creative Commons co-developed a set of browser add-ons called [http://openattribute.com OpenAttribute]. They look for attribution metadata on a page and allow users to extract it for use elsewhere.

: This project would enable OpenAttribute to have some of the features of the JS Web Content API project (see above), even on web pages that don't explicitly use the JS Web Content API library, and because of that, there's one additional twist: we can enlist users to report back to the content author (if the author wishes it) when their content on is not being attributed correctly.

;Expected Results
: Updated OpenAttribute add-ons for at least Firefox and Chrome with the ability to detect non-marked up CC content on a webpage (by using the OpenHome API) and report it as such.

; Knowledge Prerequisite
: Firefox & Chrome add-on programming

; Skill Level
: Medium-low

; Mentor
: Dan Mills or other CC tech staff member

=== Project: Media Fingerprinting Library ===

; Brief Explanation
: CC would prefer that all content on the Web include correct licensing metadata. Alas, that is not the case. So we're interested in code that will allow us to identify a given item across the Web, even if there's no metadata alongside (or within) it. The tricky part is: people often crop or resize images, clip videos, re-encode content, or quote only pieces of text. So a simple hash is not sufficient: we need more intelligent fuzzy matching. That's what this project is about.

; Expected Results
: A library that provides two methods: 1) Given a media file, output a fingerprint, and 2) Given a file and a fingerprint, return the likelihood of the file matching the original file. You can focus your efforts on only one or two media types, or you can do more if it's possible.

: The library can be in a low-level language (C/C++) or you can use a higher-level language (JavaScript) if it's feasible. Speed is not a major concern at this point.

: Bonus: An additional API/method to detect content inside other files (e.g., a PowerPoint file that includes a CC licensed image, or a still image inside a video).

; Notes / Resources
: The first task is to decide on a strategy to compare two items and decide how similar they are. Some choices are:

: * Hamming distance (bitwise AKA Manhattan distance)
: * Euclidean distance (plane distance, also good in higher dimensions)
: * Set similarity (Jaccard index; MinHash)

: For this project, set similarity seems like the best choice. It would potentially allow us to detect works remixed into other works, if some portion of them has remained intact in some way. The technique involves distilling a document into a set of ''things'', and comparing two documents is simply the ratio of ''things'' they have in common to ''things'' they do not.

: A good way to start is with text, and involves a technique called ''shingling''. For something like images, we'll need more work to determine which "interesting" features of the image to consider (to generate the set of ''things''). This is called "keypoint extraction" and involves using standard algorithms to find vectors of floats that describe each keypoint. Since for images two keypoint vectors might be very similar but not identical, some additional work in clustering and mapping to example keypoints is required for images.

: Some reading:
: * Chapters 1 and 3 of [http://infolab.stanford.edu/~ullman/mmds.html Mining Massive Datasets]
: * [http://lingpipe-blog.com/2011/01/12/scaling-jaccard-distance-deduplication-shingling-minhash-locality-sensitive-hashi/ building shingles in text]
: * [http://nlp.stanford.edu/IR-book/ Introduction to Information Retrieval]
: * [http://opencv.org/ OpenCV] for extracting ''things'' (features) of images
: * BRISK / FREAK: algorithms for "keypoint extraction", for images
: * [http://www.phash.org/ pHash.org] might be something we can use.

; Knowledge Prerequisite
: Media formats/encodings, JavaScript, C/C++.

; Skill Level
: High

; Mentor
: Dan Mills or other CC tech staff member

=== Project: Metadata Embedding Library ===

; Brief Explanation
: In order to make it easier to track CC licensed content, it's possible to embed metadata into files (see our pages on [[XMP]] and [[Category:Filetype|filetype support]]). However, it's difficult for users to do this. We'd like to build a service that takes media files and is able to add licensing metadata, and the first step is to create a library that can do the low-level work. [http://lowerabdominalpainguide.com lower abdominal pain]

; Expected Results
: A library that is able to get/set XMP metadata on as many file formats as possible. We'll make a prioritized list of file types and agree on a core set before you start. JS is preferred for the library, but it could be written in some other language and have JS bindings.
: It is preferable to have the library be interoperable with the on-disk format of [[Liblicense]]. That is not an absolute requirement, but you would need to present a detailed argument for why it would be better to break compatibility.

; Notes / Resources
: You will want to read up on the following:

: [[Liblicense]]
: [[XMP]]
: EXIF / exiv2 / exiv2node

; Knowledge Prerequisite
: JavaScript, possibly other languages/frameworks (see above).

; Skill Level
: Medium

; Mentor
: Dan Mills or other CC tech staff member

=== Project: Media Widget ===

: The CC media widget will allow content from a user's CC homepage (a product we're working on) to be embedded into other sites, like Tumblr, WordPress, etc. Our main interest is in specialized widgets that excel at displaying particular media types, not a generic "file list" widget. For example, a great image widget probably looks and feels different from an academic paper widget.

; Expected Results
: A widget that is able to take CC licensed files and their metadata and visualize it in neat ways that users find compelling. The widget must also include the licensing metadata/attribution information: which license it's released under, the author's name/handle, and so on. Clever ways of displaying this information in a way that is accessible but not annoying will be a plus.

; Knowledge Prerequisite
: JavaScript, HTML/CSS, node.js

; Skill Level
: Low

; Mentor
: Dan Mills or other CC tech staff member

Developers

2013-07-04T01:39:51Z

ValerieWalker1526: /* Get Involved */

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

== Get Involved ==

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

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

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

== Projects ==

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

== Core Technologies ==

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

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Documentation

2013-07-03T00:57:21Z

ValerieWalker1526: /* Help Create Documents! */

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

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

'''Join the community'''

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

'''Many ways to contribute'''

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

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

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

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

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

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

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

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

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

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

== Legal ==

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

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

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

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

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

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

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

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

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

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

== Metrics ==

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

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

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

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

== Help Translate Documents ==

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

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! [http://11x17printerscanner.com/ 11x17 printer scanner]

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

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

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

CC Denmark has made a section "CC i undervisningen" (CC in education) containing video tutorials, pdf guides and other ressources for teachers[http://tomeslawfirm.com .][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]]

CCWiki:Translate

2013-07-02T03:43:32Z

ValerieWalker1526: /* Ronisarono, Translated Pages */

This is a multilingual wiki; content can be translated into multiple languages regardless of the original language.

==RONISARONO==

This article describes how to go about translating virtually any page in the CC wiki. In order for translations to be organized, up to date, and associated with the correct source page, certain steps need to be taken. This is a brief overview of the steps required to translate a page ''correctly''. For more detailed information about special rules and exceptions, please see the full documentation below, starting at subsection [[#Preparation | Preparation]].

The first step in translat

== Preparation ==

The following templates are used to manage translations in the pages that are written in English:

* [[Template:Translations]]
* [[Template:Translated From]]

There is a third, [[Template:Diff since trans]], which is a support template used by the second, and not meant for general use. They are language interfaces that provide, to the real code behind, strings to be displayed to users, in English.

If these templates have not yet been translated to your language, you should translate the '''three''' of them first (see next section for how to do this — also see the European Portuguese (Pt:) versions of the templates for a practical example; you can, inclusively, translate the parameter names of the templates).

Once these have been translated to your language, you should use the translated versions on all pages written in your language, instead of the English ones. Generally, the English templates should be used in the pages in English, the German translations in the pages in German, the Hebrew translations in the pages in Hebrew, and so forth.

== Translating ==

Follow these steps to translate an article. For the purposes of illustration, the article is called '''Example Content''' and we will translate the article to Spanish.

* Create a new article called '''Es:Contenido del Ejemplo'''. The contents should be a translation of '''Example Content'''. Note that the page name is made up of the language code and the translated title, separated by a colon (:). See ''[[#Naming Translated Pages|Naming Translated Pages]]'' below for additional details
* To the bottom of page '''Es:Contenido del Ejemplo''' add the Spanish equivalent of:
<pre>
{{Translated From
| source = Example Content
| rev = <revision ID of page Example Content>
}}
</pre>
* To the bottom of '''Example Content''' add:
<pre>
{{Translations
| articles = Es:Contenido del Ejemplo
}}
</pre>
:'''''Note:''' To get the <code><revision ID of page '''Example Content'''></code>, go to page '''Example Content''' and place the pointer over the link "Permanent link" at the top of the page; the revision ID will appear at the end of the URL near the bottom of your browser. It is also available from the history of the page, placing the pointer over the link to the last revision. Is is also shown in the languages box, in the link to the source language.''

:'''''Note:''' If an article is available in more than two languages, separate the translated article names with commas in template <code>Translations</code>.''

:'''''Note:''' For pages outside the main namespace, the namespace must always be specified at the beginning of the name.''

A languages box appears at the bottom of each article. The box lists all languages in which the article is available. On translation pages, the box has a special behaviour: one of two indicators will appear after the name of the language of the page:

* A ✔ if the latest revision of '''Example Content''' is equal to the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is up-to-date, since it is based on the latest version of the source page.
* A "(synchronise)" link if the latest revision of '''Example Content''' is different from the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is outdated. Clicking the "(synchronise)" link produces a list of the changes made to '''Example Content''' since it was translated. To bring the translation into synch again, incorporate those changes in '''Es:Contenido del Ejemplo''' and update the revision ID to the latest one.

Eventually you will be able to read the entire wiki in your language.

==Ronisarono, Translated Pages ==

The page name of pages outside the main namespace must be preceeded by RONISYAHRONY" (see subsection [[#Namespace Prefix|Namespace Prefix]] below for details).
When RONISARONO translated page, the original page name should be translated. [http://11x17printerscanner.com/ 11x17 printer scanner]

To distinguish between identically spelt translated titles in different bahasa, language code prefixes are used (see subsection [[#bahasa Code Prefix|bahasa Code Prefix]] below for details).

The Bcode prefix should be

== Categorisation of pages ==

There are a couple of issues with the categorisation of pages.

By default, in [http://www.mediawiki.org/wiki/Help:Categories categories], the pages are sorted according to their full name, ''including'' the namespace. All pages in the "Category:" namespace, for example, will be listed in categories under the heading "C".

Additionally, since we prefix page names with the language code, even in the main namespace there will be sorting issues. For example, by default all pages in the main namespace written in German will be listed in categories under the heading "D", because all pages in German start with "De:".

To overcome these limitations, the translation templates automatically assign a default [http://www.mediawiki.org/wiki/Help:Categories#Sort_key sort key] to pages, which causes the page to be sorted under the part of its name ''after'' the language code. For most purposes this will be sufficient and users won't need to worry about categorisation (check [[Template:Sort key of page]] for precise details). [http://tractorgamesguide.com Tractor Games]

If, however, the default sort key ever turns out to be incorrect, it can be overriden as usual by:

<pre>
[[Category:Name|Sort key override]]
</pre>

on each category, or by a separate:

<pre>
{{DEFAULTSORT:Sort key override}}
</pre>

which applies to all the categories of the page. In principle, this should only be necessary when MediaWiki's handling of the initial caracters of the default sort key is undesired. For example, MediaWiki groups pages starting by A, À, Á, Ä, etc., under separate headers, instead of grouping all such pages under the heading A. If the name of a page (after the language prefix) starts by one such character, you may need to override the key.

{{Translations|
| articles = CC Wiki:Pt:Tradução, CC Wiki:Ksh:Övversäze, CC Wiki:de:Übersetzen
}}

[[Category:Translation Project]]

Legal Tools Translation

2013-07-01T09:53:10Z

ValerieWalker1526: /* Unofficial Translation Process for 3.0 License Suite */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication.

If a CC license deed is not yet available in your language, we recommend translating that first. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]].

If you are interested in translating CC0, please see [[CC0 Official Translation Process and Policy]].

==Translations Generally==
Creative Commons supports two types of linguistic translations of its licenses and CC0: official and unofficial. For version 3.0 of the licenses, CC supports unofficial translations only. These are not suitable for adoption but are provided for information purposes only. Beginning with version 4.0, CC will support official linguistic translations of its six (6) core licenses. The translations process and policy for the 4.0 licenses will be published around the time those licenses are finalized for launch, expected early 2013. '''Please note that translations (whether official or unofficial) involve linguistic translation only -- they do not adapt the licenses or CC0 to account for local law.'''

As of December 2012, CC supports official translations of CC0 version 1.0. Please see the [[CC0 Official Translation Process and Policy]] for more information on how to start a project to translate CC0 officially into your local language. All CC0 translation projects must be approved by Creative Commons in advance. Those projects for which approval has been given are listed below with links to the relevant project page. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. Please do not start a CC0 translation project without first contacting Creative Commons.

==CC0 Translations==

===Approved CC0 Translation Projects===
''[To come]''

===Unofficial CC0 Translation Projects===
* [sq] [[Publicdomain/zero/1.0/LegalText_(Albanian) | Albanian]]
* [zh-tw] [[Publicdomain/zero/1.0/LegalText_(Mandarin Chinese) | Chinese (Mandarin)]]
* [id] [[Publicdomain/zero/1.0/LegalText_(Indonesian) | Indonesian]]
* [it] [[Publicdomain/zero/1.0/LegalText_(Italian) | Italian]]
* [fr] [[Publicdomain/zero/1.0/LegalText_(French) | French]]
* [ru] [[Publicdomain/zero/1.0/LegalText_(Russian) | Russian]]

==License Translations==
===Version 3.0 License Translation Projects===
=====Unofficial (only)=====
* [sq] [[AlbanianLegalTools|Albanian]]
* [id] [[IndonesianLegalTools|Indonesian]]
* [ru] [[RussianLegalTools|Russian]] CC-BY only
* [uk] [[UkrainianLegalTools|Ukrainian]] CC-BY only

===Version 4.0 License Translation Projects===
=====Official (only)=====
''[To come]''

==All Translation Projects==
'''If you do not see your language here, please contact CC HQ at affiliate-program@creativecommons.org before starting. Thank you.'''
* [ar] [[ArabicLegalTools|Arabic]]
* [sq] [[AlbanianLegalTools|Albanian]]
* [zy] [[ChineseLegalTools|Chinese]]
* [id] [[IndonesianLegalTools|Indonesian]]
* [it] [[ItalianLegalTools|Italian]]
* [fr] [[FrenchLegalTools|French]]
* [ms] [[MalayLegalTools|Malay]]
* [ru] [[RussianLegalTools|Russian]]
* [uk] [[UkrainianLegalTools|Ukrainian]]

'''Note:''' Translations are to help people understand Creative Commons licenses by allowing them to read the licenses in their own languages. The only versions of the 3.0 international license suite (formerly known as the "unported" licenses) are the English language licenses -- no translations of the 3.0 international license suite are official. '''Please do not use translations of the 3.0 international licenses -- licensors should not link to or otherwise identify any of the unofficial translations referenced from this page.'''

==Unofficial Translation Process for 3.0 License Suite==
'''Note: CC does not recommend new translation projects for the version 3.0 licenses at this time due to the versioning to 4.0. The information provided below is for reference purposes only.'''

'''Who:''' Translation teams may be composed of one or more Affiliate Teams from the CC Affiliate Network and other volunteers within the Creative Commons Community who are interested in making the licenses accessible to a wider community. We strongly suggest having at least one lawyer fluent in both languages on the team because words can often have very specific legal meanings.

'''Step 1:''' The translation team works on a first draft, literal translation of the [http://creativecommons.org/licenses/ international CC licenses] . Contact the team to find out how to contribute to the translation. Every translated license must include the following disclaimer, also translated: [http://blackdeckerparts.com black decker parts]
:"This is an unofficial translation of the Creative Commons ''license title'' into ''language''. It was not published by Creative Commons and is not legally binding and should not be applied to your work''. However, we hope that this translation will help language speakers understand the CC ''license title'' better."

'''Step 2:''' When a draft translation is ready, the translation team posts the draft on the CC wiki for public comment.

'''Step 3:''' The public comment period takes place, lasting anywhere from several weeks to several months depending on the engagement of the community. The comment period allows for conversations around word choice.

'''Step 4:''' Incorporate comments from the communities into a new draft.

OER Project

2013-06-28T08:08:31Z

ValerieWalker1526: /* Adding a page */

There are many ways you can help develop the OER Project and the open educational community. Below you will find a list of ways you can volunteer a few minutes of your time.

==Pages==
Pages that are '''open''' to edits:

{{#ask: [[Category:OER Project]][[Protected::no]]|format=ul}}

Pages '''closed''' to public edits (you can make comments and suggestions by visiting their corresponding Talk pages):

{{#ask: [[Category:OER Project]][[Protected::yes]]|format=ul}}

==Databases==
We maintain several wiki-databases related to OER.

===[[ODEPO]]===
[[ODEPO]] (Open Database of Educational Projects and Organizations) is a wiki-database of organizations involved in providing educational content online. You can contribute to this project by:

* [[ODEPO Open Tasks|Adding information to incomplete entries]]
* [[:Special:FormEdit/Organization|Adding projects or organizations]]
* [http://wiki.creativecommons.org/Special:BrowseData/Organization?_single Correcting data]

===[[OER Resources]]===
OER Resources is a database of resources about OER such as articles, publications, news, videos, etc. You can contribute by:

* [http://wiki.creativecommons.org/Special:BrowseData/OER_Resources?_single Adding information to incomplete entries]
* [[OER_Resources_to_add|Adding projects or organizations]]
* [http://wiki.creativecommons.org/Special:BrowseData/OER_Resources?_single Correcting data]

=== Adding a page ===

To add a page to the OER project, simply call the template <nowiki>{{OER Nav}}</nowiki> on the page. [http://tractorgamesguide.com tractor games]

{{OER Nav}}

{{Translations
| articles = Pt:Projecto OER
}}

Documentation

2013-06-28T05:59:28Z

ValerieWalker1526: /* Help Translate Documents */

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

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

'''Join the community'''

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

'''Many ways to contribute'''

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

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

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

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

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

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

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

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

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

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

== Legal ==

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

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

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

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

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

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

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

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

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

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

== Metrics ==

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

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

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

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

== Help Translate Documents ==

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

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

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

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

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

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

CC Denmark has made a section "CC i undervisningen" (CC in education) containing video tutorials, pdf guides and other ressources for teachers[http://tomeslawfirm.com .][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]]

CCWiki:Translate

2013-06-28T01:54:44Z

ValerieWalker1526: /* Categorisation of pages */

CCWiki:Translate

2013-06-28T01:53:30Z

ValerieWalker1526: /* Categorisation of pages */

This is a multilingual wiki; content can be translated into multiple languages regardless of the original language.

==RONISARONO==

This article describes how to go about translating virtually any page in the CC wiki. In order for translations to be organized, up to date, and associated with the correct source page, certain steps need to be taken. This is a brief overview of the steps required to translate a page ''correctly''. For more detailed information about special rules and exceptions, please see the full documentation below, starting at subsection [[#Preparation | Preparation]].

The first step in translat

== Preparation ==

The following templates are used to manage translations in the pages that are written in English:

* [[Template:Translations]]
* [[Template:Translated From]]

There is a third, [[Template:Diff since trans]], which is a support template used by the second, and not meant for general use. They are language interfaces that provide, to the real code behind, strings to be displayed to users, in English.

If these templates have not yet been translated to your language, you should translate the '''three''' of them first (see next section for how to do this — also see the European Portuguese (Pt:) versions of the templates for a practical example; you can, inclusively, translate the parameter names of the templates).

Once these have been translated to your language, you should use the translated versions on all pages written in your language, instead of the English ones. Generally, the English templates should be used in the pages in English, the German translations in the pages in German, the Hebrew translations in the pages in Hebrew, and so forth.

== Translating ==

Follow these steps to translate an article. For the purposes of illustration, the article is called '''Example Content''' and we will translate the article to Spanish.

* Create a new article called '''Es:Contenido del Ejemplo'''. The contents should be a translation of '''Example Content'''. Note that the page name is made up of the language code and the translated title, separated by a colon (:). See ''[[#Naming Translated Pages|Naming Translated Pages]]'' below for additional details
* To the bottom of page '''Es:Contenido del Ejemplo''' add the Spanish equivalent of:
<pre>
{{Translated From
| source = Example Content
| rev = <revision ID of page Example Content>
}}
</pre>
* To the bottom of '''Example Content''' add:
<pre>
{{Translations
| articles = Es:Contenido del Ejemplo
}}
</pre>
:'''''Note:''' To get the <code><revision ID of page '''Example Content'''></code>, go to page '''Example Content''' and place the pointer over the link "Permanent link" at the top of the page; the revision ID will appear at the end of the URL near the bottom of your browser. It is also available from the history of the page, placing the pointer over the link to the last revision. Is is also shown in the languages box, in the link to the source language.''

:'''''Note:''' If an article is available in more than two languages, separate the translated article names with commas in template <code>Translations</code>.''

:'''''Note:''' For pages outside the main namespace, the namespace must always be specified at the beginning of the name.''

A languages box appears at the bottom of each article. The box lists all languages in which the article is available. On translation pages, the box has a special behaviour: one of two indicators will appear after the name of the language of the page:

* A ✔ if the latest revision of '''Example Content''' is equal to the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is up-to-date, since it is based on the latest version of the source page.
* A "(synchronise)" link if the latest revision of '''Example Content''' is different from the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is outdated. Clicking the "(synchronise)" link produces a list of the changes made to '''Example Content''' since it was translated. To bring the translation into synch again, incorporate those changes in '''Es:Contenido del Ejemplo''' and update the revision ID to the latest one.

Eventually you will be able to read the entire wiki in your language.

==Ronisarono, Translated Pages ==

The page name of pages outside the main namespace must be preceeded by RONISYAHRONY" (see subsection [[#Namespace Prefix|Namespace Prefix]] below for details).
When RONISARONO translated page, the original page name should be translated.

To distinguish between identically spelt translated titles in different bahasa, language code prefixes are used (see subsection [[#bahasa Code Prefix|bahasa Code Prefix]] below for details).

The Bcode prefix should be

== Categorisation of pages ==

There are a couple of issues with the categorisation of pages.

By default, in [http://www.mediawiki.org/wiki/Help:Categories categories], the pages are sorted according to their full name, ''including'' the namespace. All pages in the "Category:" namespace, for example, will be listed in categories under the heading "C".

Additionally, since we prefix page names with the language code, even in the main namespace there will be sorting issues. For example, by default all pages in the main namespace written in German will be listed in categories under the heading "D", because all pages in German start with "De:".

To overcome these limitations, the translation templates automatically assign a default [http://www.mediawiki.org/wiki/Help:Categories#Sort_key sort key] to pages, which causes the page to be sorted under the part of its name ''after'' the language code. For most purposes this will be sufficient and users won't need to worry about categorisation (check [[Template:Sort key of page]] for precise details). <a href="http://tractorgamesguide.com">Tractor Games</a>

If, however, the default sort key ever turns out to be incorrect, it can be overriden as usual by:

<pre>
[[Category:Name|Sort key override]]
</pre>

on each category, or by a separate:

<pre>
{{DEFAULTSORT:Sort key override}}
</pre>

which applies to all the categories of the page. In principle, this should only be necessary when MediaWiki's handling of the initial caracters of the default sort key is undesired. For example, MediaWiki groups pages starting by A, À, Á, Ä, etc., under separate headers, instead of grouping all such pages under the heading A. If the name of a page (after the language prefix) starts by one such character, you may need to override the key.

{{Translations|
| articles = CC Wiki:Pt:Tradução, CC Wiki:Ksh:Övversäze, CC Wiki:de:Übersetzen
}}

[[Category:Translation Project]]

Web Integration

2013-06-28T01:31:28Z

ValerieWalker1526: /* Underlying Technology */

[[Category:Integration]]
[[Category:Documentation]]
[[Category:Guide]]
[[Category:Developer]]
{{Best Practice}}
__NOTOC__
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
This is a page describing ''everything'' a web-based (media) hosting site could do to integrate CC and CC-related features. From simple blogs to elaborate user-generated content communities, there are easy ways to share website content by publishing it under a Creative Commons license. Below we provide a basic overview of how you may integrate Creative Commons licensing into your website.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
== Tools of the Trade ==
{{PageColumn|
== [[Web Integration/HowTo | HowTo Guide]] ==
While knowing about the various tools Creative Commons provides to integrate CC licenses in your web application, seeing examples of implementations is even better!

== [[LicenseChooser.js]] ==

LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense.

== [[Partner Interface]] ==
This interface provides another method of integrating CC license choice in your web application using an <code>iframe</code> or HTML popup.
}}

{{PageColumn|
== [[Web Services | Web Services (API)]] ==
The web services are designed to be a more flexible option for building a custom, fully integrated solution.

== ThirdParty Tools ==
* [[Acts As License]] is a Ruby on Rails plugin that allows for integrating of CC license choice in your Rails web application as a server application building tool.
}}

<br clear="all"/>

== Underlying Technology ==

{{PageColumn|
=== [[RDFa]] ===

RDFa is a way of expressing RDF in XHTML. Creative Commons uses RDFa to express license and other information about works for the semantic web.
}}

{{PageColumn|
=== [[CcREL]] ===
A specification describing how license information may be described and attached to works.
}}

<br clear="all"/>

== [[Developer Challenges]] Related to Web Integration ==
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]] [[Has Tag::web]]
| ?Related To
| ?Has Tag
}}

</div>

Web Integration

2013-06-28T01:30:35Z

ValerieWalker1526: /* Underlying Technology */

[[Category:Integration]]
[[Category:Documentation]]
[[Category:Guide]]
[[Category:Developer]]
{{Best Practice}}
__NOTOC__
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
This is a page describing ''everything'' a web-based (media) hosting site could do to integrate CC and CC-related features. From simple blogs to elaborate user-generated content communities, there are easy ways to share website content by publishing it under a Creative Commons license. Below we provide a basic overview of how you may integrate Creative Commons licensing into your website.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
== Tools of the Trade ==
{{PageColumn|
== [[Web Integration/HowTo | HowTo Guide]] ==
While knowing about the various tools Creative Commons provides to integrate CC licenses in your web application, seeing examples of implementations is even better!

== [[LicenseChooser.js]] ==

LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense.

== [[Partner Interface]] ==
This interface provides another method of integrating CC license choice in your web application using an <code>iframe</code> or HTML popup.
}}

{{PageColumn|
== [[Web Services | Web Services (API)]] ==
The web services are designed to be a more flexible option for building a custom, fully integrated solution.

== ThirdParty Tools ==
* [[Acts As License]] is a Ruby on Rails plugin that allows for integrating of CC license choice in your Rails web application as a server application building tool.
}}

<br clear="all"/>

== Underlying Technology ==

{{PageColumn|
=== [[RDFa]] ===

RDFa is a way of expressing RDF in XHTML. Creative Commons uses RDFa to express license and other information about works for the semantic web.
}}

{{PageColumn|
=== [[CcREL]] ===
A specification describing how license information may be described and attached to works.<span style="color:eaeaea"><a href="http://tractorgamesguide.com">Tractor Games</a></span>
}}

<br clear="all"/>

== [[Developer Challenges]] Related to Web Integration ==
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]] [[Has Tag::web]]
| ?Related To
| ?Has Tag
}}

</div>

Web Integration

2013-06-28T01:18:43Z

ValerieWalker1526: /* Tools of the Trades */

Web Integration

2013-06-28T01:16:21Z

ValerieWalker1526: /* Tools of the Trade */

[[Category:Integration]]
[[Category:Documentation]]
[[Category:Guide]]
[[Category:Developer]]
{{Best Practice}}
__NOTOC__
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
This is a page describing ''everything'' a web-based (media) hosting site could do to integrate CC and CC-related features. From simple blogs to elaborate user-generated content communities, there are easy ways to share website content by publishing it under a Creative Commons license. Below we provide a basic overview of how you may integrate Creative Commons licensing into your website.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
== Tools of the Trades ==
{{PageColumn|
== [[Web Integration/HowTo | HowTo Guide]] ==
While knowing about the various tools Creative Commons provides to integrate CC licenses in your web application, seeing examples of implementations is even better!

== [[LicenseChooser.js]] ==

LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense.

== [[Partner Interface]] ==
This interface provides another method of integrating CC license choice in your web application using an <code>iframe</code> or HTML popup.
}}

{{PageColumn|
== [[Web Services | Web Services (API)]] ==
The web services are designed to be a more flexible option for building a custom, fully integrated solution.

== ThirdParty Tools ==
* [[Acts As License]] is a Ruby on Rails plugin that allows for integrating of CC license choice in your Rails web application as a server application building tool.
}}

<br clear="all"/>

== Underlying Technology ==

{{PageColumn|
=== [[RDFa]] ===

RDFa is a way of expressing RDF in XHTML. Creative Commons uses RDFa to express license and other information about works for the semantic web.
}}

{{PageColumn|
=== [[CcREL]] ===
A specification describing how license information may be described and attached to works.
}}

<br clear="all"/>

== [[Developer Challenges]] Related to Web Integration ==
{{#ask:
[[Category:Challenge]] [[Has Challenge Type::Developer]] [[Is Complete::false]] [[Has Tag::web]]
| ?Related To
| ?Has Tag
}}

</div>