<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Sitting on the fence</title>
	<atom:link href="http://log.illsley.org/2006/12/09/sitting-on-the-fence/feed/" rel="self" type="application/rss+xml" />
	<link>http://log.illsley.org/2006/12/09/sitting-on-the-fence/</link>
	<description>There are a limited number of profound statements in this world</description>
	<lastBuildDate>Wed, 18 Jan 2012 13:03:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: davidillsley</title>
		<link>http://log.illsley.org/2006/12/09/sitting-on-the-fence/#comment-646</link>
		<dc:creator><![CDATA[davidillsley]]></dc:creator>
		<pubDate>Mon, 11 Dec 2006 20:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://davidillsley.wordpress.com/2006/12/09/sitting-on-the-fence/#comment-646</guid>
		<description><![CDATA[I totally agree that KISS is good, that HTML is a success because of sloppy parsing, and that RSS is too... and that they&#039;re great.

I think it comes back to using the right tool for the task.

When I think about a bank and credit card company exchanging information I don&#039;t believe that these simpler solutions (e.g. RSS) have proven themselves yet. So how can we deal with that? We pump up the formalism.

Do I think that we can do all of these things more simply? Yes.
Do I think that if we tried today we (and our customers) could be as confident in the solution? No
Do I think we could have a WS-* 2.0 which takes a number of years of real-world experience and simplifies everything? In another couple of years, Yes
Do I think it will happen? Maybe]]></description>
		<content:encoded><![CDATA[<p>I totally agree that KISS is good, that HTML is a success because of sloppy parsing, and that RSS is too&#8230; and that they&#8217;re great.</p>
<p>I think it comes back to using the right tool for the task.</p>
<p>When I think about a bank and credit card company exchanging information I don&#8217;t believe that these simpler solutions (e.g. RSS) have proven themselves yet. So how can we deal with that? We pump up the formalism.</p>
<p>Do I think that we can do all of these things more simply? Yes.<br />
Do I think that if we tried today we (and our customers) could be as confident in the solution? No<br />
Do I think we could have a WS-* 2.0 which takes a number of years of real-world experience and simplifies everything? In another couple of years, Yes<br />
Do I think it will happen? Maybe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Ferrier</title>
		<link>http://log.illsley.org/2006/12/09/sitting-on-the-fence/#comment-630</link>
		<dc:creator><![CDATA[Andrew Ferrier]]></dc:creator>
		<pubDate>Sun, 10 Dec 2006 19:40:13 +0000</pubDate>
		<guid isPermaLink="false">http://davidillsley.wordpress.com/2006/12/09/sitting-on-the-fence/#comment-630</guid>
		<description><![CDATA[I&#039;m not sure I really agree with everything he&#039;s saying, but Adam Bosworth&#039;s untitled talk here: (which is essentially about standards simplicity)

http://www.adambosworth.net/archives/000031.html

has a lot to say for me about the differences between SOAP, REST, etc.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I really agree with everything he&#8217;s saying, but Adam Bosworth&#8217;s untitled talk here: (which is essentially about standards simplicity)</p>
<p><a href="http://www.adambosworth.net/archives/000031.html" rel="nofollow">http://www.adambosworth.net/archives/000031.html</a></p>
<p>has a lot to say for me about the differences between SOAP, REST, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

