<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" gd:etag="W/&quot;A08BRXY5fyp7ImA9WxJXFko.&quot;"><id>tag:blogger.com,1999:blog-20843771</id><updated>2009-06-10T19:24:14.827-05:00</updated><title>Down to Earth Business Rules</title><subtitle type="html">A place to share real-life thoughts and experiences in the pursuit of Business Rules automation.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/" /><author><name>Michael J. Krouze</name><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>14</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/aai-rules" type="application/atom+xml" /><entry gd:etag="W/&quot;CUEDQn4zfCp7ImA9WBFVFkU.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-4205641652336334353</id><published>2007-04-15T19:28:00.000-05:00</published><updated>2007-04-15T19:34:33.084-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-04-15T19:34:33.084-05:00</app:edited><title>Context sensitive Rule Management – Part 2</title><summary>In my March 28th blog, I discussed process centric thinking and mapping business rules to process. As I stated earlier, business is a set of processes/services that it provides to its consumers. Business rules define how each process functions and how processes taken together allow a business to function. Let’s take an example of e-Commerce web site which takes orders from customers and fulfills </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/4205641652336334353/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=4205641652336334353" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/4205641652336334353?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/4205641652336334353" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2007/04/context-sensitive-rule-management-part.html" title="Context sensitive Rule Management – Part 2" /><author><name>Sreenivasu</name><uri>http://www.blogger.com/profile/02031579963253710281</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;D04FRns5eyp7ImA9WBFVE0g.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-117510056700729947</id><published>2007-03-28T12:47:00.000-05:00</published><updated>2007-04-12T00:31:57.523-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-04-12T00:31:57.523-05:00</app:edited><title>Context sensitive Rule Management</title><summary>In my 15 years of IT experience, I have visited quite a few companies. Every company attempted, to some degree, to document business process in the form of rules. At the beginning, everyone is over enthusiastic and starts writing every detail as a business rule. At this stage, when a new rule is added, majority of BA's will not look into whether new rule would contradict with existing rules. This</summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/117510056700729947/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=117510056700729947" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/117510056700729947?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/117510056700729947" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2007/03/context-sensitive-rule-management.html" title="Context sensitive Rule Management" /><author><name>Sreenivasu</name><uri>http://www.blogger.com/profile/02031579963253710281</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DkMNQno5eCp7ImA9WBBWGE8.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-115194969076917783</id><published>2006-07-03T13:01:00.000-05:00</published><updated>2006-12-11T02:08:13.420-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-12-11T02:08:13.420-06:00</app:edited><title>What does a team member on a rules project need to know?</title><summary>As part of a new client engagement, I will have to bring my current team mates up to speed on business rules, engine use, the business rules approach, fact modeling, rule writing and analysis.Short of enrolling the entire team in Artemis Alliance's business rules analysis, and rule engine technology training classes, I decided to turn to some free resources for now…So…what does an analyst, </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/115194969076917783/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=115194969076917783" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/115194969076917783?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/115194969076917783" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/07/what-does-team-member-on-rules-project.html" title="What does a team member on a rules project need to know?" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;DEACSXg6eCp7ImA9WBBXFks.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-115084112250737235</id><published>2006-06-20T16:57:00.000-05:00</published><updated>2006-11-27T16:32:48.610-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-27T16:32:48.610-06:00</app:edited><title>Managing Business Rules</title><summary>So…maybe this post will sound like a rant, but why aren’t there any fully mature business rule management systems (BRMS) to be found anywhere?! I can’t even count the number of times clients ask me to recommend a system and I have to give them the bad news.     Naturally, each rule engine vendor will tell you that you can perform full rule lifecycle management within their authoring/development </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/115084112250737235/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=115084112250737235" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/115084112250737235?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/115084112250737235" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/06/managing-business-rules.html" title="Managing Business Rules" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;Dk4FRX0yfip7ImA9WBBXF08.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114711669720649802</id><published>2006-05-08T14:30:00.000-05:00</published><updated>2006-11-28T08:41:54.396-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-28T08:41:54.396-06:00</app:edited><title>Pitfalls and Lessons Learned of Business Rules Implementation - A Business Analyst Perspective Perspective</title><summary>Senior Artemis Alliance staff, drawing on their practical experience with what can go wrong from management, technical, and business analysis perspectives, provided insight into how and why business rules initiatives fail and strategies to assure the success of such initiatives.by Alyce Neperud, Artemis Principal and Senior Business Analyst     Significant  analysis pitfalls include:    </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114711669720649802/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114711669720649802" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114711669720649802?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114711669720649802" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/05/pitfalls-and-lessons-learn_114711669720649802.html" title="Pitfalls and Lessons Learned of Business Rules Implementation - A Business Analyst Perspective Perspective" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;DU8HRn84eCp7ImA9WBBXGEw.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114711661152870009</id><published>2006-05-08T14:28:00.000-05:00</published><updated>2006-11-29T10:30:37.130-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-29T10:30:37.130-06:00</app:edited><title>Pitfalls and Lessons Learned of Business Rules Implementation - A Technical Perspective</title><summary>Senior Artemis Alliance staff, drawing on their practical experience with what can go wrong from management, technical, and business analysis perspectives, provided insight into how and why business rules initiatives fail and strategies to assure the success of such initiatives.by Krzysztof Karski, Artemis Senior  Consultant Significant  technical pitfalls include failing to: Architect the  </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114711661152870009/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114711661152870009" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114711661152870009?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114711661152870009" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/05/pitfalls-and-lessons-learned-of_08.html" title="Pitfalls and Lessons Learned of Business Rules Implementation - A Technical Perspective" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DUADQ3s-fip7ImA9WBBXGEw.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114711599193052925</id><published>2006-05-08T14:17:00.000-05:00</published><updated>2006-11-29T10:29:32.556-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-29T10:29:32.556-06:00</app:edited><title>Pitfalls and Lessons Learned of Business Rules Implementation - A Management Perspective</title><summary>Senior  Artemis Alliance staff, drawing on their practical experience with what can go  wrong from management, technical, and business analysis perspectives, provided  insight into how and why business rules initiatives fail and strategies to  assure the success of such initiatives. by Michael  Krouze, Artemis CTOSignificant management pitfalls include:   Management sees the  initiative as ‘only’</summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114711599193052925/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114711599193052925" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114711599193052925?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114711599193052925" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/05/pitfalls-and-lessons-learned-of.html" title="Pitfalls and Lessons Learned of Business Rules Implementation - A Management Perspective" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;CUUESHk_eyp7ImA9WBBXFUQ.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114427112566927064</id><published>2006-04-05T16:03:00.000-05:00</published><updated>2006-11-26T20:06:49.743-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-26T20:06:49.743-06:00</app:edited><title>Decision Trees</title><summary>This second and last article in this series discusses decision trees, what are they, when to use them and when not to use them.   Decision trees help systems reach a predictive decision that relies on navigating a path of historic knowledge to reach the end conclusion. An analyst or rules writer lays out the decision path with branching conditions leading to different outcomes. Decision tress </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114427112566927064/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114427112566927064" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114427112566927064?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114427112566927064" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/04/decision-trees.html" title="Decision Trees" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total></entry><entry gd:etag="W/&quot;AkIAQHw_fip7ImA9WBBXGEw.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114304719694619765</id><published>2006-03-22T10:40:00.000-06:00</published><updated>2006-11-29T10:42:21.246-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-29T10:42:21.246-06:00</app:edited><title>Decision Tables and Trees</title><summary>Rules can be graphically represented in multiple ways for usability purposes. Two structures are primarily used: decision trees and decision tables. Rule engines do not really care about the rule representation since either structure is compiled into similar executable rule statements.This is the first of two posts that will hopefully give some helpful tips about when to use and  when  not to use</summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114304719694619765/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114304719694619765" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114304719694619765?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114304719694619765" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/03/decision-tables-and-trees.html" title="Decision Tables and Trees" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry gd:etag="W/&quot;DEAERn8_eCp7ImA9WBBXFks.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114113932519432875</id><published>2006-02-28T09:08:00.000-06:00</published><updated>2006-11-27T16:31:47.140-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-27T16:31:47.140-06:00</app:edited><title>The Value of Assessments</title><summary>Many organizations have considered assessments, formal and informal, of business rules technology when looking at reengineering efforts or at new enterprise development projects slated to involve business rule technology. The promised value of using business rules—often generated by one or more of the business rule vendors---is hard to ignore, especially for industries whose IT systems have ever </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114113932519432875/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114113932519432875" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114113932519432875?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114113932519432875" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/02/value-of-assessments.html" title="The Value of Assessments" /><author><name>Steve Kenny</name><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DEMDRnc9fip7ImA9WBBXFks.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-114011930434918599</id><published>2006-02-16T13:41:00.000-06:00</published><updated>2006-11-27T16:27:57.966-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-27T16:27:57.966-06:00</app:edited><title>Why do so few companies actually manage their business rules?</title><summary>The products and services offered by today’s modern companies are increasingly virtual constructs modeled and defined through business rules and enforced by automated computer systems. Insurance policies, lending agreements and other financial products are often essentially contractual agreements between a provider and a consumer. These products and services amount to risk mitigation or behavior </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/114011930434918599/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=114011930434918599" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/114011930434918599?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/114011930434918599" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/02/why-do-so-few-companies-actually.html" title="Why do so few companies actually manage their business rules?" /><author><name>KK</name><uri>http://www.blogger.com/profile/17362218992512568650</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;AkQMQXo8fip7ImA9WBBXGEw.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-113941721122474646</id><published>2006-02-08T10:46:00.000-06:00</published><updated>2006-11-29T10:39:40.476-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-11-29T10:39:40.476-06:00</app:edited><title>The Strategic and Tactical Reasons for Prototyping</title><summary>We have found that organizations  considering the application of a business rules solution to a specific business  problem reap both strategic and tactical value from prototyping prior to  embarking on a full-blown project.      Strategically, prototyping  identifies risks and avenues for mitigation of those risks as well as providing  the basis for informed decision-making.   Management has the </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/113941721122474646/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=113941721122474646" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/113941721122474646?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/113941721122474646" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/02/strategic-and-tactical-reasons-for.html" title="The Strategic and Tactical Reasons for Prototyping" /><author><name>Michael J. Krouze</name><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry gd:etag="W/&quot;DkQAR3ozeyp7ImA9WBBWEUw.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-113718670611207026</id><published>2006-01-13T14:57:00.000-06:00</published><updated>2006-12-02T20:52:26.483-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-12-02T20:52:26.483-06:00</app:edited><title>BEST PRACTICE</title><summary>The term ’best practice’ is a simple concept. I am at point A and I want to get to point B. How should I go about it? I brainstorm some options. Have I done something like this before? Has somebody else done this before or something similar to it and what were the results? What resources are available to me? How quickly do I need to achieve my goal, what do I need to be prepared for at point B, </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/113718670611207026/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=113718670611207026" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/113718670611207026?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/113718670611207026" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/01/best-practice.html" title="BEST PRACTICE" /><author><name>Alyce Neperud</name><uri>http://www.blogger.com/profile/06708673895692097308</uri><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry gd:etag="W/&quot;D0ICR3s7fip7ImA9WBJSEkw.&quot;"><id>tag:blogger.com,1999:blog-20843771.post-113718523564757036</id><published>2006-01-13T14:40:00.000-06:00</published><updated>2006-03-01T06:19:26.506-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-03-01T06:19:26.506-06:00</app:edited><title>Welcome</title><summary>As CTO of Artemis Alliance, I want to personally welcome you to the Down to Earth Business Rules blog.  If you are tired of academic, theoretical discussions on business rules and want down to earth conversations with people like you who deal with the day-to-day issues of doing real business rules work, then this is the blog for you!The Down to Earth Business Rules blog is for both business and </summary><link rel="replies" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/113718523564757036/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=20843771&amp;postID=113718523564757036" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/20843771/posts/default/113718523564757036?v=2" /><link rel="self" type="application/atom+xml" href="http://aai-rules.blogspot.com/feeds/posts/default/113718523564757036" /><link rel="alternate" type="text/html" href="http://aai-rules.blogspot.com/2006/01/welcome.html" title="Welcome" /><author><name>Michael J. Krouze</name><email>noreply@blogger.com</email></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry></feed>
