Skip to content

Simpleoraggregated Pattern

Source: ODP portal  ·  Published by: delicias.dia.fi.upm.es  ·  Category: structural  ·  Domain: general

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.

What it answers

  • What is this object aggregated member of?
  • What elements are aggregated members of this object?

The pattern

The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.

Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.

Download the pattern

Should you use this one?
Size 4 classes, 4 properties, 51 axioms
Brings in 1 imported ontology, so adopting it adopts that too
Reasoning HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern.

A situation it was written for. This Content OP allows designers to represent aggregations relations.

Check it yourself: the published pattern  ·  an archived copy  ·  the ontology itself.

If a link does not open

ontologydesignpatterns.org, which publishes most of this library, does not currently answer over HTTPS, and its wiki redirects submission pages to its front page. The archived copy is there for exactly that reason. The ontology files themselves are still served over plain HTTP.

Terms it declares

The 8 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.

  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#AggregatedObject
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#Object
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#ObjectByCardinality
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#SimpleObject
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#hasAggregatedMember
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#hasDirectAggregatedMember
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#isAggregatedMemberOf
  • http://delicias.dia.fi.upm.es/ontologies/SimpleOrAggregated.owl#isDirectAggregatedMemberOf

An example of it in use

The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.

Download the example

Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.

Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.