| Description: |
interfaces and software design patterns. The FIPA-OS architecture can be envisaged as a non-strict layered model, supported by an underlying component model (Figure 1.3). In a non-strict layered model, entities in nonadjacent layers can access each other directly. The developer is able to extend the architecture not only by appending value-added layers, such as specialist service agents or facilitator agents, but in addition, lower or mid-layers can be replaced, modified or deleted. Figure 1.3 A schematic diagram of the FIPA-OS architecture 1.4.5.1 Agent shell There are a variety of ways in which new agents can be added to FIPA-OS platforms. Agents can be built using different types of agent shell. Agent developers can also create agents without using FIPA-OS services; provided these `non-resident' agents support a transport protocol supported by FIPA-OS, they can use FIPA-OS to interact with other IPTM ACL DF FIPA Agent Platform AMS FIPA-OS Service and User Agents ACL parser Conversation managers Content parsers Ontologies Persistence Diagnostics Visualisation Configuration Agent shells Transport protocols Profiles Agent Technology for Communications Infrastructure 16 agents on the platform. Non-resident agents can use or invoke the transport API of the platform directly or use their own non-platform transport. 1.4.5.2 Multi-tiered ACL communication Understanding an ACL message requires processing the message with regard to its temporal position within a particular interaction sequence between two or more agents. This involves understanding the type of communication called a communication act (which is specified in the message, e.g. a request, statement of fact, or query), understanding the structure of the content and finally understanding the . |