This sounds like a good short term approach--for the long term I think
there are some exciting developments underway from many research and
development groups. I couldn't resist adding my own two cents...
We are currently using Voyager as a substrate under our KAoS Java
framework, which embodies a next-generation agent communication approach
that is similar in spirit to KQML but takes conversations rather than
single speech act messages as the basic unit. The KAoS generic agent
processes and enforces common conversation policies between agents, so that
agent implementors don't have to roll their own.
There are several issues with KQML at this point, and we are working with
others as part of the FIPA and DARPA agent-based systems collaborations to
put agent communication language standards on a more firm footing, and to
get some reference implementations out where they can be used by the agent
community. RE: syntax, we are also converting to XML for message syntax
(not just the content).
In the coming months we will be adding JESS to the mix as a component of
our planner, and you will be seeing a lot more of us on the list. Sun
Microsystems will also be more active in the agents arena in the future.
More information about what we're doing can be access from papers attached
to a link from my home page below.
Cheers,
Jeff
At 6:57 PM -0500 8/6/98, Dave Carlson wrote:
>A timely query! During the past week, I've been investigating the use of
>KQML messaging between Jess "Agents". At the same time, I'm investigating
>XML as the content language for KQML messages, but that's another subject.
>
>I've previously run Jess within a java servlet, using HTTP GET/POST to send
>queries that control the Jess engine. If you maintain a session instance
>per user, then you can run the Jess engine within that session for
>continuity over multiple hits. Then I send Jess commands -- parse rules from
>a URL, reset, facts, rules, run, etc. -- from a GET/POST method, routing
>stdout back to another frame in the user's browser.
>
>Now for KQML, I just downloaded the JATLite server from Stanford (
>http://java.stanford.edu -- interesting that the JATLite home page has such
>a direct, short URL! ) This provides a basic KQML interpreter and reliable
>message router, in Java. It would be very straight forward to use my
>servlet approach to embed Jess within the KQML agent, using KQML
>performatives for the control commands. But I haven't had time to complete
>this implementation. Maybe this weekend...
>
>Dave
>
>At 01:39 PM 8/6/98 -0400, you wrote:
>>I wonder if anybody tried to use JESS within ObjectSpace's Voyager mobile
>agents framework. Also, did anybody experiment with KQML for messages and
>conversations between JESS processes?
>> Best regards,
>> Alex Bejan
>>
>>---------------------------------------------------------------------
>>To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
>>in the BODY of a message to [EMAIL PROTECTED], NOT to the
>>list. 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. List problems? Notify [EMAIL PROTECTED]
>---------------------------------------------------------------------
*******************************
Jeffrey M. Bradshaw
Visiting Associate Professor
Institute for Human and Machine Cognition
University of West Florida
(425) 865-6086 (msg)
email: [EMAIL PROTECTED]
http://www.coginst.uwf.edu/~jbradsha/
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list. List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
