<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Web 2.0 and Service Oriented Architecture: Where&#8217;s the Convergence?</title>
	<atom:link href="http://www.fastforwardblog.com/2007/10/30/web-20-and-service-oriented-architecture-wheres-the-convergence/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2007/10/30/web-20-and-service-oriented-architecture-wheres-the-convergence/</link>
	<description></description>
	<lastBuildDate>Sat, 07 Nov 2009 18:38:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Atul Rai</title>
		<link>http://www.fastforwardblog.com/2007/10/30/web-20-and-service-oriented-architecture-wheres-the-convergence/comment-page-1/#comment-66494</link>
		<dc:creator>Atul Rai</dc:creator>
		<pubDate>Thu, 01 Nov 2007 08:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/10/30/web-20-and-service-oriented-architecture-wheres-the-convergence/#comment-66494</guid>
		<description>Hi Joe,

I have been trying to figure this one out ... where exactly is the difference. When we talk SOA, and when we talk Mash-Ups, for example, arent we talking about the same thing at a conceptual level?

Though the quote from Gartner about Web 2.0 happening in the front office, and SOA in the back office rings a bell.

Thanks, Atul.</description>
		<content:encoded><![CDATA[<p>Hi Joe,</p>
<p>I have been trying to figure this one out &#8230; where exactly is the difference. When we talk SOA, and when we talk Mash-Ups, for example, arent we talking about the same thing at a conceptual level?</p>
<p>Though the quote from Gartner about Web 2.0 happening in the front office, and SOA in the back office rings a bell.</p>
<p>Thanks, Atul.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.fastforwardblog.com/2007/10/30/web-20-and-service-oriented-architecture-wheres-the-convergence/comment-page-1/#comment-66209</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Tue, 30 Oct 2007 23:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/2007/10/30/web-20-and-service-oriented-architecture-wheres-the-convergence/#comment-66209</guid>
		<description>One component of most companies that generally fall under the web 2.0 label is an embrace of open connections seen in the near ubiquity of API access in these services.

The first wave of web services fell short of their promise due more to organizational hesitancy to embrace such tools than technological gaps in the tools themselves.

Web 2.0 and SOA convergence is already taking place.  An inherently distributed system of services requires trust of those services and the network to the level of your own business.  Such a network must start with smaller actors and small investments due to the nature of the ecosystem.

Trust is rapidly growing and, as the network expands and the basic rules stabilize, it should be primed for a period of explosive growth.  Medium and larger sized firms will have more reason to enter and enough information and trust to make use of the services.

The fluffy aspects of web 2.0 aren&#039;t a hindrance to SOA adoption.  It&#039;s just a side element of a willingness to experiment that is necessary for this adoption to take place.  What matters is the culture of mashups, API&#039;s, and services that these firms are building and, more importantly, trusting with their own businesses.

Someone has to prove new technologies and new models.  After they&#039;re established the big players generally follow the opportunities (or are left behind).</description>
		<content:encoded><![CDATA[<p>One component of most companies that generally fall under the web 2.0 label is an embrace of open connections seen in the near ubiquity of API access in these services.</p>
<p>The first wave of web services fell short of their promise due more to organizational hesitancy to embrace such tools than technological gaps in the tools themselves.</p>
<p>Web 2.0 and SOA convergence is already taking place.  An inherently distributed system of services requires trust of those services and the network to the level of your own business.  Such a network must start with smaller actors and small investments due to the nature of the ecosystem.</p>
<p>Trust is rapidly growing and, as the network expands and the basic rules stabilize, it should be primed for a period of explosive growth.  Medium and larger sized firms will have more reason to enter and enough information and trust to make use of the services.</p>
<p>The fluffy aspects of web 2.0 aren&#8217;t a hindrance to SOA adoption.  It&#8217;s just a side element of a willingness to experiment that is necessary for this adoption to take place.  What matters is the culture of mashups, API&#8217;s, and services that these firms are building and, more importantly, trusting with their own businesses.</p>
<p>Someone has to prove new technologies and new models.  After they&#8217;re established the big players generally follow the opportunities (or are left behind).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
