ConceptMap¶
Superclass hierarchy
Definition¶
Correspondence between concepts in a correspondence table related to one or more Statistical Classifications.
Examples¶
A simple example might map the following 2 martial status category sets:
MS1: single, married, widowed, divorced.
MS2: single, married.
So, a correspondence table between these 2 category sets might look like this: MS1 single - MS2 single; MS1 widowed - MS2 single; MS1 divorced - MS2 single; MS1 married - MS2 married
Explanatory notes¶
A Map is the pairing of similar Concepts. Each Concept in the Map belongs to a different Collection. The collection of maps for all the Concepts in corresponding Collections is a Correspondence Table.
Subclasses¶
Properties¶
Name |
Description |
Data Type |
Multi- plicity |
---|---|---|---|
correspondence
from ConceptMap
|
Type of correspondence in terms of commonalities and differences between two members. |
0..1 |
|
displayLabel
from ConceptMap
|
A display label for the ConceptMap. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations. |
0..1 |
|
usage
from ConceptMap
|
Explanation of the ways in which some decision or object is employed. Supports the use of multiple languages and structured text. |
0..1 |
|
validDates
from ConceptMap
|
Date from which the Map became valid. The date must be defined if the Map belongs to a floating CorrespondenceTable. Date at which the Map became invalid. The date must be defined if the Map belongs to a floating Correspondence Table and is no longer valid. |
0..1 |
Inherited Properties¶
Associations¶
Multiplicity |
Association |
Navigable Class |
Multiplicity |
---|---|---|---|
0..* |
ConceptMap_hasSource_Concept |
1..* |
|
0..* |
ConceptMap_hasTarget_Concept |
1..* |
TBD
Diagram¶
TBD