How
to use OWLFCAView Tab plug-in
(For Protégé OWL
Ontology)
The OWLFCAView
Tab plug-in
provides Protégé-2000 users a novel way to visualize their OWL ontologies using the formal concept analysis (FCA)
technique. In current specification, we developed a property-oriented way for
the visualization of OWL ontology in Protégé-2000.
First
of all, please make sure that you are using Protégé-3.1 version. We assume that
you are familiar with how to configure a tab plug-in in Protégé platform.
We
use an OWL ontology “pizza.owl” that is also example
project used in Protégé OWL plug-in to demonstrate how to use OWLFCAView Tab plug-in. After opening the example project
and configuring the “OWLFCAView Tab”, you would see
the following figure.
At left panel, you would see a button Start… and a textarea for processing guidance. To start processing, please click the button Start… and then you would see the following figure.
A list of the properties of the Pizza ontology is displayed in a panel for selection. Assume that we are interested in the property “hasTopping”, and make it selected. After clicking OK button. And then you could see the following figure.
A list of the domain classes of property “hasTopping” is displayed in a panel for selection. Assume that we are interested in the class “NamedPizza”, and make it selected. And then after clicking OK button, you would see the following figure.
A panel for restriction type selection is displayed (In textarea at left panel, you could also see some message about all subclasses of the class NamedPizza that is used as the formal objects). You could select one of three types including “AllValuesFrom”, “SomeValuesFrom” and “Others”. Assume that we are interested in the type “SomeValuesFrom” and make it selected. And then after clicking OK button, you would see a formal context was formed in a cross table as follows.
In this formal context, all subclasses of selected domain class “NamedPizza” are used as formal objects and all fillers of the restriction SomeValuesFrom of the property “hasTopping” are used as formal attributes. The cross markers in the table show the binary relations between objects and attributes.
By
clicking the fifth button above the cross table (Build Lattice), you would see a lattice
diagram of the formal context as follows.
For selection of the domain class, the users should select a class that has subclasses because we use the subclasses of a selected class as the formal objects. When a class without the subclasses is selected, a warning panel is displayed to warn the users to select another class again.
For restriction type AllValuesFrom selection, the unionRangeClasses of the selected property are used as the formal attributes.
For restriction type Others selection, the fillers of the restrictions that are not AllValuesFrom type and SomeValuesFrom type of the selected property are used as the formal attributes.
In
current step, we think we only developed a basic model. Several advanced models
are under active development.
Any
questions, please contact Guoqian Jiang
( guoqian@med.hokudai.ac.jp
).
August,
2005