<?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: A Great Video Describing a Fictitious SaaS Platform</title>
	<atom:link href="http://www.saasblogs.com/2008/03/05/a-great-video-describing-a-fictitious-saas-platform/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.saasblogs.com/saas/a-great-video-describing-a-fictitious-saas-platform/</link>
	<description>Understanding the &#34;as a Service&#34; Revolution</description>
	<lastBuildDate>Thu, 09 Feb 2012 19:11:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Prakash</title>
		<link>http://www.saasblogs.com/saas/a-great-video-describing-a-fictitious-saas-platform/#comment-38189</link>
		<dc:creator>Prakash</dc:creator>
		<pubDate>Tue, 11 Mar 2008 16:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.saasblogs.com/2008/03/05/a-great-video-describing-a-fictitious-saas-platform/#comment-38189</guid>
		<description>The ideas in the video are solid and concrete. I guess the idea of using proprietary API&#039;s that the ISV provides in order to lower cost might not be attractive to most CSV&#039;s. Why lock yourself in to an ISV that provides commodity value (billing,metering etc) to your product ? I see a case for a standards body moving and defining a layer of common services that ISV&#039;s can then add value over. This would ensure minimum lock in and competition between ISVs to provide better implementations.</description>
		<content:encoded><![CDATA[<p>The ideas in the video are solid and concrete. I guess the idea of using proprietary API&#8217;s that the ISV provides in order to lower cost might not be attractive to most CSV&#8217;s. Why lock yourself in to an ISV that provides commodity value (billing,metering etc) to your product ? I see a case for a standards body moving and defining a layer of common services that ISV&#8217;s can then add value over. This would ensure minimum lock in and competition between ISVs to provide better implementations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

