From Protege Wiki
Revision as of 10:04, May 16, 2014 by JenniferVendetti (talk | contribs) (Getting started: updated menu path for finding the dl query tab)

Jump to: navigation, search

Back to Protege4UserDocs

DL Query tab


The DL Query tab provides a powerful and easy-to-use feature for searching a classified ontology. It comes with the standard distribution of Protégé Desktop (versions 4.x and above), 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


If the DL Query tab is unavailable in your Protégé workspace, make sure the DL Query item in the Window | 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


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


Here are some examples of class queries that can be performed on the 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

Dl query add to ontology.png

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 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: