<?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>Modelling the Provenance of Data in Autonomous Systems</article-title>
</title-group>

<author><a href="mailto:sm@ecs.soton.ac.uk"><name>Simon Miles</name></a></author>
<aff>School of Electronics and Computer Science <br/>University of Southampton Southampton, SO17 1BJ, UK</aff>

<author><a href="mailto:sjm@ecs.soton.ac.uk"><name>Steve Munroe</name></a></author>
<aff>School of Electronics and Computer Science <br/>University of Southampton Southampton, SO17 1BJ, UK</aff>

<author><a href="mailto:mml@ecs.soton.ac.uk"><name>Michael Luck</name></a></author>
<aff>School of Electronics and Computer Science <br/>University of Southampton Southampton, SO17 1BJ, UK</aff>

<author><a href="mailto:L.Moreau@ecs.soton.ac.uk"><name>Luc Moreau</name></a></author>
<aff>School of Electronics and Computer Science <br/>University of Southampton Southampton, SO17 1BJ, UK</aff>

</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Determining the <italic>provenance</italic> of data, i.e. the process that led to that
data, is vital in many disciplines. For example, in science, the process
that produced a given result must be demonstrably rigorous for
the result to be deemed reliable. A <italic>provenance system</italic> supports applications
in recording adequate documentation about process executions
to answer queries regarding provenance, and provides functionality
to perform those queries. Several provenance systems are
being developed, but all focus on systems in which the components
are <italic>reactive</italic>, for example Web Services that act on the basis
of a request, job submission system, etc. This limitation means that
questions regarding the motives of autonomous actors, or <italic>agents</italic>, in
such systems remain unanswerable in the general case. Such questions
include: who was ultimately responsible for a given effect,
what was their reason for initiating the process and does the effect
of a process match what was intended to occur by those initiating
the process? In this paper, we address this limitation by integrating
two solutions: a generic, re-usable framework for representing
the provenance of data in service-oriented architectures and a
model for describing the goal-oriented delegation and engagement
of agents in multi-agent systems. Using these solutions, we present
algorithms to answer common questions regarding responsibility
and success of a process and evaluate the approach with a simulated
healthcare example.</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>AAMAS07_0412_17095dfb6da34eaf185fe34fab4a73e4</hpdf>
</fpdf>
</body>
</article>

