OwlEd for MaMaS

An OWL Manager for the Match Maker Service

Valid XHTML 1.0 Transitional Valid CSS! Website statistics

Implementation Details
When started, the tool displays the GUI shown in Figure 1, where users can see the three main components of the OwlEd GUI:

OwlEd Screenshot
Figure 1

  1. toolbars that allow to access to various functions;
  2. tool panels, which make possible the management of both all objects in the selected ontology and inference services;
  3. the main panel where either objects information are displayed or other editing components are provided.
Using the first toolbar a. it possible to access to the following functions:
  1. create, open and save an ontology;
  2. cut, copy and paste the selected object;
  3. upload kb to reasoner, check ontology consistency and other reasoner interacting functions;
  4. each toggle button of this Extra Toolbar corresponds to a particular panel (Class editor, Properties Editor, Instance editor, Asks Editor) in the central area, which can be displayed selecting the corresponding button.
The second component b. is a MicrosoftOutlook-like toolbar. It stacks components and allows only one element of the stack being visible at a given time. In this way browsing, selecting or accessing an ontology object (Class, Property, Instance) with few mouse click is possible (this Swing component is part of L2Fprod Common Components).

Ontology editing and managing in OwlEd is performed using Jena2.33 API. OwlEd provides a comprehensive mapping between its extended API and the standard Jena library. OwlEd can also export the knowledge base into RDF and DIG XML formats.

In order to dynamically add new features, OwlEd is endowed of a small plug-in framework inspired to MJPF and it is based on the concept of entry point. Each plug-in may provide one or more entry points that will be initialized at starting time. The framework implements a runtime engine dynamically discovering and running plug-ins. By adding a plug-in it is possible to customize OwlEd and add new features without recompiling the code. For example is possible to add the support to new reasoners, with corresponding new inferences (standard or non standard) and macros, new entry in the Extra Toolbar, new menu entries, new panel in the preferences dialog, access to all the components of the active Knowledge Base.

OwlEd has been designed and implemented to interact with a DIG 1.1 compliant reasoner in an intuitive way. The Asks Editor is fully graphical, hence the complexity of DIG/XML editing is hidden and users can ask the reasoner to execute one or more inferences (see Figure 2) and results are graphically shown (see Figures 3,4,5,6). Nevertheless OwlEd provides a DIG console to interact with a DIG-based reasoner by editing the XML code. DIG handling and reasoner interaction is provided with our DIG4J APIs package written from scratch on top of DOM4J. We found this approach more flexible and easy to use than DIG Interface Implementation provided at http://dig.sourceforge.net/.

Copyright (C) 2012 SisInf Research Group All rights reserved.