<?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: Breaking the Chain of Inquiry &#8212; When Journals and Journalists Fall Short</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Mon, 13 Feb 2012 05:01:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dr. Gunn</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/#comment-5667</link>
		<dc:creator><![CDATA[Dr. Gunn]]></dc:creator>
		<pubDate>Thu, 19 Nov 2009 22:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6891#comment-5667</guid>
		<description><![CDATA[Kent, you&#039;ve done a fantastic job here, as did Mark. Incidents where the meat of a story wasn&#039;t written in the original article but required followup is truly on of the main advantages a blog has over traditional journalism.  That, and the &quot;go for the jugular&quot; instinct that so many pro reporters seem to have lost.]]></description>
		<content:encoded><![CDATA[<p>Kent, you&#8217;ve done a fantastic job here, as did Mark. Incidents where the meat of a story wasn&#8217;t written in the original article but required followup is truly on of the main advantages a blog has over traditional journalism.  That, and the &#8220;go for the jugular&#8221; instinct that so many pro reporters seem to have lost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier Wenker</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/#comment-5570</link>
		<dc:creator><![CDATA[Olivier Wenker]]></dc:creator>
		<pubDate>Fri, 13 Nov 2009 23:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6891#comment-5570</guid>
		<description><![CDATA[As the publisher responsible for our site I need to clarify that we have over 1,000 editorial board members around the world who volunteer their time to review our thousands of articles. Some boards are better than others and the composition of the boards is in a constant flux since we publish now 77 medical journals. We welcome discussions about our publications but at the same time I would like to defend our volunteers.]]></description>
		<content:encoded><![CDATA[<p>As the publisher responsible for our site I need to clarify that we have over 1,000 editorial board members around the world who volunteer their time to review our thousands of articles. Some boards are better than others and the composition of the boards is in a constant flux since we publish now 77 medical journals. We welcome discussions about our publications but at the same time I would like to defend our volunteers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Hellman</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/#comment-5558</link>
		<dc:creator><![CDATA[Eric Hellman]]></dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6891#comment-5558</guid>
		<description><![CDATA[It&#039;s an interesting example of whether the ethical responsibilities of an open-access publication (such as a blog or the Masters paper) is different from that of a traditional research publication as a result of search engine indexing. I think that providing a direct link to an unethical resource is unethical (don&#039;t want to bunp their Page Rank), but it&#039;s still important to &quot;show your work&quot;. In &lt;a href=&quot;http://go-to-hellman.blogspot.com/2009/11/uniqueness-of-sentences-and-j-k.html&quot; rel=&quot;nofollow&quot;&gt;an article in which I recounted&lt;/a&gt; how I used Google to find pdf&#039;s of &lt;i&gt;Harry Potter and the Deathly Hallows&lt;/i&gt;, I was careful not to link or mention the name of currently infringing sites, but I included links to the Google searches that found them. Did I draw the line in the right place? 

By publishing and linking directly to the IMSO facebook page, aren&#039;t you driving traffic and attention their way? (There&#039;s no such thing as bad publicity.) 

Perhaps Masters (or the publishing Journal) was worried about liability issues if they named names.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s an interesting example of whether the ethical responsibilities of an open-access publication (such as a blog or the Masters paper) is different from that of a traditional research publication as a result of search engine indexing. I think that providing a direct link to an unethical resource is unethical (don&#8217;t want to bunp their Page Rank), but it&#8217;s still important to &#8220;show your work&#8221;. In <a href="http://go-to-hellman.blogspot.com/2009/11/uniqueness-of-sentences-and-j-k.html" rel="nofollow">an article in which I recounted</a> how I used Google to find pdf&#8217;s of <i>Harry Potter and the Deathly Hallows</i>, I was careful not to link or mention the name of currently infringing sites, but I included links to the Google searches that found them. Did I draw the line in the right place? </p>
<p>By publishing and linking directly to the IMSO facebook page, aren&#8217;t you driving traffic and attention their way? (There&#8217;s no such thing as bad publicity.) </p>
<p>Perhaps Masters (or the publishing Journal) was worried about liability issues if they named names.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Anderson</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/#comment-5551</link>
		<dc:creator><![CDATA[Kent Anderson]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:01:50 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6891#comment-5551</guid>
		<description><![CDATA[Thanks Phil (and Mark -- you out-Googled me)!

Knowing what the site was demystifies the entire thing. This demonstrates to me the value of reporting fully.]]></description>
		<content:encoded><![CDATA[<p>Thanks Phil (and Mark &#8212; you out-Googled me)!</p>
<p>Knowing what the site was demystifies the entire thing. This demonstrates to me the value of reporting fully.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Davis</title>
		<link>http://scholarlykitchen.sspnet.org/2009/11/12/breaking-the-chain-of-inquiry/#comment-5550</link>
		<dc:creator><![CDATA[Philip Davis]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 14:46:10 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=6891#comment-5550</guid>
		<description><![CDATA[Yesterday on Liblicense-l, Mark Funk wrote up a little detective work he did attempting to identify &quot;the site.&quot;

http://www.library.yale.edu/~llicense/ListArchives/0911/msg00066.html

But as you rightly argue, we shouldn&#039;t have to speculate on the source nor validity of the data.]]></description>
		<content:encoded><![CDATA[<p>Yesterday on Liblicense-l, Mark Funk wrote up a little detective work he did attempting to identify &#8220;the site.&#8221;</p>
<p><a href="http://www.library.yale.edu/~llicense/ListArchives/0911/msg00066.html" rel="nofollow">http://www.library.yale.edu/~llicense/ListArchives/0911/msg00066.html</a></p>
<p>But as you rightly argue, we shouldn&#8217;t have to speculate on the source nor validity of the data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

