Community:View Inheritance
From Odp
(Difference between revisions)
| Line 12: | Line 12: | ||
In the case of the representation of the "pizza" domain concept: | In the case of the representation of the "pizza" domain concept: | ||
* Allow me to select a pizza based on the type of base, the toppings and(or) the name. | * Allow me to select a pizza based on the type of base, the toppings and(or) the name. | ||
| + | |Scenario=There are cases when the application intended to use the ontology requires the multiple abstractions available to classify the domain concept to be represented in the ontology. | ||
| - | + | As an example from the object-oriented design, consider the alternative criteria that are avaible to classify the abstraction of a simple domain concepts such as "employee": | |
* Employee: by contract type (permanent vs. temporary), by job type (engineering, administrative, managerial). | * Employee: by contract type (permanent vs. temporary), by job type (engineering, administrative, managerial). | ||
| Line 20: | Line 21: | ||
* Pizza: base (deep pan, thin), topping (cheese, meat, vegetable, etc.), name (margherita, american, etc.) | * Pizza: base (deep pan, thin), topping (cheese, meat, vegetable, etc.), name (margherita, american, etc.) | ||
| - | + | Now, let us think of a web site that attemtps to provide wine recommendations to its visitors or a web site to order pizza. | |
| - | + | ||
| - | + | ||
}} | }} | ||
{{Additional information header}} | {{Additional information header}} | ||
Revision as of 17:30, 9 March 2010
View Inheritance
Title: View Inheritance
Description: Representation of the multiple alternative criteria available to classify the abstractions of a certain ontology domain concept.
Diagram (this article has no graphical representation)
About
| Users | BenedictoRodriguezCastro, HughGlaser |
|---|---|
| Domains | General |
| Competency Questions | For example, in the case of the representation of the "wine" domain concept:
In the case of the representation of the "pizza" domain concept:
|
| Scenarios | There are cases when the application intended to use the ontology requires the multiple abstractions available to classify the domain concept to be represented in the ontology.
As an example from the object-oriented design, consider the alternative criteria that are avaible to classify the abstraction of a simple domain concepts such as "employee":
Similar examples exist in the ontology design field such us "wine" and "pizza":
Now, let us think of a web site that attemtps to provide wine recommendations to its visitors or a web site to order pizza. |
| Proposed Solutions (OWL files) | |
| Related patterns | |
Additional information
References
- Matthew Horridge, Nick Drummond, Simon Jupp, Georgina Moulton, Robert Stevens. A Practical Guide To Building OWL Ontologies Using Protege 4 and CO-ODE Tools Edition 1.2. Technical report, The University Of Manchester, March 2009. Documentation | reference page
- Alan L. Rector. Modularisation of domain ontologies implemented in description logics and related formalisms including owl. In K-CAP '03: Proceedings of the 2nd international conference on Knowledge capture, pages 121{128, New York, NY, USA, 2003. ACM. ISBN 1-58113-583-1. Documentation | reference page
- Denton, William. How to Make a Faceted Classification and Put It On the Web. Nov 2003. Documentation | reference page
- Normalization Ontology Design Pattern Documentation | reference page
- Bertrand Meyer. Object-Oriented Software Construction (Book/CD-ROM) (2nd Edition). Prentice Hall PTR, March 2000. ISBN 0136291554. Documentation | reference page
- N. F. Noy and D. McGuinness. Ontology development 101: A guide to creating your first ontology. Technical Report SMI-2001-0880, Stanford Medical Informatics, Stanford, 2001. Documentation | reference page
