FOUNDATION FOR INTELLIGENT PHYSICAL AGENTS
FIPA Abstract Architecture Specification
|
Document title |
FIPA Abstract Architecture Specification |
||
|
Document number |
XC00001K |
Document source |
FIPA TC Architecture |
|
Document status |
Experimental |
Date of this status |
2002/11/01 |
|
Supersedes |
None |
||
|
Contact |
fab@fipa.org |
||
|
Change history |
See Informative Annex E — ChangeLog |
||
©
1996-2002 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 where appropriate.
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 Preliminary, Experimental, Standard, Deprecated or Obsolete. More detail about the process of specification may be found in the FIPA Document Policy [f-out-00000] and the FIPA Specifications Policy [f-out-00003]. A complete overview of the FIPA specifications and their current status may be found on the FIPA Web site.
FIPA is a non-profit association registered in Geneva, Switzerland. As of June 2002, the 56 members of FIPA represented many countries worldwide. Further information about FIPA as an organization, membership information, FIPA specifications and upcoming meetings may be found on the FIPA Web site at http://www.fipa.org/.
Contents
2.2 Why an FIPA Abstract Architecture?
2.3 Scope of the FIPA Abstract Architecture
2.3.1 Areas that are not Sufficiently Abstract
2.3.2 Areas for Future Consideration
2.4 Going From Abstract to Concrete Specifications
2.6 Status of the FIPA Abstract Architecture
2.7 Evolution of the FIPA Abstract Architecture
3 Themes of the FIPA Abstract Architecture
3.1 Focus on Agent Interoperability
4.4 Service Directory Services
4.6 Agents Send Messages to Other Agents
4.7 Providing Message Validity and Encryption
4.8 Providing Interoperability
5.1.1 Classification of Elements
5.1.4 Format of Element Description
5.2.2 Relationships to Other Elements
5.3.2 Relationships to Other Elements
5.4 Agent Communication Language
5.4.2 Relationships to Other Elements
5.5.2 Relationships to Other Elements
5.6.2 Relationships to Other Elements
5.7.2 Relationships to Other Elements
5.8.2 Relationships to Other Elements
5.9.2 Relationships to Other Elements
5.10.2 Relationships to Other Elements
5.11.2 Relationships to Other Elements
5.12.2 Relationships to Other Elements
5.13.2 Relationship to Other Elements
5.14.2 Relationship to Other Elements
5.15.2 Relationships to other elements
5.16 Message Transport Service
5.16.2 Relationships to Other Elements
5.17.2 Relationships to Other Elements
5.18.2 Relationships to Other Elements
5.19.2 Relationships to Other Elements
5.20.2 Relationships to Other Elements
5.21.2 Relationships to Other Elements
5.22.2 Relationships to Other Elements
5.23 Services Directory Service
5.23.2 Relationships to Other Elements
5.24.2 Relationships to other elements
5.25 Service Location Description
5.25.2 Relationships to Other Elements
5.26.2 Relationships to Other Elements
5.27.2 Relationships to Other Elements
5.28.2 Relationships to Other Elements
5.29.2 Relationships to Other Elements
5.30.2 Relationships to Other Elements
5.31.2 Relationships to Other Elements
5.32.2 Relationships to Other Elements
5.33.2 Relationships to Other Elements
5.34 Transport Specific Address
5.34.2 Relationships to Other Elements
5.35 Transport Specific Property
5.35.2 Relationships to Other Elements
5.36.2 Relationships to Other Elements
6 Agent and Agent Information Model
6.2 Transport Message Relationships
6.3 Agent Directory Entry Relationships
6.4 Service Directory Entry Relationships
6.6 Message Transport Elements
8 Informative Annex A — Goals of Service Model
9 Informative Annex B — Goals of Message Transport Service Abstraction
9.3 Support for Alternative Transports within a Single System
9.4 Desirability of Transport Agnosticism
9.5 Desirability of Selective Specificity
9.6 Connection-Based, Connectionless and Store-and-Forward Transports
9.7 Conversation Policies and Interaction Protocols