<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>European Conference
on Articial Intelligenc e</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Multilingual Agents: Ontologies, Languages and Abstractions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ion Constantinescu</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Monique Calisti</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Steven Willmott</string-name>
          <email>Steven.Willmott@ep.c</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Laboratoire d'Intelligence, Artificielle, Ecole, Polytechnique Federal de</institution>
          ,
          <addr-line>Lausanne, Lausanne</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Laboratoire d'Intelligence, Artificielle, Ecole, Polytechnique Federal de</institution>
          ,
          <addr-line>Lausanne, Lausanne</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Laboratoire d'Intelligence, Artificielle, Ecole, Polytechnique Federal de</institution>
          ,
          <addr-line>Lausanne, Lausanne</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2000</year>
      </pub-date>
      <volume>16</volume>
      <fpage>1</fpage>
      <lpage>16</lpage>
      <abstract>
        <p />
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>knowledge.
and make it possible for the agent to manipulate all elements
stract ontology representation (AOR). This AOR then can
be used to capture abstract models of communication
reand multiple ontology representations.
terconnected and heterogeneous. This suggests that future
munication languages, multiple ways of expressing content
of messages in a uniform way - as instances of its ontological
agents will need to be able to deal with multiple agent
comissues and describes a prototype implementation.
an agent’s internal knowledge representation with an
ablated knowledge (domain models, agent communication
lanOne way to deal with this heterogeneity is by identifying
Agent Environments are becoming increasingly open,
inguages, content languages and models of how these interact)
The paper outlines the approach, highlights interesting
1. INTRODUCTION
2. DEFINITIONS
facts) and meta knowledge (knowledge about classes
of entities).
into instance knowledge (knowledge of individual
Figure 1: An agent’s knowledge is usually divided
similarities between these frameworks is beyond the scope
are: DAML, OIL, UML, Frames (such as those currently
the model chosen is in anyway \the best" for the
combinaelements below. The following is the example AOR which
will be used from now on:
of this paper, a useful intersection appears to include the
appeared to be necessary for a basic systems. Target ORs
pressed in BNF/EBNF. Although a detailed study of the
out the rest of the paper. The intention is not to argue that
used in FIPA specications), simple language grammars
exnes an abstract on tology representation which is used
throughtion of target ORs but to draw out common aspects which
The above are rather general statements, this section
de3.1.2 Abstraction from Conceptual Models
may be several useful abstractions and more than simply
didate for use as the agent’s internal knowledge
representaAbstract Ontology Representation (AOR). In general there
sitions (encoding - conceptual model, conceptual models
In the context of this paper it is referred to as an tion.2
unied conceptual model) to simply presen tation however.
two abstraction steps. We focus on these two major
tranThe product of the second step is then a potential
can</p>
      <p>3.1.1 Abstraction from Encodings
3.1.3 Example Abstract Ontology
about languages it knows at the same level as domain
knowlcompatible with the AOR dened in the previous section.</p>
      <p>For a language based on an EBNF grammar a rst pass at
generating the model could be done as follows:
nipulate them. This enables the agent to treat knowledge
An OR can be used to construct conceptual models of
lanedge. The objective is to model languages in a formalism
guages. A logical usage of this is to give the agent access
gies can in fact be seen as abstract grammars for languages.
to these language models at runtime and allow it to
maAs Craneeld et. al. point out in [1] however,
ontolo</p>
      <p>Object
Car</p>
      <p>VW</p>
      <p>Meta</p>
      <p>Car</p>
      <p>Vehicle</p>
      <p>Truck
Car</p>
      <p>Vehicle
SubClassOf
SameClassAs
3.2 Abstract Agent Languages
3.2.1 Abstraction from Encodings</p>
      <p>
        Figure 4 sketches how languages might be dened as three
separate but linked ontologies. Although FOL cannot be
3.2.2 Abstraction from Conceptual Models
3.3 Building Multilingual Agents
{ A subset of FIPA-KIF [
        <xref ref-type="bibr" rid="ref21">5</xref>
        ], corresponding to SKIF
(a limited form of KIF covering only KIF
sentences).
4. IMPLEMENTATION
4.1 Overview
4.2 Examples of Operation
1. What should the AOR include/exclude?: As noted in
dened.
a profound eect on the agent system. Although it
choices by agent toolkit developers will have a eect
on how large numbers of agents may use of ontologies
is \internal" and not shared with the outside world
Section 3.1 the choice of internal representation has
a lowest common denominator of understanding for a
are internal representations and as such do not need
given set of ontologies to ensure both can model the
to be public. Agents working in mission critical areas
others perception of the situation.
2. Do Agents need to share AORs?: In principle AORs
however are likely to need to nd w ays of establishing
3. What types of Agent Languages can be represented?:
scoping for example).
      </p>
      <p>Since the AOR as described can in principle model
functional and object oriented). How does this relate
pects of languages which could be regarded as part of
the conceptual model cannot be represented (variable
the main features of a wide range of languages (logical,
to other meta-modelling work (e.g. [1]) and what
asconcepts?: Currently the AOR chosen allows class
equivcepts in one ontology may be equivalent to a
combina4. How can we cope with equivalences between groups of
tion of concepts in another.
alence, more generally however a combination of
conhence this exibilit y does not appear very useful. For
tance.
lar for the subset of elements which correspond to FOL
In fact the syntaxes of FIPA-SL and KIF are very
simisyntaxes) this capability is likely to be of great
imporother languages with other syntaxes however (or other
4.3 Resources
6. What happened to the semantics anyway?: As with
\syntactic" relationships but say nothing about how
support eectiv e semantic checking tools.
beyond the immediate scope of the paper it would be
semantics might be managed or enforced. Although
interesting to see if the abstractions described would
current language descriptions the conceptual models
only capture the basic concepts of a language and their</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Genesereth</surname>
          </string-name>
          and
          <string-name>
            <given-names>N. J.</given-names>
            <surname>Nilsson</surname>
          </string-name>
          . Logical Foundations
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          of Articial Intelligenc e. Morgan Kaufmann,
          <year>1988</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>Physical</given-names>
            <surname>Agents</surname>
          </string-name>
          ,
          <volume>19</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [3]
          <string-name>
            <surname>FIPA. FIPA ACL</surname>
          </string-name>
          Message Structure Specication
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <source>(00037)</source>
          .
          <source>Technical report, Foundation for Intelligence</source>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Specication</surname>
          </string-name>
          (
          <volume>00070</volume>
          ).
          <source>T echnical report</source>
          , Foundation for
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [4]
          <string-name>
            <surname>FIPA. FIPA ACL</surname>
          </string-name>
          Message Representation in String
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <given-names>Intelligence</given-names>
            <surname>Physical Agents</surname>
          </string-name>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <source>(00008)</source>
          .
          <source>Technical report, Foundation for Intelligence</source>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [6]
          <string-name>
            <surname>FIPA. FIPA SL Content Language Specication</surname>
          </string-name>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <given-names>Physical</given-names>
            <surname>Agents</surname>
          </string-name>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <article-title>[7] FIPA-OS</article-title>
          .
          <source>FIPA OS v1.3.3. Technical report</source>
          , FIPA-OS
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <given-names>Open</given-names>
            <surname>Source Team</surname>
          </string-name>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          v2.
          <fpage>0</fpage>
          .
          <string-name>
            <surname>Technical</surname>
            <given-names>report</given-names>
          </string-name>
          , Jade Open Source Team,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Jade. Java</given-names>
            <surname>Agent Development Environment (JADE)</surname>
          </string-name>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          <article-title>specication v 1.7. T echnical report</article-title>
          , DAML Project,
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>DAML. Darpa</given-names>
            <surname>Agent</surname>
          </string-name>
          Markup Language: DAML+OIL
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <source>(00010)</source>
          .
          <source>Technical report, Foundation for Intelligence</source>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <given-names>Physical</given-names>
            <surname>Agents</surname>
          </string-name>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>FIPA. FIPA</given-names>
            <surname>KIF Content Language Specication</surname>
          </string-name>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>C.</given-names>
            <surname>Petrie</surname>
          </string-name>
          .
          <article-title>Agent-based engineering, the web</article-title>
          , and
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          intelligence.
          <source>IEEE Expert</source>
          ,
          <volume>11</volume>
          (
          <issue>6</issue>
          ):
          <volume>24</volume>
          {
          <fpage>29</fpage>
          ,
          <string-name>
            <surname>Dec</surname>
          </string-name>
          .
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>