<?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"
	>
<channel>
	<title>Comments on: More REST and IDL</title>
	<atom:link href="http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/feed/" rel="self" type="application/rss+xml" />
	<link>http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/</link>
	<description>Ask forgiveness, not permission.</description>
	<pubDate>Fri, 25 Jul 2008 06:15:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: links for 2008-01-23 &#171; Object neo = neo Object</title>
		<link>http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-520</link>
		<dc:creator>links for 2008-01-23 &#171; Object neo = neo Object</dc:creator>
		<pubDate>Wed, 23 Jan 2008 23:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-520</guid>
		<description>[...] More REST and IDL :: Steve Vinoski’s Blog (tags: restful) [...]</description>
		<content:encoded><![CDATA[<p>[...] More REST and IDL :: Steve Vinoski’s Blog (tags: restful) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve</title>
		<link>http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-506</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Mon, 21 Jan 2008 23:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-506</guid>
		<description>Bill: to me it looks like Joe's document is using URI templates to instruct the client how to locate resources. The fact that the URI template in the example contains a query string is immaterial, since the same approach would work for URIs that don't have query strings.</description>
		<content:encoded><![CDATA[<p>Bill: to me it looks like Joe&#8217;s document is using URI templates to instruct the client how to locate resources. The fact that the URI template in the example contains a query string is immaterial, since the same approach would work for URIs that don&#8217;t have query strings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Burke</title>
		<link>http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-504</link>
		<dc:creator>Bill Burke</dc:creator>
		<pubDate>Mon, 21 Jan 2008 22:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-504</guid>
		<description>Joe's OpenSearch document doesn't define methods or operations, but it sure does define parameters.  Although Joe's thingy doesn't "look" semantically the same as IDL, it is still providing the same semantic information except most of it is implicit.  

BTW, I'm not saying I want RESTful IDL, just that I think in this case, your argument is flawed.  The IDL vs. Human Doc was a better argument.</description>
		<content:encoded><![CDATA[<p>Joe&#8217;s OpenSearch document doesn&#8217;t define methods or operations, but it sure does define parameters.  Although Joe&#8217;s thingy doesn&#8217;t &#8220;look&#8221; semantically the same as IDL, it is still providing the same semantic information except most of it is implicit.  </p>
<p>BTW, I&#8217;m not saying I want RESTful IDL, just that I think in this case, your argument is flawed.  The IDL vs. Human Doc was a better argument.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Burke</title>
		<link>http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-503</link>
		<dc:creator>Bill Burke</dc:creator>
		<pubDate>Mon, 21 Jan 2008 21:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/20/more-rest-and-idl/#comment-503</guid>
		<description>I'd still rather look at schema than WSDL any day of the week.  With WSDL I have to look at both WSDL *and* schema.</description>
		<content:encoded><![CDATA[<p>I&#8217;d still rather look at schema than WSDL any day of the week.  With WSDL I have to look at both WSDL *and* schema.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
