<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: On Business Rules Categorization &#8211; Part IV – Rule Classification</title>
	<atom:link href="http://www.primatek.ca/blog/2008/12/16/on-business-rules-categorization-part-iv-%e2%80%93-rule-classification/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.primatek.ca/blog/2008/12/16/on-business-rules-categorization-part-iv-%e2%80%93-rule-classification/</link>
	<description>Eric Charpentier&#039;s blog on Business Rules and Business Process</description>
	<lastBuildDate>Mon, 21 Dec 2009 15:08:29 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eric Charpentier</title>
		<link>http://www.primatek.ca/blog/2008/12/16/on-business-rules-categorization-part-iv-%e2%80%93-rule-classification/comment-page-1/#comment-18</link>
		<dc:creator>Eric Charpentier</dc:creator>
		<pubDate>Tue, 23 Dec 2008 12:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.primatek.ca/blog/2008/12/16/on-business-rules-categorization-part-iv-%e2%80%93-rule-classification/#comment-18</guid>
		<description>I have taken this as advice and taken off the requirement of being a registered user on the blog’s site.

And to come back to Sandy’s inital comment, the classification is meant to be a way of identifying where rules could end up during the implementation phase of a project, hence the “Execution component” column in the classification.

Since there are BPEL execution engines and similar products and that during implementation these tools might end up being used, I created the category.

Hopefully this helps to clarify the classification.</description>
		<content:encoded><![CDATA[<p>I have taken this as advice and taken off the requirement of being a registered user on the blog’s site.</p>
<p>And to come back to Sandy’s inital comment, the classification is meant to be a way of identifying where rules could end up during the implementation phase of a project, hence the “Execution component” column in the classification.</p>
<p>Since there are BPEL execution engines and similar products and that during implementation these tools might end up being used, I created the category.</p>
<p>Hopefully this helps to clarify the classification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Kemsley</title>
		<link>http://www.primatek.ca/blog/2008/12/16/on-business-rules-categorization-part-iv-%e2%80%93-rule-classification/comment-page-1/#comment-17</link>
		<dc:creator>Sandy Kemsley</dc:creator>
		<pubDate>Tue, 23 Dec 2008 12:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.primatek.ca/blog/2008/12/16/on-business-rules-categorization-part-iv-%e2%80%93-rule-classification/#comment-17</guid>
		<description>I disagree with the separation of &quot;rules for workflow or business process&quot; since I think that they are just the application of the other rule types (e.g., rules for security, rules for rating engine, rules for decisions), not a class on their own. I would have added this as a comment on Eric&#039;s blog, but typically don&#039;t comment on sites that require me to create a login.</description>
		<content:encoded><![CDATA[<p>I disagree with the separation of &#8220;rules for workflow or business process&#8221; since I think that they are just the application of the other rule types (e.g., rules for security, rules for rating engine, rules for decisions), not a class on their own. I would have added this as a comment on Eric&#8217;s blog, but typically don&#8217;t comment on sites that require me to create a login.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
