<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments for Aleri CEP Blog</title>
	<link>http://blog.aleri.com</link>
	<description>Complex Event Processing Explained</description>
	<pubDate>Fri, 21 Nov 2008 04:32:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>Comment on The Rise of End-user Data Visualization by Jack Rusher</title>
		<link>http://blog.aleri.com/the-rise-of-end-user-data-visualization/2008/11/06/#comment-204</link>
		<dc:creator>Jack Rusher</dc:creator>
		<pubDate>Fri, 07 Nov 2008 15:47:33 +0000</pubDate>
		<guid>http://blog.aleri.com/the-rise-of-end-user-data-visualization/2008/11/06/#comment-204</guid>
		<description>Hi Hans!

I believe the future of CEP authoring will include some form of exploratory analysis.  This can be done by either capturing a portion of a stream up front or using historical data, then working out the application step-by-step as that data is fed through the operators in the engine's graph.  Optimally, changing the parameters of any operator would cause an immediate change in a downstream table that can be inspected via multiple viewing paradigms (spreadsheet view, line graph, whatever).

As for Orange in particular: I like that they've got visualizations and AI-based analysis tools in their design palette.  These same sorts of components would be very handy for many CEP application authors.  Some techniques are easy to move to real-time streams (sampling, for instance), others would be hard or impossible (any that require the entire history to be online, for instance), but the general approach is, I think, a useful one.</description>
		<content:encoded><![CDATA[<p>Hi Hans!</p>
<p>I believe the future of CEP authoring will include some form of exploratory analysis.  This can be done by either capturing a portion of a stream up front or using historical data, then working out the application step-by-step as that data is fed through the operators in the engine&#8217;s graph.  Optimally, changing the parameters of any operator would cause an immediate change in a downstream table that can be inspected via multiple viewing paradigms (spreadsheet view, line graph, whatever).</p>
<p>As for Orange in particular: I like that they&#8217;ve got visualizations and AI-based analysis tools in their design palette.  These same sorts of components would be very handy for many CEP application authors.  Some techniques are easy to move to real-time streams (sampling, for instance), others would be hard or impossible (any that require the entire history to be online, for instance), but the general approach is, I think, a useful one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Rise of End-user Data Visualization by hgilde</title>
		<link>http://blog.aleri.com/the-rise-of-end-user-data-visualization/2008/11/06/#comment-201</link>
		<dc:creator>hgilde</dc:creator>
		<pubDate>Fri, 07 Nov 2008 04:54:29 +0000</pubDate>
		<guid>http://blog.aleri.com/the-rise-of-end-user-data-visualization/2008/11/06/#comment-201</guid>
		<description>I'm sort of curious what aspects of Orange you're talking about. Orange is a tool to make exploratory data analysis easier. When I think about doing exploratory analysis over real-time streams - let's just say that this punishment could be inflicted by a Greek god on an offending statistician.

Of course, I'm all in favor of real-time data in dashboards, and of allowing the end user to customize logic. But that's not what I think of when I look at Orange...

Hans</description>
		<content:encoded><![CDATA[<p>I&#8217;m sort of curious what aspects of Orange you&#8217;re talking about. Orange is a tool to make exploratory data analysis easier. When I think about doing exploratory analysis over real-time streams - let&#8217;s just say that this punishment could be inflicted by a Greek god on an offending statistician.</p>
<p>Of course, I&#8217;m all in favor of real-time data in dashboards, and of allowing the end user to customize logic. But that&#8217;s not what I think of when I look at Orange&#8230;</p>
<p>Hans</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orange by Visual event processing languages &#171; Hans Gilde&#8217;s weblog</title>
		<link>http://blog.aleri.com/orange/2008/10/09/#comment-190</link>
		<dc:creator>Visual event processing languages &#171; Hans Gilde&#8217;s weblog</dc:creator>
		<pubDate>Sun, 12 Oct 2008 22:14:46 +0000</pubDate>
		<guid>http://blog.aleri.com/orange/2008/10/09/#comment-190</guid>
		<description>[...] up on the recent posts about Orange and how it relates to Event Processing. Jack talks about features of Orange appearing in EP products. Marc seems to like the idea of Orange and also wonders when real-time OLAP will become a [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] up on the recent posts about Orange and how it relates to Event Processing. Jack talks about features of Orange appearing in EP products. Marc seems to like the idea of Orange and also wonders when real-time OLAP will become a [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Smart Order Routing with CEP - intelligent decisions, not just workflow automation by More on modern SOR &#171; Hans Gilde&#8217;s weblog</title>
		<link>http://blog.aleri.com/smart-order-routing-with-cep-intelligent-decisions-not-just-workflow-automation/2008/08/28/#comment-171</link>
		<dc:creator>More on modern SOR &#171; Hans Gilde&#8217;s weblog</dc:creator>
		<pubDate>Fri, 05 Sep 2008 14:44:15 +0000</pubDate>
		<guid>http://blog.aleri.com/smart-order-routing-with-cep-intelligent-decisions-not-just-workflow-automation/2008/08/28/#comment-171</guid>
		<description>[...] talk lately on EP blogs about Smart Order Routing (SOR) and CEP products. There are posts from Aleri and StreamBase about how SOR is more than just simple decision making. This debate has happened [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] talk lately on EP blogs about Smart Order Routing (SOR) and CEP products. There are posts from Aleri and StreamBase about how SOR is more than just simple decision making. This debate has happened [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Future of Complex Event Processing Authoring by Does EP change the nature of data analysis? &#171; talldude</title>
		<link>http://blog.aleri.com/the-future-of-cep-authoring/2008/04/11/#comment-31</link>
		<dc:creator>Does EP change the nature of data analysis? &#171; talldude</dc:creator>
		<pubDate>Fri, 11 Apr 2008 17:29:41 +0000</pubDate>
		<guid>http://blog.aleri.com/the-future-of-cep-authoring/2008/04/11/#comment-31</guid>
		<description>[...] post was, in some way, prompted by a recent post from Jack at Aleri. But the question has been lingering in my mind since Opher posted about the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] post was, in some way, prompted by a recent post from Jack at Aleri. But the question has been lingering in my mind since Opher posted about the [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Semantic CEP by Jack Rusher</title>
		<link>http://blog.aleri.com/semantic-cep/2008/03/25/#comment-29</link>
		<dc:creator>Jack Rusher</dc:creator>
		<pubDate>Tue, 08 Apr 2008 15:41:02 +0000</pubDate>
		<guid>http://blog.aleri.com/semantic-cep/2008/03/25/#comment-29</guid>
		<description>Thanks for your comment, Claudi.  It seems that there are a number of community members who're interested in the intersection of these two technologies.  &lt;a href="http://rulecore.com/CEPblog/?p=308" rel="nofollow"&gt;Marco&lt;/a&gt;, for instance, seems to have quite similar ideas.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Claudi.  It seems that there are a number of community members who&#8217;re interested in the intersection of these two technologies.  <a href="http://rulecore.com/CEPblog/?p=308" rel="nofollow">Marco</a>, for instance, seems to have quite similar ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Semantic CEP by PatternStorm</title>
		<link>http://blog.aleri.com/semantic-cep/2008/03/25/#comment-24</link>
		<dc:creator>PatternStorm</dc:creator>
		<pubDate>Fri, 04 Apr 2008 15:15:36 +0000</pubDate>
		<guid>http://blog.aleri.com/semantic-cep/2008/03/25/#comment-24</guid>
		<description>Hi Jack,

Count me as sharing the essence of your madness too, albeit with some minor twists ;-) I would use typed first order logic where events would play the role of atomic propositions or facts, then have event processing agents define an interface defining the specific types of events (i.e. facts) to which they subscribe and the ones that they can emit. Agents would internally maintain the received events in an internal facts (i.e. event) database (one per agent). Event processing agents would be programmed using prolog-like rules interacting with the agent's fact database only in three possible ways: adding, updating and deleting facts. There would be also a primitive to emit a fact (i.e. an event) to the environment. That would be all. I like this programming model for event processing, it has some nice properties, for instance event types are "just" typed first order sentences with variables whose instances are all those facts (i.e. events) that make the sentence come true,...

Regards,
PatternStorm</description>
		<content:encoded><![CDATA[<p>Hi Jack,</p>
<p>Count me as sharing the essence of your madness too, albeit with some minor twists <img src='http://blog.aleri.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> I would use typed first order logic where events would play the role of atomic propositions or facts, then have event processing agents define an interface defining the specific types of events (i.e. facts) to which they subscribe and the ones that they can emit. Agents would internally maintain the received events in an internal facts (i.e. event) database (one per agent). Event processing agents would be programmed using prolog-like rules interacting with the agent&#8217;s fact database only in three possible ways: adding, updating and deleting facts. There would be also a primitive to emit a fact (i.e. an event) to the environment. That would be all. I like this programming model for event processing, it has some nice properties, for instance event types are &#8220;just&#8221; typed first order sentences with variables whose instances are all those facts (i.e. events) that make the sentence come true,&#8230;</p>
<p>Regards,<br />
PatternStorm</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Consistency and Determinacy by Marco on CEP&#187;Blog Archive &#187; Indeterministic CEP?</title>
		<link>http://blog.aleri.com/consistency-and-determinacy/2008/03/13/#comment-5</link>
		<dc:creator>Marco on CEP&#187;Blog Archive &#187; Indeterministic CEP?</dc:creator>
		<pubDate>Thu, 13 Mar 2008 22:11:00 +0000</pubDate>
		<guid>http://blog.aleri.com/consistency-and-determinacy/2008/03/13/#comment-5</guid>
		<description>[...] Here&#8217;s an interesting comment on a comment: http://blog.aleri.com/?p=33 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Here&#8217;s an interesting comment on a comment: <a href="http://blog.aleri.com/?p=33" rel="nofollow">http://blog.aleri.com/?p=33</a> [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
