<?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: Google converters: garden path or path to glory?</title>
	<atom:link href="http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/feed/" rel="self" type="application/rss+xml" />
	<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 16 Mar 2010 13:31:15 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Rickmann</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1285</link>
		<dc:creator>Andrew Rickmann</dc:creator>
		<pubDate>Thu, 15 Jan 2009 13:26:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1285</guid>
		<description>I must admit that I am more include to start with a blank sheet of xml but I will investigate Atom and AtomPub further to see if it is easier to do it that way. What is in my mind is that the extensions will mean it is no longer compatible with existing importers, so I wonder how beneficial it would really be. Plugins would still need to be built.</description>
		<content:encoded><![CDATA[<p>I must admit that I am more include to start with a blank sheet of xml but I will investigate Atom and AtomPub further to see if it is easier to do it that way. What is in my mind is that the extensions will mean it is no longer compatible with existing importers, so I wonder how beneficial it would really be. Plugins would still need to be built.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Rickmann</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1284</link>
		<dc:creator>Andrew Rickmann</dc:creator>
		<pubDate>Thu, 15 Jan 2009 13:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1284</guid>
		<description>While I can see the benefits I am going to avoid feature creep. My key goal is to do something very very simple that just works for most ordinary users. If someone wants to write a forum plugin that pulls the data from the format then that is great, but I won&#039;t be addressing anything specific for forums.</description>
		<content:encoded><![CDATA[<p>While I can see the benefits I am going to avoid feature creep. My key goal is to do something very very simple that just works for most ordinary users. If someone wants to write a forum plugin that pulls the data from the format then that is great, but I won&#39;t be addressing anything specific for forums.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1283</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 15 Jan 2009 11:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1283</guid>
		<description>Great idea. Setting up a system which is compatible with forums as well would be good. So you could convert your blog posts with comments to forum topics with replies and vice versa. In fact forums need a universal system more so than blogs IMO.&lt;br&gt;&lt;br&gt;Could the existing WordPress system be adapted for this? Couldn&#039;t you just make a Habari plugin which does the same thing as the built in WordPress one?</description>
		<content:encoded><![CDATA[<p>Great idea. Setting up a system which is compatible with forums as well would be good. So you could convert your blog posts with comments to forum topics with replies and vice versa. In fact forums need a universal system more so than blogs IMO.</p>
<p>Could the existing WordPress system be adapted for this? Couldn&#39;t you just make a Habari plugin which does the same thing as the built in WordPress one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaeltwofish</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1282</link>
		<dc:creator>michaeltwofish</dc:creator>
		<pubDate>Thu, 15 Jan 2009 10:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1282</guid>
		<description>There may also be problems maintaining timestamps, because an AtomPub server can choose to change or ignore things like the client-supplied time for &#039;updated&#039;.</description>
		<content:encoded><![CDATA[<p>There may also be problems maintaining timestamps, because an AtomPub server can choose to change or ignore things like the client-supplied time for &#39;updated&#39;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaeltwofish</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1281</link>
		<dc:creator>michaeltwofish</dc:creator>
		<pubDate>Thu, 15 Jan 2009 10:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1281</guid>
		<description>No, because Atom, by default, doesn&#039;t encode everything that can be expressed in each blogging platform. Owen makes a good example, Habari&#039;s metadata for posts and comments. But it does encode information about authors and content and categories (which Habari uses as tags) and much more. In theory, you could use an AtomPub client to pull down all your posts from your old blog (export) and simply POST them to your new blog (import). I don&#039;t know if there are clients that support that at the moment, however. (Aside, PUT is for editing, POST is for creating.)</description>
		<content:encoded><![CDATA[<p>No, because Atom, by default, doesn&#39;t encode everything that can be expressed in each blogging platform. Owen makes a good example, Habari&#39;s metadata for posts and comments. But it does encode information about authors and content and categories (which Habari uses as tags) and much more. In theory, you could use an AtomPub client to pull down all your posts from your old blog (export) and simply POST them to your new blog (import). I don&#39;t know if there are clients that support that at the moment, however. (Aside, PUT is for editing, POST is for creating.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Rickmann</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1280</link>
		<dc:creator>Andrew Rickmann</dc:creator>
		<pubDate>Wed, 14 Jan 2009 23:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1280</guid>
		<description>Is there a reason why Atom isn&#039;t already used as a default format? If you can get information from a blog and put that information into another then isn&#039;t the work already done? Isn&#039;t that the universal format?</description>
		<content:encoded><![CDATA[<p>Is there a reason why Atom isn&#39;t already used as a default format? If you can get information from a blog and put that information into another then isn&#39;t the work already done? Isn&#39;t that the universal format?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ringmaster</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1279</link>
		<dc:creator>ringmaster</dc:creator>
		<pubDate>Wed, 14 Jan 2009 20:33:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1279</guid>
		<description>I also don&#039;t understand WXR extending RSS.  Extending Atom makes more sense because it&#039;s transactional -- if you HTTP GET an Atom document, make changes to it and then POST it back to the same URL (with the proper credentials) it should cause the system to update with those changes.  That&#039;s a nice feature.  It uses actual HTTP verbs.  Imagine an export format that also allowed for that, but could be used for author data and other site metadata.  That&#039;s actually one thing that we were thinking of doing with Habari early on; building the admin as an Atom front-end that worked transactionally with any number of compatible back-ends.&lt;br&gt;&lt;br&gt;Also a benefit of using an existing format is that there are a lot of people working on the standard, and extending it is more trivial than building something from scratch.  Take a look at the work that went into the Atom spec to get an idea of what it takes to build something that will work just that well.&lt;br&gt;&lt;br&gt;Simple would be nice, although in that case I&#039;d emphasize the need to have someplace to collaborate on how extensions to that simple baseline work.  You definitely don&#039;t want it to be difficult for developers from any platform to join the effort and exchange ideas.</description>
		<content:encoded><![CDATA[<p>I also don&#39;t understand WXR extending RSS.  Extending Atom makes more sense because it&#39;s transactional &#8212; if you HTTP GET an Atom document, make changes to it and then POST it back to the same URL (with the proper credentials) it should cause the system to update with those changes.  That&#39;s a nice feature.  It uses actual HTTP verbs.  Imagine an export format that also allowed for that, but could be used for author data and other site metadata.  That&#39;s actually one thing that we were thinking of doing with Habari early on; building the admin as an Atom front-end that worked transactionally with any number of compatible back-ends.</p>
<p>Also a benefit of using an existing format is that there are a lot of people working on the standard, and extending it is more trivial than building something from scratch.  Take a look at the work that went into the Atom spec to get an idea of what it takes to build something that will work just that well.</p>
<p>Simple would be nice, although in that case I&#39;d emphasize the need to have someplace to collaborate on how extensions to that simple baseline work.  You definitely don&#39;t want it to be difficult for developers from any platform to join the effort and exchange ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Rickmann</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1278</link>
		<dc:creator>Andrew Rickmann</dc:creator>
		<pubDate>Wed, 14 Jan 2009 13:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1278</guid>
		<description>I will take a look at it. My main requirement is that it just works and is really simple for normal people to understand. I don&#039;t really know anything about AtomPub as I have never had cause to use it.</description>
		<content:encoded><![CDATA[<p>I will take a look at it. My main requirement is that it just works and is really simple for normal people to understand. I don&#39;t really know anything about AtomPub as I have never had cause to use it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Rickmann</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1277</link>
		<dc:creator>Andrew Rickmann</dc:creator>
		<pubDate>Wed, 14 Jan 2009 13:21:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1277</guid>
		<description>Thanks Owen. There is much to think about there. My first thought was that it should just use plain XML. I never really understood why WXR should extend RSS instead of just being an XML file with the necessary data in it.&lt;br&gt;&lt;br&gt;I think it is very possible to make it very complicated and most of all I want to keep it simple and achieve the basics. If it really needs extending beyond that it can be.&lt;br&gt;&lt;br&gt;As for licensing, I plan to just let anyone do whatever they want with it.</description>
		<content:encoded><![CDATA[<p>Thanks Owen. There is much to think about there. My first thought was that it should just use plain XML. I never really understood why WXR should extend RSS instead of just being an XML file with the necessary data in it.</p>
<p>I think it is very possible to make it very complicated and most of all I want to keep it simple and achieve the basics. If it really needs extending beyond that it can be.</p>
<p>As for licensing, I plan to just let anyone do whatever they want with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heiner</title>
		<link>http://wp-fun.co.uk/2009/01/13/google-converters-garden-path-or-path-to-glory/comment-page-1/#comment-1276</link>
		<dc:creator>Heiner</dc:creator>
		<pubDate>Wed, 14 Jan 2009 06:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-fun.co.uk/?p=1090#comment-1276</guid>
		<description>Just a little side note, the garden path evidently &lt;b&gt;is&lt;/b&gt; the path to glory ;-)</description>
		<content:encoded><![CDATA[<p>Just a little side note, the garden path evidently <b>is</b> the path to glory ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
