One simplified approach to avoid generating rules is to:
1) create a split between policies and mechanisms in your domain.
2) design an XML schema/language to describe the policies.
3) create jess/clips rules that are driven by the XML policies to implement
the mechanisms identified in #1.
4) create a GUI to generate the XML.
Once you get to step #2, steps #3 and #4 can be done in parallel.
This allows you to constrain your problem into something that can be
implemented and validated easily. It may not allow your code to solve
problems it has never seen before but should give you a lot of flexibility
in covering most of your domain with a minimum of fuss and bother.
The structure of your rules using this technique will be determined by the
XML language and are the equivalent to what a simple rule/code generator
might do internally anyway. This is essentially user configurable behavior
which, in most cases, is good enough.
Like that most valuable lesson we learned in school says - do the hard
problems last... unless it is your job to solve the hard problems ;-D
alan
-----Original Message-----
From: Graham Heyes [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 07, 2001 6:25 PM
To: Oliver Hoffmann
Cc: [EMAIL PROTECTED]
Subject: Re: JESS: natural language and Jess?
Oliver,
oops, I suppose that I shouldn't have used the term "natural language".
You
have a very good point. I had just been reading about true "natural
language" AI
and the turing test etc You are right that parsing natural language is hard
work.
What I was thinking of was some way of getting rules and facts out of a text
file
in some format closer to English than the CLIP language used by Jess.
It may be that CLIP itself will be OK but I have the feeling that people
will
have a little trouble with the syntax. It may well be that we simply write
some
program which talks to the user on one end to gather requirrements and
outputs
rules and facts at the other. What I was asking was if someone had already
done
something similar in the hope of saving some effort ;^)
Oliver Hoffmann wrote:
> At 13:47 07.05.01 -0400, Graham Heyes wrote:
> >Hello Folks
> > I dropped off the jess list for a while so I'm sorry if this topic
> >has been beaten to death already. I couldn't find much in the archives
> >though.
> > I would like to use Jess in a real-time control system to monitor
> >parameters from physical devices like power supplies, pumps, magnets
> >etc. I have writen a few clip files as part of a pilot project to test
> >the fesability. I was showing the clip to someone and their comment was
> >"I hope you don't expect our users to learn this!". It's a valid point.
> >I think I understand clip/Jess but the language itself is rather
> >cryptic. Is there any "natural language" method out there which would
> >allow us to write rules and facts in a way which a non-expert can
> >understand. I could probably get someone in my group to work on it but,
> >obviously, would rather start with something which already exists.
> > Regards,
> >
> > Graham
>
> Graham,
>
> You can do this if you solve a little problem first: Find a way to
> automatically defer meaning from non-standardized human language. But
since
> researchers from all over the globe have unsuccessfully tried to solve
this
> little problem for the last 3 millenia, hopes are dim that you will be
able
> to come up with a quick fix.
>
> ;) Oliver
>
> ---------------------------------------------------------------------
> 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]
> ---------------------------------------------------------------------
--
Graham
----------------------------------------------------------------------------
---
Beware of Geeks bearing GIFS. http://www.jlab.org/coda Jefferson lab DAQ
group
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
