description
type: Ontology
version info: 1.1 added rdfs:isDefinedBy for all named entities
version info: Created by Aldo Gangemi and Valentina Presutti
comment: The description pattern. It is extracted from DOLCE-UltraLite by partial clone of elements.
imports: cpannotationschema.owl

defines
type: ObjectProperty
comment: A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.
range: Concept
domain: Description
sub property of: uses concept

is concept used in
type: ObjectProperty
label: è un concetto usato in @it
comment: A more generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description
domain: Concept
range: Description

is defined in
type: ObjectProperty
label: è definito in @it
comment: A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.
domain: Concept
range: Description
inverse of: defines
sub property of: is concept used in

uses concept
type: ObjectProperty
label: usa il concetto @it
comment: A generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description. This last condition cannot be encoded for object properties in OWL.
range: Concept
domain: Description
inverse of: is concept used in

Concept
type: Class
subclass of: Restriction
  on property: is concept used in
  min cardinality: 1
disjoint with: Description
comment: A concept can be an idea, notion, role, or even a reified class, and isDefinedIn a Description . Once defined, a Concept can be used in other descriptions. The classifies relation (see 'classification' pattern) relates concepts to entities at some time.

Description
type: Class
comment: A Description represents a conceptualization. It can be thought also as a 'descriptive context' that defines concepts in order to see a 'relational context' out of a set of data or observations. For example, a Plan is a description of some actions to be executed by agents in a certain way, with certain parameters; a Diagnosis is a description that provides an interpretation to a set of observed entities, etc. A Description typically defines at least one Concept, for example the 'preparing a coffee' Description could define concepts such as 'Heater', 'AmountOfWater', 'CoffeeMix', etc. With respect to other patterns, descriptions are 'abstractions' of situations (cf. the 'situation' pattern), and in some complex use cases (e.g. matching executions to plan models), the two patterns can be composed (see the descriptionsituation pattern).