application to mediate the communication among a
community of experts in food technology and cus-
tomers in need for qualified information about food
products in supermarkets. For this propose, we de-
fine a mediator agent that perform the information
interchange between these communities, involving
tasks like collecting questions, searching for a con-
sent among experts, providing translations (with the
support of communication specialists), and distribut-
ing the answers.
2 MEDIATION AMONG
COMMUNITTIES
The dialogue among communities with different
jargon can be seen as a sub problem of the cross
lingual dialogue problem, a research field that looks
for highly accurate communication of semantically
complex content (Piwek and Power, 2006). The
‘Saint Graal’ for researchers in this field is to build
an automatic process to translate one language to
other, being able to cope with the different semantic
levels of each specific language. A solution to this
problem is much more important if you consider the
challenge to human-to-human communication
through a browser that has been set by the Internet.
To build an effective automatic translator for this
scenery is a dream far to be realized. However, the
necessity of communication among communities is a
reality that requires, if not the best solution, at least
one viable solution. The solution we present uses the
agents technology to facilitate the negotiation among
the communities members.
3 MIDAS DESCRIPTION
MIDAS (Middleware for Intelligent and Distributed
Agent-based Systems) (Haendchen Filho, 2006) is a
platform that provides an environment to run agents
and a WSA-compliant framework to ease its devel-
opment. WSA aims to provide a common Web Ser-
vice definition and its location inside a wider archi-
tecture in order to guide service implementers, au-
thors of services specification and Web application
developers. WSA represents the natural evolution
from traditional applications to SOA ones
(Odell, 2005).
Figure 1 shows the MIDAS generic architecture,
which is based on the coexistence of several con-
tainers, each one executing a JVM (Java Virtual
Machine). Each virtual machine provides a complete
execution environment, where agents can execute
concurrently in the same host. The architecture in-
cludes two different types of container: the Front-
End Server (FES) and the Agent Container (AC).
FES plays the integration rules of the platform, pro-
moting the synchronization services and interopera-
bility with external applications. It is similar to the
front-end server used by JADE (Adam et al., 2004).
AC is a Web container that can be inhabited by
organizations, agents and components.
Middleware and application agents are the basic
elements of the platform. The middleware agents
abstract completely generic characteristics, such as
communication, concurrency, lifecycle management,
services discovery and interoperability. They enable
the developer to focus only in the application details.
The introduction of the agent concept to play these
roles makes easier to satisfy important non-
functional requirements for Web architectures, like
flexibility, dynamic behavior, and adaptability. The
following middleware agents have been used to
perform the roles defined by the WSA reference
model,: (i) a Broker agent, playing the MOM roles;
(ii) a Proxy agent, playing the SOM roles; (iii) a
Catalog agent, playing the ROM roles and (iv) a
Manager agent, playing the MGM roles.
Figure 1: The main concepts of the MIDAS.
Application agents and components are only lo-
cated in the AC containers. AC provides a structure
composed by abstract classes (Agent and Compo-
nent) and a blackboard. The introduction of the ab-
stract agent concept extends the WSA reference
architecture specification, providing a way to group
in a super-class the common properties to all the
agents. The application agents (or components) are
implemented by extending the abstract classes,
which provide the hot-spots from which specific
ICEIS 2007 - International Conference on Enterprise Information Systems
296