<?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: BPM in the Cloud</title>
	<atom:link href="http://blogs.gartner.com/jim_sinur/2008/12/08/bpm-in-the-cloud/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/jim_sinur/2008/12/08/bpm-in-the-cloud/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Fri, 20 Nov 2009 13:06:56 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan Keldsen</title>
		<link>http://blogs.gartner.com/jim_sinur/2008/12/08/bpm-in-the-cloud/comment-page-1/#comment-821</link>
		<dc:creator>Dan Keldsen</dc:creator>
		<pubDate>Mon, 29 Dec 2008 15:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/jim_sinur/2008/12/08/bpm-in-the-cloud/#comment-821</guid>
		<description>Jim - definitely agree, and had written a bit about this trend in April 2008. Would add Open Source to that mix as well. A prime hurdle to lassoing SaaS-applications together, either with other SaaS offerings or traditionally deployed offerings, is the tendency towards closed and proprietary APIs and connectors. If BPM vendors already have the connectors for both proprietary warhorses AND the newer breed, that would indeed make for a much more sane (and lower cost) way to modernize and take advantage of multi-decade-old premise of BPM and workflow.

Still quite early - but progress is being made at least!

Best,
Dan Keldsen
Co-founder, Information Architected</description>
		<content:encoded><![CDATA[<p>Jim &#8211; definitely agree, and had written a bit about this trend in April 2008. Would add Open Source to that mix as well. A prime hurdle to lassoing SaaS-applications together, either with other SaaS offerings or traditionally deployed offerings, is the tendency towards closed and proprietary APIs and connectors. If BPM vendors already have the connectors for both proprietary warhorses AND the newer breed, that would indeed make for a much more sane (and lower cost) way to modernize and take advantage of multi-decade-old premise of BPM and workflow.</p>
<p>Still quite early &#8211; but progress is being made at least!</p>
<p>Best,<br />
Dan Keldsen<br />
Co-founder, Information Architected</p>
]]></content:encoded>
	</item>
</channel>
</rss>
