FOUNDATION FOR INTELLIGENT PHYSICAL AGENTS
Minimal FIPA and FIPA Compliance Levels Work Plan
(see author below)
Date of this status:
r, Siemens AG <Michael.Berger com >
Problem Statement: FIPA specifies agent platforms and provides a definition of
by defining normative specifications with mandatory parts for internal and
external platform behavior. To be FIPA-compliant, a platform has to implement
all current mandatory specifications while FIPA-compliance does not specify if an agent platform is running completely on one machine / device or
it is distributed over several
machines / devices.
some applications , all the mandatory functionality is not necessary at the same time.
Furthermore, there are also devices with very limited resources,
e.g. mobile phones, were it is impossible to support all relevant functionality
defined as mandatory by FIPA.
objectives of this work -plan:
We need definitions of several levels
compliance ”. There
will be a minima l-FIPA
compliance level , which
represents the lowest requirements, up to a full-FIPA compliance level which
comprises the highest requirements (all current mandatory parts of normative
specifications). In between there may be different levels which
group specific functionality together.
For the definition of these levels mandatory and optional functionality of all informal and formal specifications should be taken into account.
Until now, the definition
FIPA compliant, was related always to the platform. What we also
need , is a more device specific view which
allows to say if the software in a device is FIPA compliant. That is important for device
manufacturers, which do not want to provide platforms but want
to sell devices with FIPA-compliant software on it.
for Work and Milestones: The plan is for a
month program of work and includes the following steps:
07 Finish workplan,
publish workplan , open call for contributions
1/ 09 Deadline for contributions 2001/10Presentation of contributions,
1 Deliver first draft of preliminary spec
04 Review specification, second draft
2/0 7 Making specification as experimental
· [FIPA00001] FIPA Abstract Architecture
· Device capabilities from manufacturers
· Patricia Charlton (Motorola)
· Heimo Laamanen (Sonera)
· Heikki Helin (Sonera)
· Jamie Lawrence (Broadcom)
· John Sheperdson (British Telecommunications)
· Steven Willmot (EPFL)