From Odp

Revision as of 09:57, 6 September 2010 by EvaBlomqvist (Talk | contribs)
Jump to: navigation, search

This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 10064

Graphical representation



General description

Name: SimpleOrAggregated
Submitted by: MariaPoveda, MariCarmenDeFigueroa
Also Known As:
Intent: The goal of this pattern is to represent in a non-transitive fashion objects that can be simple or aggregated (that is, several objects gathered in another object acting as a whole).

Parts and Collections

Competency Questions:
  • What elements are aggregated members of this object?
  • What is this object aggregated member of?
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 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.

Reusable OWL Building Block: (588)
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 instanciate 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:

ObjectProperty hasAggregatedMember (owl:ObjectProperty)
hasAggregatedMember page
ObjectProperty isAggregatedMemberOf (owl:ObjectProperty)
isAggregatedMemberOf page
Class 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
Class Object (owl:Class) Any physical, social, or mental object, or a substance.

Cualquier objeto físico, social o mental o sustancia.

Object page
Class ObjectByCardinality (owl:Class)
ObjectByCardinality page
Class 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 page

Additional information


Scenarios about SimpleOrAggregated
  • Modelling simple and aggregated service providers within the mIO! ontology network. Service providers are also organized by types. >>>
  • Modelling simple and aggregated context sources within the mIO! ontology network. >>>
  • Modelling simple and aggregated resources. These resources are also organized by types, specifically, they can be computing or storage resources. >>>


Reviews about SimpleOrAggregated
Review article Posted on About revision (current is 10064)
CatherineRoussey about SimpleOrAggregated 245545010 September 2010 1006410,064
GerdGroener about SimpleOrAggregated 245545010 September 2010 1009710,097
VojtechSvatek about SimpleOrAggregated 245545616 September 2010 1009710,097

This revision (revision ID 10064) takes in account the reviews: none

Other info at evaluation tab

Modeling issues

Modeling issues about SimpleOrAggregated

There is no Modeling issue related to this proposal.


Add a reference

Submission to event


Personal tools
Quality Committee
Content OP publishers