Creative Commons - User contributions [en]

Embedded Metadata

2015-08-27T21:14:08Z

CCID-jeremyhardin:

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

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

Category:CcMixter

2015-08-27T21:11:51Z

CCID-jeremyhardin: Blanked the page

Category:CcHost

2015-08-27T21:11:34Z

CCID-jeremyhardin: Blanked the page

Cc-license-chooser

2015-08-27T21:10:58Z

CCID-jeremyhardin: Blanked the page

Web Integration

2015-08-27T21:10:12Z

CCID-jeremyhardin:

Web Integration

2015-08-27T21:09:55Z

CCID-jeremyhardin:

[[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;">
== 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"/>

Web Integration

2015-08-27T21:09:34Z

CCID-jeremyhardin:

Liblicense

2015-08-27T21:09:08Z

CCID-jeremyhardin: Blanked the page

Liblicense

2015-08-27T21:08:52Z

CCID-jeremyhardin:

Liblicense

2015-08-27T21:08:44Z

CCID-jeremyhardin:

Liblicense

2015-08-27T21:08:33Z

CCID-jeremyhardin:

Liblicense

2015-08-27T21:08:14Z

CCID-jeremyhardin:

Liblicense

2015-08-27T21:07:52Z

CCID-jeremyhardin:

{{Software Project
|Description=Low-level license metadata integration for applications.
|Bug tracker=http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=liblicense&@filter=status,project&@group=priority&project=4&@columns=id,activity,title,creator,assignedto,status&@pagesize=50&@startwith=0
|Code repository=http://code.creativecommons.org/viewgit/liblicense.git/
|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
}}
== What is liblicense? ==

liblicense provides a straight-forward way for developers to build license-aware applications. liblicense utilizes a pluggable module system for reading and writing metadata from specific file types, allowing extensibility for specific content types.

* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.

== Future Improvements ==

* Supports [[WebStatement|verification]] URLs for metadata verification

== Architecture ==
[[Image:System_architecture.png]]

[[:Image:System_architecture.svg|Liblicense Architecture - SVG]]

== Media ==

See [[Operating System Mockups]] for ideas on how '''liblicense''' could be integrated into various platforms.

== More Information ==

* [[Liblicense/Releases|Release History]] and [[Liblicense/Roadmap|Roadmap]]
* [[Liblicense/Desktop_Integration|Desktop Integration]]
* [[Liblicense/Screenshots|Screenshots]]
* [[License RDF|RDF Reference]]
* [[Liblicense/Metadata_Table|File Metadata Information]]
* [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source)
* [[Buildbot]] helps test out liblicense on various platforms.

== See Also ==

* [[Companion File metadata specification]]
* [[Tracker CC Indexing]] - also there is a great chart showing progress on reading/writing different filetypes (copied above).

{{Challenge Enabled}}

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
[[Category:Integration]]

__NOTOC__
{{lowercase}}

Liblicense

2015-08-27T21:07:21Z

CCID-jeremyhardin:

{{Software Project
|Description=Low-level license metadata integration for applications.
|Bug tracker=http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=liblicense&@filter=status,project&@group=priority&project=4&@columns=id,activity,title,creator,assignedto,status&@pagesize=50&@startwith=0
|Code repository=http://code.creativecommons.org/viewgit/liblicense.git/
|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
}}
== What is liblicense? ==

liblicense provides a straight-forward way for developers to build license-aware applications. liblicense utilizes a pluggable module system for reading and writing metadata from specific file types, allowing extensibility for specific content types.

* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.

== Future Improvements ==

* Supports [[WebStatement|verification]] URLs for metadata verification

== Architecture ==
[[Image:System_architecture.png]]

[[:Image:System_architecture.svg|Liblicense Architecture - SVG]]

== Media ==

See [[Operating System Mockups]] for ideas on how '''liblicense''' could be integrated into various platforms.

== Download ==

* [http://mirrors.creativecommons.org/software/liblicense/liblicense-0.8.1.tar.gz Latest Release tar.gz]
* Debian and Ubuntu [http://mirrors.creativecommons.org/packages/ repositories].
* Read the [[Liblicense tutorial| tutorial]].

== More Information ==

* [[Liblicense/Releases|Release History]] and [[Liblicense/Roadmap|Roadmap]]
* [[Liblicense/Desktop_Integration|Desktop Integration]]
* [[Liblicense/Screenshots|Screenshots]]
* [[License RDF|RDF Reference]]
* [[Liblicense/Metadata_Table|File Metadata Information]]
* [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source)
* [[Buildbot]] helps test out liblicense on various platforms.

== See Also ==

* [[Companion File metadata specification]]
* [[Tracker CC Indexing]] - also there is a great chart showing progress on reading/writing different filetypes (copied above).

{{Challenge Enabled}}

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
[[Category:Integration]]

__NOTOC__
{{lowercase}}

Liblicense

2015-08-27T21:06:59Z

CCID-jeremyhardin:

{{Software Project
|Description=Low-level license metadata integration for applications.
|Bug tracker=http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=liblicense&@filter=status,project&@group=priority&project=4&@columns=id,activity,title,creator,assignedto,status&@pagesize=50&@startwith=0
|Code repository=http://code.creativecommons.org/viewgit/liblicense.git/
|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
}}
== What is liblicense? ==

liblicense provides a straight-forward way for developers to build license-aware applications. liblicense utilizes a pluggable module system for reading and writing metadata from specific file types, allowing extensibility for specific content types.

* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.

== Future Improvements ==

* Supports [[WebStatement|verification]] URLs for metadata verification

== Architecture ==
[[Image:System_architecture.png]]

[[:Image:System_architecture.svg|Liblicense Architecture - SVG]]

== Bindings ==

* [[Liblicense/Python|Python]]
* [[Liblicense/Ruby|Ruby]]

== Media ==

See [[Operating System Mockups]] for ideas on how '''liblicense''' could be integrated into various platforms.

== Download ==

* [http://mirrors.creativecommons.org/software/liblicense/liblicense-0.8.1.tar.gz Latest Release tar.gz]
* Debian and Ubuntu [http://mirrors.creativecommons.org/packages/ repositories].
* Read the [[Liblicense tutorial| tutorial]].

== More Information ==

* [[Liblicense/Releases|Release History]] and [[Liblicense/Roadmap|Roadmap]]
* [[Liblicense/Desktop_Integration|Desktop Integration]]
* [[Liblicense/Screenshots|Screenshots]]
* [[License RDF|RDF Reference]]
* [[Liblicense/Metadata_Table|File Metadata Information]]
* [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source)
* [[Buildbot]] helps test out liblicense on various platforms.

== See Also ==

* [[Companion File metadata specification]]
* [[Tracker CC Indexing]] - also there is a great chart showing progress on reading/writing different filetypes (copied above).

{{Challenge Enabled}}

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
[[Category:Integration]]

__NOTOC__
{{lowercase}}

Liblicense

2015-08-27T21:06:24Z

CCID-jeremyhardin:

{{Software Project
|Description=Low-level license metadata integration for applications.
|Bug tracker=http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=liblicense&@filter=status,project&@group=priority&project=4&@columns=id,activity,title,creator,assignedto,status&@pagesize=50&@startwith=0
|Code repository=http://code.creativecommons.org/viewgit/liblicense.git/
|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
}}
== What is liblicense? ==

liblicense provides a straight-forward way for developers to build license-aware applications. liblicense utilizes a pluggable module system for reading and writing metadata from specific file types, allowing extensibility for specific content types.

* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.

== Future Improvements ==

* Supports [[WebStatement|verification]] URLs for metadata verification

== Architecture ==
[[Image:System_architecture.png]]

[[:Image:System_architecture.svg|Liblicense Architecture - SVG]]

== Bindings ==

* [[Liblicense/Python|Python]]
* [[Liblicense/Ruby|Ruby]]

== Media ==

See [[Operating System Mockups]] for ideas on how '''liblicense''' could be integrated into various platforms.

== Download ==

* [http://mirrors.creativecommons.org/software/liblicense/liblicense-0.8.1.tar.gz Latest Release tar.gz]
* Debian and Ubuntu [http://mirrors.creativecommons.org/packages/ repositories].
* Read the [[Liblicense tutorial| tutorial]].

=== Developers: Using git ===

If you want to check out the source code and develop on it, use this command:

git clone git://code.creativecommons.org/liblicense.git
git submodule init
git submodule update

That should give you a working copy you can commit to. In case you wonder: the latter two commandsfill the directories
* icons/jurisdictions
* license.rdf
* licenses
with content from external repositories similar to ''svn:externals'' for Subversion.

== More Information ==

* [[Liblicense/Releases|Release History]] and [[Liblicense/Roadmap|Roadmap]]
* [[Liblicense/Desktop_Integration|Desktop Integration]]
* [[Liblicense/Screenshots|Screenshots]]
* [[License RDF|RDF Reference]]
* [[Liblicense/Metadata_Table|File Metadata Information]]
* [http://code.creativecommons.org/doc/liblicense/ Library Documentation] (generated from source)
* [[Buildbot]] helps test out liblicense on various platforms.

== See Also ==

* [[Companion File metadata specification]]
* [[Tracker CC Indexing]] - also there is a great chart showing progress on reading/writing different filetypes (copied above).

{{Challenge Enabled}}

[[Category:Developer]]
[[Category:Metadata]]
[[Category:Desktop]]
[[Category:Labs]]
[[Category:Tools]]
[[Category:Specification]]
[[Category:Operating System]]
[[Category:Technology]]
[[Category:Integration]]

__NOTOC__
{{lowercase}}

Developers

2015-08-27T21:06:04Z

CCID-jeremyhardin:

'''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.

== 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]] (outdated)
: Library for embedding licensing metadata into files of various formats.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Cc-license-chooser

2015-08-27T21:05:05Z

CCID-jeremyhardin:

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

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

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

== Sample Usage ==

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

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

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

== Availability ==

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

== Extra features ==
=== "Seeding" ===
* If the user has already selected a license through some other means, and you want to "seed" the JavaScript widget with the choices the user has already made, just create a hidden form field whose ID is cc_js_seed_uri with the URI of the license you want to start with.
** NOTE that whatever license version you provide, we always upgrade it to the most recent version the jurisdiction offers. We do display a '''Message''' underneath the license icon saying we did this.
=== Forcing a particular jurisdiction ===
To force the user to choose a license in a particular jurisdiction:
* First, use the "seeding" feature to seed the Attribution ("by") license in your jurisdiction
* Then, disable jurisdiction selection
=== Disabling jurisdiction selection ===
If you want to not offer the user a choice of jurisdictions:
* just append ?jurisdictions=disabled to the complete.js call.

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

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

=== Styling ===
* You can use the example style provided in the example application to get you going. We '''urge''' you to put this file on your own web server and not rely on the copy hosted on labs.creativecommons.org.
* What we really want you to do is to change the style of our divs and spans and so-forth to make them fit in to your application. To do that, you should copy the example style file into one of your own CSS files and modify it until you really like it.
=== Namespacing ===
* All LicenseChooser.js HTML elements that have IDs or classes start with "cc_js_" to avoid namespace collisions.
* Similarly, all LicenseChooser.js JavaScript functions start with cc_js_. This is '''not''' true for the bundled Prototype.js library.

== Goals ==

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

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

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

== Version expectations ==
=== Zero point something (like 0.4) ===
There are no guarantees, but we'd like to keep to the same promises as a 1.0 release
=== Something point zero (like 1.0) ===
We guarantee (outside of really urgent situation where we exercise a judgement call) that these will '''not''' change:
* The programmatic interface for the widget will not change
* The user interface for selecting licenses will not change

The following are the only things that '''may'' change:
* As new translations become available, the text may become increasingly internationalized
* As jurisdictions offer new licenses, the engine will update the choices available to a user

== Resources ==

* [http://code.creativecommons.org/viewsvn/jswidget/ LicenseChooser.js development in Subversion]
* [http://cctools.svn.sourceforge.net/viewvc/cctools/cclib/trunk/js/ cclib/trunk/js] in Subversion contains the Javascript used for the [http://labs.creativecommons.org/dhtmllicense/ DHTML License Selector]
* [[JsWidget/Security|Security considerations]]

[[Category:Developer]]
[[Category:Opensource]]
[[Category:Integration]]

Content Directories

2015-08-27T21:04:33Z

CCID-jeremyhardin:

{{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, see [[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.
}}

Content Directories

2015-08-27T21:04:17Z

CCID-jeremyhardin:

Content Directories

2015-08-27T21:03:57Z

CCID-jeremyhardin: /* Video */

Content Directories

2015-08-27T21:03:40Z

CCID-jeremyhardin:

Natural Environment Research Council

2015-08-27T21:01:59Z

CCID-jeremyhardin: Blanked the page

Ru:Заглавная страница

2015-08-27T21:00:12Z

CCID-jeremyhardin: Blanked the page

Summer of Code 2013

2015-08-27T20:57:30Z

CCID-jeremyhardin:

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

Summer of Code 2013

2015-08-27T20:54:17Z

CCID-jeremyhardin: Undo revision 78987 by Mike Linksvayer (talk)

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

Developers

2015-08-27T20:53:04Z

CCID-jeremyhardin: /* 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.

== Older 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]] (outdated)
: Library for embedding licensing metadata into files of various formats.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__