<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CodeDread Blog &#187; blog</title>
	<atom:link href="http://www.codedread.com/blog/archives/tag/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codedread.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 02 Jan 2012 15:30:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Comments and the Blog Conversation</title>
		<link>http://www.codedread.com/blog/archives/2008/04/14/comments-and-the-blog-conversation/</link>
		<comments>http://www.codedread.com/blog/archives/2008/04/14/comments-and-the-blog-conversation/#comments</comments>
		<pubDate>Mon, 14 Apr 2008 14:28:07 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Life]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[atom]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[rss]]></category>

		<guid isPermaLink="false">http://blog.codedread.com/archives/2008/04/14/comments-and-the-blog-conversation/</guid>
		<description><![CDATA[There was a bitchmeme going around. Scoble, Winer got into the act&#8230; Scoble gets a part of right &#8211; we don&#8217;t really have that much control, but Winer hits on what I think is important: There are already solutions for this (Atom Threading Extensions, RFC 4685, and RSS Comments feature). We can&#8217;t control what people [...]]]></description>
			<content:encoded><![CDATA[<p><object type="image/svg+xml" width="100" height="100" align="right" hspace="10" data="http://codedread.com/clipart/feed.svgz"><span/></object>There was a <a href="http://www.louisgray.com/live/2008/04/should-fractured-feed-reader-comments.html">bitchmeme</a> going around.  <a href="http://scobleizer.com/2008/04/12/era-of-bloggers-control-is-over/">Scoble</a>, <a href="http://www.scripting.com/stories/2008/04/12/myTwoCentsOnThisWeeksBitch.html">Winer</a> got into the act&#8230;</p>
<p>Scoble gets a part of right &#8211; we don&#8217;t really have that much control, but Winer hits on what I think is important:  There are already solutions for this (<a href='http://www.ietf.org/rfc/rfc4685.txt'>Atom Threading Extensions</a>, RFC 4685, and <a href="http://cyber.law.harvard.edu/rss/rss.html#ltcommentsgtSubelementOfLtitemgt">RSS Comments</a> feature).  We can&#8217;t control what people do with our syndicated content, but we can make it easy for tools to auto-discover the conversation specific to a given blog post.</p>
<p>I&#8217;ve made available a &#8216;whole blog feed&#8217; and a &#8216;per thread&#8217; feed on each post, but I&#8217;m really glad that <a href="http://wordpress.org/">WordPress</a> 2.5 enabled the Atom Threading Extension &#8216;replies&#8217; relation by default.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.codedread.com/blog/archives/2008/04/14/comments-and-the-blog-conversation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

