Comments are always welcome ;-D
Did you notice that I tried to hedge that comment with "rely too much" and
"design some" so as not to make the remarks universal and unqualified. Maybe
I should have left that one out...
My short experience with writing jess rules is derived mainly from using it
fo
Hello All,
For developers interested in incorporating CBR (Case-Based Reasoning)
techniques
into JESS, can request a copy of NaCoDAE version-3.0 ( Navy Conversational
Decision Aids
Environment) from Len Breslow at the U.S navy (contact email shown below).
This package is
written in Java.
-
Sorry, couldn't let this one go by without a comment. (And then I really,
really have to get back to work... :-) Alan, I cut out all but one paragraph
of your response. I was in complete agreement with the rest of it. A
well-designed, goal-oriented approach actually uses (not salience - hate t
I read the article reference by Ernest, and it's quite good - excellent, in
fact. In light of that, I suppose one more voice will just confuse the issue
even further, but, nevertheless, here goes. There are any number of good
reasons to use a rulebased system (expert system, if you will) for a pr
Jeff,
My two cents worth and likely stating the obvious...
Once you decide that you want to use a rule engine, be sure your execution
is as good as your decision. Some things that can help are:
Make a clear distinction between policy and mechanism -- which is just
another way of saying that you
Section 2.1.3 of the manual is pretty clear, I think:
2.1.3. Strings
Character strings in Jess are denoted using double quotes
("). Backslashes (\) can be used to escape embedded quote
symbols. Note that Jess strings are unlike Java strings in several
important ways. First, no "escape s
Hi,
We've had the same issues for years. Its not just upper management, but the
Java programmers who need to be convinced. We've been using Jess in a
production web site and call center for two years, and we've used it other
production applications for the last 4 years. 95% of all our rules, domai
Title: RE: JESS: Is it for me...
Ernest and all,
I agree with your assessment of that article as it was written,
so let me clarify a couple things. (BTW, I recently used this
paper in developing a proposal for a company I'm currently
consulting with, and recognized the same two observations
Hi all,
I have a doubt about how insert quotations marks (") into a string?
Example:
in - (str-cat "computers are "intelligents". ")
out - computers are "intelligent".
Thanks
Tircio de Morais
To unsubscribe, send the word
Here's a nice article entitled "Some Guidelines for Deciding Whether
to Use a Rule Engine," written by our friend George Rudolph:
http://herzberg.ca.sandia.gov/jess/guidelines.shtml
This article discusses many of the important considerations. I
personally think it's a little pessimistic;
Ok, forgive the ignorence here, but I do have another
very basic question. If I have to write the rules in
the JESS language, what am I really getting over just
writing them in pure Java? I have to have some big
selling points to take to my upper ups. I would love
to use an expert system, please
Hi Jeff,
10,000 business rules should automatically qualify your project for a rules
based solution and as far as rules based solutions go I haven't run into
anything better than Jess. That's especially true as you have decided to
use Java.
Your rule
"if all of the planes were unmanned
then
I think Jeff Richley wrote:
> I have a project that has roughly 10,000 business
> rules. Another major factor is that there are 13
> programmers (not including myself) and I am the only
> one that has ever programmed in Java. The powers that
> be have decided that we are going to write the entire
I have a project that has roughly 10,000 business
rules. Another major factor is that there are 13
programmers (not including myself) and I am the only
one that has ever programmed in Java. The powers that
be have decided that we are going to write the entire
program in Java. There are some very
14 matches
Mail list logo