Hi, again.

I'm the guy thinking about using JESS for a lookup service.
After getting a couple of valuable comments about my initial idea,
I decided to give a shot to that.

So, I started to describe objects (actually agents,,, I'm working
on developing Web measurement infrastructure based on agent),,
what I found is that it is very hard to describe something completely
which is composed of subcomponents.
For example, a monitoring agent which has two tools, one tool is
to measure web page response time, the other one is just "ping",,
If I want to register this agent to the lookup service, I have to describe
this agent
like
(agent (type monitoring) (having_tools URLaccess ping)
          (cando measure_web_response_time  measure_latency)
          (location foo.bar.edu:2000) (...) (..etc..))
if the agent has "n" tools, then the description will be completely
unmanageable.

So, I came up with the idea of describing "sub-components",  then infer
the capabilities and attributes of the component containing these
sub-components.
e.g.
; description for ping
(tool (name ping) (cando measure_responstime_time))
; description for URLaccess
(tool (name URLaccess (cando measure_web_response_time))

then, with a rule,
(tool (name ?n) (cando ?what))
(agent (type...) (...) ... (..) (havingtools ?n))
=>
(assert (agent (type...) (cando ?what))
Thus,
I can generate new description of the agent,, and so on,, thus finally
get a complete description of the agent.

So, I ask for two things,, one is any comments or related research work,
the other thing is (little bit technical),,
To generate a new description about the agent,
new slots should sometimes be added,, but for easy matching, unordered
fact template looks good,, so how can I add new slots to the existing
unordered fact templates?
or any other ways to achieve this?

Thanks again,
KK.


---------------------------------------------------------------------
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]
---------------------------------------------------------------------

Reply via email to