<?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; House of Commons</title>
	<atom:link href="http://creativecommons.org/tag/house-of-commons/feed/rss" rel="self" type="application/rss+xml" />
	<link>http://creativecommons.org</link>
	<description>Share, reuse, and remix — legally.</description>
	<lastBuildDate>Wed, 19 Jun 2013 20:53:00 +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>Clarifications about CC BY in the UK Open Access&#160;Policy</title>
		<link>http://creativecommons.org/weblog/entry/36572</link>
		<comments>http://creativecommons.org/weblog/entry/36572#comments</comments>
		<pubDate>Fri, 08 Feb 2013 19:31:29 +0000</pubDate>
		<dc:creator>Timothy Vollmer</dc:creator>
				<category><![CDATA[Weblog]]></category>
		<category><![CDATA[consultation]]></category>
		<category><![CDATA[House of Commons]]></category>
		<category><![CDATA[OA]]></category>
		<category><![CDATA[open access]]></category>
		<category><![CDATA[RCUK]]></category>
		<category><![CDATA[United Kingdom]]></category>

		<guid isPermaLink="false">https://creativecommons.org/?p=36572</guid>
		<description><![CDATA[In the UK, the House of Commons has asked for feedback on their Open Access Policy. One provision of that policy requires that articles funded through the Research Councils UK (RCUK) must be released under a CC BY license. Last year, CC submitted a short comment in support. And just last month, the House of [...]]]></description>
				<content:encoded><![CDATA[<p>In the UK, the House of Commons <a href="http://www.parliament.uk/business/committees/committees-a-z/commons-select/business-innovation-and-skills/news/committee-announces-an-inquiry-into-open-access/">has asked for feedback</a> on their Open Access Policy. One provision of that policy requires that articles funded through the Research Councils UK (RCUK) must be released under a CC BY license. Last year, CC submitted a <a href="http://wiki.creativecommons.org/RCUK_comments">short comment</a> in support. </p>
<p>And just last month, the House of Lords completed a consultation period which has <a href="http://www.parliament.uk/documents/lords-committees/science-technology/Openaccess/OpenAccessevidence.pdf">generated some misinformation</a> about how the CC BY license operates. So, in order to clarify some of these misconceptions, Creative Commons and <a href="http://www.creativecommons.org.uk/">Creative Commons UK</a> submitted a joint response to the Business, Innovation and Skills Committee to set the record straight. </p>
<p>We&#8217;ve <a href="http://wiki.creativecommons.org/BIS_committee_UK_OA_Policy">pulled together some clarifications</a> to some of the uncertainty lobbed at the CC BY license provision in the Open Access Policy. Some of the reasons given that CC BY should not be retained include:</p>
<ul>
<li>it would promote &#8220;misuse of research or would cause authors to &#8220;lose control of their work&#8221;</li>
<li>third party rights negotiations for content that authors wish to include within an openly licensed article would prove too difficult</li>
<li>open licensing provides less protection against plagiarism</li>
<li>CC BY is not widely used in OA publishing</li>
<li>authors should choose licensing conditions, not funders</li>
</ul>
<p>These claims are confusing, misguided, or not backed up by evidence. We offer our responses and support <a href="http://wiki.creativecommons.org/BIS_committee_UK_OA_Policy">here</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://creativecommons.org/weblog/entry/36572/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
