Distinctive categories of COBRA-ONT ontologies are grouped into different RDF/XML documents. Key ontology categories are action, agent, time, space, device, document, meeting, and UMBC.
| Action Ontologies (5 of 31) |
|
defines the top-level classes that represent different types of actions |
|
defines an intentional action that represents an agent's intention to adjust the room lighting |
|
defines an intentional action that represents an agent's intention to book a meeting room |
|
defines an intentional action that represents an agent's intention to set up Power Point presentations |
|
defines a doable action that represents the participation of an agent at a meeting |
| Agent Ontologies (5 of 31) |
|
defines the top-level classes that represent human and software agents |
|
defines a subset of the FOAF ontology |
|
defines an ontology for describing roles and associated actions |
|
defines an ontology for describing FIPA software agents |
|
defines typical concepts for describing people in an academia environment |
| Time Ontologies (2 of 31) |
|
defines an ontology for describing calendar dates and clock time. Based on the DAML-Time and Time Entry ontology. |
|
defines an ontlogy for describing time instant, interval, and temporal relations. Based on the DAML-Time and Time Entry ontology. |
| Device Ontologies (2 of 31) |
|
defines an ontology for describing devices profiles (extended from the FIPA device ontology) |
|
defines an ontology for describing popular personal devices and associated properties |
| Space Ontologies (4 of 31) |
|
defines a simple spatial ontology based on the part-whole relations |
|
defines the ontology for describing spatial entities and relations based on the OpenCyc spatial ontology |
|
defines the ontology for describing spatial entities and relations using terms from the Region Connection Calculus (RCC) |
|
defines the ontology for describing the spatial and temporal properties of physical objects (e.g., people, devices) |
| UMBC Ontologies (3 of 31) |
|
defines an example ontology about the UMBC campus (e.g., its location, departments) |
|
|
defines an example ontology about the Information Technology/Engineering (ITE) building at UMBC (e.g. rooms and floors in the building) |
|
|
defines an example ontology about the Engineering and Computer Science (ECS) building at UMBC (e.g., rooms and floors in the building) |
| Meeting Ontologies (2 of 31) |
|
defines an ontology for describing meetings (extends the ITTalks talk ontology v2.1) |
|
defines an ontology for describing demo sessions, which is a special type of meeting |
| Document Ontologies (4 of 31) |
|
defines an ontology for describing digital documents |
|
defines an ontology for describing digital image documents, which is a special type of document |
|
defines an ontology for describing digital photos, which is a special type of image document |
|
defines an ontology for describing MS PowerPoint documents, which is a special type of document. |
| CoBrA System Ontology (4 of 31) |
|
an ontology for supporting agent communication. Typically this ontology is used by agents to compose ACL content messages for communicating with a Context Broker |
|
an ontology that is intended to be used by the internal implementation of a Context Broker |
|
an ontology for describing the runtime configuration of a Context Broker |
|
an ontology for supporting agent communication. Typically this ontology is used in conjection with the broker-comm to define ACL content messages for communicating with a Context Broker. For example, requesting a Context Broker to inform an agent about a person's location context or user profile. |
The following documents only applies to COBRA-ONT v0.4. They are useful for understanding the role of COBRA-ONT and should not be used as an user guide for building applications.
