On Oct 8, 2008, at 7:20 PM, Ozsariyildiz, S.S. wrote:
Well it is matter of choice how open and interoperable you need the
system. If you want more application dependent (specific) solution /
integration both your suggestions are valid. You can also combine
RuleML+OWL and even combine with RDF for more open solutions. So,
it's matter of choice between application integration or open
communication.
There's also expressiveness to consider. OWL and Jess have rather
different goals; the subset where they overlap -- i,e., the part of
the Jess language that can be translated into OWL (or RuleML for that
matter) is not large. It depends how much of Jess's power you need to
use.
That said: JessML and OWL are two different XML dialects; transforming
from one to the other is just a "small matter of programming." So it's
certainly possible using XSLT, for example. There may even be tools
out there on the Net that do it already.
--------------------------------------------------------------------------------------------
Section Design and Construction Processes
Department of Building Technology,
Faculty of Civil Engineering and Geosciences
Delft University of Technology.
PO Box 5048, 2600 GA Delft / The Netherlands
Phone +31.15.2784330 (direct) +31.15.2786636 (secr)
Email: [EMAIL PROTECTED]
------------------------------------------------------------------------------------------------------------
From: [EMAIL PROTECTED] on behalf of levent kent
Sent: Wed 10/8/2008 23:34
To: [email protected]
Subject: JESS: Architecture decisions
Hi everyone,
I am doing an academic project on Modal Dialogue Systems.
The main idea is to provide multi agent environments with people,
where people communicate
with robots/agents through natural language.
In another project, someone is going to implement/design the natural
lang. processing presumably with TrindiKit,
which uses Prolog to interpret knowledgebase.
In my project, the agents will take derived knowledge from natural
language proc. part and will make final decisions and act accordingly.
The knowledgebase(KB) is not a static one. So, the software should
accept the global (known to all agents) and local (agent-specific)
knowledge as files.
At first I had the plan to use OWL for the communication between
Prolog and Jess. (KB) files would be stored as OWL too. So, I could
use Jess+Jade+OWL to deal wıth everything. By the way, my knowledge
on OWL or Protege is very very limited.
After downloading JessTab,Protege,Jess and Jade, I discovered that
Jess also has some language for such purposes(JessML).
Should I use OWL+Protege or just JessML for this kind of a project?
My first guess is that JessML requires less tutorials to understand
things and it would be easier. Would that be easily possible to
transform JessML to OWL if that is required in the future?
Thanks for any responses,
--
Levent Kent
---------------------------------------------------------
Ernest Friedman-Hill
Informatics & Decision Sciences, Sandia National Laboratories
PO Box 969, MS 9012, Livermore, CA 94550
http://www.jessrules.com
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
