I would say that if you reorganized the facts and get a different answer and/or 
reorganize your rules and get a different answer, your inference engine is not 

I worked on a pagination app that provided the xy coords for the layout of each 
page.  Certainly all of the facts were already there, text, graphics, etc.  The 
rules nibbled away 8 pages at a time, when it had 10 scores for each page it 
took the highest and get then worked on the next pages.  I tneeded many facts 
in advance but it didn't make sense to paginate dozens of pages forward.

It was the controll facts at runtime that made the rules fire correctly.  The 
inference engine went into phases, facts asserted by rules.  It was that 
controll that made this work.   Not whether rules or facts are loaded in any 
certain order.

But yeah I have no idea if that was good form?

<meta http-equiv="Content-Type" Content="text/html; charset=iso-8859-1">
<body><a href="http://jakarta.apache.org/tapestry/";><img 
src="http://howardlewisship.com/images/no-struts.png"; width="200" height="154" 
alt="Friends Don't Let Friends Code Struts" border="0"/></a>

---- Matthew Hutchinson <[EMAIL PROTECTED]> wrote: 
> Hi everyone,
> Just a conceptual question... since starting with Jess, it always seemed to
> me generally you have the rules established first, then load in facts which
> in turn trigger these rules. No problems there. But is it "proper" to
> consider having the facts already in memory and *then* adding rules which I
> know will trigger - basically a sort of "query on the data" mentality? Is
> this a bad concept?
> Cheers,
> Matt
> --
> Matthew Hutchinson
> Ph.D. Candidate
> Department of Spatial Sciences
> Curtin University of Technology
> GPO Box U1987
> Perth, Western Australia 6845

To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]

Reply via email to