 <?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: EPTS looking at ROI</title>
	<atom:link href="http://tibcoblogs.com/cep/index.php/2009/09/30/epts-looking-at-roi/feed/" rel="self" type="application/rss+xml" />
	<link>http://tibcoblogs.com/cep/2009/09/30/epts-looking-at-roi/</link>
	<description>Complex Event Processing (CEP)</description>
	<pubDate>Sat, 11 Feb 2012 17:44:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Vincent</title>
		<link>http://tibcoblogs.com/cep/2009/09/30/epts-looking-at-roi/comment-page-1/#comment-910</link>
		<dc:creator>Paul Vincent</dc:creator>
		<pubDate>Thu, 01 Oct 2009 19:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=834#comment-910</guid>
		<description>Hi Brian - well said. I think you already have the ORF, BRF and RuleML events up on the EPTS website.

Although I wrote the original comment tongue-in-cheek, I was a little disturbed to read http://tech.groups.yahoo.com/group/CEP-Interest/message/2136 and hear about Dieter's resignation as co-chair of the EPTS UC WG. EPTS is a community and yes we should probably be doing more - one for the steering committee to guide on I suspect.

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Brian - well said. I think you already have the ORF, BRF and RuleML events up on the EPTS website.</p>
<p>Although I wrote the original comment tongue-in-cheek, I was a little disturbed to read <a href="http://tech.groups.yahoo.com/group/CEP-Interest/message/2136" rel="nofollow">http://tech.groups.yahoo.com/group/CEP-Interest/message/2136</a> and hear about Dieter&#8217;s resignation as co-chair of the EPTS UC WG. EPTS is a community and yes we should probably be doing more - one for the steering committee to guide on I suspect.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Connell</title>
		<link>http://tibcoblogs.com/cep/2009/09/30/epts-looking-at-roi/comment-page-1/#comment-909</link>
		<dc:creator>Brian Connell</dc:creator>
		<pubDate>Thu, 01 Oct 2009 12:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=834#comment-909</guid>
		<description>I'd also add, that the onus is on everybody to contribute to marketing and promotion of EP and EPTS.  That means we need people to submit information, news, events, papers, etc, too.  So if there's any EP events that TIBCO are hosting, don't forget to get it onto the www.ep-ts.com website also!</description>
		<content:encoded><![CDATA[<p>I&#8217;d also add, that the onus is on everybody to contribute to marketing and promotion of EP and EPTS.  That means we need people to submit information, news, events, papers, etc, too.  So if there&#8217;s any EP events that TIBCO are hosting, don&#8217;t forget to get it onto the <a href="http://www.ep-ts.com" rel="nofollow">http://www.ep-ts.com</a> website also!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Connell</title>
		<link>http://tibcoblogs.com/cep/2009/09/30/epts-looking-at-roi/comment-page-1/#comment-908</link>
		<dc:creator>Brian Connell</dc:creator>
		<pubDate>Thu, 01 Oct 2009 12:28:43 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=834#comment-908</guid>
		<description>I think it's probably less "ironic", and more to illustrate the fact that the EPTS doesn't have a single channel to communicate with the outside world.  It reinforces the need.  Now, if Opher had posted after the workgroup had been accepted and started, that would be closer to "ironic".  Still, I'm glad that you managed to illustrate so clearly the dysfunctional nature of EPTS "marketing".</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s probably less &#8220;ironic&#8221;, and more to illustrate the fact that the EPTS doesn&#8217;t have a single channel to communicate with the outside world.  It reinforces the need.  Now, if Opher had posted after the workgroup had been accepted and started, that would be closer to &#8220;ironic&#8221;.  Still, I&#8217;m glad that you managed to illustrate so clearly the dysfunctional nature of EPTS &#8220;marketing&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Vincent</title>
		<link>http://tibcoblogs.com/cep/2009/09/30/epts-looking-at-roi/comment-page-1/#comment-905</link>
		<dc:creator>Paul Vincent</dc:creator>
		<pubDate>Wed, 30 Sep 2009 21:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=834#comment-905</guid>
		<description>Thanks Opher - of course, but its still ironic... :)
Cheers</description>
		<content:encoded><![CDATA[<p>Thanks Opher - of course, but its still ironic&#8230; <img src='http://tibcoblogs.com/cep/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Opher Etzion</title>
		<link>http://tibcoblogs.com/cep/2009/09/30/epts-looking-at-roi/comment-page-1/#comment-904</link>
		<dc:creator>Opher Etzion</dc:creator>
		<pubDate>Wed, 30 Sep 2009 13:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/?p=834#comment-904</guid>
		<description>Hi Paul.  These action items have been communicated to all EPTS members before putting on my Blog.  I expect the people who will work on the EPTS awareness and promotion to reshape the EPTS website and communication processes with the rest of the universe.

cheers.

Opher</description>
		<content:encoded><![CDATA[<p>Hi Paul.  These action items have been communicated to all EPTS members before putting on my Blog.  I expect the people who will work on the EPTS awareness and promotion to reshape the EPTS website and communication processes with the rest of the universe.</p>
<p>cheers.</p>
<p>Opher</p>
]]></content:encoded>
	</item>
</channel>
</rss>

