Sounds good, makes sense to even somebody like me :-)<br><br><div class="gmail_quote">On Fri, Jun 13, 2008 at 3:54 PM, Mark Proctor &lt;<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I&#39;m in the process of splitting drools up into sub projects and looking for feed on names. Each sub project will have it&#39;s own manual.<br>
<br>
<br>
Drools the Business Logic integration Platform<br>
-----------------------------------------------<br>
<br>
Drools Expert<br>
This is the expert system rule engine, as you expect from Drools 4.0 now, Ruleflow has moved to the Flow project<br>
<br>
Drools Flow<br>
This is becoming a full blown workflow and process engine and includes the ruleflow work for rule engine integration<br>
<br>
Drools Fusion<br>
Temporal Reason system providing CEP capabilities. The syntax is an orthogonal extension to the DRL. While it could possible live as a chapter in the &quot;Drools Expert&quot; manual we expect there will be enough information on adapters and integration and general theory to justify its own sub project.<br>

<br>
Drools Guvnor<br>
This is the Guvovernance system for Drools and all it&#39;s sub projects. It&#39;s still primarily a BRMS, but we are trying to expand it to provide a governance platform for processes and cep too, which will be a long term effort post 5.0<br>

<br>
<br>
Mark<br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote></div><br>