Community:View Inheritance - Revision history

BenedictoRodriguezCastro at 18:26, 6 September 2010

2010-09-06T18:26:01Z

BenedictoRodriguezCastro at 17:52, 5 September 2010

2010-09-05T17:52:39Z

BenedictoRodriguezCastro at 19:15, 9 March 2010

2010-03-09T19:15:39Z

BenedictoRodriguezCastro at 19:13, 9 March 2010

2010-03-09T19:13:28Z

BenedictoRodriguezCastro at 19:11, 9 March 2010

2010-03-09T19:11:44Z

BenedictoRodriguezCastro at 17:50, 9 March 2010

2010-03-09T17:50:34Z

BenedictoRodriguezCastro at 17:30, 9 March 2010

2010-03-09T17:30:13Z

BenedictoRodriguezCastro at 17:25, 9 March 2010

2010-03-09T17:25:06Z

EnricoDaga at 16:52, 8 March 2010

2010-03-08T16:52:23Z

MichaelUschold at 06:06, 5 March 2010

2010-03-05T06:06:17Z

@@ 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.
-|RelatedPattern=Normalization
+|RelatedPattern=Partition, ClassAsPropertyValue, Normalization, Faceted Classification Scheme,
 }}
 {{Additional information header}}

@@ 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.
 }}
 {{Additional information header}}

@@ Line 12: / Line 12: @@
 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.
-|Scenario=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.
+|Scenario=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]):
+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]):
 * Employee: by contract type (permanent vs. temporary), by job type (engineering, administrative, managerial).
-Similar examples exist in the ontology design field such us "wine" [Noy and McGuiness, 2001] and "pizza" [Horridge et al., 2009]:
+Similar examples exist in the ontology design field such us "wine" [Noy and McGuiness 2001] and "pizza" [Horridge et al. 2009]:
 * Wine: color, region, flavour, ocassion, etc.
 * Pizza: base (deep pan, thin), topping (cheese, meat, vegetable, etc.), name (margherita, american, etc.)

@@ Line 12: / Line 12: @@
 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.
-|Scenario=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.
+|Scenario=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]):
+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]):
 * Employee: by contract type (permanent vs. temporary), by job type (engineering, administrative, managerial).
-Similar examples exist in the ontology design field such us "wine" [Noy 2001] and "pizza" [Horridge 2009]:
+Similar examples exist in the ontology design field such us "wine" [Noy and McGuiness, 2001] and "pizza" [Horridge et al., 2009]:
 * Wine: color, region, flavour, ocassion, etc.
 * Pizza: base (deep pan, thin), topping (cheese, meat, vegetable, etc.), name (margherita, american, etc.)

@@ Line 12: / Line 12: @@
 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.
-|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.
+|Scenario=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.
-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":
+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.
 * Employee: by contract type (permanent vs. temporary), by job type (engineering, administrative, managerial).
-Similar examples exist in the ontology design field such us "wine" and "pizza":
+Similar examples exist in the ontology design field such us "wine" [Noy 2001] and "pizza" [Horridge 2009]:
 * Wine: color, region, flavour, ocassion, etc.
 * Pizza: base (deep pan, thin), topping (cheese, meat, vegetable, etc.), name (margherita, american, etc.)

@@ Line 1: / Line 1: @@
 {{TitleDescription Template
 |Title=View Inheritance
-|Description=Representation of multiple alternative abstraction criteria of a certain ontology domain concept
+|Description=Representation of the multiple alternative criteria available to classify the abstractions of a certain ontology domain concept.
 }}
 {{Graphical representation}}
@@ Line 7: / Line 7: @@
 |Author=BenedictoRodriguezCastro, HughGlaser
 |Domain=General
 }}
 {{Additional information header}}

← Older revision		Revision as of 16:52, 8 March 2010
Line 12:		Line 12:
	{{My references}}		{{My references}}
	{{Modeling Issue toolbar}}		{{Modeling Issue toolbar}}
−	~~<noinclude>=====5-03-2010 [[User:MichaelUschold]] says:=====~~
−	~~This is a response to the comment left by Bene Rodriguez-Castro in the discussion tab.~~
−
−	A description logic provides a very natural way to characterize concepts/classes by multiple criteria using the idea of a restriction. Furthermore, the classification hierarchy is generated automatically for you.
−
−	~~The elaboration you gave is a very good continuation of this issue. You may wish to move some of it into the main issue page.</noinclude>~~

← Older revision		Revision as of 06:06, 5 March 2010
Line 17:		Line 17:
	A description logic provides a very natural way to characterize concepts/classes by multiple criteria using the idea of a restriction. Furthermore, the classification hierarchy is generated automatically for you.		A description logic provides a very natural way to characterize concepts/classes by multiple criteria using the idea of a restriction. Furthermore, the classification hierarchy is generated automatically for you.

−	The elaboration you gave is a very good continuation of this issue. ~~Feel free~~ to move some of it into the main issue page.</noinclude>	+	The elaboration you gave is a very good continuation of this issue. You may wish to move some of it into the main issue page.</noinclude>