|
|||||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||||
| Classes in zeus.concepts used by Default Package | |
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| Classes in zeus.concepts used by JADE_SL | |
| FIPAParser
|
|
| FIPAPerformative
FIPAPerformative extends the performative class so that when getReceivers() is called it converts the values in the vector into strings from FIPA_AID_Addresses. |
|
| Classes in zeus.concepts used by JADE_SL.onto.basic | |
| FIPA_AID_Address
FIPA_AID_Address is an implementation of the Address interface that is used to hold addresses of agents that have identified themselves with FIPA format aid's ISSUES Resolvers: we don't do them yet, and we might need to. |
|
| Classes in zeus.concepts used by zeus.actors | |
| AbilityDbItem
AbilityDbItem is a conveinience class for holding the items that will be put in the agents AbilityDb Change Log ------------ Simon put a () init method in so that this could be extended gracefully. |
|
| AbilitySpec
Change Log ---------- 07/06/01 () init added 21/06/02 - DAML-S changes 26/9/02 - DAML-s changes back - moved to a name so that a URL can be generated that is used in the service registration |
|
| Address
Address is a pure virtual class because we need to deal with Zeus based port and socket addressing, and FIPA GUI addressing, and any bizzar LEAP or Biz talk addressing that is implemented in the future |
|
| AddressBook
|
|
| AttributeList
|
|
| Bindings
|
|
| BindResults
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| MessageAction
|
|
| MessageRule
MessageRule is an interface that is implemented by MessageRuleImpl. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| PlannerEnactStruct
|
|
| PlannerQueryStruct
|
|
| PrimitiveTask
PrimativeTask is the representation that the Agent Generator uses to store task specifications and write them into Java using the TaskWriter |
|
| ProtocolInfo
|
|
| ReportRec
|
|
| ResourceItem
|
|
| StrategyInfo
|
|
| SummaryTask
|
|
| SuppliedDb
|
|
| SuppliedItem
|
|
| SuppliedRequester
|
|
| Task
|
|
| TaskLink
|
|
| TaskNode
|
|
| Classes in zeus.concepts used by zeus.actors.event | |
| AbilityDbItem
AbilityDbItem is a conveinience class for holding the items that will be put in the agents AbilityDb Change Log ------------ Simon put a () init method in so that this could be extended gracefully. |
|
| AbilitySpec
Change Log ---------- 07/06/01 () init added 21/06/02 - DAML-S changes 26/9/02 - DAML-s changes back - moved to a name so that a URL can be generated that is used in the service registration |
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| MessageRule
MessageRule is an interface that is implemented by MessageRuleImpl. |
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| ProtocolInfo
|
|
| Relationship
|
|
| ResourceItem
|
|
| StrategyInfo
|
|
| Task
|
|
| Classes in zeus.concepts used by zeus.actors.graphs | |
| AbilitySpec
Change Log ---------- 07/06/01 () init added 21/06/02 - DAML-S changes 26/9/02 - DAML-s changes back - moved to a name so that a URL can be generated that is used in the service registration |
|
| BindResults
|
|
| PlannerQueryStruct
|
|
| Classes in zeus.concepts used by zeus.actors.intrays | |
| Address
Address is a pure virtual class because we need to deal with Zeus based port and socket addressing, and FIPA GUI addressing, and any bizzar LEAP or Biz talk addressing that is implemented in the future |
|
| FIPA_AddressBook
FIPA_AddressBook is an extention of the addressbook that can cope with fipa AID addresses, the intention is that this should be used to implement an ACC agent that can act as a gateway from Zeus agencies to the FIPA world. |
|
| FIPA_AID_Address
FIPA_AID_Address is an implementation of the Address interface that is used to hold addresses of agents that have identified themselves with FIPA format aid's ISSUES Resolvers: we don't do them yet, and we might need to. |
|
| FIPAPerformative
FIPAPerformative extends the performative class so that when getReceivers() is called it converts the values in the vector into strings from FIPA_AID_Addresses. |
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| ZeusParser
|
|
| Classes in zeus.concepts used by zeus.actors.outtrays | |
| Address
Address is a pure virtual class because we need to deal with Zeus based port and socket addressing, and FIPA GUI addressing, and any bizzar LEAP or Biz talk addressing that is implemented in the future |
|
| FIPA_AID_Address
FIPA_AID_Address is an implementation of the Address interface that is used to hold addresses of agents that have identified themselves with FIPA format aid's ISSUES Resolvers: we don't do them yet, and we might need to. |
|
| FIPAPerformative
FIPAPerformative extends the performative class so that when getReceivers() is called it converts the values in the vector into strings from FIPA_AID_Addresses. |
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| Classes in zeus.concepts used by zeus.actors.rtn | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| PlannerQueryStruct
|
|
| RoutingRecord
|
|
| Classes in zeus.concepts used by zeus.actors.rtn.util | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| Classes in zeus.concepts used by zeus.agents | |
| AbilityDbItem
AbilityDbItem is a conveinience class for holding the items that will be put in the agents AbilityDb Change Log ------------ Simon put a () init method in so that this could be extended gracefully. |
|
| AbstractTask
this interface is instantiatied by a number of different types of task, and is used to store user defined parameters and info that are entered into the task at design time using the Zeus Agent Generator tool CHANGE LOG 20/9/02 added a description field to let users put in a description of the task for some use cases; this information is used by the service description system I have added some feilds and client methods to the class to collect service description information, I think that this is the right place to do it because while the Zeus reasoner only looks at plan atoms (primitive tasks) in an open environment the ability to write service descriptions for reactive tasks may be useful, so this interface provides the common root that the two subclasses can inheret the functionality from. |
|
| AddressEvent
|
|
| AddressListener
|
|
| AMS_Description
AMS_Description holds a description of an AMS as per fipa |
|
| DF_Description
df_Description holds a description of an df as per fipa |
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| ProtocolInfo
|
|
| ReteKB
this is the definition of a kb in Zeus for the Rulebase tasks. |
|
| Classes in zeus.concepts used by zeus.agentviewer | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.agentviewer.acquaintances | |
| AbilitySpec
Change Log ---------- 07/06/01 () init added 21/06/02 - DAML-S changes 26/9/02 - DAML-s changes back - moved to a name so that a URL can be generated that is used in the service registration |
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.agentviewer.mail | |
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| Classes in zeus.concepts used by zeus.agentviewer.msghandler | |
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| Classes in zeus.concepts used by zeus.agentviewer.protocol | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| StrategyInfo
|
|
| Classes in zeus.concepts used by zeus.agentviewer.resources | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.agentviewer.task | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Ordering
Ordering is used in the task chaining process for PrimitiveTasks ChangeLog --------- 07 -06 -01 Simon adds () init for extensibility |
|
| PrimitiveTask
PrimativeTask is the representation that the Agent Generator uses to store task specifications and write them into Java using the TaskWriter |
|
| Classes in zeus.concepts used by zeus.concepts | |
| AbilityDbItem
AbilityDbItem is a conveinience class for holding the items that will be put in the agents AbilityDb Change Log ------------ Simon put a () init method in so that this could be extended gracefully. |
|
| AbilitySpec
Change Log ---------- 07/06/01 () init added 21/06/02 - DAML-S changes 26/9/02 - DAML-s changes back - moved to a name so that a URL can be generated that is used in the service registration |
|
| AbstractTask
this interface is instantiatied by a number of different types of task, and is used to store user defined parameters and info that are entered into the task at design time using the Zeus Agent Generator tool CHANGE LOG 20/9/02 added a description field to let users put in a description of the task for some use cases; this information is used by the service description system I have added some feilds and client methods to the class to collect service description information, I think that this is the right place to do it because while the Zeus reasoner only looks at plan atoms (primitive tasks) in an open environment the ability to write service descriptions for reactive tasks may be useful, so this interface provides the common root that the two subclasses can inheret the functionality from. |
|
| Acquaintance
|
|
| Address
Address is a pure virtual class because we need to deal with Zeus based port and socket addressing, and FIPA GUI addressing, and any bizzar LEAP or Biz talk addressing that is implemented in the future |
|
| AddressBook
|
|
| AddressEvent
|
|
| AddressListener
|
|
| AgentDescription
|
|
| AMS_Description
AMS_Description holds a description of an AMS as per fipa |
|
| ASCII_CharStream
An implementation of interface CharStream, where the stream is assumed to contain only ASCII characters (without unicode processing). |
|
| AttributeList
|
|
| Bindings
|
|
| BindingsRecord
|
|
| ConditionalNode
|
|
| ConsumerRecord
|
|
| ContentElement
|
|
| DF_Description
df_Description holds a description of an df as per fipa |
|
| DuplicationTable
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| FactDescription
|
|
| FactSummary
|
|
| FIPA_AID_Address
FIPA_AID_Address is an implementation of the Address interface that is used to hold addresses of agents that have identified themselves with FIPA format aid's ISSUES Resolvers: we don't do them yet, and we might need to. |
|
| FIPA_AMS_Management_Content
|
|
| FIPA_AP_Description
|
|
| FIPA_DF_Management_Content
this class is used to construct and store content if the FIPA Agent Management ontology that is either to be passed to, or from the DF |
|
| FIPA_MTP_Description
FIPA_MTP_Description is used to store the result of parsing a mtp-description fragment. |
|
| FIPA_Property
|
|
| FIPA_Received
FIPA_Received is used to store the stamps that FIPA says you should be able to attach to the various messages that they allow |
|
| FIPA_Search_Constraints
|
|
| FIPA_Service_Description
provide a datatype that is used to hold the service descriptions and provide matching services for them |
|
| FIPA_Transport_Profile
FIPA_Transport_Profile is used to store the results of parsing transport profiles, and to generate a string (with toString()) which can be sent to FIPA agent platforms. |
|
| FIPAParser.JJCalls
|
|
| FIPAParserConstants
|
|
| FIPAParserTokenManager
|
|
| FIPAPerformative
FIPAPerformative extends the performative class so that when getReceivers() is called it converts the values in the vector into strings from FIPA_AID_Addresses. |
|
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| GoalSummary
|
|
| MessageAction
|
|
| MessagePattern
|
|
| MessageRule
MessageRule is an interface that is implemented by MessageRuleImpl. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| OntologyParserConstants
|
|
| OntologyParserTokenManager
|
|
| Ordering
Ordering is used in the task chaining process for PrimitiveTasks ChangeLog --------- 07 -06 -01 Simon adds () init for extensibility |
|
| ParseException
This exception is thrown when parse errors are encountered. |
|
| Parser.JJCalls
|
|
| ParserConstants
|
|
| ParserTokenManager
|
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| PerformativeParserConstants
|
|
| PerformativeParserTokenManager
|
|
| PlanScript
PlanScripts are (I think) a set of tasks chained together to form a meta task |
|
| PrimitiveTask
PrimativeTask is the representation that the Agent Generator uses to store task specifications and write them into Java using the TaskWriter |
|
| ProducerRecord
|
|
| ProtocolInfo
|
|
| Reference
|
|
| Relationship
|
|
| ReportRec
|
|
| ReservationEntry
|
|
| ResolutionContext
|
|
| Restriction
|
|
| RestrictionParser.JJCalls
|
|
| RestrictionParserConstants
|
|
| RestrictionParserTokenManager
|
|
| ReteKB
this is the definition of a kb in Zeus for the Rulebase tasks. |
|
| RoutingRecord
|
|
| SimpleCharStream
An implementation of interface CharStream, where the stream is assumed to contain only ASCII characters (without unicode processing). |
|
| StrategyInfo
|
|
| Summary
|
|
| SummaryTask
|
|
| SuppliedDb
|
|
| SuppliedItem
|
|
| SuppliedRequester
|
|
| Task
|
|
| TaskLink
|
|
| TaskNode
|
|
| TaskSummary
|
|
| Token
Describes the input token stream. |
|
| Classes in zeus.concepts used by zeus.concepts.fn | |
| Bindings
|
|
| DuplicationTable
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| ResolutionContext
|
|
| Classes in zeus.concepts used by zeus.generator | |
| AbstractTask
this interface is instantiatied by a number of different types of task, and is used to store user defined parameters and info that are entered into the task at design time using the Zeus Agent Generator tool CHANGE LOG 20/9/02 added a description field to let users put in a description of the task for some use cases; this information is used by the service description system I have added some feilds and client methods to the class to collect service description information, I think that this is the right place to do it because while the Zeus reasoner only looks at plan atoms (primitive tasks) in an open environment the ability to write service descriptions for reactive tasks may be useful, so this interface provides the common root that the two subclasses can inheret the functionality from. |
|
| AgentDescription
|
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.generator.agent | |
| AbilitySpec
Change Log ---------- 07/06/01 () init added 21/06/02 - DAML-S changes 26/9/02 - DAML-s changes back - moved to a name so that a URL can be generated that is used in the service registration |
|
| Acquaintance
|
|
| AgentDescription
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| ProtocolInfo
|
|
| Classes in zeus.concepts used by zeus.generator.code | |
| AgentDescription
|
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| PrimitiveTask
PrimativeTask is the representation that the Agent Generator uses to store task specifications and write them into Java using the TaskWriter |
|
| ReteKB
this is the definition of a kb in Zeus for the Rulebase tasks. |
|
| Classes in zeus.concepts used by zeus.generator.event | |
| AbstractTask
this interface is instantiatied by a number of different types of task, and is used to store user defined parameters and info that are entered into the task at design time using the Zeus Agent Generator tool CHANGE LOG 20/9/02 added a description field to let users put in a description of the task for some use cases; this information is used by the service description system I have added some feilds and client methods to the class to collect service description information, I think that this is the right place to do it because while the Zeus reasoner only looks at plan atoms (primitive tasks) in an open environment the ability to write service descriptions for reactive tasks may be useful, so this interface provides the common root that the two subclasses can inheret the functionality from. |
|
| AgentDescription
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Classes in zeus.concepts used by zeus.generator.task | |
| AbstractTask
this interface is instantiatied by a number of different types of task, and is used to store user defined parameters and info that are entered into the task at design time using the Zeus Agent Generator tool CHANGE LOG 20/9/02 added a description field to let users put in a description of the task for some use cases; this information is used by the service description system I have added some feilds and client methods to the class to collect service description information, I think that this is the right place to do it because while the Zeus reasoner only looks at plan atoms (primitive tasks) in an open environment the ability to write service descriptions for reactive tasks may be useful, so this interface provides the common root that the two subclasses can inheret the functionality from. |
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| PrimitiveTask
PrimativeTask is the representation that the Agent Generator uses to store task specifications and write them into Java using the TaskWriter |
|
| SummaryTask
|
|
| Task
|
|
| TaskLink
|
|
| TaskNode
|
|
| Classes in zeus.concepts used by zeus.generator.task.rulebase | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| ReteKB
this is the definition of a kb in Zeus for the Rulebase tasks. |
|
| Classes in zeus.concepts used by zeus.generator.util | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.gui.dialog | |
| Acquaintance
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| Task
|
|
| Classes in zeus.concepts used by zeus.ontology | |
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.ontology.attributes | |
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.ontology.database | |
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.ontology.facts | |
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.ontology.restrictions | |
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.rete | |
| Bindings
|
|
| DuplicationTable
|
|
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| ReteKB
this is the definition of a kb in Zeus for the Rulebase tasks. |
|
| Classes in zeus.concepts used by zeus.rete.action | |
| Fact
The Fact class is key conceptual data structure in ZEUS, since Fact objects store the information that collectively forms the application ontology. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Classes in zeus.concepts used by zeus.util | |
| TransportConfig
this class is used to load the configuration info for the various FIPA transports that could be set for Zeus. |
|
| Classes in zeus.concepts used by zeus.visualiser.basic | |
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| Classes in zeus.concepts used by zeus.visualiser.control | |
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| SummaryTable
|
|
| Classes in zeus.concepts used by zeus.visualiser.report | |
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| ReportRec
|
|
| Classes in zeus.concepts used by zeus.visualiser.society | |
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
| Relationship
|
|
| Classes in zeus.concepts used by zeus.visualiser.statistics | |
| Goal
The Goal class is an important agent-level conceptual data structure. |
|
| OntologyDb
This implements the Ontology Database component, which has two main roles: database - to store the conceptual descriptions that make up an ontology factory - to create new Fact objects from the stored fact descriptions
Aside from the fact creation and query methods, developers are unlikely to
need the other methods of this class.
|
|
| Performative
The Performative class provides a standard data structure for inter-agent messaging. |
|
|
|||||||||||
| PREV NEXT | FRAMES NO FRAMES | ||||||||||