Protege4TutorialErrata

Protege 4.x Tutorial Errata

This page contains a list of errata for the current Protege 4.x version of the Protege-OWL Tutorial.

Protege 4.x is under heavy development so it is difficult to keep such a comprehensive document completely up-to-date. If you find that the most recent version is not in sync with the tutorial, please add to this page to describe the problem (and a solution if you have one). We can then use this page when we incrementally update the tutorial and your contributions will allow this to be done more easily.

Back to Protege4UserDocs

Protege-OWL Tutorial Edition 1.1

Misleading or out of date

Please give a location of the error where possible (page number, section/paragraph, figure number etc).

Location	Error
page 29, Exercise 10, step 4	requires rewording. Follow the same procedure as step 2, but select isBaseOf. If isBaseOf does not exist it can be created within the dialog by selecting isIngredientOf and pressing the add sub property button.
page 42, Exercise 16, step 2	Subclass Of should be Superclasses. see #Terminology.
page 56, Figure 4.44	out of date. see #Terminology.
page 57, Exercise 29, steps 3 & 5	see #Drag_and_Drop_support. Use cut and paste (in the Edit menu or using keyboard shortcuts) to move restrictions.

General notes about the tutorial

Terminology

Some references to the class description view currently use slightly different terminology from the current release. The tutorial is in line with Protege 3.x terminology, whereas the Protege 4.x environment has intentionally used the terminology of the OWL 1.1 specification.

Therefore, in the tutorial when the term Necessary Conditions is used it is synonymous with Superclasses in the Class Description View. Also, in the tutorial when the term Necessary & Sufficient is used it is synonymous with Equivalent classes in the Class Description View.

Some screenshots of the view may need to be updated to reflect this.

Drag and Drop support

Much of the drag and drop support has temporarily been removed as many people were finding it easy to perform operations by mistake while moving around the interface. It is likely that we will re-implement this once we can work out way around these problems. Drag and Drop is still available in the entity hierarchy views (eg for "moving classes" to a new superclass), but has been replaced in favour of cut and paste within other views (eg the class description view).

Minor Typos

Location	Typo
page 21, Exercise 6, steps 1 & 2	hierarchy misspelled twice.