Calo   Ontology: Browsing and Accessing the Ontology
 
 

Browsing and Accessing the CALO Ontology

There are at least four ways to access and browse the CALO ontology.

  • 1. Cognitive view of the ontology: The key entities in the office domain are: People, Projects, Tasks, Meetings, Emails, and Calendar. The CALO system learns relationships amongst these entities. A natural and the easiest way to access the ontology is to use the relational view of the user's world as an index. We have linked various sub sections of the ontology from a graphic showing the relational view. In the cognitive view, for each entity such as Task, we can see the relevant classes and relations applicable to it. You can access this view via the Cognitive View link.
  • 2. Browsing the ontology documentation: We maintain a collection of documentation file that are similar in style to the Javadoc style of documentation. These files are generated using a tool called Owldoc. In this documentation, there is a page for every single term in the ontology. For each term, we also show its relationship to other terms. For example, for a class, we show its subclasses, and applicable relations. View the owldoc pages by clicking on the links labeled Owldocs on the Ontology Map.
  • 3.Browsing the ontology source files: We distribute the source code for the whole ontology as a collection of OWL files. There is hierarchical relationship amongst these files. These files can be loaded into Protege for browsing either in isolation or by loading all the referenced OWL files. You can access these source files clicking on the .owl links (e.g. abstractTask.owl, bindingPaths.owl, core-plus-office.owl etc) on the Ontology Map. Alternatively, if you have access to the cvs sources for iris, you can find them in the iris/data/ directory.
  • 4.Ontology Usage Documentation: The ontology usage documentation (may take several seconds to load) is primarily aimed at IRIS developers. It specifies the Java level APIs for accessing and updating the knowledge in the knowledge base. It can also tell you what parts of IRIS use what ontology components.