29/11/2004CS646: N. Drummond, M. Horridge1 Presented by the CO-ODE and HyOntUse projects Funded by CS646: OWL Tutorial (session 2)

29/11/2004CS646: N. Drummond, M. Horridge2 CS646: This session Issue: Primitive Classes & Polyhierarchies Advanced: Reasoning Advanced: Creating Defined Classes Union Classes: Covering Axioms Example: Creating a Vegetarian Pizza Issue: Open World Assumption Union Classes: Closure

29/11/2004CS646: N. Drummond, M. Horridge3 Loading OWL files from scratch 1.If youve only got an OWL file: Select OWL Files as the Project Format, then Build to select the.owl file 2.If youve got a valid project file*: Select OWL Files as the Project Format, and then Open Other to find the.pprj file (if youve already opened it, it will be in Open Recent) 3.Open C:\Protégé_3.2_beta\examples\pizza\pizza.owl * ie one created on this version of Protégé - the s/w gets updated once every few days, so dont count on it unless youve created it recently– safest to build from the.owl file if in doubt Run Protégé.exe

29/11/2004CS646: N. Drummond, M. Horridge4 Primitive Classes All classes in our ontology so far are Primitive We describe primitive pizzas Primitive Class = only Necessary Conditions They are marked as yellow in the class hierarchy We condone building a disjoint tree of primitive classes

29/11/2004CS646: N. Drummond, M. Horridge5 Describing Primitive Pizza Classes 1.Create a new pizza under NamedPizza either choose from the menu or make it up 2.Create a new Existential (SomeValuesFrom) Restriction with the hasTopping property and a filler from PizzaTopping (eg HamTopping) 3.Add more Restrictions in the same way to complete the description each restriction is added to an intersection – so a Pizza must have toppingA and must have toppingB etc see MargheritaPizza for an example 4.Create another pizza that has at least one meat ingredient remember disjoints Start with pizzas2_0.owl

29/11/2004CS646: N. Drummond, M. Horridge6 Polyhierarchies By the end of this tutorial we intent to create a VegetarianPizza Some of our existing Pizzas should be types of VegetarianPizza However, they could also be types of SpicyPizza or CheeseLoversPizza We need to be able to give them multiple parents

29/11/2004CS646: N. Drummond, M. Horridge7 Vegetarian Pizza attempt 1 1.Create a new pizza called VegetarianPizza under Pizza make this disjoint from its siblings as we have been doing 2.Select MargheritaPizza you will notice that it only has a single parent, NamedPizza 3.Add VegetarianPizza as a new parent using the conditions widget Add Named Class button notice that MargheritaPizza now occurs in 2 places in the asserted hierarchy we have asserted that MargheritaPizza has 2 parents Start with pizzas2_1.owl

29/11/2004CS646: N. Drummond, M. Horridge8 Reasoning Wed like to be able to check the logical consistency of our model Wed also like to make automatic inferences about the subsumption hierarchy. A process known as classifying –ie Moving classes around in the hierarchy based on their logical definition Generic software capable of these tasks are known as reasoners (although you may hear them being referred to as Classifiers) FaCT++ is a reasoner

29/11/2004CS646: N. Drummond, M. Horridge9 Running Racer 1.Open C:\Protégé_3.2_beta 2.Run Fact++.Server.exe A cmd window will open and two service enabled messages will appear in the ouput FaCT++ is now ready for use as an http server using a standard interface called DIG 3.Goto OWL – Preferences & change ReasonerURL to NB. Alternative DIG reasoners like Racer can also be used

29/11/2004CS646: N. Drummond, M. Horridge10 Classifying Classify taxonomy (and check consistency) Just check consistency (for efficiency) Compute inferred types (for individuals)

29/11/2004CS646: N. Drummond, M. Horridge11 Reasoning about our Pizzas 1.Classify your ontology You will see an inferred hierarchy appear, which will show any movement of classes in the hierarchy You will also see a results window appear at the bottom of the screen which describes the results of the reasoner Start with pizzas2_2.owl MargheritaPizza turns out to be inconsistent – why?

29/11/2004CS646: N. Drummond, M. Horridge12 Why is MargheritaPizza inconsistent? We are asserting that a MargheritaPizza is a subclass of two classes we have stated are disjoint The disjoint means nothing can be a NamedPizza and a VegetarianPizza at the same time This means that the class of MargheritaPizzas can never contain any individuals The class is therefore inconsistent

29/11/2004CS646: N. Drummond, M. Horridge13 Attempting again 1.Close the inferred hierarchy and classification results pane 2.Remove the disjoint between VegetarianPizza and its siblings When prompted, choose to remove only between this class and its siblings 3.Re-Classify your ontology This should now be accepted by the reasoner with no inconsistencies Start with your current ontology

29/11/2004CS646: N. Drummond, M. Horridge14 Asserted Polyhierarchies We believe asserting polyhierarchies is bad let the reasoner do it! We lose some encapsulation of knowledge Difficult to maintain

29/11/2004CS646: N. Drummond, M. Horridge15 Defined Classes Have a definition. That is at least one Necessary and Sufficient condition Are marked in orange in the interface Classes, all of whose individuals satisfy this definition, can be inferred to be subclasses Reasoners can perform this inference

29/11/2004CS646: N. Drummond, M. Horridge16 Describing a MeatyPizza 1.Create a subclass of Pizza called MeatyPizza Dont put in the disjoints or youll get the same problems as before In general, defined classes are not disjoint 2.Add a restriction to say: Every MeatyPizza must have at least one meat topping 3.Classify your ontology What happens? Start with pizzas2_3.owl, close the reasoner panes

29/11/2004CS646: N. Drummond, M. Horridge17 Defining a MeatyPizza 1.Click and drag your hasTopping MeatTopping restriction from Necessary to Necessary & Sufficient The MeatyPizza class now turns orange, denoting that it is now a defined class 2.Click and drag the Pizza Superclass from Necessary toNecessary & Sufficient Make sure when you release you are on top of the existing restriction otherwise you will get 2 sets of conditions. You should have a single orange icon on the right stretching across both conditions like this… 3.Classify your ontology What happens? Start with pizzas2_4.owl, close the reasoner panes

29/11/2004CS646: N. Drummond, M. Horridge18 Reasoner Classification The reasoner has been able to infer that anything that is a Pizza that has at least one topping from MeatTopping is a MeatyPizza Therefore, classes fitting this definition are found to be subclasses of MeatyPizza, or are subsumed by MeatyPizza The inferred hierarchy is updated to reflect this and moved classes are highlighted in blue

29/11/2004CS646: N. Drummond, M. Horridge19 How do we Define a Vegetarian Pizza? Nasty Define in words? –a pizza with only vegetarian toppings? –a pizza with no meat (or fish) toppings? –a pizza that is not a MeatyPizza? More than one way to model this

29/11/2004CS646: N. Drummond, M. Horridge20 Defining a Vegetarian Topping 1.Create a subclass of PizzaTopping called VegetarianTopping 2.Click Create New Expression in the Conditions Widget Type in or select each of the top level PizzaToppings that are not meat or fish (ie DairyTopping, FruitTopping etc) and between each, type the word or the or will be translated into a union symbol 3.Press Return when finished you have created an anonymous class described by the expression 4.Make this a defined class by moving both conditions from the Necessary to the Necessary & Sufficient conditions 5.Classify your ontology Start with pizzas2_5.owl

29/11/2004CS646: N. Drummond, M. Horridge21 AKA disjunction This OR That OR TheOther (This That TheOther) Set theory Commonly used for: –Covering axioms (like VegetarianTopping) –Closure Class Constructors: Union

29/11/2004CS646: N. Drummond, M. Horridge22 Covering Axioms Covered class – that to which the condition is added Covering classes – those in the union expression A covering axiom in the Necessary & Sufficient Conditions means: the covered class cannot contain any instances from a class other than one of the covering classes Gender Female Male In this example, the class Gender is covered by Male or Female All individuals in Gender must be individuals from Male or Female There are no other types of Gender Gender Male Female

29/11/2004CS646: N. Drummond, M. Horridge23 Vegetarian Pizza attempt 2 1.Select MargheritaPizza and remove VegetarianPizza from its superclasses 2.Select VegetarianPizza and create a restriction to say that it only has toppings from VegetarianTopping 3.Make this a defined class by moving all conditions fromNecessary to Necessary & Sufficient Make sure when you release you are on top of the existing restriction otherwise you will get 2 sets of conditions. You should have a single orange icon on the right stretching across both conditions 4.Classify your ontology What happens? Start with pizzas2_6.owl

29/11/2004CS646: N. Drummond, M. Horridge24 Open World Assumption The reasoner does not have enough information to classify pizzas under VegetarianPizza Typically several Existential restrictions on a single property with different fillers – like primitive pizzas Existential should be paraphrased by amongst other things… Must state that a description is complete We need closure for the given property This is in the form of a Universal Restriction with a Union of the other fillers using that property

29/11/2004CS646: N. Drummond, M. Horridge25 Closure Example: MargheritaPizza All MargheritaPizzas must have: at least 1 topping from MozzarellaTopping and at least 1 topping from TomatoTopping and only toppings from MozzarellaTopping or TomatoTopping The last part is paraphrased into no other toppings The union closes the hasTopping property on MargheritaPizza

29/11/2004CS646: N. Drummond, M. Horridge26 Closing Pizza Descriptions 1.Select MargheritaPizza 2.Create a Universal Restriction on the hasTopping property with a filler of TomatoTopping MozzarellaTopping Remember, you can type or to achieve this, or you can use the expression palette 3.Close your other pizzas Each time you need to create a filler with the union of all the classes used on the hasTopping property (ie all the toppings used on that pizza) 4.Classify your ontology Finally, the defined class VegetarianPizza should subsume any classes that only have vegetarian toppings Start with pizzas2_7.owl

29/11/2004CS646: N. Drummond, M. Horridge27 Summary You should now be able to: Use Defined Classes allow a polyhierarchy to be computed Classify and check consistency using a Reasoner Create Covering Axioms Close Class Descriptions to cope with Open World Reasoning

29/11/2004CS646: N. Drummond, M. Horridge28 Viewing our Hierarchy Graphically

29/11/2004CS646: N. Drummond, M. Horridge29 OWLViz Tab View Inferred Model View Asserted Model Polyhierarchy tangle

29/11/2004CS646: N. Drummond, M. Horridge30 Your Pizza Finder Once you have a pizza ontology you are happy with, you can plug it in to the PizzaFinder Instructions available on line at

29/11/2004CS646: N. Drummond, M. Horridge31 Other Exercises: Create a ProteinLoversPizza Create a new subclass of Pizza Define this as: Any Pizza that has at least one MeatTopping and at least one CheeseTopping and at least one FishTopping If you dont have any pizzas that will classify under this, create one which should (SicilianaPizza should) Classify to check that it works Start with pizzas2_8.owl

29/11/2004CS646: N. Drummond, M. Horridge32 Other Exercises: Define RealItalianPizza Convert RealItalianPizza to a defined class Add information to your pizzas to allow some of them to classify under this one Classify remember to check your disjoint if you have problems Start with pizzas2_9.owl

29/11/2004CS646: N. Drummond, M. Horridge33 Thankyou Feedback on tutorial appreciated Powerpoint slides available from Software / resources / community at: – –