<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<!--<href>banner.jpg</href>-->
<size width="100%"/>
</banner>
</journal-meta>
<article-meta>
<title-group>
<article-title>Aborting Tasks in BDI Agents</article-title>
</title-group>

<author><a href="mailto:johthan@cs.rmit.edu.au"><name>John Thangarajah</name></a></author>
<aff>RMIT University Melbourne, Australia</aff>

<author><a href="mailto:jah@cs.rmit.edu.au"><name>James Harland</name></a></author>
<aff>RMIT University Melbourne, Australia</aff>

<author><a href="mailto:morley@ai.sri.com"><name>David Morley</name></a></author>
<aff>Artificial Intelligence Center<br/> SRI International Menlo Park, CA 94025 U.S.A.</aff>

<author><a href="mailto:nysmith@ai.sri.com"><name>Neil Yorke-Smith</name></a></author>
<aff>Artificial Intelligence Center<br/> SRI International Menlo Park, CA 94025 U.S.A.</aff>



</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Intelligent agents that are intended to work in dynamic environments
must be able to gracefully handle unsuccessful tasks and
plans. In addition, such agents should be able to make rational decisions
about an appropriate course of action, which may include
aborting a task or plan,either as a result of the agent's own deliberations,
or potentially at the request of another agent. In this paper
we investigate the incorporation of aborts into a BDI-style architecture.
We discuss some conditions under which aborting a task or
plan is appropriate, and how to determine the consequences of such
a decision. We augment each plan with an optional <italic>abort-method</italic>,
analogous to the failure method found in some agent programming
languages. We provide an operational semantics for the execution
cycle in the presence of aborts in the abstract agent language CAN,
which enables us to specify a BDI-based execution model without
limiting our attention to a particular agent system (such as JACK,
Jadex, Jason, or SPARK). A key technical challenge we address is
the presence of parallel execution threads and of sub-tasks, which
require the agent to ensure that the abort methods for each plan are
carried out in an appropriate sequence.</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>AAMAS07_0253_8a217af898f9f9ca938d55d5d76dc610</hpdf>
</fpdf>
</body>
</article>

