<?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: To Err (Worldwide On the Web) is Human; to Correct, Problematic</title>
	<atom:link href="http://magpub.com/to-err-worldwide-on-the-web-is-human-to-correct-problematic/feed/" rel="self" type="application/rss+xml" />
	<link>http://magpub.com/to-err-worldwide-on-the-web-is-human-to-correct-problematic/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=to-err-worldwide-on-the-web-is-human-to-correct-problematic</link>
	<description>For the Knowledgeable Reader</description>
	<lastBuildDate>Thu, 03 May 2012 04:15:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Kristen King</title>
		<link>http://magpub.com/to-err-worldwide-on-the-web-is-human-to-correct-problematic/comment-page-1/#comment-68</link>
		<dc:creator>Kristen King</dc:creator>
		<pubDate>Mon, 19 May 2008 13:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://theeditorialadvantage.com/?p=217#comment-68</guid>
		<description>I got to deal with this issue firsthand when a reader asked a clarifying question about a blog post I authored, and I realized that the confusion was the result of an error on my part.

Here&#039;s the correction: http://tinyurl.com/42aofh
Here&#039;s how I noted it in the original post: http://tinyurl.com/524hby

Important points
- I described the error and the correct information.
- I linked the correction to the original post.
- I linked the original post to the correction prominently.

I don&#039;t have a formal corrections policy on that site, but this is how I intend to handle all corrections because it covers all bases. I will be creating a corrections policy and including a link to it in the site sidebar.

Regarding other types of errors, like &quot;wtih&quot; instead of &quot;with&quot; or other issues that don&#039;t materially affect the information being provided, well, typos happen, and I think just fixing them without fanfare is fine. Factual errors, though, definitely need acknowledgment, and, in some cases, an apology.

Your mileage may vary.</description>
		<content:encoded><![CDATA[<p>I got to deal with this issue firsthand when a reader asked a clarifying question about a blog post I authored, and I realized that the confusion was the result of an error on my part.</p>
<p>Here&#8217;s the correction: <a href="http://tinyurl.com/42aofh" rel="nofollow">http://tinyurl.com/42aofh</a><br />
Here&#8217;s how I noted it in the original post: <a href="http://tinyurl.com/524hby" rel="nofollow">http://tinyurl.com/524hby</a></p>
<p>Important points<br />
- I described the error and the correct information.<br />
- I linked the correction to the original post.<br />
- I linked the original post to the correction prominently.</p>
<p>I don&#8217;t have a formal corrections policy on that site, but this is how I intend to handle all corrections because it covers all bases. I will be creating a corrections policy and including a link to it in the site sidebar.</p>
<p>Regarding other types of errors, like &#8220;wtih&#8221; instead of &#8220;with&#8221; or other issues that don&#8217;t materially affect the information being provided, well, typos happen, and I think just fixing them without fanfare is fine. Factual errors, though, definitely need acknowledgment, and, in some cases, an apology.</p>
<p>Your mileage may vary.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

