FOUNDATION FOR INTELLIGENT PHYSICAL AGENTS
FIPA Abstract Architecture Specification
|
Document title |
FIPA Abstract Architecture Specification |
||
|
Document number |
PC00001C |
Document source |
FIPA TC Architecture |
|
Document status |
Preliminary |
Date of this status |
2000/08/03 |
|
Supersedes |
None |
||
|
Contact |
arch@fipa.org |
||
|
Change history |
|||
|
2000/02/15 |
While this is the first version of this document published under the new document control system, it an update from earlier drafts of this document. The changes are Agent-directory-entry becomes directory-entry, Agent-name becomes FIPA-Entity-name, added Transform-service for gateway support, new entity FIPA-Entity-Attributes and made Agent-platform a FIPA-Service; Remove references to future work. These will be published as soon as the FAB assigns a number for that document. |
||
|
2000/04/04 |
Removed all agent-platform constructs; Cleaned up various hanging references; Added service-references. |
||
|
2000/07/31 |
This revision restores the definitions of the actions supported by the directory and communication services. The Transform-service material is withdrawn, since it seems premature (and possibly wrong) to assume that gateways are explicitly addressable entities. |
||
|
2000/08/03 |
Editorial changes for consistency with FIPA 2000 specifications |
||
İ 2000 Foundation for Intelligent Physical Agents - http://www.fipa.org/
Geneva, Switzerland
|
Notice |
|
Use of the technologies described in this specification may infringe
patents, copyrights or other intellectual property rights of FIPA Members and
non-members. Nothing in this specification should be construed as granting
permission to use any of the technologies described. Anyone planning to make
use of technology covered by the intellectual property rights of others
should first obtain permission from the holder(s) of the rights. FIPA
strongly encourages anyone implementing
any part of this specification to determine first whether part(s)
sought to be implemented are covered by the intellectual property of others,
and, if so, to obtain appropriate licenses or other permission from the
holder(s) of such intellectual property prior to implementation. This
specification is subject to change without notice. Neither FIPA nor any of
its Members accept any responsibility whatsoever for damages or liability,
direct or consequential, which may result from the use of this specification. |
Foreword
The Foundation for Intelligent Physical Agents
(FIPA) is an international organization that is dedicated to promoting the
industry of intelligent agents by openly developing specifications supporting
interoperability among agents and agent-based applications. This occurs through
open collaboration among its member organizations, which are companies and
universities that are active in the field of agents. FIPA makes the results of
its activities available to all interested parties and intends to contribute
its results to the appropriate formal standards bodies.
The members of FIPA are individually and
collectively committed to open competition in the development of agent-based
applications, services and equipment. Membership in FIPA is open to any
corporation and individual firm, partnership, governmental body or
international organization without restriction. In particular, members are not
bound to implement or use specific agent-based standards, recommendations and
FIPA specifications by virtue of their participation in FIPA.
The FIPA specifications are developed through
direct involvement of the FIPA membership. The status of a specification can be
either Preliminary, Experimental, Standard, Deprecated or Obsolete. More detail about the process of
specification may be found in the FIPA Procedures for Technical Work. A
complete overview of the FIPA specifications and their current status may be
found in the FIPA List of Specifications. A list of terms and abbreviations
used in the FIPA specifications may be found in the FIPA Glossary.
FIPA is a non-profit association registered in
Geneva, Switzerland. As of January 2000, the 56 members of FIPA represented 17 countries worldwide. Further
information about FIPA as an organization, membership information, FIPA
specifications and upcoming meetings may be found at http://www.fipa.org/.
Contents
2.2 Why an Abstract Architecture?
2.3 Scope of the
Abstract Architecture
2.3.1 Areas that are not
Sufficiently Abstract
2.3.2 Areas to be
Considered in the Future
2.4 Going From
Abstract to Concrete Specifications
2.6 Status of the
Abstract Architecture
3.1 FIPA Entities,
FIPA Services and Agents
3.4 Agents Send
Messages to Other Agents
3.5 Providing Message
Validity and Encryption
3.6 Providing Interoperability
4 Agent and Agent Information Model
4.2 Transport Message
Relationships
4.3 Directory Entry
Relationships
4.5 Message Transport
Elements
5.1.1 Classification of
Elements
5.1.4 Format of Element
Description
5.2.2 Relationships to
Other Elements
5.2.3 Relationship to
Concrete Specification
5.3 Agent
Communication Language
5.3.2 Relationships to
Other Elements
5.3.3 Relationship to
Concrete Specification
5.4.2 Relationships to
Other Elements
5.4.3 Relationship to
Concrete Specification
5.5.1 Relationships to
Other Elements
5.5.2 Relationship to
Concrete Specification
5.6.2 Relationships to
Other Elements
5.6.3 Relationship to
Concrete Specification
5.7.2 Relationships to
Other Elements
5.7.3 Relationship to
Concrete Specification
5.8.2 Relationship to
Other Elements
5.8.3 Relationship to
Concrete Specification
5.9.2 Relationships to
Other Elements
5.9.3 Relationship to
Concrete Specification
5.10.2 Relationships to
Other Elements
5.10.3 Relationship to
Concrete Specification
5.11.2 Relationships to
Other Elements
5.11.3 Relationship to
Concrete Specification
5.12.2 Relationships to
other elements
5.12.3 Relationship to
Concrete Specification
5.13.2 Relationships to
Other Elements
5.13.3 Relationship to
Concrete Specification
5.14.2 Relationships to
Other Elements
5.14.3 Relationship to
Concrete Specification
5.15 Message Encoding
Representation
5.15.2 Relationships to
Other Elements
5.15.3 Relationship to
Concrete Specification
5.16 Message Transport
Service
5.16.2 Relationships to
Other Elements
5.16.3 Relationship to
Concrete Specification
5.17.2 Relationships to
Other Elements
5.17.3 Relationship to
Concrete Specification
5.18.2 Relationships to
Other Elements
5.18.3 Relationship to
Concrete Specification
5.19.2 Relationships to
Other Elements
5.19.3 Relationship to
Concrete Specification
5.20.2 Relationships to
Other Elements
5.20.3 Relationship to
Concrete Specification
5.21.2 Relationships to
Other Elements
5.21.3 Relationship to
Concrete Specification
5.22 Transport
Specific Properties
5.22.2 Relationships to
Other Elements
5.22.3 Relationship to
Concrete Specification
5.23.2 Relationships to
Other Elements
5.23.3 Relationship to
Concrete Specification
6 Evolution of the Architecture
7 Informative Annex A: Goals of Message Transport Abstractions
7.3 Support for
Alternative Transports Within a Single System
7.4 Desirability of
Transport Agnosticism
7.5 Desirability of
Selective Specificity
7.6 Connection-Based,
Connectionless and Store-and-Forward Transports
7.7 Conversation
Policies and Interaction Protocols
7.8 Point-to-Point and
Multiparty Interactions
7.13 Interoperability
and Gateways
7.14 Reasoning about
Agent Communications
7.15 Testing,
Debugging and Management
8 Informative Annex B: Goals of Directory Service Abstractions