I could be mistaken, but if you use <a href="http://blog.gmane.org/gmane.comp.java.drools.user">http://blog.gmane.org/gmane.comp.java.drools.user</a> then it will include the old stuff as well, the gmane people kindly migrated the old data to the new list.
<br><br><div><span class="gmail_quote">On 3/1/07, <b class="gmail_sendername">Rahul Phadnis</b> <<a href="mailto:rahul.phadnis@fatspaniel.com">rahul.phadnis@fatspaniel.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I understand that the jboss rules mailing list<br>migrated to the current server recently.<br><br>Can somebody tell me where can I find archives from<br>the previous mailing list?<br><br>-Rahul<br><br>--- Edson Tirelli <
<a href="mailto:tirelli@post.com">tirelli@post.com</a>> wrote:<br><br>><br>> Alexander,<br>><br>> Seems a really interesting project indeed!<br>> Trying to answer:<br>><br>> 1. I'm not sure what you mean by "rule hierarchy".
<br>> Drools does not<br>> support rule "inheritence" if that is what you mean<br>> by hierarchy... can<br>> you please ellaborate?<br>><br>> 2. Dynamically adding rules to a rulebase will not<br>
> force a full<br>> reevaluation. Only the new rules are evaluated and<br>> if they eventually<br>> have Patterns that may be shared, they are not even<br>> evaluated, as they<br>> already were.<br>><br>
> The problem I think you will face is that Drools<br>> does not support<br>> uncertanty reasoning. You will need to code<br>> uncertanty by hand if you<br>> use drools. I suggest you a POC to check how it
<br>> goes.<br>><br>> []s<br>> Edson<br>><br>> Alexander Richter wrote:<br>><br>> > Hello,<br>> > I work in a bioinformatics group and we're<br>> interested in using Drools<br>
> > for setting up an assertion engine for biological<br>> processes.<br>> > We have over 300 genomes ( == sets of facts), each<br>> with upwards of<br>> > 10K genes/features with annotations ( == facts).
<br>> We want to be able<br>> > to predict whether various biological processes<br>> exist, based on<br>> > presence of the annotated genes that are the<br>> components of the<br>> > process. Asserted processes are not black and
<br>> white; we may have<br>> > various levels of certainty, based on the<br>> percentage of component<br>> > genes found (because we can't be certain that not<br>> finding a certain<br>> > annotation means the the gene isn't in the genome
<br>> -- it could mean<br>> > that we just didn't find it). In addition,<br>> processes tend to be<br>> > composed of sub-processes. The assertions then get<br>> used to make<br>> > additional annotations on the features, which we
<br>> then use to help us<br>> > look for missing components. Therefore, we need to<br>> be able to display<br>> > the decisions that led to a specific assertion, as<br>> well as the<br>> > features that went into the component assertions.
<br>> > In addition, we regularly add new processes, as we<br>> get new ways to<br>> > annotate genes, or read about newly worked-out<br>> processes. We really<br>> > don't want to have to run all rules against all
<br>> the genomes every<br>> > time we add a new rule, but just add that rule.<br>> ><br>> > We would like to define the actual rules for the<br>> assertions in<br>> > Drools, but don't know how we would do certain
<br>> parts.<br>> > 1) Can one walk through the rule hierarchy from a<br>> given rule and<br>> > tease out the hierarchy of rules and the facts<br>> that went into that rule?<br>> > 2) Is it possible to add a rule, or set of
<br>> interacting rules, and<br>> > have them incrementally evaluated, instead of<br>> forcing full<br>> > evaluation? Alternatively, can the rulesets be<br>> individually defined<br>> > and run in such a way that they interact?
<br>> ><br>> ><br>> > Thanks,<br>> > Alexander Richter<br>> > _______________________________________________<br>> > rules-users mailing list<br>> > <a href="mailto:rules-users@lists.jboss.org">
rules-users@lists.jboss.org</a><br>> ><br>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>> ><br>><br>><br>> --<br>> Edson Tirelli
<br>> Software Engineer - JBoss Rules Core Developer<br>> Office: +55 11 3124-6000<br>> Mobile: +55 11 9218-4151<br>> JBoss, a division of Red Hat @ <a href="http://www.jboss.com">www.jboss.com</a><br>>
<br>><br>> _______________________________________________<br>> rules-users mailing list<br>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users">
https://lists.jboss.org/mailman/listinfo/rules-users</a><br>><br><br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org
</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a><br></blockquote></div><br>