<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Blogging a Book about Bio-Ontologies</title>
	<atom:link href="http://duncan.hull.name/2010/01/21/ontogenesis/feed/" rel="self" type="application/rss+xml" />
	<link>http://duncan.hull.name/2010/01/21/ontogenesis/</link>
	<description>A personal laboratory notebook</description>
	<lastBuildDate>Fri, 27 Jan 2012 13:01:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Phil Lord</title>
		<link>http://duncan.hull.name/2010/01/21/ontogenesis/#comment-3710</link>
		<dc:creator><![CDATA[Phil Lord]]></dc:creator>
		<pubDate>Wed, 27 Jan 2010 12:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://duncan.hull.name/?p=2610#comment-3710</guid>
		<description><![CDATA[Actually, one of the reasons for using a blog rather than a wiki is that the pages don&#039;t change after they have been published and have permalinks. Of course, this isn&#039;t an absolute, as the authors can change things, but essentially, we are working on the basis that once an article has hit the virtual shelves, it will remain essentially unchanged. In time, I expect we will just uncover the version history of the articles. 

For my mind, the state of &quot;finished-ness&quot; of a book is not an advantage. Every book publication process I have ever been involved with &quot;finished&quot; means 2 or 3 years out-of-date. Most of the time, when I have a book chapter finally published, I can barely remember having written it, yet alone what&#039;s in it. Why replicate this? The articles, when published, are peer reviewed and finished. 

I agree with the ISBN or, better, a DOI, though. I don&#039;t think these actually are any better technically, but from a social point of view they add something.]]></description>
		<content:encoded><![CDATA[<p>Actually, one of the reasons for using a blog rather than a wiki is that the pages don&#8217;t change after they have been published and have permalinks. Of course, this isn&#8217;t an absolute, as the authors can change things, but essentially, we are working on the basis that once an article has hit the virtual shelves, it will remain essentially unchanged. In time, I expect we will just uncover the version history of the articles. </p>
<p>For my mind, the state of &#8220;finished-ness&#8221; of a book is not an advantage. Every book publication process I have ever been involved with &#8220;finished&#8221; means 2 or 3 years out-of-date. Most of the time, when I have a book chapter finally published, I can barely remember having written it, yet alone what&#8217;s in it. Why replicate this? The articles, when published, are peer reviewed and finished. </p>
<p>I agree with the ISBN or, better, a DOI, though. I don&#8217;t think these actually are any better technically, but from a social point of view they add something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ontogenesis: rapid reviewing and publishing of articles on semantics and ontologies &#171; the mind wobbles</title>
		<link>http://duncan.hull.name/2010/01/21/ontogenesis/#comment-3704</link>
		<dc:creator><![CDATA[Ontogenesis: rapid reviewing and publishing of articles on semantics and ontologies &#171; the mind wobbles]]></dc:creator>
		<pubDate>Mon, 25 Jan 2010 12:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://duncan.hull.name/?p=2610#comment-3704</guid>
		<description><![CDATA[[...] it a blog, how the blog software is being used isn&#8217;t the way many people use it. And, though Duncan has called it &#8220;blogging a book&#8221;, this isn&#8217;t quite right either: while content, once completed, will not be changed, new [...]]]></description>
		<content:encoded><![CDATA[<p>[...] it a blog, how the blog software is being used isn&#8217;t the way many people use it. And, though Duncan has called it &#8220;blogging a book&#8221;, this isn&#8217;t quite right either: while content, once completed, will not be changed, new [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Gardner</title>
		<link>http://duncan.hull.name/2010/01/21/ontogenesis/#comment-3697</link>
		<dc:creator><![CDATA[Paul Gardner]]></dc:creator>
		<pubDate>Fri, 22 Jan 2010 07:44:58 +0000</pubDate>
		<guid isPermaLink="false">http://duncan.hull.name/?p=2610#comment-3697</guid>
		<description><![CDATA[Wikibooks seems like another good alternative:
http://en.wikibooks.org/wiki/Main_Page]]></description>
		<content:encoded><![CDATA[<p>Wikibooks seems like another good alternative:<br />
<a href="http://en.wikibooks.org/wiki/Main_Page" rel="nofollow">http://en.wikibooks.org/wiki/Main_Page</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KnowledgeBlog: bloging a book about ontologies &#171; Mikeleganaaranguren&#39;s Blog</title>
		<link>http://duncan.hull.name/2010/01/21/ontogenesis/#comment-3695</link>
		<dc:creator><![CDATA[KnowledgeBlog: bloging a book about ontologies &#171; Mikeleganaaranguren&#39;s Blog]]></dc:creator>
		<pubDate>Thu, 21 Jan 2010 15:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://duncan.hull.name/?p=2610#comment-3695</guid>
		<description><![CDATA[[...]   I&#8217;m participating on an experiment about using blogs to create a book about bio-ontologies. Duncan Hull has a more in depths explanation.    Dejar un [...]]]></description>
		<content:encoded><![CDATA[<p>[...]   I&#8217;m participating on an experiment about using blogs to create a book about bio-ontologies. Duncan Hull has a more in depths explanation.    Dejar un [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Clegg</title>
		<link>http://duncan.hull.name/2010/01/21/ontogenesis/#comment-3691</link>
		<dc:creator><![CDATA[Andrew Clegg]]></dc:creator>
		<pubDate>Thu, 21 Jan 2010 11:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://duncan.hull.name/?p=2610#comment-3691</guid>
		<description><![CDATA[PS... Another advantage of books over blogs is permanence. Even if only a handful of copies are printed, if you&#039;ve got an ISBN, and got into the British Library and the Library of Congress, then that&#039;s a fair bit more stability than a collection of potentially transient URLs.

Not that I&#039;m a particular advocate of turning trees into low-density non-searchable storage :-)

Maybe online writing and review + limited print run + open access digital edition = publishing sweet spot.]]></description>
		<content:encoded><![CDATA[<p>PS&#8230; Another advantage of books over blogs is permanence. Even if only a handful of copies are printed, if you&#8217;ve got an ISBN, and got into the British Library and the Library of Congress, then that&#8217;s a fair bit more stability than a collection of potentially transient URLs.</p>
<p>Not that I&#8217;m a particular advocate of turning trees into low-density non-searchable storage <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Maybe online writing and review + limited print run + open access digital edition = publishing sweet spot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Clegg</title>
		<link>http://duncan.hull.name/2010/01/21/ontogenesis/#comment-3690</link>
		<dc:creator><![CDATA[Andrew Clegg]]></dc:creator>
		<pubDate>Thu, 21 Jan 2010 11:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://duncan.hull.name/?p=2610#comment-3690</guid>
		<description><![CDATA[There&#039;s another approach you didn&#039;t list, which is writing a book but also releasing it as an open-access online version. This has the benefit of having a state of &#039;finished-ness&#039; which an evolving resource like a blog might not ever reach, so one can cite a particular section or page [in a particular edition if necessary] and know that it won&#039;t have changed when the time someone chases that link.

See e.g. http://nlp.stanford.edu/IR-book/information-retrieval-book.html which is published by CUP -- a good sign that trad publishers are open to this sort of thing. 

Which approach is better? Well, there&#039;s probably no fixed answer to that. Horses for courses, etc. Your approach has the benefit of transparent peer review, and people getting to see and comment on the material as it&#039;s written.

Question: is it getting published as a proper book when it&#039;s complete? Because that would give the best of both worlds.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s another approach you didn&#8217;t list, which is writing a book but also releasing it as an open-access online version. This has the benefit of having a state of &#8216;finished-ness&#8217; which an evolving resource like a blog might not ever reach, so one can cite a particular section or page [in a particular edition if necessary] and know that it won&#8217;t have changed when the time someone chases that link.</p>
<p>See e.g. <a href="http://nlp.stanford.edu/IR-book/information-retrieval-book.html" rel="nofollow">http://nlp.stanford.edu/IR-book/information-retrieval-book.html</a> which is published by CUP &#8212; a good sign that trad publishers are open to this sort of thing. </p>
<p>Which approach is better? Well, there&#8217;s probably no fixed answer to that. Horses for courses, etc. Your approach has the benefit of transparent peer review, and people getting to see and comment on the material as it&#8217;s written.</p>
<p>Question: is it getting published as a proper book when it&#8217;s complete? Because that would give the best of both worlds.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

