<?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: BPMN vs BPEL (again?!)</title>
	<atom:link href="http://www.bp-3.com/blogs/2009/12/bpmn-vs-bpel-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bp-3.com/blogs/2009/12/bpmn-vs-bpel-again/</link>
	<description>A Blog about Enterprise BPM and Business Process Improvement by the folks at BP3</description>
	<lastBuildDate>Fri, 10 Feb 2012 16:13:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tweets that mention Process for the Enterprise » Blog Archive » BPMN vs BPEL (again?!) -- Topsy.com</title>
		<link>http://www.bp-3.com/blogs/2009/12/bpmn-vs-bpel-again/comment-page-1/#comment-1040</link>
		<dc:creator>Tweets that mention Process for the Enterprise » Blog Archive » BPMN vs BPEL (again?!) -- Topsy.com</dc:creator>
		<pubDate>Wed, 09 Dec 2009 22:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1456#comment-1040</guid>
		<description>[...] This post was mentioned on Twitter by Scott Francis and bp3 bpm, Active Endpoints. Active Endpoints said: RT @sfrancisatx the debate that never dies (in #bpm) RT @bp3bpm: Blog Post: BPMN vs BPEL (again?!) http://bit.ly/8KKg8B #soa #bpm #jboss [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Scott Francis and bp3 bpm, Active Endpoints. Active Endpoints said: RT @sfrancisatx the debate that never dies (in #bpm) RT @bp3bpm: Blog Post: BPMN vs BPEL (again?!) <a href="http://bit.ly/8KKg8B" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/8KKg8B?referer=');">http://bit.ly/8KKg8B</a> #soa #bpm #jboss [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

