Line 24: | Line 24: | ||
Now, let us think of a web site that attemtps to provide wine recommendations to its visitors or a web site to order 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. | ||
− | |RelatedPattern=Normalization | + | |RelatedPattern=Partition, ClassAsPropertyValue, Normalization, Faceted Classification Scheme, |
}} | }} | ||
{{Additional information header}} | {{Additional information header}} |
Title: View Inheritance
Diagram (this article has no graphical representation)
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 | This modeling problem is discussed in object-oriented design as the motivation to introduce "View Inheritance" (see page 824 of [Meyer 2000]). "View Inheritance" corresponds to one of the 12 valid uses of inheritance identified by the author.
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" (page 852 in [Meyer 2000]):
Similar examples exist in the ontology design field such us "wine" [Noy and McGuiness 2001] and "pizza" [Horridge et al. 2009]:
|
Proposed Solutions (OWL files) | |
Related patterns |
After some time looking at this type of modeling problem, another domain that deals with this type of conceptual modelling scenario is "facet analisys" and "faceted classification" in Library Science.
It seems that there is a strong correlation across different disciplines regarding how they address the modeling problem presented here: