I think, I would use both mechanism in case of the forward chaining is confuse due to several matching set in my study( - let say searching for nodes to run Simulation which require Mathlab Software). In this case, I don't wants to fire the first matching rules instead needs to search further for another attribute such as "which machine is free at the time?".
On Nov 20, 2007 11:42 AM, Wolfgang Laun <[EMAIL PROTECTED]> wrote: > I doubt very much that an approach combining forward and backward chaining > would simplify matters. Given that we're still discussing the > user/systems/resources application: I'd extend the set of rules (including > dynamically created ones) so that the system would come up with the info > which resource (combination) is missing whenever the rule(s) determining the > applicable system won't fire. > > Regards > Wolfgang > > > > > On 11/19/07, Mohd. Noor <[EMAIL PROTECTED]> wrote: > > > > > > Hi All > > Forward chaining is based on the supplied facts whereas backward > > chaining based on the goals. > > How about in the first run during the forward chaining- the rules cannot > > be fired; could be due to the limited information (of resources), do I have > > to infer the rules using the backward chaining after that based on the goals > > approaches ( with refers to complex rules and template that not statically > > defined) > > > > > > cheers > > mnoor > > > > >
