<?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: First Look &#8211; InRule Technology</title>
	<atom:link href="http://jtonedm.com/2008/04/21/first-look-inrule-technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtonedm.com/2008/04/21/first-look-inrule-technology/</link>
	<description>James Taylor on Everything Decision Management</description>
	<lastBuildDate>Wed, 17 Mar 2010 09:47:49 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BizTalk Training</title>
		<link>http://jtonedm.com/2008/04/21/first-look-inrule-technology/comment-page-1/#comment-11454</link>
		<dc:creator>BizTalk Training</dc:creator>
		<pubDate>Fri, 31 Oct 2008 03:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=357#comment-11454</guid>
		<description>&lt;strong&gt;BizTalk Training...&lt;/strong&gt;

Windows Server, das. NET- Framework, der Microsoft SQL Server und dem Biztalk Server sind die tragenden Komponenten des Systems. Mit Amalga mÃ¶chte Microsoft in Deutschland vor allem bei KlinikverbÃ¤nden punkten, in denen etwa das KIS von SAP lÃ¤uft, a...</description>
		<content:encoded><![CDATA[<p><strong>BizTalk Training&#8230;</strong></p>
<p>Windows Server, das. NET- Framework, der Microsoft SQL Server und dem Biztalk Server sind die tragenden Komponenten des Systems. Mit Amalga mÃ¶chte Microsoft in Deutschland vor allem bei KlinikverbÃ¤nden punkten, in denen etwa das KIS von SAP lÃ¤uft, a&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Leannah</title>
		<link>http://jtonedm.com/2008/04/21/first-look-inrule-technology/comment-page-1/#comment-10510</link>
		<dc:creator>William Leannah</dc:creator>
		<pubDate>Thu, 03 Jul 2008 13:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=357#comment-10510</guid>
		<description>&lt;a&gt;&lt;/a&gt;&lt;a&gt;When it comes to the world of BRE&#039;s, people spend way too much time worrying about pattern matching algorithms; AKA RETE, etc.   At the end of the day, only three things really matter when buying a Business Rules System: 1. Easy-to-use, 2. Reliable, and 3. Fast.   InRule is all three of these and more; the technology is great and so are the people. If you&#039;re considering a BRE for .NET, you&#039;ll want to look at them.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a></a><a>When it comes to the world of BRE&#8217;s, people spend way too much time worrying about pattern matching algorithms; AKA RETE, etc.   At the end of the day, only three things really matter when buying a Business Rules System: 1. Easy-to-use, 2. Reliable, and 3. Fast.   InRule is all three of these and more; the technology is great and so are the people. If you&#8217;re considering a BRE for .NET, you&#8217;ll want to look at them.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Lin</title>
		<link>http://jtonedm.com/2008/04/21/first-look-inrule-technology/comment-page-1/#comment-10467</link>
		<dc:creator>Peter Lin</dc:creator>
		<pubDate>Tue, 24 Jun 2008 23:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=357#comment-10467</guid>
		<description>I&#039;ve looked at InRule in the past and some of the things they say are blantantly wrong and misguided. For example, from their &quot;rete or not&quot; article, they make the following statement.
&quot;Rete is not always adept at handling complex or procedural logic, such as looping or nested if statements.&quot;
Rete rule engines are perfectly capable of handling looping and nested statements. They&#039;re right, when they say RETE has a steep learning curve. Their comparison of RETE to their own inference engine is disingenuous. The main reason for using RETE is writing rules in a declarative manner.
I would argue the rule engine doesn&#039;t really matter from an authoring perspective. As long as the authoring tools make it easy for the end user, the underlying engine could be anything assuming the number of rules does not require high performance and scalability to thousands of rules.
The statistics quoted by InRule do not represent the spectrum of business rules. From my own experience, many situations call for a powerful rule engine.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve looked at InRule in the past and some of the things they say are blantantly wrong and misguided. For example, from their &#8220;rete or not&#8221; article, they make the following statement.<br />
&#8220;Rete is not always adept at handling complex or procedural logic, such as looping or nested if statements.&#8221;<br />
Rete rule engines are perfectly capable of handling looping and nested statements. They&#8217;re right, when they say RETE has a steep learning curve. Their comparison of RETE to their own inference engine is disingenuous. The main reason for using RETE is writing rules in a declarative manner.<br />
I would argue the rule engine doesn&#8217;t really matter from an authoring perspective. As long as the authoring tools make it easy for the end user, the underlying engine could be anything assuming the number of rules does not require high performance and scalability to thousands of rules.<br />
The statistics quoted by InRule do not represent the spectrum of business rules. From my own experience, many situations call for a powerful rule engine.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->