2009-06-04T14:58:49Z

Nickdrummond: /* Manchester OWL syntax */

Back to [[Protege4UserDocs]]

__TOC__

= DL Query tab =

[[Image:Protege4DLQueryTab.gif|left|thumb]]
The DL Query tab provides a powerful and easy-to-use feature for searching a classified ontology. It is a standard Protégé 4 plugin, available both as a tab and also as a view widget that can be positioned into any other tab. The query language (''class expression'') supported by the plugin is based on the Manchester OWL syntax, a user-friendly syntax for OWL DL that is fundamentally based on collecting all information about a particular class, property, or individual into a single construct, called a frame.

 

== Getting started ==

[[Image:UnclassifiedVsClassifiedOntology.gif|right]]

If the DL Query tab is unavailable in your Protégé workspace, make sure the DL Query item in the Tabs menu is checked. Alternatively, you can add the Query view widget to any other tab by selecting '''View | Misc views | Query''' and then placing the widget anywhere in a layout.

You can only execute a query on a classified ontology. Before attempting to execute a query, run a classifier:

* Ensure that one of the built-in reasoners (a.k.a classifiers) is selected. From the Reasoner menu, select FaCT++ or Pellet. When you first select a reasoner, the active ontology will be classified. You can also select '''Reasoner | Classify...''' to classify again at any time.
* Validate that your ontology is classified by selecting the Entities tab and then the Inferred Class Hierarchy tab that appears in the class hierarchy view. It should contain classes that sub-class Thing. If you see only the root class, Thing, your ontology may not be classified. Following is an example comparing what an Inferred Class Hierarchy looks like before and after classification.

* Once you've validated that your ontology is classified, you can execute a query.

 

== Individual query examples ==

[[Image:DLQueryResults.gif|right]]
[[Image:DLQueryIndividualsOfAClass.gif|right]]

Suppose we have an ontology like this:

* Class:
** Person
* Data Properties:
** hasGivenName
** hasSurname

And suppose also that we have several hundred instances of class Person in our ontology. To find an individual named "Matthew", we could enter the following query:

'''hasGivenName value "Matthew"'''

But clicking on the execute button may not return any results. We also need to check the "Individuals" option. Any individuals found will then be displayed in the query results as shown below:

The following query would also be valid for the same result:

'''Person and hasGivenName value "Matthew"'''

We could also show all instances of person by simply providing the class in the query like this:

Of course, these are extremely simple queries; the Manchester syntax is much more capable.

Literal constants can be expressed with type by using ^^ and then the type:

'''hasAge value "21"^^long'''

Or, a more general expression that uses type:

'''hasAge some int'''

Following are just a few more examples to get you going:

'''hasChild some Man'''

'''hasSibling only Woman'''

'''hasCountryOfOrigin value England'''

'''hasChild min 3'''

'''hasChild exactly 3'''

'''hasChild max 3'''

 

== Class query examples ==

[[Image:Dl-query-equip-blur.png|right|400px]]
[[Image:Dl-query-lens.png|right|400px]]

Here are some examples of class queries that can be performed on the [http://www.co-ode.org/ontologies/photography/ ontology of photography] (work in progress).

Firstly, it can be useful to see which things classify "under" this expression.

'''Q: "Which equipment can reduce blur?"'''

We need to get the subclasses of the expression (or descendants if the hierarchy of equipment is deeper than 1 level):
Equipment and reduces some Blur

Then, we might be interested to see under which existing classes in our hierarchy a given class will classify:

'''Q: "What types of lens is a 35-120mm?"'''

We need to get the superclasses of the expression:
Lens and (hasMinEffectiveFocalLength value 35) and (hasMaxEffectiveFocalLength value 120)

Other examples might be:

'''Q: "Which adjustments can I use to increase the exposure without affecting the depth of field"'''

We need to get the subclasses of the expression:
Adjustment and increases some ExposureLevel and not(affects some DepthOfField)

 

== Saving a query in the ontology ==

[[Image:Dl_query_add_to_ontology.png|right|400px]]

This feature that will be available from build 105 onwards.

The DL Query tab becomes a useful way of testing a definition before creating appropriate classes.

If you find a particular query useful and would like to create a class to represent it you can now select '''Add to ontology'''.

This will create a defined class in the ontology and the dialog allows you to either name it or leave it as [[P4AnonymousClasses|anonymous]].

 

== Manchester OWL syntax ==

We have only provided a few simple examples here designed to help you understand how to use the DL Query tab and the Query view widget. To learn more about the Manchester syntax, check out these resources:

* [http://www.co-ode.org/resources/reference/manchester_syntax/ The Manchester Syntax] - describes the syntax for class expressions and is aimed at people who already know the previous Protege-OWL compact class expression syntax.
* [[media:Owled2008dc_paper_11.pdf‎|Manchester Syntax for OWL 1.1]] - a more detailed whitepaper (PDF) including revisions for OWL 1.1.
* [http://www.w3.org/2007/OWL/wiki/ManchesterSyntax Manchester Syntax for OWL 2] - the official OWL 2 working group note

DLQueryTab

2009-06-04T14:57:38Z

Nickdrummond: /* Manchester OWL syntax */

CompileProtege4InIntelliJ

2009-05-26T14:09:13Z

Nickdrummond: /* Running */

<div class="orangeBox">
Setup and Run P4.x in IntelliJ 
This page describes the simple steps required to setup P4.x for development in jetbrains [http://www.jetbrains.com/idea/ IntelliJ].
</div> 

Back to [[Protege4DevDocs]]

__TOC__

== Check out sources ==

Use an SVN client to checkout the Protege 4 trunk from SVN to a local directory (say ''trunk'').
svn co https://smi-protege.stanford.edu/repos/protege/protege4/protege-standalone/trunk/ trunk

If using IntelliJ to checkout the sources and it prompts you to create a new project, select '''No'''.

== Create the IntelliJ project files ==

Matthew Horridge has created a very easy to use tool to create a nice tidy intelliJ project.
You can download this from [http://www.co-ode.org/downloads/protege-x/Protege4IntelliJProjectBuilder.jar here].

* Open a command line

* Change directory into ''trunk''
cd trunk

* Run the command line tool (notice the current path - dot - is a parameter)
java -jar Protege4IntelliJProjectBuilder.jar .

* Open the project in IntelliJ

You should now have a multi-module project containing the various pieces of the core and owl editor, as well as several plugins that are part of the default distribution (DL Query, OWLViz, pellet and FaCT++)

== Building ==

Build the project the usual way. Some versions of IntelliJ may complain that the directory could not be created. Just try again and it should be built.

Build products are placed into the ''build/dist/equinox directory'', which is in the Protege trunk directory.

== Running ==

You can add a run configuration by specifying the following settings:

Main class: '''org.eclipse.core.runtime.adaptor.EclipseStarter'''
VM parameters: '''-Dosgi.clean=true'''
Working directory: '''<PATH TO PROTEGE TRUNK>/build/dist/equinox'''
Use classpath and JDK of module: '''runtime'''

See the screen shot below. It is particularly important that the working directory is set to be the equinox build directory and that the class path and JDK module be set to runtime.

[[Image:RunP4inIntelliJ.png]]

=== Troubleshooting ===

On running, if you have errors in your log window, check that a '''logs/''' directory exists in the '''equinox''' directory. If not, create an empty one.

Also, '''log4j.xml''' should exist in the '''equinox''' directory. If it does not then copy it from the root of your source directory.

2009-05-15T10:06:07Z

Nickdrummond: /* OWLViz */