<?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; jonathan bailey</title>
	<atom:link href="http://creativecommons.org/tag/jonathan-bailey/feed/rss" rel="self" type="application/rss+xml" />
	<link>http://creativecommons.org</link>
	<description>Share, reuse, and remix — legally.</description>
	<lastBuildDate>Fri, 24 May 2013 18:34:42 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>PlagarismToday on Why You Shouldn&#8217;t Write Your Own&#160;License</title>
		<link>http://creativecommons.org/weblog/entry/14822</link>
		<comments>http://creativecommons.org/weblog/entry/14822#comments</comments>
		<pubDate>Thu, 28 May 2009 19:46:36 +0000</pubDate>
		<dc:creator>Fred Benenson</dc:creator>
				<category><![CDATA[Weblog]]></category>
		<category><![CDATA[jonathan bailey]]></category>
		<category><![CDATA[license proliferation]]></category>
		<category><![CDATA[plagiarismtoday]]></category>

		<guid isPermaLink="false">http://creativecommons.org/?p=14822</guid>
		<description><![CDATA[Jonathan Bailey at PlagiarismToday has a great post dissecting the various issues raised by the bizarre &#8220;WE ARE COPYRIGHTED BLOGS&#8221; license he recently came across. Jonathan correctly recommends that you leave it to the professionals (Creative Commons is a good example :) to draft your copyright licenses: This license displays some of the many hazards [...]]]></description>
				<content:encoded><![CDATA[<p>Jonathan Bailey at <a href="http://plagiarismtoday.com">PlagiarismToday</a> has <a href="http://www.plagiarismtoday.com/2009/05/28/why-to-not-write-your-own-license/">a great post dissecting the various issues</a> raised by the bizarre &#8220;<a href="http://copyrightedblog.blogspot.com/">WE ARE COPYRIGHTED BLOGS</a>&#8221; license he recently came across. Jonathan <a href="http://www.plagiarismtoday.com/2009/05/28/why-to-not-write-your-own-license/">correctly recommends that you leave it to the professionals (Creative Commons is a good example :) to draft your copyright licenses</a>:</p>
<blockquote><p>This license displays some of the many hazards that people face when they try to craft their own copyright licenses. This is why, whenever possible, you should either use an “All Rights Reserved” license and grant permissions on a case-by-case basis, use a Creative Commons or other license that has been vetted and written by professionals or [an]other license that has been vetted and written by professionals.</p></blockquote>
<p>And remember kids, <a href="http://en.wikipedia.org/wiki/License_proliferation">just say NO to license proliferation</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://creativecommons.org/weblog/entry/14822/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
