Designation

Package: 
Extends: 
Version: 
4
Is Abstract: 
yes
Is Pattern: 
no
Definition: 

A sign denoting a concept.

Explanatory Notes: 

The representation of a concept by a sign (e.g., string, pictogram, bitmap) which denotes it. An example is the code M designating the marital status Married, which is a concept. In this context, M means Married.

Example: 
A linking of the term “Unemployment” to an particular underlying concept.
Property: 
NameCardinalityDatatypeDescription
representation
0..1
A perceivable object used to denote a signified, i.e. a concept in this case.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
denotes
The concept denoted by the designation.
0..n
0..1
Neither
realizes
Class in the Signification Pattern realized by Designation. A Designation is a type of Sign.
0..n
1..1
Neither

Stage:

Is extendable: 
GSIM: 
Designation
Is property: 
0
RDF Mapping: 

Comments

larry's picture

We had this drawn as a Vocabulary is an aggregation of Designations this is the relationship here but the Description doesn't quite reflect that

larry's picture

Many relationships are described as Composition but that is not how we had them drawn. We should probably come to a common understanding of what the relationship types mean.

This is the definition of a Code within a CodeList in DDI terminology. The current consensus seems to be to use the traditional DDI names for heavily used objects such as this one. It will specify the GSIM object in the documentation

Renamed association to Concept to "denotes", in line with the latest MT discussion.

Designation is now a realization of Sign in the Signification Pattern. It also includes a representation property, which contains the actual string. It needs to be reviewed again to make sure the changes are consistent with its use elsewhere in the model.