<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Science in the Open</title>
	
	<link>http://cameronneylon.net</link>
	<description>The online home of Cameron Neylon</description>
	<lastBuildDate>Tue, 09 Feb 2010 11:54:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ScienceInTheOpen" /><feedburner:info uri="scienceintheopen" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Peer review: What is it good for?</title>
		<link>http://feedproxy.google.com/~r/ScienceInTheOpen/~3/qdN73xzIfxk/</link>
		<comments>http://cameronneylon.net/blog/peer-review-what-is-it-good-for/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 15:03:25 +0000</pubDate>
		<dc:creator>Cameron Neylon</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[peer review]]></category>
		<category><![CDATA[publishing]]></category>

		<guid isPermaLink="false">http://cameronneylon.net/?p=801</guid>
		<description><![CDATA[



Image by Gideon Burton via Flickr



It hasn&#8217;t been a real good week for peer review. In the same week that the Lancet fully retract the original Wakefield MMR article (while keeping the retraction behind a login screen &#8211; way to go there on public understanding of science), the main stream media went to town on the report of 14 stem cell scientists writing an open letter making the claim that peer review in that area was being dominated by a small group of people blocking the publication of innovative work. ...]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img" style="width: 250px;">
<div>
<dl class="wp-caption alignleft">
<dt class="wp-caption-dt"><a href="http://www.flickr.com/photos/33895652@N04/3157622458"><img title="Peer Review Monster" src="http://farm4.static.flickr.com/3112/3157622458_b19d039158_m.jpg" alt="Peer Review Monster" /></a></dt>
<dd class="wp-caption-dd zemanta-img-attribution">Image by <a href="http://www.flickr.com/photos/33895652@N04/3157622458">Gideon Burton</a> via Flickr</dd>
</dl>
</div>
</div>
<p>It hasn&#8217;t been a real good week for peer review. In the same week that <a class="zem_slink" title="The Lancet" rel="homepage" href="http://www.thelancet.com/">the Lancet</a> fully <a href="http://www.thelancet.com/journals/lancet/article/PIIS0140-6736(10)60175-7/fulltext">retract the original Wakefield MMR article</a> (while keeping the retraction behind a login screen &#8211; way to go there on public understanding of science), the <a href="http://news.bbc.co.uk/2/hi/science/nature/8490291.stm">main stream media went to town</a> on the report of<a href="http://eurostemcell.org/commentanalysis/peer-review"> 14 stem cell scientists writing an open letter</a> making the claim that peer review in that area was being dominated by a small group of people blocking the publication of innovative work. I don&#8217;t have the information to actually comment on the substance of either issue but I do want to reflect on what this tells us about the state of peer review.</p>
<p>There remains much reverence of the traditional process of peer review. I may be over interpreting the tenor of <a href="http://www3.interscience.wiley.com/cgi-bin/fulltext/123248917/HTMLSTART">Andrew Morrison&#8217;s editorial</a> in <a class="zem_slink" title="BioEssays" rel="homepage" href="http://eu.wiley.com/WileyCDA/WileyTitle/productCd-BIES.html">BioEssays</a> but it seems to me that he is saying, as many others have over the years &#8220;if we could just have the rigour of traditional peer review with the ease of publication of the web then all our problems would be solved&#8221;.  Scientists worship at the altar of peer review, and I use that metaphor deliberately because it is rarely if ever questioned. Somehow the process of peer review is supposed to sprinkle some sort of magical dust over a text which makes it &#8220;scientific&#8221; or &#8220;worthy&#8221;, yet while we quibble over details of managing the process, or complain that we don&#8217;t get paid for it, rarely is the fundamental basis on which we decide whether science is formally published examined in detail.</p>
<p>There is a good reason for this. THE EMPEROR HAS NO CLOTHES! [sorry, had to get that off my chest]. The evidence that peer review as traditionally practiced is of any value at all is equivocal at best (<a href="http://www.sciencemag.org/cgi/content/abstract/214/4523/881">Science 214, 881; 1981</a>, <a href="http://jis.sagepub.com/cgi/content/abstract/30/1/2">J Clinical Epidemiology 50, 1189; 1998</a>, <a href="http://brain.oxfordjournals.org/cgi/content/full/123/9/1964">Brain 123, 1954; 2000</a>, <a href="http://clrcraldidcotgbr.library.ingentaconnect.com/content/alpsp/lp/2009/00000022/00000002/art00007">Learned Publishing 22, 117; 2009</a>). It&#8217;s not even really negative. That would at least be useful. There are a few studies that suggest peer review is somewhat better than throwing a dice and a bunch that say it is much the same. It is at its best at dealing with narrow technical questions, and at its worst at determining &#8220;importance&#8221; is perhaps the best we might say. Which for anyone who has tried to get published in a top journal or written a grant proposal ought to be deeply troubling. Professional editorial decisions may in fact be more reliable, something that Philip Campbell hints at in his response to questions about the open letter [<a href="http://news.bbc.co.uk/1/hi/sci/tech/8490291.stm">BBC article</a>]:</p>
<blockquote><p>Our editors [...] have always used their own judgement in what we publish. We have not infrequently overruled two or even three sceptical referees and published a paper.</p></blockquote>
<p>But there is perhaps an even more important procedural issue around peer review. Whatever value it might have we largely throw away. Few journals make referee&#8217;s reports available, virtually none track the changes made in response to referee&#8217;s comments enabling a reader to make their own judgement as to whether a paper was improved or made worse. Referees get no public credit for good work, and no public opprobrium for poor or even malicious work. And in most cases a paper rejected from one journal starts completely afresh when submitted to a new journal, the work of the previous referees simply thrown out of the window.</p>
<p>Much of the commentary around the open letter has suggested that the peer review process should be made public. But only for published papers. This goes nowhere near far enough. One of the key points where we lose value is in the transfer from one journal to another. The authors lose out because they&#8217;ve lost their priority date (in the worse case giving the malicious referees the chance to get their paper in first). The referees miss out because their work is rendered worthless. Even the journals are losing an opportunity to demonstrate the high standards they apply in terms of quality and rigor &#8211; and indeed the high expectations they have of their referees.</p>
<p>We never ask what the cost of not publishing a paper is or what the cost of delaying publication could be. <a href="http://www.eric-weinstein.net/">Eric Weinstein</a> provides the most sophisticated view of this that I have come across and I recommend watching <a href="http://pirsa.org/08090036/">his talk at Science in the 21st Century</a> from a few years back. There is a direct cost to rejecting papers, both in the time of referees and the time of editors, as well as the time required for authors to reformat and resubmit. But the bigger problem is the <a class="zem_slink" title="Opportunity cost" rel="wikipedia" href="http://en.wikipedia.org/wiki/Opportunity_cost">opportunity cost</a> &#8211; how much that might have been useful, or even important, is never published? And how much is research held back by delays in publication? How many follow up studies not done, how many leads not followed up, and perhaps most importantly how many projects not refunded, or only funded once the carefully built up expertise in the form of research workers is lost?</p>
<p>Rejecting a paper is like gambling in a game where you can only win. There are no real downside risks for either editors or referees in rejecting papers. There are downsides, as described above, and those carry real costs, but those are never borne by the people who make or contribute to the decision. Its as though it were a futures market where you can only lose if you go long, never if you go short on a stock. In Eric&#8217;s terminology those costs need to be carried, we need to require that referees and editors who &#8220;go short&#8221; on a paper or grant are required to unwind their position if they get it wrong. This is the only way we can price in the downside risks into the process. If we want open peer review, indeed if we want peer review in its traditional form, along with the caveats, costs and problems, then the most important advance would be to have it for unpublished papers.</p>
<p>Journals need to acknowledge the papers they&#8217;ve rejected, along with dates of submission. Ideally all referees reports should be made public, or at least re-usable by the authors. If full publication, of either the submitted form of the paper or the referees report is not acceptable then journals could publish a hash of the submitted document and reports against a local key enabling the authors to demonstrate submission date and the provenance of referees reports as they take them to another journal.</p>
<p>In my view referees need to be held accountable for the quality of their work. If we value this work we should also value and publicly laud good examples. And conversely poor work should be criticised. Any scientist has received reviews that are, if not malicious, then incompetent. And even if we struggle to admit it to others we can usually tell the difference between critical, but constructive (if sometimes brutal), and nonsense. Most of us would even admit that we don&#8217;t always do as good a job as we would like. After all, why should we work hard at it? No credit, no consequences, why would you bother? It might be argued that if you put poor work in you can&#8217;t expect good work back out when your own papers and grants get refereed. This again may be true, but only in the long run, and only if there are active and public pressures to raise quality. None of which I have seen.</p>
<p>Traditional peer review is <a href="http://www.rin.ac.uk/our-work/communicating-and-disseminating-research/activities-costs-and-funding-flows-scholarly-commu">hideously expensive</a>. And currently there is little or no pressure on its contributors or managers to provide good value for money. It is also unsustainable at its current level. My solution to this is to radically cut the number of peer reviewed papers probably by 90-95% leaving the rest to be published as either pure data or pre-prints. But the whole industry is addicted to traditional peer reviewed publications, from the funders who can&#8217;t quite figure out how else to measure research outputs, to the researchers and their institutions who need them for promotion, to the publishers (both OA and toll access) and metrics providers who both feed the addiction and feed off it.</p>
<p>So that leaves those who hold the purse strings, the funders, with a responsibility to pursue a value for money agenda. A good place to start would be a serious critical analysis of the costs and benefits of peer review.</p>
<p><em>Addition after the fact: Pointed out in the comments that there are other posts/papers I should have referred to where people </em>have<em> raised similar ideas and issues. In particular<a href="http://network.nature.com/people/mfenner/blog/2009/07/13/the-value-of-peer-review"> Martin Fenner&#8217;s post at Nature Network</a>. The comments are particularly good as an expert analysis of the usefulness of the kind of &#8220;value for money&#8221; critique I have made. Also a <a href="http://arxiv.org/abs/0911.0344">paper in the Arxiv</a> from Stefano Allesina. Feel free to mention others and I will add them here.</em></p>
<div class="zemanta-pixie"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/b5743b7d-0c7c-4113-a3a2-10a6691b5e3f/"><img class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=b5743b7d-0c7c-4113-a3a2-10a6691b5e3f" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=qdN73xzIfxk:-3fTk95VoXA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=qdN73xzIfxk:-3fTk95VoXA:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?i=qdN73xzIfxk:-3fTk95VoXA:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ScienceInTheOpen/~4/qdN73xzIfxk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://cameronneylon.net/blog/peer-review-what-is-it-good-for/feed/</wfw:commentRss>
		<slash:comments>78</slash:comments>
		<feedburner:origLink>http://cameronneylon.net/blog/peer-review-what-is-it-good-for/</feedburner:origLink></item>
		<item>
		<title>Everything I know about software design I learned from Greg Wilson – and so should your students</title>
		<link>http://feedproxy.google.com/~r/ScienceInTheOpen/~3/kr1WdMoxRSM/</link>
		<comments>http://cameronneylon.net/blog/greg-wilson-software-carpentry/#comments</comments>
		<pubDate>Wed, 27 Jan 2010 19:19:20 +0000</pubDate>
		<dc:creator>Cameron Neylon</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[funding]]></category>
		<category><![CDATA[Revision control]]></category>
		<category><![CDATA[Software design]]></category>
		<category><![CDATA[software-carpentry]]></category>
		<category><![CDATA[training]]></category>

		<guid isPermaLink="false">http://cameronneylon.net/?p=798</guid>
		<description><![CDATA[



Image via Wikipedia



Which is not to say that I am any good at software engineering, good practice, or writing decent code. And you shouldn&#8217;t take Greg to task for some of the dodgy demos I&#8217;ve done over the past few months either. What he does need to take the credit for is enabling me to go from someone who knew nothing at all about software design, the management of software development or testing to being able to talk about these things, ask some of the right questions, and even begin ...]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img" style="width: 230px;">
<div>
<dl class="wp-caption alignleft">
<dt class="wp-caption-dt"><a href="http://commons.wikipedia.org/wiki/Image:Revision_controlled_project_visualization.svg"><img title="Visualization of the &quot;history tree&quot; ..." src="http://upload.wikimedia.org/wikipedia/commons/thumb/f/f4/Revision_controlled_project_visualization.svg/220px-Revision_controlled_project_visualization.svg.png" alt="Visualization of the &quot;history tree&quot; ..." /></a></dt>
<dd class="wp-caption-dd zemanta-img-attribution">Image via <a href="http://commons.wikipedia.org/wiki/Image:Revision_controlled_project_visualization.svg">Wikipedia</a></dd>
</dl>
</div>
</div>
<p>Which is not to say that I am any good at software engineering, good practice, or writing decent code. And you shouldn&#8217;t take <a href="http://pyre.third-bit.com">Greg</a> to task for some of the dodgy demos I&#8217;ve done over the past few months either. What he does need to take the credit for is enabling me to go from someone who knew nothing at all about software design, the management of software development or testing to being able to talk about these things, ask some of the right questions, and even begin to make some of my own judgements about code quality in an amazingly short period of time. From someone who didn&#8217;t know how to execute a python script to someone who feels uncomfortable working with services where I can&#8217;t use a testing framework before deploying software.</p>
<p>This was possible through the online component of the training programme, called<a href="http://software-carpentry.org/"> Software Carpentry</a>, that Greg has been building, delivering and developing over the past decade. This isn&#8217;t a course in software engineering and it isn&#8217;t built for computer science undergraduates. It is a course focussed on taking scientists who have done a little bit of tinkering or scripting and giving them the tools, the literacy, and the knowledge to apply the best of knowledge base of software engineering to building useful high quality code that solves their problems.</p>
<p>Code and computational quality has never been a priority in science and there is a strong argument that we are currently paying, and will continue to pay a heavy price for that unless we sort out the fundamentals of computational literacy and practices as these tools become ubiquitous across the whole spread of scientific disciplines. We teach people how to write up an experiment; but we don&#8217;t teach them how to document code. We teach people the importance of significant figures but many computational scientists have never even heard of version control. And we teach the importance of proper experimental controls but never provide the basic training in testing and validating software.</p>
<p>Greg is seeking support to enable him to update Software Carpentry to provide an online resource for the effective training of scientists in basic computational literacy. It won&#8217;t cost very much money; we&#8217;re talking a few hundred thousand dollars here. And the impact is potentially both important and large. If you care about the training of computational scientists; not computer scientists, but the people who need, or could benefit from, some coding, data managements, or processing in their day to day scientific work, and you have money then I encourage you to contribute. If you know people or organizations with money please encourage them to contribute. Like everything important, especially anything to do with education and preparing for the future, these things are tough to fund.</p>
<p>You can find Greg at his blog: <a href="http://pyre.third-bit.com">http://pyre.third-bit.com</a></p>
<p>His description of what wants to do and what he needs to do it is at: <a href="http://pyre.third-bit.com/blog/archives/3400.html">http://pyre.third-bit.com/blog/archives/3400.html</a></p>
<h6 class="zemanta-related-title">Related articles by Zemanta</h6>
<ul class="zemanta-article-ul">
<li class="zemanta-article-ul-li"><a href="http://blog.jonudell.net/2010/01/12/talking-with-greg-wilson-about-software-carpentry/">Talking with Greg Wilson about software carpentry</a> (jonudell.net)</li>
<li class="zemanta-article-ul-li"><a href="http://mndoci.com/2009/09/10/iterative-software-development/">Iterative software development</a> (mndoci.com)</li>
</ul>
<div class="zemanta-pixie"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/2b8c3a94-0a86-41e3-a64b-b2e71f370742/"><img class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=2b8c3a94-0a86-41e3-a64b-b2e71f370742" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=kr1WdMoxRSM:B5ghqWIrlRs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=kr1WdMoxRSM:B5ghqWIrlRs:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?i=kr1WdMoxRSM:B5ghqWIrlRs:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ScienceInTheOpen/~4/kr1WdMoxRSM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://cameronneylon.net/blog/greg-wilson-software-carpentry/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		<feedburner:origLink>http://cameronneylon.net/blog/greg-wilson-software-carpentry/</feedburner:origLink></item>
		<item>
		<title>Why I am disappointed with Nature Communications</title>
		<link>http://feedproxy.google.com/~r/ScienceInTheOpen/~3/EJnUvjoZoEY/</link>
		<comments>http://cameronneylon.net/blog/why-i-am-disappointed-with-nature-communications/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 19:06:08 +0000</pubDate>
		<dc:creator>Cameron Neylon</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[business model]]></category>
		<category><![CDATA[Creative Commons licenses]]></category>
		<category><![CDATA[nature-communications]]></category>
		<category><![CDATA[npg]]></category>
		<category><![CDATA[open access]]></category>
		<category><![CDATA[publishing]]></category>

		<guid isPermaLink="false">http://cameronneylon.net/?p=772</guid>
		<description><![CDATA[Towards the end of last year I wrote up some initial reactions to the announcement of Nature Communications and the communications team at NPG were kind enough to do a Q&#038;A to look at some of the issues and concerns I raised. Specifically I was concerned about two things. The licence that would be used for the "Open Access" option and the way that journal would be positioned in terms of "quality", particularly as it related to the other NPG journals and the approach to peer review.]]></description>
			<content:encoded><![CDATA[<p>Towards the end of last year I wrote up some <a href="http://cameronneylon.net/blog/nature-communications-a-breakthrough-for-open-access/">initial reactions</a> to the announcement of <a href="http://www.nature.com/ncomms/">Nature Communications</a> and the communications team at <a href="http://nature.com">NPG</a> were kind enough to do a <a href="http://cameronneylon.net/blog/nature-communications-qa/">Q&amp;A</a> to look at some of the issues and concerns I raised. Specifically I was concerned about two things. The licence that would be used for the &#8220;<a class="zem_slink" title="Open access (publishing)" rel="wikipedia" href="http://en.wikipedia.org/wiki/Open_access_%28publishing%29">Open Access</a>&#8221; option and the way that journal would be positioned in terms of &#8220;quality&#8221;, particularly as it related to the other NPG journals and the approach to peer review.</p>
<p>Unfortunately I have to say that I feel these have been fudged, and this is unfortunate because there was a real opportunity here to do something different and quite exciting.  I get the impression that that may even have been the original intention. But from my perspective what has resulted is a poor compromise between my hopes and commercial concerns.</p>
<p>At the centre of my problem is the use of a <a class="zem_slink" title="Creative Commons" rel="homepage" href="http://creativecommons.org/">Creative Commons</a> Attribution <em>Non-commercial</em> licence for the &#8220;Open Access&#8221; option. This doesn&#8217;t qualify under the <a href="http://www.digital-scholarship.org/oab/2statements.htm">BBB declarations</a> on Open Access publication and it doesn&#8217;t qualify for the <a href="http://www.doaj.org/doaj?func=loadTempl&amp;templ=080423">SPARC seal</a> for Open Access. But does this really matter or is it just a side issue for a bunch of hard core zealots? After all if people can see it that&#8217;s a good start isn&#8217;t it? Well yes, it is a good start but non-commercial terms raise serious problems. Putting aside the fact that there is <a href="http://brains.parslow.net/node/1581">an argument that universities are commercial entities</a> and therefore can&#8217;t legitimately use content with non-commercial licences the problem is that NC terms limit the ability of people to create new business models that re-use content and are capable of scaling.</p>
<p>We need these business models because the current model of scholarly publication is simply unaffordable. The argument is often made that if you are unsure whether you are allowed to use content then you can just ask, but this simply doesn&#8217;t scale. And lets be clear about some of the things that NC means you&#8217;re not licensed for: using a paper for commercially funded research even within a university, using the content of paper to support a grant application, using the paper to judge a patent application, using a paper to assess the viability of a business idea&#8230;the list goes on and on. Yes you can ask if you&#8217;re not sure, but asking each and every time <em>does not scale</em>. This is the <em>central</em> point of the <a href="http://www.digital-scholarship.org/oab/2statements.htm">BBB</a> declarations. For scientific communication to scale it must allow the free movement and re-use of content.</p>
<p>Now if this were coming from any old toll access publisher I would just roll my eyes and move on, but NPG sets itself up to be judged by a higher standard. NPG is a privately held company, not beholden to share holders. It is a company that states that it is committed to advancing scientific communication not simply traditional publication. Non-commercial licences do not do this. From the Q&amp;A:</p>
<blockquote><p>Q: Would you accept that a CC-BY-NC(ND) licence does not qualify as Open Access under the terms of the Budapest and Bethesda Declarations because it limits the fields and types of re-use?</p>
<p>A: Yes, we do accept that. But we believe that we are offering authors and their funders the choices they require.Our licensing terms enable authors to comply with, or exceed, the public access mandates of all major funders.</p></blockquote>
<p>NPG is offering the minimum that allows compliance. Not what will most effectively advance scientific communication. Again, I would expect this of a shareholder-controlled profit-driven toll access dead tree publisher but I am holding NPG to a higher standard. Even so there is a legitimate argument to be made that non-commercial licences are needed to make sure that NPG can continue to support these and other activities. This is why I asked in the Q&amp;A whether NPG made significant money off re-licensing of content for commercial purposes. This is a discussion we could have on the substance &#8211; the balance between a commercial entity providing a valuable service and the necessary limitations we might accept as the price of ensuring the continued provision of that service. It is a value for money judgement. But not one we can make without a clear view of the costs and benefits.</p>
<p>So I&#8217;m calling NPG on this one. Make a case for why non-commercial licences are necessary or even beneficial, not why they are acceptable. They damage scientific communication, they create unnecessary confusion about rights, and more importantly they damage the development of new business models to support scientific communication. Explain why it is commercially necessary for the development of these new activities, or roll it back, and take a lead on driving the development of science communication forward. Don&#8217;t take the kind of small steps we expect from other, more traditional, publishers. Above all, lets have that discussion. What is the price we would have to pay to change the license terms?</p>
<p>Because I think it goes deeper. I think that NPG are actually limiting their potential income by focussing on the protection of their income from legacy forms of commercial re-use. They could make more money off this content by growing the pie than by protecting their piece of a specific income stream. It goes to the heart of a misunderstanding about how to effectively exploit content on the web. There is money to be made through re-packaging content for new purposes. The content is obviously key but the real value offering is the Nature brand. Which is much better protected as a <a class="zem_slink" title="Trademark" rel="wikipedia" href="http://en.wikipedia.org/wiki/Trademark">trademark</a> than through licensing. Others could re-package and sell on the content but they can never put the Nature brand on it.</p>
<p>By making the material available for commercial re-use NPG would help to expand a high value market for re-packaged content which they would be poised to dominate. Sure, if you&#8217;re a business you could print off your OA Nature articles and put them on the coffee table, but if you want to present them to investors you want that Nature logo and Nature packaging that you can only get from one place.  And that NPG does damn well. NPG often makes the case that it adds value through selection, presentation, and aggregation. It is the editorial brand that is of value. Let&#8217;s see that demonstrated though monetization of the brand, rather than through unnecessarily restricting the re-use of the content, especially where authors are being charged $5000 to cover the editorial costs.</p>
<div class="zemanta-pixie"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/880fb92c-27f1-48e2-a45e-957632d28eaf/"><img class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=880fb92c-27f1-48e2-a45e-957632d28eaf" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=EJnUvjoZoEY:6hTas745AGg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=EJnUvjoZoEY:6hTas745AGg:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?i=EJnUvjoZoEY:6hTas745AGg:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ScienceInTheOpen/~4/EJnUvjoZoEY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://cameronneylon.net/blog/why-i-am-disappointed-with-nature-communications/feed/</wfw:commentRss>
		<slash:comments>24</slash:comments>
		<feedburner:origLink>http://cameronneylon.net/blog/why-i-am-disappointed-with-nature-communications/</feedburner:origLink></item>
		<item>
		<title>New Year – New me</title>
		<link>http://feedproxy.google.com/~r/ScienceInTheOpen/~3/wQ2fps2GvtU/</link>
		<comments>http://cameronneylon.net/blog/new-year-new-me/#comments</comments>
		<pubDate>Sat, 23 Jan 2010 17:00:23 +0000</pubDate>
		<dc:creator>Cameron Neylon</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Headline]]></category>
		<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[New Year]]></category>
		<category><![CDATA[Website]]></category>

		<guid isPermaLink="false">http://cameronneylon.net/?p=762</guid>
		<description><![CDATA[Over the holidays I set up my own web presence both to be able to put more content and tools up and also to explore how I present myself as a scientist on the web. In a Semantic Web world where I am represented by a URL, what should that URL look like?]]></description>
			<content:encoded><![CDATA[<p><em><a href="http://www.flickr.com/photos/mauricedb/1264936124/"><img class="alignleft" title="Fireworks" src="http://farm2.static.flickr.com/1204/1264936124_6c28d80c36.jpg" alt="Fireworks" width="210" height="194" /></a>Apologies for any wierdness in your feed readers. The following is the reason why as I try to get things working properly again.</em></p>
<p>The past two years on this blog I wrote made some New Year&#8217;s resolutions and last year I assessed my performance against the previous year&#8217;s aims. This year I will admit to simply being a bit depressed about how much I achieved in real terms and how effective I&#8217;ve been at getting ideas out and projects off the ground. This year I want to do more in terms of walking the walk, creating examples, or at least lashups of the things I think are important.</p>
<p>One thing that has been going around in my head for at least 12 months is the question of identity. How I control what I present, who I depend on, and in the world of a semantic web where I am represented by a URL what should actually be there when someone goes to that address. So the positive thing I did over the holiday break, rather than write a new set of resolutions was to start setting up my own presence on the web, to think about what I might want to put there and what it might look like.</p>
<p>This process is not as far along as I would like but its far enough along that this will be the last post at this address. <a title="Open Wet Ware" href="http://openwetware.org">OpenWetWare</a> has been an amazing resource for me over the past several years and we will continue to use the wiki for laboratory information and I hope to work with the team in whatever way I can as the next generation of tools develops. OpenWetWare was also a safe place where I could learn about blogging without worrying about the mechanics, confident in the knowledge that Bill Flanagan was covering the backstops. Bill is the person who has kept things running through the various technical ups and down and I&#8217;d particularly like to thank him for all his help.</p>
<p>However I have now learnt enough to be dangerous and want to try some more things out on my own. More than can be conveniently managed on a website that someone else has to look after. I will write a bit more about the idea and choices I&#8217;ve made in setting up the site soon but for the moment I just want to point you to the new site and offer you some choices about subscribing to different feeds.</p>
<p>If you are on the feedburner feed for the blog you should be automatically transferred over to the feed on the new site. If you&#8217;re reading in a feed reader you can check this by just clicking through to the item on my site. If you end up at a url starting <a href="http://cameronneylon.net/">http://cameronneylon.net/</a> then you are in the right place. If not, just change your reader to point at <a href="http://feeds.feedburner.com/ScienceInTheOpen">http://feeds.feedburner.com/ScienceInTheOpen</a>.</p>
<p>This feed will include posts on things like papers and presentations as well as blog posts so if you are already getting that content in another stream and prefer to just get the blog posts via RSS you should point your reader at <a href="http://feeds.feedburner.com/ScienceInTheOpen_blog">http://feeds.feedburner.com/ScienceInTheOpen_blog</a>.  I can&#8217;t test this until I actually post something so just hold tight if it doesn&#8217;t work and I will try to get it working as soon as I can. The comments feed for all seven of you subscribed to it should keep working. All the posts are mirrored on the new site and will continue to be available at OpenWetWare</p>
<p>Once again I&#8217;d like to thank all the people at OpenWetWare that got me going in the blogging game and hope to see you over at the new site as I figure out what it means to present yourself as a scientist on the web.</p>
<div class="zemanta-pixie"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/e24cf0fc-08a4-45d6-b71f-49378a02cc99/"><img class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=e24cf0fc-08a4-45d6-b71f-49378a02cc99" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=wQ2fps2GvtU:wPPsEpxHw88:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=wQ2fps2GvtU:wPPsEpxHw88:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?i=wQ2fps2GvtU:wPPsEpxHw88:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ScienceInTheOpen/~4/wQ2fps2GvtU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://cameronneylon.net/blog/new-year-new-me/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		<feedburner:origLink>http://cameronneylon.net/blog/new-year-new-me/</feedburner:origLink></item>
		<item>
		<title>Google Wave: Ripple or Tsunami?</title>
		<link>http://feedproxy.google.com/~r/ScienceInTheOpen/~3/w6ReEbZNIHI/</link>
		<comments>http://cameronneylon.net/presentations/google-wave-ripple-or-tsunami/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 17:11:48 +0000</pubDate>
		<dc:creator>Cameron Neylon</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Presentations]]></category>
		<category><![CDATA[googlewave]]></category>
		<category><![CDATA[University of Edinburgh]]></category>
		<category><![CDATA[wave-in-research]]></category>

		<guid isPermaLink="false">http://cameronneylon.net/?p=715</guid>
		<description><![CDATA[A talk given at the Edinburgh University IT Futures meeting late in 2009. The talk discusses the strengths and weaknesses of Wave as a tool for research and provides some pointers on how to think about using it in an academic setting. The talk was recorded in a Wave with members of the audience taking notes around images of the slides which I had previously uploaded.]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img" style="margin:1em;display:block">
<div>
<dl class="wp-caption alignright" style="width: 250px; ">
<dt class="wp-caption-dt"><a href="http://www.flickr.com/photos/44124400268@N01/1972425722"><img src="http://farm3.static.flickr.com/2125/1972425722_9e91780558_m.jpg" alt="Big Wave Surfing in Tahiti at Teahupoo" title="Big Wave Surfing in Tahiti at Teahupoo" width="240" height="160"></a></dt>
<dd class="wp-caption-dd zemanta-img-attribution" style="font-size:0.8em">Image by <a href="http://www.flickr.com/photos/44124400268@N01/1972425722">thelastminute</a> via Flickr</dd>
</dl>
</div>
</div>
<p>A talk given at the <a class="zem_slink" href="http://www.ed.ac.uk" title="University of Edinburgh" rel="homepage">Edinburgh University</a> IT Futures meeting late in 2009. The talk discusses the strengths and weaknesses of Wave as a tool for research and provides some pointers on how to think about using it in an academic setting. The talk was recorded in a Wave with members of the audience taking notes around images of the slides which I had previously uploaded.</p>
<p>You will only be able to see the wave if you have a Wave preview account and are logged in. If you don&#8217;t have an account the slides are included below (or will be as soon as I can get slideshare to talk to me).</p>

		<div id="waveframe-1" style="width:;height:;" ></div>
		 <script type="text/javascript">

				add_wave("waveframe-1",{
					bgcolor:"#ffffff",
					color:"#000000",
					font:"",
					font_size:"1em",
					width:"",
					height:"",
					server:"https://wave.google.com/wave/",
					id:"googlewave.com!w+-c2g1ggkA"		});

		</script>
		
<div class="zemanta-pixie" style="margin-top:10px;height:15px"><a class="zemanta-pixie-a" href="http://reblog.zemanta.com/zemified/5e5df369-a36b-48e8-a53d-70f97422dcb8/" title="Reblog this post [with Zemanta]"><img class="zemanta-pixie-img" src="http://img.zemanta.com/reblog_e.png?x-id=5e5df369-a36b-48e8-a53d-70f97422dcb8" alt="Reblog this post [with Zemanta]" style="border:none;float:right"></a><span class="zem-script more-related pretty-attribution"><script type="text/javascript" src="http://static.zemanta.com/readside/loader.js" defer="defer"></script></span></div>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=w6ReEbZNIHI:PGXkwBmCQWM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ScienceInTheOpen?a=w6ReEbZNIHI:PGXkwBmCQWM:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/ScienceInTheOpen?i=w6ReEbZNIHI:PGXkwBmCQWM:D7DqB2pKExk" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/ScienceInTheOpen/~4/w6ReEbZNIHI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://cameronneylon.net/presentations/google-wave-ripple-or-tsunami/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://cameronneylon.net/presentations/google-wave-ripple-or-tsunami/</feedburner:origLink></item>
	</channel>
</rss><!-- Dynamic page generated in 1.930 seconds. --><!-- Cached page generated by WP-Super-Cache on 2010-02-09 11:55:54 -->
