Calls for lightning talks,
highlight talks and fast abstracts opened.
read more news
Rule Responder:
RuleML-2008 Description
The RuleML-2008 Responder use case implements the RuleML-2008 organization as a virtual organization consisting of self-autonomous rule-based agents who fulfil typical conference organization and project management tasks and respond respectively react to incoming requests to the RuleML-2008 organization.
The RuleML-2008 Responder agent (organizational agent) acts as a single point of entry for the RuleML-2008 organization. It filters, decides and delegates incoming queries and requested tasks to the organizations' members (e.g. the organizing committee members) which are implemented as distributed rule-based personal agents. Project management methodologies such as a responsibility assignment matrix are used by the RuleML-2008 Responder to describe the roles and responsibilities of the personal agents in the virtual organization and typical negotiation and distributed coordination mechanisms are used to manage and communicate with the project team and external agents. The personal agents act as self-autonomous agents having their own rule-based decision and behavioural logic on top of their personal information sources, web services, vocabularies / ontologies and knowledge structures. This allows them, e.g., to selectively reveal personal information such contact information (e.g. show only parts of FOAF profiles or vCards) or react respectively proactively plan according to the situation (e.g. schedule a meeting based on personal iCal calendar data).
Each agent in the RuleML-2008 virtual organization is implemented as a web-based service consisting of a set of internal or external data and knowledge sources and a rule execution environment (a rule engine). An enterprise service bus (ESB) is used as a scalable, highly distributable object broker to manage, integrate and seamlessly handle the interactions between the distributed rule-based agents using disparate transport and messaging technologies. In the concrete reference implementation of this use case Reaction RuleML (Reaction RuleML project) is applied as rule interchange and event messaging format, Prova (Prova project) and OO jDrew (OO jDrew project) are used as two exemplary rule engines in the implementation of the organizational and personal agents, and Mule (Mule project) is used as communication middleware between the agent endpoints. Reaction RuleML messages (event messages) are transported by the ESB to the appropriate internal agent nodes or external communication interfaces based on a broad spectrum of selectable transport protocols such as HTTP, JMS, Web Service protocols (SOAP) or agent communication languages (JADE). The platform-independent interchanged RuleML messages which contain the message payload, e.g. queries or answers, as well as meta information about the conversation and the pragmatic context of the message, are translated by translator services (e.g. XSLT style sheets) into the platform-dependent, specific execution language of the rule-based execution environment at the agent endpoint(s). According to their rule-based decision logic the agents derive answers and react appropriately to the incoming messages, e.g. by sending out further messages, e.g. with answers to the original query or with new messages starting a sub-conversation. The rules typically access various data such as organizational project management data and personal information either by external data integration, e.g., by Provas' integration interfaces for distributed relational databases or Semantic Web data (RDF, RDFS, OWL), or by replication of pre-translated data into the rule engines fact base.