<?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: Use Atom for a Universal Blog Transfer Protocol</title>
	<atom:link href="http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol/feed" rel="self" type="application/rss+xml" />
	<link>http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol</link>
	<description>It's all spinning wheels and self-doubt until the first pot of coffee.</description>
	<lastBuildDate>Fri, 19 Mar 2010 00:06:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<item>
		<title>By: Mark Paschal</title>
		<link>http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol/comment-page-1#comment-1211</link>
		<dc:creator>Mark Paschal</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=524#comment-1211</guid>
		<description>&lt;p&gt;I wrote a script to export an MT weblog to an Atom feed, but the new reality of web hosting servers killing &quot;runaway&quot; processes makes it a terrible pain for large archives. It has to export X entries, then have the browser make a new request to push the next X. The script exports in text chunks, so that&#039;s okay, but I couldn&#039;t figure how to parse an XML document in parts similarly.&lt;/p&gt;

&lt;p&gt;I was planning to use that to transport my weblog from MT 2 to MT 3, but I ended up writing the sqlite schema upgrade code instead.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I wrote a script to export an MT weblog to an Atom feed, but the new reality of web hosting servers killing &#8220;runaway&#8221; processes makes it a terrible pain for large archives. It has to export X entries, then have the browser make a new request to push the next X. The script exports in text chunks, so that&#8217;s okay, but I couldn&#8217;t figure how to parse an XML document in parts similarly.</p>
<p>I was planning to use that to transport my weblog from MT 2 to MT 3, but I ended up writing the sqlite schema upgrade code instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rick</title>
		<link>http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol/comment-page-1#comment-1212</link>
		<dc:creator>rick</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=524#comment-1212</guid>
		<description>&lt;p&gt;Yes!  This is what I&#039;ve been trying to say.  Use RSS as a simple syndication feed, but Atom when you need a rich data model and API.&lt;/p&gt;

&lt;p&gt;Having drop-dead-simple Atom import/export in MT (and all blogging tools) should reduce any fears of lock-in.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Yes!  This is what I&#8217;ve been trying to say.  Use RSS as a simple syndication feed, but Atom when you need a rich data model and API.</p>
<p>Having drop-dead-simple Atom import/export in MT (and all blogging tools) should reduce any fears of lock-in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Bernstein</title>
		<link>http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol/comment-page-1#comment-1213</link>
		<dc:creator>Mark Bernstein</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=524#comment-1213</guid>
		<description>&lt;p&gt;Tinderbox will support the Atom API, once it&#039;s actually an API.  There&#039;s still a lot of uncertainty what the real atom API will look like, either on paper or as implemented in deployed systems.&lt;/p&gt;

&lt;p&gt;For now, Metaweblog and Blogger API should work with most of the tools you want to work with...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Tinderbox will support the Atom API, once it&#8217;s actually an API.  There&#8217;s still a lot of uncertainty what the real atom API will look like, either on paper or as implemented in deployed systems.</p>
<p>For now, Metaweblog and Blogger API should work with most of the tools you want to work with&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: l.m.orchard</title>
		<link>http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol/comment-page-1#comment-1214</link>
		<dc:creator>l.m.orchard</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=524#comment-1214</guid>
		<description>&lt;p&gt;Mark:  Fair enough - I can respect you not wanting to track a moving target of an API.  So far I like the direction it has been taking, though.&lt;/p&gt;

&lt;p&gt;Oh, and thanks again for Tinderbox!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Mark:  Fair enough &#8211; I can respect you not wanting to track a moving target of an API.  So far I like the direction it has been taking, though.</p>
<p>Oh, and thanks again for Tinderbox!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PapaScott</title>
		<link>http://decafbad.com/blog/2004/05/17/use-atom-for-a-universal-blog-transfer-protocol/comment-page-1#comment-1215</link>
		<dc:creator>PapaScott</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=524#comment-1215</guid>
		<description>&lt;p&gt;&lt;strong&gt;0xDECAFBAD: Use Atom for a Universal Blog Transfer Protocol&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;0xDECAFBAD: Use Atom for a Universal Blog Transfer Protocol...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>0xDECAFBAD: Use Atom for a Universal Blog Transfer Protocol</strong></p>
<p>0xDECAFBAD: Use Atom for a Universal Blog Transfer Protocol&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
