<?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: Remash! &#8211; Blueprints for RESTful Situational Web Applications</title>
	<atom:link href="http://www.webofthings.com/2009/04/20/remash-blueprints-for-restful/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webofthings.com/2009/04/20/remash-blueprints-for-restful/</link>
	<description>Architecting the Web of Things, for techies and thinkers!</description>
	<lastBuildDate>Fri, 12 Feb 2010 16:30:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: R.Seiji &#187; links for 2009-04-22</title>
		<link>http://www.webofthings.com/2009/04/20/remash-blueprints-for-restful/comment-page-1/#comment-834</link>
		<dc:creator>R.Seiji &#187; links for 2009-04-22</dc:creator>
		<pubDate>Wed, 22 Apr 2009 21:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.webofthings.com/?p=292#comment-834</guid>
		<description>[...] Remash! - Blueprints for RESTful Situational Web Applications &#124; Web of Things Steffen Haak is providing us with some blueprints for RESTful apps. He starts with a number of principles: 1) Resource oriented architectures -&gt; services should expose data instead of functionality 2) Lightweight composition and flexible binding -&gt; services should be re-composables 3) Mass collaboration, customization and perpetual beta -&gt; ability to share the compositions. (tags: hybrid mashup rest) [...]</description>
		<content:encoded><![CDATA[<p>[...] Remash! &#8211; Blueprints for RESTful Situational Web Applications | Web of Things Steffen Haak is providing us with some blueprints for RESTful apps. He starts with a number of principles: 1) Resource oriented architectures -&gt; services should expose data instead of functionality 2) Lightweight composition and flexible binding -&gt; services should be re-composables 3) Mass collaboration, customization and perpetual beta -&gt; ability to share the compositions. (tags: hybrid mashup rest) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
