|
Hi All, Really new to Ontology and has taken some time for the terms to sync in, I have been through the Pizza ontology tutorial. Now my question is related to Gruber statement "an explicit specification of conceptualization". How do i distinguish the two terms "specification" and "conceptualization" within context of the Pizza ontology? Would the "conceptualization" relate to the abstract model so in the case of the Pizza ontology, Pizza, PizzaBase, PizzaTopping, NamedPizza? Whereas the specification is the language implementation of this conceptual model, MeatTopping, ReginaPizza. |
|
Conceptualization is the process to create abstract description of (real world) entities. During this process you try to grasp a characteristic feature and create a classification on it. The specification is really the formal description of your conceptualization. In the case of Pizza Ontology, a decision was made to think in terms of toppings and bases and styles (vegetarian, spicy, etc.) Once you have the list of concepts in your mind (Pizza, PizzaBase, PizzaTopping, SpicyBeefPizza, etc.) you can add all the descriptions and relations (e.g. broader concept), this way you start specifying the concept. |
|
Thanks, trying to digest this. I am trying to clear the difference between where does conceptualization stop and specification starts. So if I understand you correctly, Conceptualization - Form all my concepts as you mentioned, Pizza,PizzaBase,PizzaTopping, would this concept include their relationships? Would this be a model (UML) diagram?
Specification - This wills start with actually defining the concepts into for example OWL (Protege). Building the conceptual model including relationships, axioms,disjointed axioms. In the end the owl file? This would allow the reasoner to make decisions. Once you create a formal description of your concepts, like the UML above, thats already a specification.It is the result of the overall process, doesn't matter in what format you do (can be UML, OWL, etc.) I'm not sure if you can draw a borderline between conceptualization and specification. One is the idea, the second one is the formal description of the idea. Thanks, so in short, conceptualization is to bed down the concepts (Pizza, VegetarianPizza, SpicyTopping etc), all loose no relationships etc). The specification will be when you start relating these concepts (implementing axioms, disjoint classes, etc), for example on the Pizza Ontology, a vegetarian pizza cannot have any meattoppings but can contain vegetariantoppings, a pizza must contain at least one pizzabase. Hope this sounds right... You are misusing UML generalization. The arrows should point backwards. Thanks, will check it out. |
