<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Making Elsevier look good</title>
	<atom:link href="http://library.duke.edu/blogs/scholcomm/2008/07/16/making-elsevier-look-good/feed/" rel="self" type="application/rss+xml" />
	<link>http://library.duke.edu/blogs/scholcomm/2008/07/16/making-elsevier-look-good/</link>
	<description>Duke&#039;s source for advice and information about copyright and publication issues</description>
	<lastBuildDate>Tue, 17 Nov 2009 04:32:11 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stevan Harnad</title>
		<link>http://library.duke.edu/blogs/scholcomm/2008/07/16/making-elsevier-look-good/comment-page-1/#comment-142591</link>
		<dc:creator>Stevan Harnad</dc:creator>
		<pubDate>Mon, 21 Jul 2008 13:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/scholcomm/?p=771#comment-142591</guid>
		<description>See:

&lt;a href=&quot;http://openaccess.eprints.org/index.php?/archives/268-guid.html&quot; title=&quot;Elsevier Still Solidly on the Side of the Angels on Open Access&quot; rel=&quot;nofollow&quot;&gt;Elsevier Still Solidly on the Side of the Angels on Open Access&lt;/a&gt;

and

&lt;a href=&quot;http://openaccess.eprints.org/index.php?/archives/436-guid.html&quot; title=&quot;APA&#039;s Not Responsible; NIH Is&quot; rel=&quot;nofollow&quot;&gt;APA&#039;s Not Responsible; NIH Is&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>See:</p>
<p><a href="http://openaccess.eprints.org/index.php?/archives/268-guid.html" title="Elsevier Still Solidly on the Side of the Angels on Open Access" rel="nofollow">Elsevier Still Solidly on the Side of the Angels on Open Access</a></p>
<p>and</p>
<p><a href="http://openaccess.eprints.org/index.php?/archives/436-guid.html" title="APA's Not Responsible; NIH Is" rel="nofollow">APA&#8217;s Not Responsible; NIH Is</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathleen Wallace</title>
		<link>http://library.duke.edu/blogs/scholcomm/2008/07/16/making-elsevier-look-good/comment-page-1/#comment-141461</link>
		<dc:creator>Kathleen Wallace</dc:creator>
		<pubDate>Fri, 18 Jul 2008 19:32:59 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/scholcomm/?p=771#comment-141461</guid>
		<description>Just seconding Kevin&#039;s last two points -- authors need to take control of their own rights instead of transferring them to the publishers. The last couple of &quot;copyright agreements&quot; that publishers have sent me, I&#039;ve   rewritten (so as to not transfer copyright or exclusive licensing rights) and then signed. It&#039;s been working so far; I know of others who do likewise. SPARC has lots of suggestions for authors if one isn&#039;t sure how to start. The publishers&#039; line that they have to have the copyright and exclusive licensing rights in order to publish and &quot;protect&quot; the work is nonsense; they primarily want  those rights in order to protect their ability to profit from your work.</description>
		<content:encoded><![CDATA[<p>Just seconding Kevin&#8217;s last two points &#8212; authors need to take control of their own rights instead of transferring them to the publishers. The last couple of &#8220;copyright agreements&#8221; that publishers have sent me, I&#8217;ve   rewritten (so as to not transfer copyright or exclusive licensing rights) and then signed. It&#8217;s been working so far; I know of others who do likewise. SPARC has lots of suggestions for authors if one isn&#8217;t sure how to start. The publishers&#8217; line that they have to have the copyright and exclusive licensing rights in order to publish and &#8220;protect&#8221; the work is nonsense; they primarily want  those rights in order to protect their ability to profit from your work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
