MariaPoveda (Talk | contribs) m |
MariaPoveda (Talk | contribs) m |
||
| Line 17: | Line 17: | ||
|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). | |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). | ||
In summary, this pattern allows to represent both simple objects and aggregated objects and their members. | 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 | + | 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". |
|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. | |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. | ||
}} | }} | ||
|
Last modified date is: 2010-09-28 |
Diagram
| Name: | SimpleOrAggregated |
|---|---|
| Submitted by: | MariaPoveda, MariCarmenDeFigueroa |
| Also Known As: | |
| 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. |
| Domains: | |
| Competency Questions: | |
| Solution description: | 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 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 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. |
| Reusable OWL Building Block: | 1 (604) |
| 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).
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". |
| Scenarios: | 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. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The SimpleOrAggregated Content OP locally defines the following ontology elements:
AggregatedObject (owl:Class) An object that is an aggregation of two or more objects.
Un objeto resultante de la agregación de dos o más objetos.
AggregatedObject page Object (owl:Class) Any physical, social, or mental object, or a substance.
Cualquier objeto fÃsico, social o mental o sustancia.
Object page SimpleObject (owl:Class) A simple object, that is, an object that has no aggregated objects.
Un objeto simple, es decir, un objeto que no tiene objetos agregados.
SimpleObject pageNo scenario is added to this Content OP.
This revision (revision ID 10158) takes in account the reviews: none
Other info at evaluation tab
|
Submission to event |
|---|
'Ontology Design Patterns'
