Difference between revisions of "Protege4TutorialErrata"
(→Misleading or out of date) |
(→Misleading or out of date) |
||
| Line 38: | Line 38: | ||
| valign="top" style="border-bottom:1px dashed #BC8F8F;" | page 70, Exercises 36 & 37 | | valign="top" style="border-bottom:1px dashed #BC8F8F;" | page 70, Exercises 36 & 37 | ||
| valign="top" style="border-bottom:1px dashed #BC8F8F;" | There is currently no action for automatically creating closure axioms. This operation must be performed by hand as per exercise 35. | | valign="top" style="border-bottom:1px dashed #BC8F8F;" | There is currently no action for automatically creating closure axioms. This operation must be performed by hand as per exercise 35. | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| valign="top" | page 71, Section 4.14 | | valign="top" | page 71, Section 4.14 | ||
Revision as of 11:51, July 3, 2008
Protege 4.x Tutorial Errata
This page contains a list of errata for the current Protege 4.x version of the Protege-OWL Tutorial.
Back to Protege4UserDocs
Contents
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 51, Section 4.9.1 | Species Validation not supported. To validate OWL1.0 ontologies, it is possible to use the Wonderweb Validator. |
| 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. Or to make a single equivalent class out of several superclasses, select the classes then right click and select Convert selected rows to defined class. |
| page 62, Section 4.11.1 | No classification results pane is shown. This proved to be an annoying feature for many people. The inferred axioms can be viewed in a separate view in the Active ontology tab. |
| page 70, Exercises 36 & 37 | There is currently no action for automatically creating closure axioms. This operation must be performed by hand as per exercise 35. |
| page 71, Section 4.14 | The patterns plugin for editing value partitions is currently not available. Value partitions should be created by hand using the manual step specified. |
| page 84, Exercise 48 | In step 4, when the text ('PizzaSize that hasDiameter some int[>=12]') is entered in the Class Expression Editor, it reports an error on the '[>=12]' part. Protege version 4.0 build 59. |
| page 84, Meaning | The text says "We have described a LargePizzaSize to be a subclass of Food", while there is no Food class defined anywhere in the tutorial. |
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).
Icons
The use of colour and the symbols on the icons have both been minimised to provide a consistent look.
Minor Typos
| Location | Typo |
|---|---|
| page 21, Exercise 6, steps 1 & 2 | hierarchy misspelled twice |
