<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Creative Commons &#187; Creative Commons Licensing Application</title>
	<atom:link href="http://creativecommons.org/tag/creative-commons-licensing-application/rss" rel="self" type="application/rss+xml" />
	<link>http://creativecommons.org</link>
	<description>Share, reuse, and remix — legally.</description>
	<lastBuildDate>Thu, 24 May 2012 19:21:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Coca-Cola Using CC on&#160;Facebook</title>
		<link>http://creativecommons.org/weblog/entry/17299</link>
		<comments>http://creativecommons.org/weblog/entry/17299#comments</comments>
		<pubDate>Tue, 01 Sep 2009 12:55:02 +0000</pubDate>
		<dc:creator>Fred Benenson</dc:creator>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Weblog]]></category>
		<category><![CDATA[CC BY-NC-SA]]></category>
		<category><![CDATA[coca-cola]]></category>
		<category><![CDATA[coke]]></category>
		<category><![CDATA[Creative Commons Licensing Application]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[milestone]]></category>
		<category><![CDATA[terms of service]]></category>

		<guid isPermaLink="false">http://creativecommons.org/?p=17299</guid>
		<description><![CDATA[It recently came to our attention that Coca-Cola relaunched their Facebook Page (apparently one of the largest pages on the social network, with over 3.6 million fans), and included a policy that content shared by fans be available under our Attribution-NonCommercial-ShareAlike license. The specific CC license badge appears in the sidebar on the Coke wall, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.facebook.com/cocacola"><img src="http://creativecommons.org/wp-content/uploads/2009/09/Picture-9.png" alt="Coca-Cola Using Coke on Facebook" title="Coca-Cola Using Coke on Facebook" width="777" height="324" class="aligncenter size-full wp-image-17300" /></a></p>
<p>It recently came to our attention that <a href="http://www.coke.com">Coca-Cola</a> relaunched their <a href="http://facebook.com/cocacola">Facebook Page</a> (apparently one of the largest pages on the social network, with over 3.6 million fans), and included a policy that content shared by fans be available under our <a href="http://creativecommons.org/licenses/by-nc-sa/3.0/">Attribution-NonCommercial-ShareAlike license</a>.  The specific CC license badge <a href="http://www.facebook.com/cocacola?v=wall&#038;viewas=121130">appears in the sidebar on the Coke wall</a>, but is also referenced in <a href="http://assets.facebook.coca-cola.com/ccfbtou/">the Coca-Cola Facebook Terms of Service</a>.</p>
<p>It appears that Coke is using a Facebook App called <a href="http://www.facebook.com/apps/application.php?id=4949752878&#038;ref=s">Static FBML</a> that helps Page administrators include arbitrary HTML in Facebook pages.  Since this is such a good idea, I&#8217;m going to work on a new version of our <a href="http://creativecommons.org/?p=14563">Official Unofficial CC License Facebook application</a> that will enable all Page administrators to add CC license policies to their pages. More on that later this week.</p>
<p>Anyway, this is a great step forward for encouraging CC content and choices on Facebook, so kudos to Coke for thinking about user generated content in the right way!</p>
]]></content:encoded>
			<wfw:commentRss>http://creativecommons.org/weblog/entry/17299/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Official Unofficial Creative Commons Facebook&#160;Application</title>
		<link>http://creativecommons.org/weblog/entry/14563</link>
		<comments>http://creativecommons.org/weblog/entry/14563#comments</comments>
		<pubDate>Mon, 18 May 2009 16:10:50 +0000</pubDate>
		<dc:creator>Fred Benenson</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[Weblog]]></category>
		<category><![CDATA[Creative Commons Licensing Application]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[RDFa]]></category>

		<guid isPermaLink="false">http://creativecommons.org/?p=14563</guid>
		<description><![CDATA[Last weekend I spent Saturday morning writing the Creative Commons License Application for Facebook. The premise is simple: installing the application allows Facebook users choose and place a CC license badge on their profile page indicating which license they want their content to be available under. Alongside the badge is text that explains what content [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.facebook.com/editapps.php#/apps/application.php?id=78186376044"><img class="alignleft size-full wp-image-14564" title="Creative Commons License on Facebook" src="http://creativecommons.org/wp-content/uploads/2009/05/picture-13.png" alt="Creative Commons License on Facebook" width="380" height="262" /></a>Last weekend I spent Saturday morning writing the <a href="http://www.facebook.com/editapps.php#/apps/application.php?id=78186376044">Creative Commons License Application</a> for Facebook. The premise is simple: <a href="http://apps.facebook.com/creativecommons/">installing the application</a> allows Facebook users choose and place a CC license badge on their profile page indicating which license they want their content to be available under. Alongside the badge is text that explains what content (Photos, Videos and Status &#038; Profile text are currently available as options) is licensed. </p>
<p>This surrounding text also contains <a href="http://wiki.creativecommons.org/RDFa">RDFa</a>, though this is of limited utility to <a href="http://developer.yahoo.net/blog/archives/2008/09/searchmonkey_support_for_rdfa_enabled.html">search</a> <a href="http://rdfa.info/2009/05/12/google-announces-support-for-rdfa/">engines</a> since Facebook profiles are not yet publicly indexed. </p>
<p>Users also have the option to allow the application to update their status so that news of their license choice will appear in their friends&#8217; feed. Selecting this option will help grow our application&#8217;s audience exponentially, so we would encourage you to choose it.</p>
<p>There are some limitations to this application and you should consider it in beta, so apologies in advance if things break or don&#8217;t work properly. Perhaps the largest limitation is that works can only be licensed on a per-profile basis. This means that you must make the decision to license all of your work of a given media type (e.g., all of your photos) under a particular CC license or none at all. Unless Facebook integrates CC license choices into their Photo application, licensing works on a per-photo basis (as users have the freedom to do on sites like Flickr and Wikimedia Commons) is not possible. Thus, this implementation of a CC licenses on Facebook is a stop-gap solution to true integration into the service. If you&#8217;ve got other ideas or find other bugs for our application, <a href="http://wiki.creativecommons.org/Facebook_Application">please head over to our wiki and post them</a>. </p>
<p>Otherwise, <a href="http://apps.facebook.com/creativecommons/">go now and install the Creative Commons License Application</a> and let your friends know that you&#8217;ve chosen a CC license for your content on Facebook!</p>
<p>Thanks to everyone who helped me conceptualize and test this application, and especially to the &#8220;<a href="http://www.facebook.com/group.php?gid=55178542061">Creative Commons on Facebook</a>&#8221; group of 5,000+ users who kept encouraging us to move forward.</p>
]]></content:encoded>
			<wfw:commentRss>http://creativecommons.org/weblog/entry/14563/feed</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>

