|
I couldn't disagree
more.
Currently, the vast majority of software
end-users are not knowledgable about expert-systems, but you expect them to
gain various levels of proficiencies before they take advantage of
Jess. In my opinion, the assumption that
our end-users will understand software engineering to the point that they can
program is Jess is an invalid one. That assumption creates massive
obstacles to broad adoption of this kind of technology. Rules engines'
largest area of potential growth can only be realized by leveraging Rules'
engines ability to act as an interface between true experts and thier
machines. If we require subject matter experts in all areas to also become
software engineering experts in Jess, there wont' be that many people
adopting the technology.
Imagine you are working with an old-sage of
an analyst who has a very highly developed specialty in a critical area, but no
computer proficiency? How would you capture thier expert
knowledge? Would you require they spend 6 months learning a specific type
of rules-engine syntax? Wouldn't that be a bit of a waste of thier time?
Would you assign an AI specialist to take notes from this end-user's stories and
have the AI specialist write the rules-engine code? Wouldn't that be a
waste of two individual's time? Why not create an interface that would
allow them to select from a list f "Facts", "Predicates", "Actions", and
"Logical connectors" in order to create thier own highly evolved logic?
Imagine a mechanical-looking interface that would allow such interaction, even
in a 3-D environment; they are not too far off. We (industry) is already
seeing requirements evolving in the medical and military industries to leverage
these technologies to thier fullest.
RulesML and JSR-94 intermixed with
Web-services, the J2EE and a number of mature implementation scenarios make this
kind of interaction more of an option today than ever before. However,
these standardizations go even one more step further. What if you wanted
to use fuzzy logic instead of Jess' binary logic? What if you wanted to
use a logic engine based on ontologic data-mining? JSR-94 and RulesML
combined have the potential to make the changing of logic-engines as simple as
changing J2EE plugins. Will you require that everyone then become masters
of every logic engine they want to plug-into their architecture?
So then, why do I disagree with you?
Well, the idea that a person must spend years mastering one logic engine before
learning another only increases the obstacles to wide accessability of expert
systems. If expert system's true potential is to be realized, it can only
be done by removing obstacles. If someone wants to get an understanding of
a number of expert-systems and thier logical algorithms, allow it. If they
ask seemingly stupid questions, answe them. Be proud of your
accomplishments as a "black-belt" of numerous expert systems; but be wary when
your pride becomes arrogance and vanity.
v/r,
Mike Van, PMP From: [EMAIL PROTECTED] on behalf of James C. Owen Sent: Thu 5/25/2006 1:56 PM To: James Owen Cc: [email protected] Subject: [SPAM] - JESS: Date: Thu, 25 May 2006 11:43:56 -0500 - Bayesian Filter detected spam All:
Frequently I see folks wanting (needing?) to know about some books that
they can read to learn more about AI and Expert Systems. One of the
principles of the martial arts is to fully learn ONE system (meaning get a black
belt in one style) before trying to learn another. Too many times students
jump from one style to another trying to find an easy way to do something.
If you start with one expert system, such as Jess, the for PETE"S SAKE learn
that system first! Learn all about it. Get your black belt in Jess.
THEN move on to another one, such as CLIPS, drools, Mandarex, ILOG JRules,
Blaze Advisor, PegaRules, Haley, ART, MindBox, Aion or one of the others.
You'll find most of the principles are about the same from one to another even
though the language may change a bit. BU,T get a good foundation
before you jump around.
One of the best all-round books is a rather old one (1979) and is a
collection of white papers from the God Fathers and God Mother (only one in the
batch in this particular book) of rulebased systems, including one rather good
article on page 177 on conflict resolution. The name of the book is
"Pattern Directed Inference Systems" and is edited by D.A. Waterman and F.
Hayes-Roth. The list of authors is like a Who's Who of the early days of
AI at Stanford and Carnegie-Mellon as well as a few others. You have to go
to the used book list to get this one though. It costs from US $8 to US
$45 depending on condition. None of the articles actually tell you HOW to
program a rulebased system - very few real examples. BUT, it does give you
a really, really good view from an academic viewpoint. The same book is
probably in your university library or can be found at Amazon
http://www.amazon.com/gp/product/0534384471/qid=1148574693/sr=1-1/ref=sr_1_1/002-5741779-1658435?s=books&v=glance&n=283155
Now, go forth and study to show thyself a workman approved .... well,
you probably know the rest of the quotation, right?
SDG
jco
[EMAIL PROTECTED]
http://www.kbsc.com
"This above all: to thine own self
be true,
And it must follow, as the night the
day,
Thou canst not then be false to any
man."
Hamlet, Act 1, Scene III
|
- JESS: Date: Thu, 25 May 2006 11:43:56 -0500 James C. Owen
- RE: [SPAM] - JESS: Date: Thu, 25 May 2006 11:43:5... Mike L. VanGeertruy
- JESS: Pattern Directed Inference Systems James C. Owen
- JESS: Using multiple instances of Jess in one... Jim Goodwin
- Re: JESS: Using multiple instances of Jes... ejfried
- Re: JESS: Using multiple instances of Jes... Adam Winkler
- Re: JESS: Using multiple instances of Jes... Jim Goodwin
- JESS: Re: Rich Halsey
