EntityFeatureValueDomain
type: Class
additional information: See also the Entity-Quality ODP and the Entity-Property-Value ODP
aim: To model features with the simplest structure possible
classification: Good Practice
elements: The most important elements are the object properties (one for each aspect), the feature, and the values of the aspects
implementation: For each aspect of the feature, an object property and a value partition should be created. For each of them, the domain should be the class Feature and the range the aspect value. The feature is really an Nary relationship ODP, and it is linked to each aspect by existential restrictions. The entity is linked to the feature with a Qualified Cardinality Restriction (QCR) of exactly one
motivation: This ODP is used to represent modifiers with multiple aspects, thus features (e.g. colour with a certain brightness and saturation)
name: Entity-Feature-Value
reference: A. Gangemi, N. Guarino, C. Masolo, A. Oltramari and L. Schneider. Sweetening ontologies with dolce. In: LNCS, EKAW. (2002) 166-182
reference: Alan Rector (Personal Communication)
reference: Mikel Egana, Alan Rector, Robert Stevens and Erick Antezana. Applying Ontology Design Patterns in bio-ontologies. EKAW 2008. LNCS 5268, pp. 7-16, 2008
result: The entities, que features of those entities and the aspects of the features are properly separated
sample: ../img/EntityFeatureValue_instance.png
side effects: Although this ODP can obviously handle multi aspect qualities, it is difficult to author because of the amount of entities that need to be added
structure: ../img/EntityFeatureValue_abstract.png
subclass of: Thing

basal
type: Class
subclass of: position
disjoint with: central

Thing
on class: apical complex position
qualified cardinality: 1