<?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: REST design question #3: meaning of a link</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/</link>
	<description>XML and the Web.</description>
	<pubDate>Thu, 20 Nov 2008 21:33:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Bo</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/#comment-145</link>
		<dc:creator>Bo</dc:creator>
		<pubDate>Tue, 22 Feb 2005 23:25:50 +0000</pubDate>
		<guid isPermaLink="false">/?p=22#comment-145</guid>
		<description>Don't really see what you're getting at here though I'd be happy to continue discussing RESTful architectures with you.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t really see what you&#8217;re getting at here though I&#8217;d be happy to continue discussing RESTful architectures with you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AsynchronousBlog</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/#comment-104</link>
		<dc:creator>AsynchronousBlog</dc:creator>
		<pubDate>Sat, 19 Feb 2005 23:24:15 +0000</pubDate>
		<guid isPermaLink="false">/?p=22#comment-104</guid>
		<description>&lt;strong&gt;REST Design questions 2 and 3&lt;/strong&gt;
Dave Megginson continues with his REST design questions. Herein, I respond: Question #2 ... Yup, I've used query-paramaters in the way you describe to paramaterize a large resource space. I don't consider it particular inelegant or ugly, but maybe th...</description>
		<content:encoded><![CDATA[<p><strong>REST Design questions 2 and 3</strong><br />
Dave Megginson continues with his REST design questions. Herein, I respond: Question #2 &#8230; Yup, I&#8217;ve used query-paramaters in the way you describe to paramaterize a large resource space. I don&#8217;t consider it particular inelegant or ugly, but maybe th&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quoderat &#187; REST design question #4: how much normalization?</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/#comment-147</link>
		<dc:creator>Quoderat &#187; REST design question #4: how much normalization?</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=22#comment-147</guid>
		<description>[...] find the name of the director or production company, but it still knows where to look for &lt;a href="http://www.megginson.com/blogs/quoderat/archives/2005/02/18/rest-design-question-meaning-of-a-link/"&gt;more complete information&lt;/a&gt;.  It can also use t [...]</description>
		<content:encoded><![CDATA[<p>[...] find the name of the director or production company, but it still knows where to look for <a href="http://www.megginson.com/blogs/quoderat/archives/2005/02/18/rest-design-question-meaning-of-a-link/">more complete information</a>.  It can also use t [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quoderat &#187; REST design question #5: the &#8220;C&#8221; word (content)</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/#comment-153</link>
		<dc:creator>Quoderat &#187; REST design question #5: the &#8220;C&#8221; word (content)</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=22#comment-153</guid>
		<description>[...] nd the edge of the content problem dipping in its toes with issues like identification and &lt;a href="http://www.megginson.com/blogs/quoderat/archives/2005/02/18/rest-design-question-meaning-of-a-link/"&gt;linking&lt;/a&gt;, but now that the design questions ar [...]</description>
		<content:encoded><![CDATA[<p>[...] nd the edge of the content problem dipping in its toes with issues like identification and <a href="http://www.megginson.com/blogs/quoderat/archives/2005/02/18/rest-design-question-meaning-of-a-link/">linking</a>, but now that the design questions ar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quoderat &#187; REST design question #5: the &#8220;C&#8221; word (content)</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/02/18/rest-design-question-meaning-of-a-link/#comment-154</link>
		<dc:creator>Quoderat &#187; REST design question #5: the &#8220;C&#8221; word (content)</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">/?p=22#comment-154</guid>
		<description>[...] nd the edge of the content problem dipping in its toes with issues like identification and &lt;a href="http://www.megginson.com/blogs/quoderat/archives/2005/02/18/rest-design-question-meaning-of-a-link/"&gt;linking&lt;/a&gt;, but now that the design questions ar [...]</description>
		<content:encoded><![CDATA[<p>[...] nd the edge of the content problem dipping in its toes with issues like identification and <a href="http://www.megginson.com/blogs/quoderat/archives/2005/02/18/rest-design-question-meaning-of-a-link/">linking</a>, but now that the design questions ar [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
