<?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: Scientific communication in the 21st century</title>
	<atom:link href="http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/</link>
	<description></description>
	<lastBuildDate>Mon, 07 May 2012 21:35:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Michael Nielsen</title>
		<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/comment-page-1/#comment-6563</link>
		<dc:creator>Michael Nielsen</dc:creator>
		<pubDate>Fri, 12 Oct 2007 00:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://michaelnielsen.org/blog/?p=275#comment-6563</guid>
		<description>DM: Thanks for the pointer to ikiwiki, looks very interesting!</description>
		<content:encoded><![CDATA[<p>DM: Thanks for the pointer to ikiwiki, looks very interesting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DM</title>
		<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/comment-page-1/#comment-6550</link>
		<dc:creator>DM</dc:creator>
		<pubDate>Wed, 10 Oct 2007 11:41:41 +0000</pubDate>
		<guid isPermaLink="false">http://michaelnielsen.org/blog/?p=275#comment-6550</guid>
		<description>You don&#039;t actually need to mash anything up. There is already wiki software that uses version control software (including subversion, mercurial, git, and others) for storage/version control. &lt;a href=&quot;http://ikiwiki.info/&quot; rel=&quot;nofollow&quot;&gt;Ikiwiki&lt;/a&gt; is that wiki software. There are things there that could be improved, but it seems to have a healthy community around it.</description>
		<content:encoded><![CDATA[<p>You don&#8217;t actually need to mash anything up. There is already wiki software that uses version control software (including subversion, mercurial, git, and others) for storage/version control. <a href="http://ikiwiki.info/" rel="nofollow">Ikiwiki</a> is that wiki software. There are things there that could be improved, but it seems to have a healthy community around it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Nielsen</title>
		<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/comment-page-1/#comment-6494</link>
		<dc:creator>Michael Nielsen</dc:creator>
		<pubDate>Fri, 05 Oct 2007 12:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://michaelnielsen.org/blog/?p=275#comment-6494</guid>
		<description>&lt;p&gt;Let me just throw out a couple of comments:&lt;/p&gt;
&lt;p&gt;(1) Peter identifies Wikipedia as a good example of new models for publication.  Open source software, considered as a publication / collaboration process, also suggests some really interesting new ideas.  A recent development is distributed version control systems such as git and Mercurial (Linux is now using git, which was developed by Linus Torvalds) which are potentially far more useful for large-scale collaboration than old-fashioned version control systems like those used in Wikipedia.  &lt;/p&gt;
&lt;p&gt;It&#039;d be &lt;em&gt;very&lt;/em&gt; interesting to mashup a wiki like MediaWiki (or something more lightweight) with something like git.  Probably only take a few days to get something workable if you picked the right projects to mash. &lt;/p&gt;
&lt;p&gt;(2) &lt;a href=&quot;http://scholarpedia.org&quot; rel=&quot;nofollow&quot;&gt;Scholarpedia&lt;/a&gt; is an interesting example of a new tool that is getting input from some very eminent scientists, along the lines advocated by Peter in his last paragraph.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Let me just throw out a couple of comments:</p>
<p>(1) Peter identifies Wikipedia as a good example of new models for publication.  Open source software, considered as a publication / collaboration process, also suggests some really interesting new ideas.  A recent development is distributed version control systems such as git and Mercurial (Linux is now using git, which was developed by Linus Torvalds) which are potentially far more useful for large-scale collaboration than old-fashioned version control systems like those used in Wikipedia.  </p>
<p>It&#8217;d be &lt;em&gt;very&lt;/em&gt; interesting to mashup a wiki like MediaWiki (or something more lightweight) with something like git.  Probably only take a few days to get something workable if you picked the right projects to mash. </p>
<p>(2) &lt;a href=&#8221;http://scholarpedia.org&#8221; rel=&#8221;nofollow&#8221;&gt;Scholarpedia&lt;/a&gt; is an interesting example of a new tool that is getting input from some very eminent scientists, along the lines advocated by Peter in his last paragraph.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Rohde</title>
		<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/comment-page-1/#comment-6488</link>
		<dc:creator>Peter Rohde</dc:creator>
		<pubDate>Thu, 04 Oct 2007 10:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://michaelnielsen.org/blog/?p=275#comment-6488</guid>
		<description>Hi James,

Presently you are right, it&#039;s difficult to write papers in this way. I think the main reason for this is that the required software tools are not in place. Before the Wikipedia was in place one could have made the same criticism of highly modularized, hyperlinked articles. But once the Wiki software was in place and tailored for this particular application it became quite straightforward to do this. I think the same ought to apply to the suggestion I made.</description>
		<content:encoded><![CDATA[<p>Hi James,</p>
<p>Presently you are right, it&#8217;s difficult to write papers in this way. I think the main reason for this is that the required software tools are not in place. Before the Wikipedia was in place one could have made the same criticism of highly modularized, hyperlinked articles. But once the Wiki software was in place and tailored for this particular application it became quite straightforward to do this. I think the same ought to apply to the suggestion I made.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/comment-page-1/#comment-6487</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 03 Oct 2007 21:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://michaelnielsen.org/blog/?p=275#comment-6487</guid>
		<description>Peter, I think you underestimate the amount of work required to put papers into this form.  Wikipedia works because there are a lot of people who spend a lot of time on it.  And even still much of Wikipedia is really awful.  

Why don&#039;t you try writing a paper in this way?  (Or rewriting a paper you already have?)  Everything you need is out there.  And it would make your suggestions much more concrete.</description>
		<content:encoded><![CDATA[<p>Peter, I think you underestimate the amount of work required to put papers into this form.  Wikipedia works because there are a lot of people who spend a lot of time on it.  And even still much of Wikipedia is really awful.  </p>
<p>Why don&#8217;t you try writing a paper in this way?  (Or rewriting a paper you already have?)  Everything you need is out there.  And it would make your suggestions much more concrete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis</title>
		<link>http://michaelnielsen.org/blog/scientific-communication-in-the-21st-century/comment-page-1/#comment-6482</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Wed, 03 Oct 2007 07:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://michaelnielsen.org/blog/?p=275#comment-6482</guid>
		<description>Great article. All the advantages you cite for e-publishing over paper are very true, but paper has three key advantages (for the moment):

1) Contrast. Reading papers on, well, paper, is easy on the eyes.

2) Annotate-ability. Writing notes wherever I want on paper is easy. Doing the same on PDFs is hard, especially if I want to write equations.

3) Works on the plane. Paper doesn&#039;t require an internet connection to be readable.

1 and 2 will eventually change as tablet PC technology improves, but for now, they&#039;re big stumbling blocks. The best compromise I can think of is to allow people to &quot;customize&quot; their version of the paper by collapsing explanations they don&#039;t need and expanding details they want to read. Once the paper is electronically customized, it can be printed if further reading is desired. Of course, I would only need this for the (small) subset of papers that I actually read in detail, but those papers are the ones I care about most. I have one or two papers I&#039;ve actually had to re-print because the original copies got so worn and covered with scribbled notes that they became hard to read.</description>
		<content:encoded><![CDATA[<p>Great article. All the advantages you cite for e-publishing over paper are very true, but paper has three key advantages (for the moment):</p>
<p>1) Contrast. Reading papers on, well, paper, is easy on the eyes.</p>
<p>2) Annotate-ability. Writing notes wherever I want on paper is easy. Doing the same on PDFs is hard, especially if I want to write equations.</p>
<p>3) Works on the plane. Paper doesn&#8217;t require an internet connection to be readable.</p>
<p>1 and 2 will eventually change as tablet PC technology improves, but for now, they&#8217;re big stumbling blocks. The best compromise I can think of is to allow people to &#8220;customize&#8221; their version of the paper by collapsing explanations they don&#8217;t need and expanding details they want to read. Once the paper is electronically customized, it can be printed if further reading is desired. Of course, I would only need this for the (small) subset of papers that I actually read in detail, but those papers are the ones I care about most. I have one or two papers I&#8217;ve actually had to re-print because the original copies got so worn and covered with scribbled notes that they became hard to read.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

