<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Too much information &#187; Event Processing Technical Society</title>
	<atom:link href="http://blogs.the451group.com/information_management/tag/event-processing-technical-society/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.the451group.com/information_management</link>
	<description>The 451 Take on information management</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:53:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Defining the language of complex events</title>
		<link>http://blogs.the451group.com/information_management/2008/07/16/defining-the-language-of-complex-events/</link>
		<comments>http://blogs.the451group.com/information_management/2008/07/16/defining-the-language-of-complex-events/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 10:46:38 +0000</pubDate>
		<dc:creator>Matthew Aslett</dc:creator>
				<category><![CDATA[Data management]]></category>
		<category><![CDATA[complex event processing]]></category>
		<category><![CDATA[Event Processing Technical Society]]></category>
		<category><![CDATA[glossary]]></category>

		<guid isPermaLink="false">http://blogs.the451group.com/information_management/?p=72</guid>
		<description><![CDATA[The Event Processing Technical Society, an organization formed in June by Complex Event Processing bigwigs to collaborate on the future direction of event processing, has announced its first deliverable: a glossary of terms designed to provide &#8220;a common language for developing applications and software infrastructure that use event processing concepts&#8221;. The glossary is available for [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.ep-ts.com/">Event Processing Technical Society</a>, an organization <a href="http://www.ep-ts.com/content/view/60/9/">formed</a> in June by Complex Event Processing <a href="http://www.ep-ts.com/content/blogcategory/26/92/">bigwigs</a> to collaborate on the future direction of event processing, has <a href="http://www.ep-ts.com/content/view/65/9/">announced</a> its first deliverable: a glossary of terms designed to provide &#8220;a common language for developing applications and software        infrastructure that use event processing concepts&#8221;.</p>
<p>The glossary is <a href="http://www.ep-ts.com/component/option,com_docman/task,doc_download/gid,66/Itemid,84/">available</a> for download (PDF) while EPTS members can also comment and make suggestions on its wiki. It is based on an initial glossary <a href="http://complexevents.com/?p=362">published</a> by David Luckham and Roy Schulte in late June. The glossary has three goals:</p>
<ul>
<li class="bwlistitemmarginbottom">&#8220;to accelerate the learning of the event processing concept;</li>
<li class="bwlistitemmarginbottom">to further community communication by enabling practitioners to          utilize common concepts and terms; and,</li>
<li class="bwlistitemmarginbottom">most importantly, to provide a foundation for analysis and the development of best practices, publications and industry standards.&#8221;</li>
</ul>
<p>The glossary should also useful in defining the CEP sector for outsiders given the  widespread use of <a href="http://www.thecepblog.com/2008/07/16/muddy-waters/">apparently interchangable</a> phrases such as Event Stream Processing, Event Processing, Stream Processing and Complex Event processing.</p>
<p>Here&#8217;s some edited highlights for the uninitiated.</p>
<p>&#8220;<strong>Event</strong>: Anything that happens, or is contemplated as happening.&#8221;</p>
<p>&#8220;<strong>Event </strong>(also event object, event message, event tuple): An object that represents encodes or records an event, generally for the purpose of computer processing.&#8221;</p>
<p>&#8220;<strong>Complex event</strong>: an event that is an abstraction of other events called its members.&#8221;</p>
<p>&#8220;<strong>Complex-event processing</strong> (CEP): Computing that performs operations on complex events, including reading, creating, transforming or abstracting them.&#8221;</p>
<p>&#8220;<strong>Event stream</strong>: a linearly ordered sequence of events.&#8221;</p>
<p>&#8220;<strong>Event Stream Processing </strong>(ESP): Computing on inputs that are event streams.&#8221;</p>
<p>Simple really. For the full context, you are encouraged to refer to the <a href="http://www.ep-ts.com/component/option,com_docman/task,doc_details/gid,66/Itemid,84/">full glossary</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.the451group.com/information_management/2008/07/16/defining-the-language-of-complex-events/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

