<?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:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: When editors bury that which cannot die</title>
	<atom:link href="http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 04:28:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: OlivesDad</title>
		<link>http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/#comment-7891</link>
		<dc:creator>OlivesDad</dc:creator>
		<pubDate>Tue, 17 Jul 2012 00:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/jackshafer/?p=1046#comment-7891</guid>
		<description>Jack...Jack...Jack

Is your personal editorial tour de force (the &quot;MonkeyFish&quot; saga) still on line?  

Answer:  NO!  Nor should it be.

You are either a hypocrite or an amnesiac.  (I forget which!)

Geez...Jack</description>
		<content:encoded><![CDATA[<p>Jack&#8230;Jack&#8230;Jack</p>
<p>Is your personal editorial tour de force (the &#8220;MonkeyFish&#8221; saga) still on line?  </p>
<p>Answer:  NO!  Nor should it be.</p>
<p>You are either a hypocrite or an amnesiac.  (I forget which!)</p>
<p>Geez&#8230;Jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ejsofel</title>
		<link>http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/#comment-7538</link>
		<dc:creator>ejsofel</dc:creator>
		<pubDate>Wed, 11 Jul 2012 21:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/jackshafer/?p=1046#comment-7538</guid>
		<description>A book publisher would not include plagiarized material in a new printing of a book and may well stop an existing printing if the material were believed to be stolen. 

That is, the analogy between print and online publishing isn&#039;t a clean one. Publication is continuous and by leaving the file accessible on the server, the publisher continues to publish--something they would not do in the print world. 

You focus only on the archive. And it&#039;s true that print publisher&#039;s don&#039;t try to expunge previously printed records of their mistakes and misdeeds. But perhaps the Wayback Machine and the various other caches--personal and institutional--are better analogues to print archives than the production servers maintained by the publisher, which, as I say, have the dual role of &quot;printing&quot; the current and archiving the past. 

At any rate, I can&#039;t give you the win on this one. I think if NPR tried to remove the content and pretend it never happened, you&#039;d have a clear case. If they maintain the URL and substitute a summary of the affair, I can&#039;t really blame them. Again, no book publisher could crank out a new printing with a prepended announcement that one of the essays was plagiarized from another author. Nor, I imagine, would the victim of the plagiarism sit still for such. But that appears to be your suggested course of action here.</description>
		<content:encoded><![CDATA[<p>A book publisher would not include plagiarized material in a new printing of a book and may well stop an existing printing if the material were believed to be stolen. </p>
<p>That is, the analogy between print and online publishing isn&#8217;t a clean one. Publication is continuous and by leaving the file accessible on the server, the publisher continues to publish&#8211;something they would not do in the print world. </p>
<p>You focus only on the archive. And it&#8217;s true that print publisher&#8217;s don&#8217;t try to expunge previously printed records of their mistakes and misdeeds. But perhaps the Wayback Machine and the various other caches&#8211;personal and institutional&#8211;are better analogues to print archives than the production servers maintained by the publisher, which, as I say, have the dual role of &#8220;printing&#8221; the current and archiving the past. </p>
<p>At any rate, I can&#8217;t give you the win on this one. I think if NPR tried to remove the content and pretend it never happened, you&#8217;d have a clear case. If they maintain the URL and substitute a summary of the affair, I can&#8217;t really blame them. Again, no book publisher could crank out a new printing with a prepended announcement that one of the essays was plagiarized from another author. Nor, I imagine, would the victim of the plagiarism sit still for such. But that appears to be your suggested course of action here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tmc</title>
		<link>http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/#comment-7514</link>
		<dc:creator>tmc</dc:creator>
		<pubDate>Wed, 11 Jul 2012 19:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/jackshafer/?p=1046#comment-7514</guid>
		<description>Dude, you just don&#039;t like paying heed to any laws do you? It also seems that you often write that others should break laws that help you be a better journalist.  I&#039;m really starting to wonder what groups you are associated with.</description>
		<content:encoded><![CDATA[<p>Dude, you just don&#8217;t like paying heed to any laws do you? It also seems that you often write that others should break laws that help you be a better journalist.  I&#8217;m really starting to wonder what groups you are associated with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MIKEROL</title>
		<link>http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/#comment-7500</link>
		<dc:creator>MIKEROL</dc:creator>
		<pubDate>Wed, 11 Jul 2012 19:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/jackshafer/?p=1046#comment-7500</guid>
		<description>d&#039;accord x m.r</description>
		<content:encoded><![CDATA[<p>d&#8217;accord x m.r</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DCA331</title>
		<link>http://blogs.reuters.com/jackshafer/2012/07/11/when-editors-bury-that-which-cannot-die/#comment-7486</link>
		<dc:creator>DCA331</dc:creator>
		<pubDate>Wed, 11 Jul 2012 18:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reuters.com/jackshafer/?p=1046#comment-7486</guid>
		<description>Jack,

Were I in NPR&#039;s shoes, I would have done the same - had they left the article up, they would have been accused of mining plagiarized material for ad revenue, which would certainly harm their reputation more than pulling down an intern&#039;s partially stolen work.  I think NPR does understand that the mistake isn&#039;t going to go away, given their public apology on the matter - the &quot;Streisand Effect&quot; is well-documented and understood by most major media outlets - so this seems to have been the optimal means of handling the issue from a PR perspective.</description>
		<content:encoded><![CDATA[<p>Jack,</p>
<p>Were I in NPR&#8217;s shoes, I would have done the same &#8211; had they left the article up, they would have been accused of mining plagiarized material for ad revenue, which would certainly harm their reputation more than pulling down an intern&#8217;s partially stolen work.  I think NPR does understand that the mistake isn&#8217;t going to go away, given their public apology on the matter &#8211; the &#8220;Streisand Effect&#8221; is well-documented and understood by most major media outlets &#8211; so this seems to have been the optimal means of handling the issue from a PR perspective.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
