Creative Commons - User contributions [en]

Content Directories

2012-08-16T09:24:22Z

MartiniPeres: /* Other */

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== [[Text#Featured_Text_sites|Text]] ==

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

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

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

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

__NOTOC__

Other

2012-08-16T09:09:24Z

MartiniPeres: /* Featured Sites */

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

== Featured Sites ==

{{#ask:
[[Category:Content_Directory]]
[[format::other]]
|mainlabel=YCLW
|?mainurl=URL
|?size=30
}}

Other

2012-08-16T09:08:03Z

MartiniPeres: /* Featured Sites */

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

== Featured Sites ==

{{#ask:
[[Category:Content_Directory]]
[[format::other]]
|mainlabel=YCLW
|?mainurl=http://www.cyberworldltd.co.uk/cases-for-apple-model-ipad-3.htm
|?size=30
}}

Applications Using CC

2012-08-13T09:23:37Z

MartiniPeres: /* Mobile Applications */

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

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

=== Photography Applications ===

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

=== Graphics Applications ===

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

=== Blog Applications ===

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

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

=== Authoring Tools ===

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

=== Mobile Applications ===

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

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

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

{{Challenge Enabled}}:

Publish/Audio/Jamendo

2012-08-13T09:16:07Z

MartiniPeres: /* How to publish on Jamendo */

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

[[Image:jamendo1.png|border]]

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

[[Image:jamendo2.png|border]]

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

[[Image:jamendo3.png|border]]

Embedded Metadata

2012-08-13T09:14:31Z

MartiniPeres: /* Embedding the metadata */

[[Category:Developer]]
[[Category:example]]
[[Category:guide]]
[[Category:Technology]]
[[Category:Metadata]]

Creative Commons licenses are attached to Web pages. But we also want our licenses to be useful for materials distributed in file formats around the Net. The protocol described here works for many [[:Category:Filetype|filetypes]].

If your software does not transparently support embedding CC license metadata (you should only have to select a license), do not attempt to do it yourself (it will be a frustrating experience).

<div id="1"></div>

== Embedding the metadata ==

Let's say Anita wants to license her song, "Volcano Love," with a Creative Commons license, and release it as an MP3. Here's what she'd do:

<div style="text-align:center">
http://creativecommons.org/images/comics/mp3/1.gif
</div>

First, Anita would put a "Some Rights Reserved" button on the page displaying here work where her song could be downloaded — along with a link to a license, some RDF metadata, and an assertion about the copyright status of the work. Nothing new here: this is what Creative Commons licensors do now.

<div style="text-align:center">
http://creativecommons.org/images/comics/mp3/2.gif
</div>

With file embedding, though, this page will now serve the added function of '''verification'''. Here's how: Anita would insert the URL to that webpage in the copyright field of the MP3 file, along with a short, plain description of the work's license status. We call this the license '''verification link''' because it points back to a page that Anita herself controls.

<div style="text-align:center">
http://creativecommons.org/images/comics/mp3/4.gif
</div>

Next, imagine Anita puts the MP3 on a file-sharing network. A user comes across her MP3 and can follow the verification link to Anita's page. In the future, we hope that file-sharing networks, media players, and other applications will build tools that read the verification link automatically and inform users of the copyright assertions like Anita's.

<div id="2"></div>

== The advantage of the verification link ==

Embedding this kind of "verification link" in MP3s, as opposed to merely the license metadata, is a measure of protection for artists against the incorrect or fraudulent labeling and sharing of their work.




Ravi circulates the photos among his schoolmates, whose photo-viewing software reads the copyright fields and takes them to the SNAP website, where they can see Ravi's whole catalog of photography and links to other SNAP services.

== Technical Explanation ==

See [[Nonweb Tagging]], and for specific formats, see [[MP3]] and [[XMP]] (PDF, JPEG, video).

Marking Works Technical

2012-08-13T09:13:59Z

MartiniPeres: /* Principles */

{{Best Practice}}

This article describes best practices for marking works licensed with a Creative Commons license or dedicated to the public domain with both human readable and machine readable notices, on the web and otherwise.

Although the importance of human-visible attribution and notice is stressed, this primary focus of this article is machine-readable metadata. Best practice for presentation of human-visible attribution and notice in various formats (apart from collocation with machine-readable equivalents) is currently beyond the scope of this article and will be presented [[Marking|elsewhere]]. An index of specific technical recommendations, organized by file type, is [[:Category:Filetype|available]].

= Principles =

* Copyright notice should be published on the '''web'''. Offline or peer-distributed works should refer to notice published on the web. A web notice allows content to be found via web search, content owners to be found by viewers of untethered works, may be trusted to the extent a web page may be trusted, and allows for further annotation by the owner and others.
* Copyright notice should be '''visible''' and unambiguous to humans and computers, especially the former. Human and computer visible notices should be one and the same.Offline or peer-distributed works should not refer to notice published on the web.
* Copyright notice best practices should be '''general''' rather than applicable only to works offered under one of the Creative Commons licenses.

=Web=

A web page is the preferred venue for published copyright notices. Notices published elsewhere should refer to an equivalent notice published on the web.

<nowiki>This text is licensed to the public under the <a rel="license"
href="http://creativecommons.org/licenses/by-sa/2.5/">Creative
Commons Attribution 2.5 License</a>.</nowiki>

That HTML snippet says that the current document is licensed under CC Attribution 2.5. The current document is the default subject, <code>rel="license"</code> sets the predicate or verb, the URL in the <code>href</code> value sets the object.

For detailed background on the web metadata model and syntax being used, see [[RDFa]].

This use follows the aforementioned principles:

* On the '''web''' (obviously, so long as the HTML page in question is published to a website).
* The metadata is '''visible''' -- it is colocated with an actionable link and may further be styled with CSS for human consumption.
* It is '''general''' -- the model used can accomodate any sort of statement about anything that has a URI and the <code>license</code> predicate can take any license that has a URI as its object, not only a Creative Commons license.

Now we will see how to use the model to further annotate works with licensing-relevant metadata.

=== Attribution ===

A licensor can specify how they wish to be attributed for use of their work (see, for example, § 4(b) of http://creativecommons.org/licenses/by/2.5/legalcode). This includes:

# The title of the work
# The name of the person, group or organization to attribute the work to
# The URL to link the attribution to

Ideally this information would also be available as machine-readable metadata. As an example, this could be encoded in the following triples (assuming the work in question is the current document):

# <> dc:title "Compact Representation of Blank Pages" .
# <> cc:attributionName "James Roberts" .
# <> cc:attributionURL <http://example.org/crobp.html> .

Why the new properties?

# dcterms:rightsHolder and dc:creator don't say which should be attributed -- or if someone else should be; cc:attributionName has the semantics necessary for the task.
# The attribution URL will often be the current URL, but we need some way to specify that it should be cited; cc:attributionURL provides this.

Fortunately RDFa allows us to annotate human readable notices and include both the custom properties needed for attribution as well as additional useful properties, e.g.

<a rel="cc:attributionURL" href="http://example.org/crobp.html"
property="dc:title">Compact Representation of Blank Pages</a> by
<a rel="dc:creator" href="http://example.org/jr.html"
property="cc:attributionName">James Roberts</a>, a <a
rel="dc:source" href="http://example.org/bps.html">translation
of 'Paginas Blancos Si!'</a>, is licensed to the public under
the <a rel="license"
href="http://creativecommons.org/licenses/by/2.5/">Creative
Commons Attribution 2.5 License</a>.

This produces the triples above plus these:

# <> dc:creator <http://example.org/jr.html> .
# <> dc:source <http://example.org/bps.html> .
# <> license <http://creativecommons.org/licenses/by/2.5/> .

=== Included Objects ===

Objects included in web pages, such as images, should be annotated as above within their "host" web pages. Ideally all included objects should also embed object [[:Category:Filetype|format native]] notice and metadata as described below, but this is only crucial for objects where the publisher intends for or is concerned about distribution outside the context of the "host" web page.

Metadata about include objects that have their own URIs should be qualified with <code>about</code>, as <code>rel="license"</code> without an <code>about</code> attribute makes a statement about the current document (which is the "host" web page). Example:

<nowiki>Photo licensed under <a about="http://example.com/some-image.png"
rel="license" href="http://creativecommons.org/licenses/by/2.5/">cc by 2.5</a>.</nowiki>

See the RDFa Primer on [http://www.w3.org/2006/07/SWD/RDFa/primer/#beyond-current-document beyond the current document] for additional examples.

=== More Rights ===

A page may provide any sort of metadata for itself and its included components. The following example has some obviously useful statements:

<nowiki><span rel="dc:type" href="http://purl.org/dc/dcmitype/Sound"/>Audio</span> <a rel="license"
href="http://creativecommons.org/licenses/by-nc/2.5/">(cc)</a> <span property="dc:date">2006</span>.
See <a rel="cc:morePermissions" href="http://johnsmith.com/store">my store</a> to obtain permissions not
granted by the CC license, signed CDs, and concert tickets.</nowiki>

In addition to the familiar <code>license</code> statement and <code>dc:type</code> from Dublin Core we have <code>cc:morePermissions</code>. The intention of <code>cc:morePermissions</code> is to point to a URL at which one can discover permissions outside the scope of those granted to the public by the licensor via a CC license.

See [[CCPlus]] for more information on specifying <code>cc:morePermissions</code>.

=== Interoperability with other web-based metadata formats ===

==== RDF/XML ====

RDF/XML is another RDF serialization that can be used to make any statement that can be made with RDFa. RDF/XML may be <code><link></code>ed in the <code><head></code> of a web page or [[Extend_Metadata#Embedding_RDF_in_HTML|included in HTML comments]], as the deprecated CC recommendation advocated.

RDF/XML is perfectly interoperable with RDFa, but the latter is preferred as it is collocated with human-visible content.

==== Microformats ====

[[RelLicense|rel=license]] is both an [http://microformats.org/wiki/elemental-microformat elemental microformat] (specifically [http://microformats.org/wiki/rel-license rel license]) and an [[RDFa]] statement. Compound Microformats should be interoperable via [http://www.w3.org/TR/grddl/ GRDDL] or [http://www.w3.org/2001/sw/BestPractices/HTML/2006-08-08-hgrddl-xhtml1 hGRDDL].

Use cases for licensing and related metadata as microformats may be found at [http://microformats.org/wiki/licensing on the microformats wiki]; they remain hypothetical as microformats, but generalize to use cases for Creative Commons web metadata.

==== Feeds ====

RSS 1.0, RSS 2.0, and Atom 1.0 syndication formats each may include [[Syndication|license annotations]]. These should also be reflected on web pages referenced by feed items.

= Non-Web =

Objects not native to the web should adhere to the following principles regarding license notice and metadata.

* To the extent possible copyright notice should be '''visible''' to users of the licensed object.
* The licensed object should contain a '''web reference''' to a web page that provides an equivalent licensing notice for the object in question. This makes a non-web object's licesning status as certain as that of a web page's status -- if the web reference does not agree with the non-web object's license notice, ignore the latter.
* To the extent possible license notice provided by non-web objects should use mechanisms and conventions in '''common use''' for the format of the non-web object in question.

We will now apply these principles to a variety of content formats, after describing two building blocks for Non-Web metadata -- web statement metadata and XMP.

== Web Statement ==

The web page that provides licensing notice equivalent to any included in the object itself may be only human readable. Ideally the web page will publish metadata that is explicitly associated with the object in question. To do this the object must be identified, ideally with a content-derived identifier, such that a client may verify that the web page metadata concerns precisely the object in question. An example of a content-derived identifier is a content hash.

Following is an example of RDFa describing a resource indentified by a hash:

<nowiki><span about="urn:sha1:DATAG7ENBVHFNQPM4W626VDVK25RYECI">
'Good Dream' is licensed under
<a rel="license" href="http://creativecommons.org/licenses/by/2.5/">CC BY</a>.
</span></nowiki>

Produces the following triple:

<urn:sha1:DATAG7ENBVHFNQPM4W626VDVK25RYECI> license <http://creativecommons.org/licenses/by/2.5/> .

== XMP ==

[[XMP]] has the broadest support of any embedded metadata format (perhaps it is the only such format with anything approaching broad support) across many different media formats. With the exception meida formats where a workable embedded metadata format is already ubiquituous, Creative Commons recommends adopting XMP as an embedded metadata standard and use of the following two fields in particluar:

* Web reference: value of <code>xapRights:WebStatement</code>
* License: value of <code>cc:license</code>

== Audio ==

Human visible metadata is not possible, and audio notice is not acceptable in most music contexts. With the exception of MP3 and OGG below, XMP embedded metadata is recommended.

=== MP3 ===

[[MP3]] is the primary exception to the XMP recommendation above, as ID3 is widely supported. The following two fields are recommended:

* Web reference: value of <code>WOAF</code> ("official audio file" URL)
* License: value of <code>WCOP</code> (copyright URL)

=== OGG ===

"Vorbis Comments" are widely supported for [[OGG]] files. The following two fields are recommended:

* Web reference: value of <code>CONTACT</code>
* License: value of <code>LICENSE</code>

Note that OGG is a container format that also supports video.

== Still Images ==

Although possible, visible attribution and copyright notice generally either does not fit in an image due to size or aesthetic limitations. Even where possible human-visible notice will not be collocated with machine-readable metadata (for bitmap formats currently in use).

For embedded metadata XMP is recommended.

== Video ==

Visible attribution and copyright notice is generally provided in video frames (e.g., credit roll) or [[Marking_work#Video|overlays]].

Preferably relevant regions of the video will be clickable or otherwise interactively linked with web pages.

There are many video formats, each with its own ill-supported embedded metadata specification (if any). Creative Commons recommends adopting XMP across video formats, with the possible exception of OGG (see audio above).

== Document formats ==

"Document" formats meaning word processor, presentation and spreadsheet document files or their output formats such as PDF.

All of these formats are intended for human consumption and all modern versions support web links, so '''visibility''' is easy -- the license and '''web reference''' should be noted in thee document text wherever '''common use''' dictates a copyright notice would appear. Looks like we just took care of the other principles as well.

Many document formats support some form of embedded metadata that can be accessed, e.g., by selecting <code>File|Document Properties</code> from a menu. Where such metadata includes licensing or copyright-relevant fields, these should be populated with first priority to the '''web reference''' and second priority to the URL of the license the document in question is under.

Ideally these metadata fields should be used to directly populate the human-visible parts of the document, e.g., via a document field, as is typically used to automatically place page numbers and document titles throughout such documents. This gives us the best of both worlds -- any software that indexes embedded metadata can easily find license information, and that information is perfectly reflected in notices humans see.

Details of how metadata may be embedded in specific file formats is available [[:Category:Filetype|here]].

Publish/Audio

2012-08-13T09:13:11Z

MartiniPeres: /* Internet Archive */

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

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

==SoundCloud==

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

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

==Jamendo==

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

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

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

Publish/Video

2012-08-13T09:12:37Z

MartiniPeres: /* Vimeo */

==Vimeo==
__NOTOC__
<div class="smimg">[[Image:Vimeo_logo.png‎|link=|left]]
[http://vimeo.com Vimeo] is a high quality video-sharing website for creators that has enabled CC licensing. See the [[Case_Studies/Vimeo|Case Study]] for more information on case studies for vimeo.

:::'''[[Publish/Video/Vimeo|How to publish on Vimeo]]'''
</div>

==YouTube==
<div class="smimg">[[Image:YouTube_logo.jpg|link=http://youtube.com|left]]
[http://youtube.com YouTube] is a popular video-sharing platform that has enabled the [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution (CC BY) license] as an option for creators to license their work when uploading their videos. YouTube has created a tutorial on how to mark your video as CC BY when uploading videos to its platform at http://www.youtube.com/t/creative_commons.
</div>

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

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

==Wikimedia Commons==
<div class="smimg">[[Image:Wikimedia_Commons_logo.png|link=|left]]
[http://commons.wikimedia.org Wikimedia Commons] is a media file repository of CC-licensed and public domain images and videos that supports Wikipedia articles and other Wikimedia Foundation projects.

'''[[Publish/Wikimedia Commons|How to publish on Wikimedia Commons]]'''
</div>

==Other communities==
*[[Content Directories#Video]]
*[[Filmmaker|Filmmakers and CC]]
*[[Films]] under CC

Marking your work with a CC license

2012-08-13T09:11:02Z

MartiniPeres: /* External Links */

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Marking Specific Media ==

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

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

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

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

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

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

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

== Marking on Other Sites ==

===[[Publish]]===

One way to increase visibility and access to your work is to share it with an existing community. Many content platforms have already enabled CC licensing, making it easy for you to indicate the license along with other information, such as who to attribute. In addition, search engines like Google and Yahoo! will index your work as CC licensed if the [[metadata]] is properly attached.

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

== Marking third-party content in your work ==
Marking best practices also apply for any third party content your work incorporates. If you are incorporating another person's work, then you should be sure you are allowed to incorporate that work. Third party content may be offered under the same or different terms, such as other CC licenses or "all-rights-reserved" copyright. If you are permitted to incorporate that work and it is offered under a CC license, then you should consider adhering to best practices for marking that content as a user, available at [[Marking/Users]]. We also offer additional explanation and tips on [[Marking/Creators/Marking_third_party_content|marking third-party content]].

== Marking in your TOU or TOS ==

== External Links ==

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

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

{{Best Practice}}

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