<?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: WOA = Web-Oriented Architecture</title>
	<atom:link href="http://blog.restlet.com/2006/05/02/woa-web-oriented-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.restlet.com/2006/05/02/woa-web-oriented-architecture/</link>
	<description>Realize your RESTful web APIs !</description>
	<lastBuildDate>Sun, 11 Mar 2012 13:57:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: wen-z</title>
		<link>http://blog.restlet.com/2006/05/02/woa-web-oriented-architecture/#comment-17</link>
		<dc:creator><![CDATA[wen-z]]></dc:creator>
		<pubDate>Thu, 02 Apr 2009 22:16:09 +0000</pubDate>
		<guid isPermaLink="false">https://noelios.wordpress.com/2006/05/02/woa-web-oriented-architecture/#comment-17</guid>
		<description><![CDATA[I think WOA is neither SOA or REST:

- A WOA is not a SOA because it is not description oriented. Without a description language such as WSDL, publishing and subscribing to services becomes problematic.

- A WOA is not REST because it does address “state transfer” part of REST. While I can see WOA works well in many simple cases of web application design, I believe it needs to be complement with, yes, traditional SOA, and semantic web technologies to solve complex problems, for one simple reason: not all service interactions can be modeled as CRUD.]]></description>
		<content:encoded><![CDATA[<p>I think WOA is neither SOA or REST:</p>
<p>- A WOA is not a SOA because it is not description oriented. Without a description language such as WSDL, publishing and subscribing to services becomes problematic.</p>
<p>- A WOA is not REST because it does address “state transfer” part of REST. While I can see WOA works well in many simple cases of web application design, I believe it needs to be complement with, yes, traditional SOA, and semantic web technologies to solve complex problems, for one simple reason: not all service interactions can be modeled as CRUD.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cosa significa web-oriented e web-based? - MasterDrive.it - Information Technology Developers Community</title>
		<link>http://blog.restlet.com/2006/05/02/woa-web-oriented-architecture/#comment-16</link>
		<dc:creator><![CDATA[Cosa significa web-oriented e web-based? - MasterDrive.it - Information Technology Developers Community]]></dc:creator>
		<pubDate>Sun, 23 Mar 2008 16:57:49 +0000</pubDate>
		<guid isPermaLink="false">https://noelios.wordpress.com/2006/05/02/woa-web-oriented-architecture/#comment-16</guid>
		<description><![CDATA[[...] Web 2.0 &#124; ZDNet.com[*] Representational State Transfer - Wikipedia, the free encyclopedia[*] WOA = Web-Oriented Architecture Noelios Consulting [/ul]  E&#039; un discorso molto più ampio del semplice &quot;girare su un web server&quot;... ha a che [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] Web 2.0 | ZDNet.com[*] Representational State Transfer &#8211; Wikipedia, the free encyclopedia[*] WOA = Web-Oriented Architecture Noelios Consulting [/ul]  E&#8217; un discorso molto più ampio del semplice &quot;girare su un web server&quot;&#8230; ha a che [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WSTC - oriented to the Web &#171; The lost outpost</title>
		<link>http://blog.restlet.com/2006/05/02/woa-web-oriented-architecture/#comment-15</link>
		<dc:creator><![CDATA[WSTC - oriented to the Web &#171; The lost outpost]]></dc:creator>
		<pubDate>Fri, 27 Apr 2007 19:51:37 +0000</pubDate>
		<guid isPermaLink="false">https://noelios.wordpress.com/2006/05/02/woa-web-oriented-architecture/#comment-15</guid>
		<description><![CDATA[[...] mentioning is &#8220;WOA&#8221; - Web Oriented Architecture. I did a little research and found that it&#8217;s not a completely new term. It seems to me to be complementary to SOA on the user experience end of [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] mentioning is &#8220;WOA&#8221; &#8211; Web Oriented Architecture. I did a little research and found that it&#8217;s not a completely new term. It seems to me to be complementary to SOA on the user experience end of [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: frevvo blog &#187; How do I use my brand new WOA?</title>
		<link>http://blog.restlet.com/2006/05/02/woa-web-oriented-architecture/#comment-14</link>
		<dc:creator><![CDATA[frevvo blog &#187; How do I use my brand new WOA?]]></dc:creator>
		<pubDate>Tue, 24 Apr 2007 19:02:33 +0000</pubDate>
		<guid isPermaLink="false">https://noelios.wordpress.com/2006/05/02/woa-web-oriented-architecture/#comment-14</guid>
		<description><![CDATA[[...] been thinking a bit more about how frevvo fits in with the corporate IT world. I came across this article on my friend Jérôme Louvel&#8217;s blog and it led me to these posts by Nick Gall and Dion [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] been thinking a bit more about how frevvo fits in with the corporate IT world. I came across this article on my friend Jérôme Louvel&#8217;s blog and it led me to these posts by Nick Gall and Dion [...] </p>
]]></content:encoded>
	</item>
</channel>
</rss>

