Difference between revisions of "Using Reasoners"

From Protege Wiki
Jump to: navigation, search
(New page: <br /> <span style="font-size:18px; font-weight:bold;">Using DL reasoners in Protege-OWL</span> <em>This tutorial assumes a basic working knowledge of Protege-OWL. Please refer first to ...)
 
Line 3: Line 3:
  
  
<em>This tutorial assumes a basic working knowledge of Protege-OWL. Please refer first to the [http://www.co-ode.org/resources/tutorials/ProtegeOWLTutorial.pdf| Protege-OWL Tutorial] section 4.9 Using a Reasoner. This page explains some additions (e.g. the direct reasoner) that occurred after the publication of the Protege-OWL tutorial.</em>
+
<em>This tutorial assumes a basic working knowledge of Protege-OWL. Please refer first to the [http://www.co-ode.org/resources/tutorials/ProtegeOWLTutorial.pdf Protege-OWL Tutorial] section "4.9 Using a Reasoner". This page explains some additions (e.g. the direct reasoner) that occurred after the publication of the Protege-OWL tutorial.</em>
  
  
 
__TOC__
 
__TOC__
 +
 +
== Using the DIG Reasoner ==
 +
 +
=== Getting the DIG-compliant reasoner ===
 +
 +
First, you need to make sure that you have downloaded a DIG compliant reasoner, such as:
 +
 +
* [http://pellet.owldl.com Pellet]  -  open source, implemented in Java
 +
* [http://owl.man.ac.uk/factplusplus Fact++]  -  open source, implemented in C++
 +
* [http://www.racer-systems.com/RacerPro RacerPro]  -  commercial
 +
* [http://kaon2.semanticweb.org KAON2]  -  commercial, free of charge for universities and for noncommecial academic usage
 +
 +
Second step is to install the reasoner and start the DIG HTTP service. Please read the documentation of the reasoner to see how to start the DIG service.
 +
 +
=== Configure the DIG reasoner URL ===
 +
 +
Then you need to configure the port on which the reasoner DIG service is running. The most common port used by the reasoner is 8080, and that is also the default configuration for Protege-OWL. If the reasoner runs on this port (which you can usually figure out from the console window in which the reasoner is running), then you can skip this step. If however, the reasoner runs on a different port (e.g. '''Pellet runs by default on 8081'''), then you need to do the following steps:
 +
 +
Go to the '''OWL Menu -> Preferences -> General Tab''' and in the Reasoner URL text field adjust the URL and port on which the reasoner is running.
 +
 +
For example, if Pellet would run on localhost and port 8081, then the reasoner URL should be:<nowiki> http://localhost:8081</nowiki>.

Revision as of 16:03, April 18, 2008


Using DL reasoners in Protege-OWL


This tutorial assumes a basic working knowledge of Protege-OWL. Please refer first to the Protege-OWL Tutorial section "4.9 Using a Reasoner". This page explains some additions (e.g. the direct reasoner) that occurred after the publication of the Protege-OWL tutorial.


Using the DIG Reasoner

Getting the DIG-compliant reasoner

First, you need to make sure that you have downloaded a DIG compliant reasoner, such as:

  • Pellet - open source, implemented in Java
  • Fact++ - open source, implemented in C++
  • RacerPro - commercial
  • KAON2 - commercial, free of charge for universities and for noncommecial academic usage

Second step is to install the reasoner and start the DIG HTTP service. Please read the documentation of the reasoner to see how to start the DIG service.

Configure the DIG reasoner URL

Then you need to configure the port on which the reasoner DIG service is running. The most common port used by the reasoner is 8080, and that is also the default configuration for Protege-OWL. If the reasoner runs on this port (which you can usually figure out from the console window in which the reasoner is running), then you can skip this step. If however, the reasoner runs on a different port (e.g. Pellet runs by default on 8081), then you need to do the following steps:

Go to the OWL Menu -> Preferences -> General Tab and in the Reasoner URL text field adjust the URL and port on which the reasoner is running.

For example, if Pellet would run on localhost and port 8081, then the reasoner URL should be: http://localhost:8081.