Creative Commons - User contributions [en]

Government use of Creative Commons

2009-11-07T17:02:21Z

Fred Benenson: /* Greece */

Currently this is a scratchpad for referencing known government uses of CC licensing (and government recommendations of CC licensing). Please add to the list and turn compelling uses into [[Case Studies]].

== Armenia ==
* [http://www.president.am/president/cover/eng/ Official website of the Armenian President]. CC BY-ND 3.0 Unported.

== Australia ==

* [http://abs.gov.au/websitedbs/D3310114.nsf/Home/Website+Changes+Coming+Soon Australian Bureau of Statistics website] - Australia's census and statistical data are now licensed under CC BY 2.5 Australia.
* [http://www.pool.og.au ABC Pool] - this initiative of Australia's largest public broadcaster, the Australian Broadcasting Corporation (ABC), is releasing material from the ABC archives for reuse under CC licences. It's first major release has been as part of the [http://www.pool.org.au/genepool Gene Pool project], celebrating Charles Darwin's Centenary.
* National Library of Australia - various [http://www.nla.gov.au/policy/cdp/ policy materials]
* Powerhouse Museum - releases a large range of material under CC, including its [http://www.powerhousemuseum.com/imageservices/ photo of the day] project, [http://play.powerhousemuseum.com/ downloadable pdfs] from its Play program and the museum's general [http://www.creativecommons.org.au/node/225 collection information and data]
* NSW Department of Education and Training - [http://www.smartcopying.edu.au/scw/go/pid/921' Dynamic Calculus': Teaching Resource]
* Aged Care Queensland's [http://www.creativecommons.org.au/node/247 eMentoring Handbook]
* National Copyright Unit - [http://www.smartcopying.edu.au/scw/go/pid/956 Creative Commons for Educators fact sheets] produced for the Smartcopying website in conjunction with Creative Commons Australia.
* Department of Broadband, Communication and the Digital Economy - [https://www.staysmartonline.gov.au/budd-e/common/info/copyright.html Buddie E-security Education Package]
* [http://www.mosman.nsw.gov.au/ Mosman Municipal Council]'s [http://mosmanroundtable.net/ces Community Engagement Strategy] is released under a Creative Commons licence and includes as a key priority “to promote the use and dissemination of Council’s materials while retaining Council’s rights of authorship”;

'''Australian government reports recommending CC usage'''
* [http://www.gilf.gov.au Government Information and Licensing Framework] - a Queensland Government strategy on open access and use of information
* [http://www.innovation.gov.au/innovationreview/Pages/home.aspx Venturous Australia: the National Innovation Review] - report recommends government use of CC licences, and is released under CC
* [http://creativecommons.org.au/node/250 Victorian Government's Economic Development Committee] recommends CC licensing for public sector information.

== Bulgaria ==
* [http://www.president.bg/main.php Bulgarian President]. CC BY ND 2.5 Bulgaria.
* [http://www.prb.bg Chief Prosecutor of the Republic of Bulgaria]. CC BY 2.5 Bulgaria
* [http://www.mfa.bg Bulgarian Foreign Ministry]. CC BY ND 2.5 Bulgaria.

== Chile ==
* [http://www.bcn.cl The Library of the National Congress], whose site is licensed under CC BY NC SA 2.0 Chile.
* [http://www.guiaweb.cl/ The Guidelines for Governmental Websites] and [http://www.observatoriodeusabilidad.cl its Observatory], run by the Ministry of Economy, are licensed under CC BY NC SA 2.0 Chile.

== Colombia ==
* [http://www.siac.net.co/Home.php?opc=2 Official website of the Colombian Biodiversity Information System depending from the Ministry of Environment].

== Greece ==
* http://apps.opengov.gr/ under CC BY-ND Greece
* http://www.opengov.gr/ under CC BY-ND Greece

==Mexico==

* President Felipe Calderon Website, BY NC ND 2.5 Mexico. http://www.presidencia.gob.mx
* National Sports Comission http://www.conade.gob.mx
*[http://www.sip.gob.mx/guiafinal.pdf Federal Government guide for website building] recommends the use CC licenses

== Netherlands ==

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

== New Zealand ==

* Draft for [http://www.e.govt.nz/policy/information-data/nzgoalframework.html NZ Government Open Access and Licensing (NZGOAL) framework] released for public discussion on August 27, 2009. The framework will enable greater access to many public sector works by encouraging State Services agencies to license material for reuse on liberal terms, and recommends Creative Commons as an important tool in this process.
* The [http://koordinates.com/maps/environment/ Ministry for the Environment’s Land Cover Database and the Land Environments New Zealand classification] has been released under a [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution licence] on the [http://koordinates.com/ Koordinates] website - http://www.creativecommons.org.nz/news_and_events/news/koordinates_showcases_govt_cc_datasets

== OECD ==

* http://thepublicvoice.org/events/seoul08/seoul-declaration.pdf

== Russian Federation ==

* All materials (fotos, texts, videos, audios, etc.) of [http://kremlin.ru/eng/ Kremlin.ru (Official Website of President of the Russian Federation)], Creative Commons Attribution 3.0 Unported (CC-BY 3.0 Unported)
** [http://upload.wikimedia.org/wikipedia/commons/d/db/Kremlin_authorisation-English.pdf Letter of authorisation from the Press Secretary to the President of the Russian Federation allowing use of Kremlin.ru materials under the Creative Commons Attribution 3.0 Unported licence (PDF, English, 3 October 2008)]
** [http://commons.wikimedia.org/wiki/Template:Kremlin.ru Template on Wikimedia Commons (English and Russian)]

== Spain ==

* http://www.slideshare.net/justicia/the-use-of-creative-commons-licences-in-the-ministry-of-justice-of-the-government-of-catalonia/

== United States ==
* http://www.whitehouse.gov/copyright White House web site, President Barack Obama, CC BY 3.0 US
* http://change.gov/about/copyright_policy President-Elect Transition Team, Barack Obama and Joseph Biden. CC BY 3.0 Unported.
* http://recoverysf.org/intranet/RecoverySF/ RecoverySF Content by http://recoverysf.org. CC BY 3.0 US.
* [[New York State Senate]], Senate Content, CC-BY-NC-ND with CC+ allowing non-political fundraising use of content.
* [http://leg1.state.va.us/cgi-bin/legp504.exe?091+ful+CHAP0791 State of Virginia], legislation that indicates a preference for state-funded materials to be released with a CC (or equivalent open) license.
* Works by the US federal government are automatically part of the [[public domain]] in the US as stipulated by http://www.copyright.gov/title17/92chap1.html#105

[[Category:Lists of CC use by jurisdiction]]

CC Friendly Lawyers

2009-10-23T22:25:52Z

Fred Benenson: /* First Name Last Name */

= US =
== NYC ==
=== Christine Creamer ===
*christine [at] telegraph21.com

== SF ==
=== First Name Last Name ===
*Address
*Phone Number
*E-mail

CC Friendly Lawyers

2009-10-12T16:41:31Z

Fred Benenson: /* US */

= US =
== NYC ==
=== First Name Last Name ===
*Address
*Phone Number
*E-mail
== SF ==
=== First Name Last Name ===
*Address
*Phone Number
*E-mail

CC Friendly Lawyers

2009-10-12T16:40:47Z

Fred Benenson: /* First Name Last Name */

= US =
== NYC ==
=== First Name Last Name ===
*Address
*Phone Number
*E-mail

== SF ==

CC Friendly Lawyers

2009-10-12T16:40:31Z

Fred Benenson: Creation!

= US =
== NYC ==
=== First Name Last Name ===
Address
Phone Number
E-mail
== SF ==

Casestudies Count

2009-10-09T19:59:53Z

Fred Benenson: Created page with '{{#ask: Category:Casestudy | {{REVISIONYEAR}}::2008 | format=count }}'

{{#ask: [[Category:Casestudy]]
| {{REVISIONYEAR}}::2008
| format=count
}}

Open Education - Legal, Technical, and Social Dimensions

2009-08-11T22:51:09Z

Fred Benenson:

{{Presentation
|venue=2009 West Virginia Statewide Technology Conference
|date=2009/08/06
|presenter=Fred Benenson
|slidesurl=http://www.slideshare.net/mecredis/2009-west-virginia-statewide-technology-conference-presentation
}}

Web Integration/RDFaExample

2009-08-11T17:34:15Z

Fred Benenson:

[[File:RDFa-Explanation.png|500px|border|<br>Read more about how CC uses [[RDFa]] and [[ccREL]] to signal to machines that a work is CC licensed.]]

Using [[RDFa]] and [[CcREL|ccREL]] to add metadata about your Creative Commons licensed works will enable machines (search engines, web browsers, etc) to learn more about your work. To learn more, see [[RDFa]] and [[CcREL|ccREL]].

The advantages of doing this include being indexed by new search capabilities, such as from Yahoo! or Google, to limit image results to only images licensed under a specific CC license.

Another advantage of using this metadata is that when someone clicks on the license text/button on your site and is brought to the CC license deed, the [[Metadata Scraper]] will parse the original page and display added personalized info to the deed. See in the below image that the name of the author is shown along with copyable text to attribute the work:

[[File:Metadata scrapper example.png]]

The copyable text is:
: <div xmlns:cc="http://creativecommons.org/ns#" about="http://grossmeier.net/"><a rel="cc:attributionURL" property="cc:attributionName" href="http://grossmeier.net">Greg Grossmeier</a> / <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">CC BY-SA 3.0</a></div>

This produces text that looks to the viewer as simply "Greg Grossmeier / CC BY-SA 3.0" where the name is linked to the original work (http://grossmeier.net) and the license name is linked to the actual license (http://creativecommons.org/licenses/by-sa/3.0/). The added metadata also tells machines what those links mean and who the author is.

The html code that was on the original site to enable this feature is (line breaks added for readability):
<pre>
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/80x15.png" /></a>
by <a xmlns:cc="http://creativecommons.org/ns#" href="http://grossmeier.net" property="cc:attributionName" rel="cc:attributionURL">Greg Grossmeier</a>

<br />

<rdf:RDF xmlns="http://web.resource.org/cc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<Work rdf:about="">
<dc:type rdf:resource="http://purl.org/dc/dcmitype/Text" />
<license rdf:resource="http://creativecommons.org/licenses/by-sa/3.0/" />
</Work>

<License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/">
<permits rdf:resource="http://web.resource.org/cc/Reproduction" />
<permits rdf:resource="http://web.resource.org/cc/Distribution" />
<requires rdf:resource="http://web.resource.org/cc/Notice" />
<requires rdf:resource="http://web.resource.org/cc/Attribution" />

<permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" />
<requires rdf:resource="http://web.resource.org/cc/ShareAlike" />
</License>

</rdf:RDF>
</pre>

== See Also ==

: '''[[Web_Integration/CopyableExample]]'''
: '''Back to the [[Web Integration/HowTo|HowTo]].'''
: '''Back to [[Web Integration]].'''
: '''Back to [[Developers]].'''

Web Integration/HowTo/Draft

2009-08-11T17:27:16Z

Fred Benenson: Created page with '<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"> The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporati…'

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporating CC license metadata functionality into your web application. This guide has been generalized from various plans for video, audio, or image sharing sites.

Below are 5 areas where integration can occur in your web application. While each web application may not need each of the 5 integrations, Creative Commons recommends that as many as practical are implemented.
</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;">

== [[Web Integration/FileUploadExample|License Choice on file upload]] ==
Users should be able to choose which license they want for each file they upload.

This will allow users to make fine-grain decisions about their works (so that some are CC and some are still All Rights Reserved)

: '''Tools to use''':

:: [[LicenseChooser.js]] or [[Web Services]]

: '''Best Practices Example''': [[SoundCloud]]

: [[File:Sound Cloud License Choice on Upload.png|thumb|260px|border|
<br>
[[SoundCloud]]'s [http://soundcloud.com/upload#old-skool license chooser] on upload is a good way to let users choose a CC license.]]

== [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
In account settings, users should be able to specify a default license for their content they create on the site.

This can be combined with License Choice on File Upload to allow users to have the default license be, for example, CC:BY and in special cases some others be CC:BY-SA, or even All Rights Reserved.

: Tools to use:

:: [[LicenseChooser.js]] or [[Web Services]]

: '''Best Practices Example''': [[Flickr]]

: [[File:Flickr Default License Choice.png|thumb|260px|border|<br>[[Flickr]]'s account settings provide a default license for users to apply to all of their uploaded works.]]

== [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.

This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.

: Tools to use:

:: [[RDFa]] and [[CcREL|ccREL]]

: '''Best Practices Example''': [[Thingiverse]]

: [[File:RDFa-Explanation.png|thumb|260px|border|<br>Read more about how CC uses [[RDFa]] and [[ccREL]] to signal to machines that a work is CC licensed.]]

== [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.

: Tools to use:

:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]

: '''Best Practices Example''': CC license deeds

: [[File:Attribution box via RDFa and Javascript.png|thumb|260px|border|<br>CC license deeds will automatically generate Attribution HTML if the referring page contains relevant RDFa.]]

== [[Web Integration/InterfaceExample|License aware user interfaces]] ==
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.

: '''Tools to use''':

:: [[RDFa]], and [[CcREL|ccREL]]

: '''Best Practices Example''': [[Flickr]]

: [[File:Flickr Creative Commons Exploration portal.png|thumb|260px|border|[[Flickr]]'s CC portal represents a good way to break down CC content for end users.]]

== Adopters ==

We have a long list of [[Content Directories]] which are basically sites, projects and people who have implemented CC licensing and/or have some type of CC licensing. This is the best list of high level CC license adopters, all generated from the community. NOTE: CC does not have a database of content or keep a defacto list of all those who use CC licenses. The list above is used to provide examples.

== Assistance ==

If you are hoping to adopt this, please contact Fred Benenson (fred [at] creativecommons.org) and/or http://creativecommons.org/contact

<br clear="all"/>
</div>

=== See also ===

: Back to '''[[Web Integration]]'''
: '''[[Desktop Integration]]'''
: '''[[Developers]]'''

Web Integration/HowTo

2009-08-10T21:19:43Z

Fred Benenson:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporating CC license metadata functionality into your web application. This guide has been generalized from various plans for video, audio, or image sharing sites.

Below are 5 areas where integration can occur in your web application. While each web application may not need each of the 5 integrations, Creative Commons recommends that as many as practical are implemented.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
== [[Web Integration/FileUploadExample|License Choice on file upload]] ==
Users should be able to choose which license they want for each file they upload.

This will allow users to make fine-grain decisions about their works (so that some are CC and some are still All Rights Reserved)

: '''Tools to use''':

:: [[LicenseChooser.js]] or [[Web Services]]

: '''Best Practices Example''': [[SoundCloud]]

: [[File:Sound Cloud License Choice on Upload.png|thumb|260px|border|
<br>
[[SoundCloud]]'s [http://soundcloud.com/upload#old-skool license chooser] on upload is a good way to let users choose a CC license.]]

== [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
In account settings, users should be able to specify a default license for their content they create on the site.

This can be combined with License Choice on File Upload to allow users to have the default license be, for example, CC:BY and in special cases some others be CC:BY-SA, or even All Rights Reserved.

: Tools to use:

:: [[LicenseChooser.js]] or [[Web Services]]

: '''Best Practices Example''': [[Flickr]]

: [[File:Flickr Default License Choice.png|thumb|260px|border|<br>[[Flickr]]'s account settings provide a default license for users to apply to all of their uploaded works.]]

== [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.

This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.

: Tools to use:

:: [[RDFa]] and [[CcREL|ccREL]]

: '''Best Practices Example''': [[Thingiverse]]

: [[File:RDFa-Explanation.png|thumb|260px|border|<br>Read more about how CC uses [[RDFa]] and [[ccREL]] to signal to machines that a work is CC licensed.]]

}}

{{PageColumn|
== [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.

: Tools to use:

:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]

: '''Best Practices Example''': CC license deeds

: [[File:Attribution box via RDFa and Javascript.png|thumb|260px|border|<br>CC license deeds will automatically generate Attribution HTML if the referring page contains relevant RDFa.]]

== [[Web Integration/InterfaceExample|License aware user interfaces]] ==
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.

: '''Tools to use''':

:: [[RDFa]], and [[CcREL|ccREL]]

: '''Best Practices Example''': [[Flickr]]

: [[File:Flickr Creative Commons Exploration portal.png|thumb|260px|border|[[Flickr]]'s CC portal represents a good way to break down CC content for end users.]]

}}

== Adopters ==

We have a long list of [[Content Directories]] which are basically sites, projects and people who have implemented CC licensing and/or have some type of CC licensing. This is the best list of high level CC license adopters, all generated from the community. NOTE: CC does not have a database of content or keep a defacto list of all those who use CC licenses. The list above is used to provide examples.

== Assistance ==

If you are hoping to adopt this, please contact Fred Benenson (fred [at] creativecommons.org) and/or http://creativecommons.org/contact

<br clear="all"/>
</div>

=== See also ===

: Back to '''[[Web Integration]]'''
: '''[[Desktop Integration]]'''
: '''[[Developers]]'''

Web Integration/HowTo

2009-08-10T20:29:24Z

Fred Benenson:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporating CC license metadata functionality into your web application. This guide has been generalized from various plans for video, audio, or image sharing sites.

Below are 5 areas where integration can occur in your web application. While each web application may not need each of the 5 integrations, Creative Commons recommends that as many as practical are implemented.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
== [[Web Integration/FileUploadExample|License Choice on file upload]] ==
Users should be able to choose which license they want for each file they upload.

This will allow users to make fine-grain decisions about their works (so that some are CC and some are still All Rights Reserved)

: '''Tools to use''':

:: [[LicenseChooser.js]] or [[Web Services]]

: '''Best Practices Example''': [[SoundCloud]]

: [[File:Sound Cloud License Choice on Upload.png|thumb|260px|border|
<br>
[[SoundCloud]]'s [http://soundcloud.com/upload#old-skool license chooser] on upload is a good way to let users choose a CC license.]]

== [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
In account settings, users should be able to specify a default license for their content they create on the site.

This can be combined with License Choice on File Upload to allow users to have the default license be, for example, CC:BY and in special cases some others be CC:BY-SA, or even All Rights Reserved.

: Tools to use:

:: [[LicenseChooser.js]] or [[Web Services]]

: '''Best Practices Example''': [[Flickr]]

: [[File:Flickr Default License Choice.png|thumb|260px|border|<br>[[Flickr]]'s account settings provide a default license for users to apply to all of their uploaded works.]]

== [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.

This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.

: Tools to use:

:: [[RDFa]] and [[CcREL|ccREL]]

: '''Best Practices Example''': [[Flickr]]

: [[File:RDFa-Explanation.png|thumb|260px|border|<br>Read more about how CC uses [[RDFa]] and [[ccREL]] to signal to machines that a work is CC licensed.]]

}}

{{PageColumn|
== [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.

: Tools to use:

:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]

: '''Best Practices Example''': CC license deeds

: [[File:Attribution box via RDFa and Javascript.png|thumb|260px|border|<br>CC license deeds will automatically generate Attribution HTML if the referring page contains relevant RDFa.]]

== [[Web Integration/InterfaceExample|License aware user interfaces]] ==
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.

: '''Tools to use''':

:: [[RDFa]], and [[CcREL|ccREL]]

: '''Best Practices Example''': [[Flickr]]

: [[File:Flickr Creative Commons Exploration portal.png|thumb|260px|border|[[Flickr]]'s CC portal represents a good way to break down CC content for end users.]]

}}

== Adopters ==

We have a long list of [[Content Directories]] which are basically sites, projects and people who have implemented CC licensing and/or have some type of CC licensing. This is the best list of high level CC license adopters, all generated from the community. NOTE: CC does not have a database of content or keep a defacto list of all those who use CC licenses. The list above is used to provide examples.

== Assistance ==

If you are hoping to adopt this, please contact Fred Benenson (fred [at] creativecommons.org) and/or http://creativecommons.org/contact

<br clear="all"/>
</div>

=== See also ===

: Back to '''[[Web Integration]]'''
: '''[[Desktop Integration]]'''
: '''[[Developers]]'''

File:RDFa-Explanation.png

2009-08-10T20:18:37Z

Fred Benenson: A visual image of how ccREL / RDFa renders to become a license badge.

A visual image of how [[ccREL]] / [[RDFa]] renders to become a license badge.

File:Flickr Default License Choice.png

2009-08-10T19:59:04Z

Fred Benenson: A great example of how to let users choose a default CC license in their account settings.

A great example of how to let users choose a default CC license in their account settings.

File:Sound Cloud License Choice on Upload.png

2009-08-10T19:56:07Z

Fred Benenson: A great example of how to let users choose a CC license on upload.

A great example of how to let users choose a CC license on upload.

File:Flickr Creative Commons Exploration portal.png

2009-08-10T19:46:44Z

Fred Benenson: A great example of how to expose CC content to end users.

A great example of how to expose CC content to end users.

Open Education - Legal, Technical, and Social Dimensions

2009-08-05T16:25:26Z

Fred Benenson: Created page with '{{Presentation |venue=2009 West Virginia Statewide Technology Conference |date=2009/08/06 |presenter=Fred Benenson }}'

{{Presentation
|venue=2009 West Virginia Statewide Technology Conference
|date=2009/08/06
|presenter=Fred Benenson
}}

Open Video and Metadata

2009-08-05T16:23:52Z

Fred Benenson: Created page with '{{Presentation |venue=Open Video Conference |date=2009/06/20 |presenter=Fred Benenson |slidesurl=http://www.slideshare.net/mecredis/open-video-and-metadata-presentation }}'

{{Presentation
|venue=Open Video Conference
|date=2009/06/20
|presenter=Fred Benenson
|slidesurl=http://www.slideshare.net/mecredis/open-video-and-metadata-presentation
}}

Copyright War Summit

2009-08-05T16:21:36Z

Fred Benenson: Created page with '{{Presentation |venue=BrightTalk |date=2009/06/09 |presenter=Fred Benenson |slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation |audiourl=http:…'

{{Presentation
|venue=BrightTalk
|date=2009/06/09
|presenter=Fred Benenson
|slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation
|audiourl=http://www.brighttalk.com/webcasts/3892/play
}}

Presentation to the New Yorker and Conde Nast

2009-08-05T16:16:44Z

Fred Benenson: moved Presentation to the New Yorker / Conde Nast to Presentation to the New Yorker and Conde Nast

{{Presentation
|venue=The New Yorker, Conde Nast Building
|date=2009/06/01
|presenter=Fred Benenson
}}

Presentation to the New Yorker / Conde Nast

2009-08-05T16:16:44Z

Fred Benenson: moved Presentation to the New Yorker / Conde Nast to Presentation to the New Yorker and Conde Nast

#REDIRECT [[Presentation to the New Yorker and Conde Nast]]

Presentation to the New Yorker and Conde Nast

2009-08-05T16:15:24Z

Fred Benenson:

{{Presentation
|venue=The New Yorker, Conde Nast Building
|date=2009/06/01
|presenter=Fred Benenson
}}

Presentation to the New Yorker and Conde Nast

2009-08-05T16:15:05Z

Fred Benenson: Created page with '{{Presentation |venue=Conde Nast Building |date=2009/06/01 |presenter=Fred Benenson }}'

{{Presentation
|venue=Conde Nast Building
|date=2009/06/01
|presenter=Fred Benenson
}}

Presentation to Brooklyn Public Library

2009-08-05T16:12:46Z

Fred Benenson: Created page with '{{Presentation |venue=Brooklyn Public LIbrary |date=2009/04/03 |presenter=Fred Benenson |slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation }}'

{{Presentation
|venue=Brooklyn Public LIbrary
|date=2009/04/03
|presenter=Fred Benenson
|slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation
}}

New Licensing Options for the Information Age

2009-08-05T16:11:00Z

Fred Benenson: Created page with '{{Presentation |venue=International Intellectual Property Society of NY |date=2009/02/19 |presenter=Fred Benenson |slidesurl=http://www.slideshare.net/mecredis/creative-commons-s…'

{{Presentation
|venue=International Intellectual Property Society of NY
|date=2009/02/19
|presenter=Fred Benenson
|slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation
}}
"The “information age” has posed new challenges to copyright protection. IIPS is most fortunate to have Fred Benenson, Outreach Manager for Creative Commons, and Marc Jonas Block, Esq. present New Licensing Options for the Information Age on Thursday, February 19, 2009 from 6:00 to 8:00 p.m. at the IBM building (57th and Madison), New York, NY 10022. Mr. Benenson and Mr. Block will discuss alternatives for creators to protect their original works, but yet encourage the sharing of ideas."

Florida State University Presentation

2009-08-05T16:08:32Z

Fred Benenson: Created page with '{{Presentation |venue=FSU - Online Presentation |date=2009/02/19 |presenter=Fred Benenson |slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation …'

{{Presentation
|venue=FSU - Online Presentation
|date=2009/02/19
|presenter=Fred Benenson
|slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation
}}
Online "virtual" presentation to graduate class on media.

Creative Commons Presentation to Wahab and Medenica

2009-08-05T15:06:31Z

Fred Benenson:

{{Presentation
|venue=Wahab & Medenica LLC, 1115 Broadway, 24th and 25th, 12th Floor
|date=2009/01/20
|presenter=Fred Benenson,
|slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation
}}
Presentation to Law Firm. Virginia Rutledge in attendance.

Creative Commons Presentation to Wahab and Medenica

2009-08-05T15:03:21Z

Fred Benenson: moved Creative Commons Presentation to Wahab to Creative Commons Presentation to Wahab and Medenica

{{Presentation
|venue=Wahab & Medenica LLC, 1115 Broadway, 24th and 25th, 12th Floor
|date=2009/01/20
|presenter=User:Fred Benenson,
|slidesurl=http://www.slideshare.net/mecredis/creative-commons-spring-2009-presentation
}}
Presentation to Law Firm. Virginia Rutledge in attendance.

Creative Commons Presentation to Wahab

2009-08-05T15:03:21Z

Fred Benenson: moved Creative Commons Presentation to Wahab to Creative Commons Presentation to Wahab and Medenica

#REDIRECT [[Creative Commons Presentation to Wahab and Medenica]]

Creative Commons Presentation to Wahab and Medenica

2009-08-05T15:02:45Z

Fred Benenson:

Creative Commons Presentation to Wahab and Medenica

2009-08-05T15:02:35Z

Fred Benenson:

Creative Commons Presentation to Wahab and Medenica

2009-08-05T15:02:15Z

Fred Benenson: Created page with '{{Presentation |venue=Wahab & Medenica LLC, 1115 Broadway, 24th and 25th, 12th Floor |date=2009/01/20 |presenter=User:Fred Benenson, |slidesurl=http://www.slideshare.net/mecredi…'

Google Policy Fellowship Final Symposium

2009-08-05T14:33:35Z

Fred Benenson: moved Presentation Title to Google Policy Fellowship Final Symposium: Fixing name.

{{Presentation
|venue=Google
|date=2009/07/29
|presenter=Aurelia Schultz
|slidesurl=https://docs.google.com/a/creativecommons.org/fileview?id=0B7ZzbwL4sYsYMTMzYTU4MzUtNmM5MS00ZjAxLWJmY2QtNGMzYzBhYWM2YTgx&hl=en

}}
5 minute presentation given at Google Policy Fellowship Final Symposium.

Presentation Title

2009-08-05T14:33:35Z

Fred Benenson: moved Presentation Title to Google Policy Fellowship Final Symposium: Fixing name.

#REDIRECT [[Google Policy Fellowship Final Symposium]]

Web Integration/HowTo

2009-08-03T21:52:12Z

Fred Benenson:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporating CC license metadata functionality into your web application. This guide has been generalized from various plans for video, audio, or image sharing sites.

Below are 5 areas where integration can occur in your web application. While each web application may not need each of the 5 integrations, Creative Commons recommends that as many as practical are implemented.
</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;">
== 1. [[Web Integration/FileUploadExample|License Choice on file upload]] ==
Users should be able to choose which license they want for each file they upload.

This will allow users to make fine-grain decisions about their works (so that some are CC and some are still All Rights Reserved)

: Tools to use:
:: [[LicenseChooser.js]] or [[Web Services]]

== 2. [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
In account settings, users should be able to specify a default license for their content they create on the site.

This can be combined with License Choice on File Upload to allow users to have the default license be, for example, CC:BY and in special cases some others be CC:BY-SA, or even All Rights Reserved.

: Tools to use:
:: [[LicenseChooser.js]] or [[Web Services]]

== 3. [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.

This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.

: Tools to use:
:: [[RDFa]] and [[CcREL|ccREL]]

== 4. [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.

: Tools to use:
:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]

== 5. [[Web Integration/InterfaceExample|License aware user interfaces]] ==
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.

: Tools to use:
:: [[RDFa]], and [[CcREL|ccREL]]

</div>

<br clear="all"/>

== Adopters ==

We have a long list of [[Content Directories]] which are basically sites, projects and people who have implemented CC licensing and/or have some type of CC licensing. This is the best list of high level CC license adopters, all generated from the community. NOTE: CC does not have a database of content or keep a defacto list of all those who use CC licenses. The list above is used to provide examples.

== Assistance ==

If you are hoping to adopt this, please contact Fred Benenson (fred [at] creativecommons.org) and/or http://creativecommons.org/contact

<br clear="all"/>

=== See also ===

: Back to '''[[Web Integration]]'''
: '''[[Desktop Integration]]'''
: '''[[Developers]]'''

Web Integration/HowTo

2009-08-03T21:48:03Z

Fred Benenson:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
The goal of this HowTo is to provide a basic step-by-step guide to the technical concerns when incorporating CC license metadata functionality into your web application. This guide has been generalized from various plans for video, audio, or image sharing sites.

Below are 5 areas where integration can occur in your web application. While each web application may not need each of the 5 integrations, Creative Commons recommends that as many as practical are implemented.
</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;">
== 1. [[Web Integration/FileUploadExample|License Choice on file upload]] ==
Users should be able to choose which license they want for each file they upload.

This will allow users to make fine-grain decisions about their works (so that some are CC and some are still All Rights Reserved)

: Tools to use:
:: [[LicenseChooser.js]] or [[Web Services]]

== 2. [[Web Integration/DefaultLicenseExample|Default License choice in account settings]] ==
In account settings, users should be able to specify a default license for their content they create on the site.

This can be combined with License Choice on File Upload to allow users to have the default license be, for example, CC:BY and in special cases some others be CC:BY-SA, or even All Rights Reserved.

: Tools to use:
:: [[LicenseChooser.js]] or [[Web Services]]

== 3. [[Web Integration/RDFaExample|Include license RDFa on content pages]] ==
Including RDFa code signals to machines (search engines, browsers, etc) exactly how a specific work is licensed.

This allows works to be scraped by search engines and other automatic content discovery services with associated license metadata.

: Tools to use:
:: [[RDFa]] and [[CcREL|ccREL]]

== 4. [[Web Integration/CopyableExample|Include copyable attribution language with RDFa]] ==
This is similar to practice to video embed code from services such as YouTUBE. However, this HTML is for bloggers and other republishers easily attribute a work fully and correctly.

: Tools to use:
:: [[Web Services]], [[RDFa]], and [[CcREL|ccREL]]

== 5. [[Web Integration/InterfaceExample|License aware user interfaces]] ==
Utilize all of the license metadata to provide new and interesting interfaces to view content based on the license data.

: Tools to use:
:: [[RDFa]], and [[CcREL|ccREL]]

</div>

<br clear="all"/>

== Adopters ==

We have a long list of [[Content Directories]] which are basically sites, projects and people who have implemented CC licensing and/or have some type of CC licensing. This is the best list of high level CC license adopters, all generated from the community. NOTE: CC does not have a database of content or keep a defacto list of all those who use CC licenses. The list above is used to provide examples.

== Assistance ==

If you are hoping to adopt this, please contact Fred Benenson (fred [at] creativecommons.org) and/or http://creativecommons.org/contact

<br clear="all"/>
</div>

=== See also ===

: Back to '''[[Web Integration]]'''
: '''[[Desktop Integration]]'''
: '''[[Developers]]'''

CC REL

2009-07-13T16:59:25Z

Fred Benenson:

{{lowercase}}
[[Category:Metadata]]
[[Category:Developer]]

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

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

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

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

== Presentations ==

* [[Creative Commons Technology Summit 2009-06-26]], '''upcoming, CFP open'''
* [[Creative Commons Technology Summit 2008-12-12]], multiple
* [[An Introduction to ccREL and The Use of Semantic Technology at Creative Commons]]
* [[ccREL update]]
* [[Creative Commons Technology Summit 2008-06-18]], multiple
* [[Deploying the Semantic Web with ccREL and RDFa]]
* [[COMMUNIA January 2008]]

== Examples ==

=== Simple ===
<pre>
My Book by Jon Phillips is licensed under a

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

Permissions beyond the scope of this license may be available at
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions"
href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.
</pre>

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

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

is licensed under a

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

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

</span>
</pre>

== Examples of ccREL in the Wild ==

* [http://www.thingiverse.com/ Thingiverse]
* Add yours!

== See Also ==

* [[RDFa]] is the cored technology behind [[ccREL]]
* [[XMP]]
* [[ccPlus]] uses [[ccREL]]

{{Challenge Enabled}}

File:New York State Senate Logo.png

2009-06-22T16:23:48Z

Fred Benenson: Logo for the New York State Senate website.

Logo for the New York State Senate website.

Government use of Creative Commons

2009-06-22T16:22:51Z

Fred Benenson: /* United States */

The Dabbler...

2009-06-02T01:33:24Z

Fred Benenson: Created page with '{{Films |director=Reid Gershbein |producer=Reid Gershbein |filmtype=FeatureFilm |mainurl=http://www.royalbaronialtheatre.com/blog/the-dabbler-film-details-2wkfilm.html |distribut...'

{{Films
|director=Reid Gershbein
|producer=Reid Gershbein
|filmtype=FeatureFilm
|mainurl=http://www.royalbaronialtheatre.com/blog/the-dabbler-film-details-2wkfilm.html
|distributer=Self
|releasedate=1 June 2009
|license=http://creativecommons.org/licenses/by-sa/3.0/
|cclicensed=http://blip.tv/file/get/Thraveboy-TheDabblerFullFeatureFilm2wkfilm712.mov
}}

Here. My Explosion..

2009-06-02T01:31:33Z

Fred Benenson: Created page with '{{Films |director=Reid Gershbein |producer=Reid Gershbein |filmtype=FeatureFilm |mainurl=http://www.royalbaronialtheatre.com/blog/here-my-explosion-film-details.html |imdburl=htt...'

{{Films
|director=Reid Gershbein
|producer=Reid Gershbein
|filmtype=FeatureFilm
|mainurl=http://www.royalbaronialtheatre.com/blog/here-my-explosion-film-details.html
|imdburl=http://www.imdb.com/title/tt1374890/
|distributer=Self
|releasedate=15 May 2009
|license=http://creativecommons.org/licenses/by-sa/3.0/
|cclicensed=http://a28.video2.blip.tv/3070001299401/Thraveboy-HereMyExplosionFullFeatureFilm733.mov
}}

Facebook Application

2009-05-28T16:16:47Z

Fred Benenson:

[[File:Creative Commons License Application on Facebook.png|right]]
=About=
The Creative Commons License application allows users to choose one of the six Creative Commons licenses to apply to the content they upload to Facebook.

This application was developed by [[User:Fred Benenson]] for Creative Commons.
*[http://www.facebook.com/editapps.php#/apps/application.php?id=78186376044 Creative Commons License Application on Facebook]
=Install=
*[http://apps.facebook.com/creativecommons/ Install the Application here].
=Features=
*License chooser modeled on [http://creativecommons.org/license Creative Commons']
*Choose either photos, video, or profile text & Status updates
*[[RDFa]] expression of Author, Title, license.
=Known Issues=
*Licensing only works on a per-profile basis.
*Only allows one license-per-profile
**Photos could be licensed one way, text another, videos another, etc.
=Bugs=
*Adds News Feed update before badge is selected (if users decide to go back and change license, then wrong status update is sent).

=Suggested Features=
*CC Zero waiver support.
*More thorough popup w/ CC license descriptions.
*Translation & choice of localized license
*"Other" textfield to allow variable content types.
*CC Network integration
*Search users content who have chosen a CC license.

=Code=
*[http://code.creativecommons.org/viewgit/cc_license_facebook_app.git/ Git Repository]

Facebook Application

2009-05-19T13:50:43Z

Fred Benenson: /* Bugs */

Facebook Application

2009-05-18T18:22:23Z

Fred Benenson: /* Suggested Features */

[[File:Creative Commons License Application on Facebook.png|right]]
=About=
The Creative Commons License application allows users to choose one of the six Creative Commons licenses to apply to the content they upload to Facebook.

This application was developed by [[User:Fred Benenson]] for Creative Commons.
*[http://www.facebook.com/editapps.php#/apps/application.php?id=78186376044 Creative Commons License Application on Facebook]
=Install=
*[http://apps.facebook.com/creativecommons/ Install the Application here].
=Features=
*License chooser modeled on [http://creativecommons.org/license Creative Commons']
*Choose either photos, video, or profile text & Status updates
*[[RDFa]] expression of Author, Title, license.
=Known Issues=
*Licensing only works on a per-profile basis.
*Only allows one license-per-profile
**Photos could be licensed one way, text another, videos another, etc.
=Bugs=
=Suggested Features=
*CC Zero waiver support.
*More thorough popup w/ CC license descriptions.
*Translation & choice of localized license
*"Other" textfield to allow variable content types.
*CC Network integration
*Search users content who have chosen a CC license.

Facebook Application

2009-05-18T16:55:30Z

Fred Benenson: /* Suggested Features */

[[File:Creative Commons License Application on Facebook.png|right]]
=About=
The Creative Commons License application allows users to choose one of the six Creative Commons licenses to apply to the content they upload to Facebook.

This application was developed by [[User:Fred Benenson]] for Creative Commons.
*[http://www.facebook.com/editapps.php#/apps/application.php?id=78186376044 Creative Commons License Application on Facebook]
=Install=
*[http://apps.facebook.com/creativecommons/ Install the Application here].
=Features=
*License chooser modeled on [http://creativecommons.org/license Creative Commons']
*Choose either photos, video, or profile text & Status updates
*[[RDFa]] expression of Author, Title, license.
=Known Issues=
*Licensing only works on a per-profile basis.
*Only allows one license-per-profile
**Photos could be licensed one way, text another, videos another, etc.
=Bugs=
=Suggested Features=
*CC Zero waiver support.
*Translation & choice of localized license
*"Other" textfield to allow variable content types.
*CC Network integration
*Search users content who have chosen a CC license.

Facebook Application

2009-05-18T15:47:39Z

Fred Benenson:

[[File:Creative Commons License Application on Facebook.png|right]]
=About=
The Creative Commons License application allows users to choose one of the six Creative Commons licenses to apply to the content they upload to Facebook.

This application was developed by [[User:Fred Benenson]] for Creative Commons.
*[http://www.facebook.com/editapps.php#/apps/application.php?id=78186376044 Creative Commons License Application on Facebook]
=Install=
*[http://apps.facebook.com/creativecommons/ Install the Application here].
=Features=
*License chooser modeled on [http://creativecommons.org/license Creative Commons']
*Choose either photos, video, or profile text & Status updates
*[[RDFa]] expression of Author, Title, license.
=Known Issues=
*Licensing only works on a per-profile basis.
*Only allows one license-per-profile
**Photos could be licensed one way, text another, videos another, etc.
=Bugs=
=Suggested Features=
*CC Zero waiver support.
*Translation & choice of localized license
*"Other" textfield to allow variable content types.

File:Creative Commons License Application on Facebook.png

2009-05-18T15:46:39Z

Fred Benenson: A screenshot of the Creative Commons License Application on Facebook.

A screenshot of the Creative Commons License Application on Facebook.

Facebook Application

2009-05-08T19:49:03Z

Fred Benenson: /* Later Features */

This is information about Creative Commons' Facebook application.

Its not written yet, so there's not much to say about it.

=Initial Spec=

* Ability to choose one of the six Creative Commons licenses
* Ability to chose what types of licensed:
** Photos
** Video
** Text / Profile Info
** Status Updates
** Other
* Expression of RDFa
* Update User news feed with CC license choice

=Later Features=
*Creative Commons.net Link
*CC Zero Waiver
*??

Facebook Application

2009-05-08T19:48:00Z

Fred Benenson: Created page with 'This is information about Creative Commons' Facebook application. Its not written yet, so there's not much to say about it. =Initial Spec= * Ability to choose one of the six C...'

RDFa

2009-03-11T19:50:23Z

Fred Benenson:

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. When you select a license in our [http://creativecommons.org/license license chooser], you are given a snippet of HTML that contains RDFa. Sites like [http://www.thingiverse.com Thingiverse] have implemented RDFa across their platform so that every object uploaded expresses semantic information about itself to machines.

By using RDFa, Creative Commons is helping build the semantic web. Here are some frequently asked questions which can help you understand RDFa and the semantic web.

=What is the point of the semantic web?=
Traditionally, machines have had a very poor understanding of what humans are actually talking about when they create content. Computers may understand that a file is a text file or another file is an image file, but they typically don't understand what knowledge, or semantics, are expressed inside that file. This has been remedied to some extent by metadata such as [http://en.wikipedia.org/wiki/Tag_(metadata) tags] or [http://en.wikipedia.org/wiki/EXIF EXIF data].

But to a machine, the web is merely a heap of human-readable-data that needs to be classified by seemingly arbitrary rules. Google and other search engines have engineered meaning out of how humans create HTML documents. By interpreting a link expressed in HTML as a semantically meaningful "vote" for another page, Google can accurately value and rank all linked pages on the web.

While incoming links are good semantic indicators of value (or popularity) of a page, web pages should be able to express much more sophisticated statements to machines. Currently, web pages only express sophisticated statements to humans, but this can change.

Furthermore, humans should have the ability to query these knowledge statements in sophisticated ways. Just think if you could ask a question to Google about how many US presidents were born in Kentucky and receive an answer not because Google had somehow magically interpreted what you meant, but simply because Google maintained a database of statements about presidents and Kentucky that was trivially easy to query?

The vision behind the semantic web is that storing and retrieving information on the web should not require machines parsing human language but rather machines parsing machine language. The web has the potential to offer massive amounts of structured information in conjunction with the massive amounts of unstructured information that already exists and if we are careful to create the proper standards and platforms that can render these statements, then the semantic web will become a reality.

=What is RDF?=
RDF stands for "Resource Description Framework" which is not a particularly informative acronym. Put simply, RDF is the way information is expressed semantically on the web. RDF is constituted by ''triples'' which are subject-predicate-objects statements. This lets machines understand human knowledge statements. When many triples are aggregated they are stored in what's called a "triple store." By querying a triple store, we can learn information that might otherwise be hard to gather by just browsing the web with our eyes. As the semantic web evolves, it will become easier to query triple stores using natural language, and hopefully, discover things we wouldn't have ordinarily.

=What is a RDF triple?=
A RDF triple can formed from any semantically meaningful statement. Here are some examples:
<pre><This website> <has> <a wiki>.
<That photo> <is licensed under> <a Creative Commons Attribution license>.</pre>
Depending on the format chosen, RDF triples can live inside an XML or XHTML file.

=What is RDFa?=
RDFa is a way of expressing RDF triples inside XHTML pages using span tags.

This makes it much easier for people to casually express semantic information in conjunction with a normal web page. While there are many ways to express RDF (such as in serialized XML files that live next to standard web pages), RDFa helps machines and humans read exactly the same content.

=Why does CC use RDFa?=
Creative Commons licenses are expressed in three different formats: the human readable license deed, the lawyer readable legal code, and the machine readable code. RDFa is one of the ways in which we've chosen to make our licenses machine readable. By using RDFa CC licensed objects can be discovered by search engines and auto-discovery mechanisms without the need for a human to hand-curate content directories or lists.

Moreover, by using RDFa CC has made our licenses and their meta data compatible with a larger movement towards the open standard of a semantic web.

=How does CC use RDFa?=
When creators fill out the "Additional Information" section of our license chooser form, they are given a snippet of XHTML code that contains an image badge, a link to our license, some text, and some span tags. Inside these span tags, RDFa is expressed.

Let's take a look at some example code to learn more about RDFa:

<pre>
<a rel="license" href="http://creativecommons.org/licenses/by/3.0/us/">
<img alt="Creative Commons License" style="border-width:0"
src="http://i.creativecommons.org/l/by/3.0/us/88x31.png" /></a><br />
<span xmlns:dc="http://purl.org/dc/elements/1.1/" href="http://purl.org/dc/dcmitype/Text"
property="dc:title" rel="dc:type">RDFa FAQ</span> by <a
xmlns:cc="http://creativecommons.org/ns#" href="www.example.com"
property="cc:attributionName" rel="cc:attributionURL">John Doe</a>
is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by/3.0/us/">Creative Commons
Attribution 3.0 United States License</a>.<br />Based on a work at
<a xmlns:dc="http://purl.org/dc/elements/1.1/" href="http://wiki.creativecommons.org/RDFa"
rel="dc:source">wiki.creativecommons.org</a>.<br />
Permissions beyond the scope of this license may be available at <a
xmlns:cc="http://creativecommons.org/ns#" href="http://moreperms"
rel="cc:morePermissions">http://moreperms</a>.
</pre>
==Breaking Down RDFa==
===dc:title/dc:type===
dc represents "Dublin Core" which is one of the oldest vocabularies or schemas on the semantic web. The full dublin core is available [http://purl.org/dc/ here]. It allows one to express typical things like a work's title, or its date. Here you can CC using this to express the work's title which I've fictitiously named RDFa FAQ.

<pre><span xmlns:dc="http://purl.org/dc/elements/1.1/"
href="http://purl.org/dc/dcmitype/Text" property="dc:title" rel="dc:type">
RDFa FAQ</span></pre>

CC is using a XML name-space abbreviation or "xmlns" for short. This enables CC to use shorthand to refer to the dublin core schema. Instead of having to repeatedly state a URL such as http://purl.org/dc/title to reference the title property, we can simply use dc: and achieve the same thing. This principle works across all RDF.

The dc:type references the Dublin Core definition for "Text" using the rel tag. Rel is used to specify the attribute's relationship to another resource. When rel is used inside a anchor tag, it is specifying that the document at the URL in the href attribute is of a particular relationship to the work. In this case that relationship is the Dublin Core "Type" attribute, and the href is the DC Text specification. Another document Type that could be specified with the href is http://purl.org/dc/dcmitype/StillImage or http://purl.org/dc/dcmitype/Sound, depending on the medium being licensed.
===cc:attributionName/cc:attributionURL===
In this case, CC is using its own XML namespace, abbreviated using cc:
<pre><a xmlns:cc="http://creativecommons.org/ns#"
href="http://www.example.com" property="cc:attributionName"
rel="cc:attributionURL">John Doe</a></pre>
Again, the property is CC's AttributionName attribute, the value is the content inside the anchor tag (in this case, the fictitious John Doe), and a relationship of cc:AttributionURL is defined as being http://www.example.com.
===rel="license"===
This is the most basic and fundamental part of CC's useage of RDFa, and is always included in the HTML offered, regardless of whether users fill out the "Additional Information" section.
<pre><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/us/">
Creative Commons Attribution-Share Alike 3.0 United States License</a>.</pre>
The rel specifies the relationship of the href's URL. In this case, the relationship is "license" and the URL is a standard Creative Commons license.
===dc:source===
Similar to dc:title, dc:source specifies where the original source of the file is located.
<pre>Based on a work at <a xmlns:dc="http://purl.org/dc/elements/1.1/"
href="http://wiki.creativecommons.org/RDFa" rel="dc:source">
wiki.creativecommons.org</a></pre>
In this case it is pointing to this document.
===cc:morePermissions===
Finally, as part of the CC+ protocol, creators can specify a URL where re-users of CC licenses can obtain more rights to the work. Visit the CC+ page for more information and examples of CC+ in action. Here, the nonexistent URL of http://moreperms is used as a placeholder.
<pre>Permissions beyond the scope of this license may be available at <a
xmlns:cc="http://creativecommons.org/ns#" href="http://moreperms"
rel="cc:morePermissions">http://moreperms</a>.</pre>

==CC Deeds using RDFa and Javascript==
CC licenses scrape RDFa metadata from referring pages in order to create a "live" box on the Deed page that suggests how to attribute the work:
[[Image:Attribution box via RDFa and Javascript.png]]
This will allow reusers to easily and properly attribute CC licensed works using RDFa.

=What does it mean that RDFa is a W3C recommendation?=
The [http://www.w3.org World Wide Web Consortium] agrees to recommend certain standards for helping the web run smoothly. One of those recommendations is that [http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014/ RDFa be used to expressed license information on the semantic web].

=How do I use RDFa?=
==If you're a creator using CC licenses==
Make sure to fill out the "Additional Information" box when selecting your license.
==If you're a user of CC licensed works==
Make sure to copy the attribution XHTML from the license deed if it is available. Otherwise, feel free to roll your own RDFa span tags.
==I'm a developer, how do I implement RDFa into my platform?==
Implementing RDFa into your platform shouldn't require much more work than implementing CC, it's merely a matter of adding a couple more print statements inside the RDFa framework detailed above. Just make sure you swap out John Doe's name with the user's name, and fill in the proper license URLs.

=Content discovery=
A key use case for RDFa is the annotation of resources included or embedded in web pages. Existing annotations apply to the current document. For example, http://example.com/foo contains
<nowiki><a rel="license" href="http://creativecommons.org/licenses/by/3.0/">cc</a></nowiki>
This says that http://example.com/foo is licensed under CC BY 3.0. What about http://example.com/bar.jpg which is displayed in http://example.com/foo via a <nowiki><img src="/bar.jpg"></nowiki> element?

To specify that bar.jpg is licensed, even under a different license, we can qualify the link with an about attribute:
<nowiki><a about="/bar.jpg" rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">cc</a></nowiki>
Found in http://example.com/foo this says http://example.com/bar.jpg is licensed under CC BY-NC 3.0.

See [http://www.w3.org/2006/07/SWD/RDFa/primer/#qualifying-other-documents Qualifying Other Documents and Document Chunks] in the RDFa primer for more examples.

The [http://www.w3.org/2006/07/SWD/RDFa/impl/js/ RDFa highlighter bookmarklet] provides visual cues for statements about included resources.

== CC Tools ==

RDFa is used or supported in the following CC tools:

* '''License Deeds'''<br/>When visiting a license deed (for example, http://creativecommons.org/licenses/by/3.0/), the deed loads Javascript which looks at the [http://en.wikipedia.org/wiki/HTTP_REFERER referrer] for RDFa. If it finds attribution or network membership metadata, this is displayed on the deed.
* [[MozCC]] (see [[What's New in MozCC 2]])
* [[RdfaDict]] is a Python RDFa parser

==References==
* http://www.w3.org/2006/07/SWD/RDFa/primer/
* http://www.w3.org/TR/rdfa-syntax/
* [http://rdfa.info RDFa.info]
* [http://en.wikipedia.org/wiki/RDFa Wikipedia article]
* [http://esw.w3.org/topic/RDFa RDFa @ the W3 Wiki]

==Presentations==
* http://ben.adida.net/presentations/w3c-2006-04-06/html/w3c
* http://ben.adida.net/presentations/semantic-2006-03-08.pdf
* http://skimstone.x-port.net/introduction-to-rdfa

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

Facebook CC Integration/BoRR

2009-02-26T18:22:14Z

Fred Benenson:

== Readme ==

This is a collaborative work page for the Facebook user proposed integration of Creative Commons licenses for Facebook user generated content. This proposal is being generated by the Facebook group: [http://www.facebook.com/groups.php?ref=sb#/group.php?gid=55178542061 'Why not include Creative Commons in Facebook TOS?']

== Other Info ==

[[Facebook_CC_Integration/BoRR/News | News]]

[[Facebook_CC_Integration/BoRR/BasicInfo | Basic info on Creative Commons]]

== Versions of this proposal ==

{{Translations|
articles=Facebook CC Integration/Es:BoRR
}}

== English BoRR Proposal ==

==='''History:'''===
The movement to integrate [[Creative Commons]] [[licensing]] options into [http://facebook.com Facebook] user profiles is growing out of Facebook user response to the February 4th, 2009 revision of [http://www.facebook.com/groups.php?ref=sb#/terms.php?ref=pf Facebook's Terms of Use]. The only notice of this change was posted to the [http://blog.facebook.com/blog.php?post=50531412130 Facebook Blog] February 4th, 2009 and was not widely read by Facebook users. Several days later when, through media reports, users discovered this change and responded in protest, Facebook reverted to the prior Terms of Use dated September 23rd, 2008 and opened the group titled '[http://www.facebook.com/groups.php?ref=sb#/group.php?gid=69048030774 Facebook Bill of Rights and Responsibilities]' (BoRR), resulting in a user request that Facebook integrate creative commons and other licensing options. The group '[http://www.facebook.com/groups.php?ref=sb#/group.php?gid=55178542061 Why not include Creative Commons in Facebook TOS?]' (cconfb) was formed in order to focus this movement effectively. The need to produce a [[collaborative proposal for a Facebook/CC integration]] to present to the BoRR group that will provide users with choice about how their Facebook content is shared arose. This wiki document is the result.

===Objectives===
To create a collaborative proposal to the BoRR group submitting the advantages to both Facebook and Facebook users of integrating more versatile licensing options to user profiles and uploaded content, including Creative Commons licensing, similar to the way this has been successfully modeled by Flickr. View mockups of what this might look like in the '''Mockups''' section of this document.

===Justification===
We believe in the free exchange of knowledge and ideas, we also believe that any content creator has the right to distribute their original content as they choose fully copyrighted or with only some rights reserved. Creative Commons enables this, aiming to encourage creative sharing in creative ways that protect content creators, content providers and content consumers.

On February 16th, 2009, in response to user protest of the sudden change of Facebook's ToS without proper notice to it's users, Mark Zuckerberg [http://blog.facebook.com/blog.php?post=54434097130 responded] on the Official Facebook Blog "In reality, we wouldn't share your information in a way you wouldn't want. The trust you place in us as a safe place to share information is the most important part of what makes Facebook work."

The ability for users to select a licensing option ensures that there is clear agreement between Facebook and Facebook users regarding how users want their information used that does not rely user's trust in Facebook's judgment. This is especially important in the event Facebook should sometime in the future sell the company to another party.

Also, as we found on a post made by Julius Harper admin of the BoRR group (ref: http://www.facebook.com/topic.php?uid=69048030774&topic=8399). When he compiled of all the objections made by the users in the BoRR group:

'''Facebook’s use of my content should be subject to an easy-to-understand license, like Creative Commons, which lets me maintain ownership and control.'''

So our request is also supported by the people on the BoRR group (130000 people).

===The Problem===
Quote problematic sections from current Facebook TOS (revised September 23, 2008
Current Facebook TOS (dated from Sept. 23 2008) is (CC from [http://amandafrench.net/2009/02/16/facebook-terms-of-service-compared/ Amanda French])

''You hereby grant Facebook an irrevocable, perpetual, non-exclusive, transferable, fully paid, worldwide license (with the right to sublicense) to (a) use, copy, publish, stream, store, retain, publicly perform or display, transmit, scan, reformat, modify, edit, frame, translate, excerpt, adapt, create derivative works and distribute (through multiple tiers), any User Content you (i) Post on or in connection with the Facebook Service or the promotion thereof subject only to your privacy settings or (ii) enable a user to Post, including by offering a Share Link on your website and (b) to use your name, likeness and image for any purpose, including commercial or advertising, each of (a) and (b) on or in connection with the Facebook Service or the promotion thereof.
''

===Proposed Solutions===

While It is clear that the 'non-exclusive' license granted to Facebook by users does not exclude users also licensing their content under a Creative Commons license, we request the language "subject only to your privacy settings" be changed to "subject only to your privacy and license settings", and that license selection interface be added to user profiles and content uploads.

This is because, Facebook users should have the ability to choose not only with whom they want to share their content, but whether to grant commercial license or not, as well as whether to allow copy and remix or not.

To respect the wishes of it's users, we request from Facebook to adopt a ToS similar to Flickr's:

(taken from [http://amandafrench.net/2009/02/16/facebook-terms-of-service-compared/ Amanda French's Website])

''Yahoo! does not claim ownership of Content you submit or make available for inclusion on the Yahoo! Services. However, with respect to Content you submit or make available for inclusion on publicly accessible areas of the Yahoo! Services, you grant Yahoo! the following worldwide, royalty-free and non-exclusive license(s), as applicable [...]:''

''With respect to photos, graphics, audio or video you submit or make available for inclusion on publicly accessible areas of the Yahoo! Services other than Yahoo! Groups, the license to use, distribute, reproduce, modify, adapt, publicly perform and publicly display such Content on the Yahoo! Services solely for the purpose for which such Content was submitted or made available. This license exists only for as long as you elect to continue to include such Content on the Yahoo! Services and will terminate at the time you remove or Yahoo! removes such Content from the Yahoo! Services. ''

The only problem with Flickr's license is the right of modify and adapt they claim. That right isn't compatible with all the Creative Commons licenses. So we ask Facebook to make limits to that clause in order to use only in facebook's service and not against the Creative Commons NoDerivatives license.

Rewrite Facebook Terms of Service in [[Human Readable]] terms which communicate clearly that Facebook users maintain ownership of their IP, copyright and control over their choice of license.

===Mockups===

This is a Mockup where we can see all the Creative Commons options to define a specific license, we request something similar to be implemented in Facebook.

With informational purpose only, there are others Mockups here [[Facebook CC Integration]]

This Mockup is licenced as Creative Commons by Fabricio Campos Z.

[[Image:Fb_cc_mockup.png#file]]

===Benefits of Proposed Solutions===

We see three benefits

First of all, the benefit of being friendly with their users. Facebook was severely criticized for his draconian ToS, then, this will be a ToS that goes in the opposite direction, so we expect from the CC crowd and from the general users a very good reception and a restoration of confidence in Facebook.

Second, an improvement of all CC Situation in the world. Facebook could bring a lot of Creative Commons content to the world heritage.

Third, Facebook will enjoy some of his competitors market share (example: the CC share of flickr)