<?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/"
		>
<channel>
	<title>Comments on: The economics of open access, part two</title>
	<atom:link href="http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/</link>
	<description></description>
	<lastBuildDate>Sun, 03 Jan 2010 10:48:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Socialism in science, or why Open Access may ultimately fail &#171; Molecular Philosophy</title>
		<link>http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/comment-page-1/#comment-16863</link>
		<dc:creator>Socialism in science, or why Open Access may ultimately fail &#171; Molecular Philosophy</dc:creator>
		<pubDate>Fri, 27 Feb 2009 07:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/#comment-16863</guid>
		<description>[...] on Bench Marks blog [...]</description>
		<content:encoded><![CDATA[<p>[...] on Bench Marks blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Crotty</title>
		<link>http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/comment-page-1/#comment-16429</link>
		<dc:creator>David Crotty</dc:creator>
		<pubDate>Fri, 11 Jul 2008 14:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/#comment-16429</guid>
		<description>There&#039;s a good, level-headed article on the subject (with an equally non-inflammatory discussion going on) over at one of the Nature Blogs:
http://network.nature.com/blogs/user/wilbanks/2008/07/07/on-the-plos-nature-business-model-story</description>
		<content:encoded><![CDATA[<p>There&#8217;s a good, level-headed article on the subject (with an equally non-inflammatory discussion going on) over at one of the Nature Blogs:<br />
<a href="http://network.nature.com/blogs/user/wilbanks/2008/07/07/on-the-plos-nature-business-model-story" rel="nofollow">http://network.nature.com/blogs/user/wilbanks/2008/07/07/on-the-plos-nature-business-model-story</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Gayle</title>
		<link>http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/comment-page-1/#comment-16425</link>
		<dc:creator>Richard Gayle</dc:creator>
		<pubDate>Wed, 09 Jul 2008 19:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.cshblogs.org/cshprotocols/2008/07/08/the-economics-of-open-access-part-two/#comment-16425</guid>
		<description>David,

One of the interesting aspects of the Nature kerfuffle has more to do with people&#039;s perceptions than anything else. Nature seemed to be indicating that PLoS was a failure because it was not making money and was changing its business model from what it said it was going to do.

Thus Open access proponents hit the roof because as a non-profit, PLoS does not need to make money and besides, changing is a feature, not a bug.

In my view, both will be successful, just for slightly different markets (and of course, my perception is the one that counts;-) There is a market niche for a  highly selective, reputation enhancing journal like Nature, as well as one that is not as selective but which does publish high impact articles, such as PLoS.

Nature has examined more innovative approaches to enhance their business model (blogs, Connectea, etc.) than any other traditional publisher, as PLoS has done for the newer publishers. They both are trying to find creative solutions to changing market conditions.

So it is a little painful to see the acrimony, since they both have very valuable niches to fill. Heck, Nature is at least still affordable for the individual in many cases and with its favorable copyright and open access after 6 months, it is by far one of the most liberal of the for-profit organizations.

The publisher whose business model may well be in real danger is Elsevier, who does not really have any of the niche benefits Nature or PLoS has.</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>One of the interesting aspects of the Nature kerfuffle has more to do with people&#8217;s perceptions than anything else. Nature seemed to be indicating that PLoS was a failure because it was not making money and was changing its business model from what it said it was going to do.</p>
<p>Thus Open access proponents hit the roof because as a non-profit, PLoS does not need to make money and besides, changing is a feature, not a bug.</p>
<p>In my view, both will be successful, just for slightly different markets (and of course, my perception is the one that counts;-) There is a market niche for a  highly selective, reputation enhancing journal like Nature, as well as one that is not as selective but which does publish high impact articles, such as PLoS.</p>
<p>Nature has examined more innovative approaches to enhance their business model (blogs, Connectea, etc.) than any other traditional publisher, as PLoS has done for the newer publishers. They both are trying to find creative solutions to changing market conditions.</p>
<p>So it is a little painful to see the acrimony, since they both have very valuable niches to fill. Heck, Nature is at least still affordable for the individual in many cases and with its favorable copyright and open access after 6 months, it is by far one of the most liberal of the for-profit organizations.</p>
<p>The publisher whose business model may well be in real danger is Elsevier, who does not really have any of the niche benefits Nature or PLoS has.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
