Submissions:SimpleOrAggregated - Revision history

MariCarmenSuarezFigueroa at 10:19, 29 September 2010

2010-09-29T10:19:29Z

MariCarmenSuarezFigueroa at 10:17, 29 September 2010

2010-09-29T10:17:56Z

MariaPoveda at 09:19, 29 September 2010

2010-09-29T09:19:41Z

MariaPoveda at 09:16, 29 September 2010

2010-09-29T09:16:07Z

MariaPoveda at 09:13, 29 September 2010

2010-09-29T09:13:37Z

MariaPoveda at 08:40, 29 September 2010

2010-09-29T08:40:23Z

MariCarmenSuarezFigueroa at 15:56, 28 September 2010

2010-09-28T15:56:03Z

MariaPoveda at 15:24, 28 September 2010

2010-09-28T15:24:23Z

MariaPoveda at 15:20, 28 September 2010

2010-09-28T15:20:12Z

MariCarmenSuarezFigueroa at 15:14, 28 September 2010

2010-09-28T15:14:59Z

@@ Line 19: / Line 19: @@
 |Consequences=This Content OP allows designers to represent both simple individuals of a given concept (that is, an individual that is made up of itself) and aggregated individuals of a given concept (that is, an individual that is made up of several individuals of the same concept).
 In summary, this pattern allows to represent both simple objects and aggregated objects and their members.
-In addition, this pattern can be used to detect the following contradictory situation by means of applying a reasoner: 'to instantiate the relationship "hasAggregatedMember" for an Object that belongs to "SimpleObject"'. This situation represents a consistency error and it is detected when a resoner is applied due to the following modelling decisions included in the pattern: (a) "AggregatedObject" class represents the "hasAggregatedMember" domain and (b) it is disjoint with "SimpleObject".
+In addition, this pattern can be used to detect the following contradictory situation by means of applying a reasoner: 'to instantiate the relationship "hasAggregatedMember" for an Object that belongs to "SimpleObject"'. This situation represents a consistency error and it is detected when a resoner is applied due to the following modelling decisions included in the pattern: (a) "AggregatedObject" class represents the "hasAggregatedMember" domain and (b) "AggregatedObject" is disjoint with "SimpleObject".
 |Scenario=A service provider can be simple or  be an aggregate of a set of service providers. A context source can be simple or be an aggregate of a set of context sources.  A computing or storage resource can be simple or be an aggregate of a set of computing or storage resources.
 }}

@@ Line 7: / Line 7: @@
 |SubmittedBy=MariaPoveda, MariCarmenDeFigueroa
 |Name=SimpleOrAggregated
-|Intent=The goal of this pattern is to represent objects that can be simple or aggregated (that is, several objects gathered in another object acting as a whole). The main difference between the aggregation relation and other mereological relationships (such as part of or composition) is that the aggregated object and its aggregated members should belong to the same concept. For example, a turbine is part of an engine, whereas an aggregated provider is formed by providers.
+|Intent=The goal of this pattern is to represent objects that can be simple or aggregated (that is, several objects gathered in another object acting as a whole).
 |Domain=Parts and Collections,
 |CompetencyQuestion=What elements are aggregated members of this object?, What is this object aggregated member of?
 |ContentODPDescription=The class "ObjectByCardinality" has been created to classify simple and aggregated objects into its subclasses "SimpleObject" and "AggregatedObject", respectively. These subclasses are disjoint among them.
-The aggregation relationship between objects, that means that objects can be composed by other objects, is represented by means of the transtive property "hasAggregatedMember" and its inverse "isAggregatedMemberOf". These properties have as subproperties the non transitive properties "hasDirectAggregatedMember" and its inverse "isDirectAggregatedMemberOf" respectively. By  means of this structure of properties we provide a mechanism to represent transitive aggregation relationships (that its, if A has B as aggregated member and B has C as aggregated member then A has C as aggregated member) and to link each aggregated member just to the next level (that its, A has B as direct aggregated member).
-Finally, the class "AggregatedObject" has been defined as equivalent to those things that have some values for the property "hasAggregatedMember" with the aim of allowing the automatic classification of aggregated objects in this class when a reasoner is applied.
+Finally, the class "AggregatedObject" has been defined as equivalent to those things that have some values for the property "hasAggregatedMember". This modelling allows the automatic classification of aggregated objects in this class when a reasoner is applied.
 |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl
 |Consequences=This Content OP allows designers to represent both simple individuals of a given concept (that is, an individual that is made up of itself) and aggregated individuals of a given concept (that is, an individual that is made up of several individuals of the same concept).

@@ Line 12: / Line 12: @@
 |ContentODPDescription=The class "ObjectByCardinality" has been created to classify simple and aggregated objects into its subclasses "SimpleObject" and "AggregatedObject", respectively. These subclasses are disjoint among them.
 The aggregation relationship between objects, that means that objects can be composed by other objects, is represented by means of the transtive property "hasAggregatedMember" and its inverse "isAggregatedMemberOf". These properties have as subproperties the non transitive properties "hasDirectAggregatedMember" and its inverse "isDirectAggregatedMemberOf" respectively. By  means of this structure of properties we provide a mechanism to represent transitive aggregation relationships (that its, if A has B as aggregated member and B has C as aggregated member then A has C as aggregated member) and to link each aggregated member just to the next level (that its, A has B as direct aggregated member).
 Finally, the class "AggregatedObject" has been defined as equivalent to those things that have some values for the property "hasAggregatedMember" with the aim of allowing the automatic classification of aggregated objects in this class when a reasoner is applied.
 |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl

@@ Line 11: / Line 11: @@
 |CompetencyQuestion=What elements are aggregated members of this object?, What is this object aggregated member of?
 |ContentODPDescription=The class "ObjectByCardinality" has been created to classify simple and aggregated objects into its subclasses "SimpleObject" and "AggregatedObject", respectively. These subclasses are disjoint among them.
-The aggregation relationship between objects is represented by means of the transtive "hasAggregatedMember" property and its inverse "isAggregatedMemberOf". These properties have as subproperties the non transitive properties "hasDirectAggregatedMember" and its inverse "isDirectAggregatedMemberOf" respectively. By  means of this structure of properties we provide a mechanism to represent transitive aggregation relationships (that its, if A has B as aggregated member and B has C as aggregated member then A has C as aggregated member) and to link each aggregated member just to the next level (that its, A has B as direct aggregated member).
+The aggregation relationship between objects, that means that objects can be composed by other objects, is represented by means of the transtive property "hasAggregatedMember" and its inverse "isAggregatedMemberOf". These properties have as subproperties the non transitive properties "hasDirectAggregatedMember" and its inverse "isDirectAggregatedMemberOf" respectively. By  means of this structure of properties we provide a mechanism to represent transitive aggregation relationships (that its, if A has B as aggregated member and B has C as aggregated member then A has C as aggregated member) and to link each aggregated member just to the next level (that its, A has B as direct aggregated member).
-The aggregation relation between objects means that objects can be composed by other objects.
-−
 Finally, the class "AggregatedObject" has been defined as equivalent to those things that have some values for the property "hasAggregatedMember" with the aim of allowing the automatic classification of aggregated objects in this class when a reasoner is applied.
 |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl

@@ Line 11: / Line 11: @@
 |CompetencyQuestion=What elements are aggregated members of this object?, What is this object aggregated member of?
 |ContentODPDescription=The class "ObjectByCardinality" has been created to classify simple and aggregated objects into its subclasses "SimpleObject" and "AggregatedObject", respectively. These subclasses are disjoint among them.
-The aggregation relationship between objects is represented by means of the transtive "hasAggregatedMember" property and its inverse "isAggregatedMemberOf". These properties have as subproperties the non transitive properties "hasDirectAggregatedMember" and its inverse "isDirectAggregatedMemberOf" respectively. By  means of this structure of properties we can distinguish whether an object is aggregated directly by other objects.
+The aggregation relationship between objects is represented by means of the transtive "hasAggregatedMember" property and its inverse "isAggregatedMemberOf". These properties have as subproperties the non transitive properties "hasDirectAggregatedMember" and its inverse "isDirectAggregatedMemberOf" respectively. By  means of this structure of properties we provide a mechanism to represent transitive aggregation relationships (that its, if A has B as aggregated member and B has C as aggregated member then A has C as aggregated member) and to link each aggregated member just to the next level (that its, A has B as direct aggregated member).
 The aggregation relation between objects means that objects can be composed by other objects.

@@ Line 13: / Line 13: @@
 The relationship of aggregation between objects is represented by means of the "hasAggregatedMember" property and its inverse "isAggregatedMemberOf".
-Finally, the class "AggregatedObject" has been defined as equivalent to those things that have at least two values for the property "hasAggregatedMember" with the aim of allowing the automatic classification of aggregated objects in this class when a reasoner is applied.
+Finally, the class "AggregatedObject" has been defined as equivalent to those things that have some values for the property "hasAggregatedMember" with the aim of allowing the automatic classification of aggregated objects in this class when a reasoner is applied.
 |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl
 |Consequences=This Content OP allows designers to represent simple individuals of a given concept (that is, an individual that is made up of itself) and aggregated individuals of a given concept (that is, an individual that is made up of several individuals of the same concept).