ConceptMap

Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptMap

Definition

Correspondence between concepts in a correspondence table.

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 concept 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.

Diagram

Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

correspondence

- own class -

Type of correspondence in terms of commonalities and differences between two members.

CorrespondenceDefinition

0..1

displayLabel

- own class -

A human-readable display label for the object. Supports the use of multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.

LabelForDisplay

0..1

identifier

- own class -

Identifier for objects requiring short- or long-lasting referencing and management.

Identifier

0..1

usage

- own class -

Explanation of the ways in which the object is employed.

InternationalString

0..1

validDates

- own class -

The dates describing the validity period of the object. The date from which the object became valid must be defined if the map belongs to a “floating” construct. The date at which the object became invalid must be defined if the map belongs to a “floating” construct and is no longer valid.

DateRange

0..1

Associations

Direction

Association

Description

Multiplicity of ConceptMap

Package of Other Class

Other Class

Multiplicity of other class

Aggregation Kind

Inherited from

from

ConceptMap hasSource Concept

Concept map has one to many source concepts.

0..*

- own package -

Concept

1..*

none

- own class -

from

ConceptMap hasTarget Concept

Concept map has one to many target concepts.

0..*

- own package -

Concept

1..*

none

- own class -

to

ConceptSystemCorrespondence has ConceptMap

Concept system correspondence has zero to many concept maps.

0..*

- own package -

ConceptSystemCorrespondence

0..1

none

- own class -

to

CorrespondenceTable has ConceptMap

Correspondence table has zero to many concept maps.

0..*

Representations

CorrespondenceTable

0..1

none

- own class -

Syntax representations / encodings

All syntax representations except the Canonical XMI are provided as reference points for specific implementations, or for use as defaults if sufficient in the form presented.

Fragment for the class ConceptMap (entire model as XMI)

  1<packagedElement xmlns:StandardProfile="http://www.eclipse.org/uml2/5.0.0/UML/Profile/Standard"
  2                 xmlns:uml="http://www.eclipse.org/uml2/5.0.0/UML"
  3                 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
  4                 xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap"
  5                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap"
  6                 xmi:type="uml:Class">
  7   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedComment"
  8                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedComment"
  9                 xmi:type="uml:Comment">
 10      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap"/>
 11      <body>Definition 
 12============ 
 13Correspondence between concepts in a correspondence table.  
 14
 15Examples 
 16========== 
 17A 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. 
 18
 19Explanatory notes 
 20=================== 
 21A concept 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.</body>
 22   </ownedComment>
 23   <name>ConceptMap</name>
 24   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-correspondence"
 25                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-correspondence"
 26                   xmi:type="uml:Property">
 27      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-correspondence-ownedComment"
 28                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-correspondence-ownedComment"
 29                    xmi:type="uml:Comment">
 30         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-correspondence"/>
 31         <body>Type of correspondence in terms of commonalities and differences between two members.</body>
 32      </ownedComment>
 33      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-correspondence-lowerValue"
 34                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-correspondence-lowerValue"
 35                  xmi:type="uml:LiteralInteger"/>
 36      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-correspondence-upperValue"
 37                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-correspondence-upperValue"
 38                  xmi:type="uml:LiteralUnlimitedNatural">
 39         <value>1</value>
 40      </upperValue>
 41      <name>correspondence</name>
 42      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CorrespondenceDefinition"/>
 43   </ownedAttribute>
 44   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-displayLabel"
 45                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-displayLabel"
 46                   xmi:type="uml:Property">
 47      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-displayLabel-ownedComment"
 48                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-displayLabel-ownedComment"
 49                    xmi:type="uml:Comment">
 50         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-displayLabel"/>
 51         <body>A human-readable display label for the object. Supports the use of multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</body>
 52      </ownedComment>
 53      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-displayLabel-lowerValue"
 54                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-displayLabel-lowerValue"
 55                  xmi:type="uml:LiteralInteger"/>
 56      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-displayLabel-upperValue"
 57                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-displayLabel-upperValue"
 58                  xmi:type="uml:LiteralUnlimitedNatural">
 59         <value>1</value>
 60      </upperValue>
 61      <name>displayLabel</name>
 62      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-LabelForDisplay"/>
 63   </ownedAttribute>
 64   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-identifier"
 65                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-identifier"
 66                   xmi:type="uml:Property">
 67      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-identifier-ownedComment"
 68                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-identifier-ownedComment"
 69                    xmi:type="uml:Comment">
 70         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-identifier"/>
 71         <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
 72      </ownedComment>
 73      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-identifier-lowerValue"
 74                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-identifier-lowerValue"
 75                  xmi:type="uml:LiteralInteger"/>
 76      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-identifier-upperValue"
 77                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-identifier-upperValue"
 78                  xmi:type="uml:LiteralUnlimitedNatural">
 79         <value>1</value>
 80      </upperValue>
 81      <name>identifier</name>
 82      <isID>true</isID>
 83      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
 84   </ownedAttribute>
 85   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedAttribute_1"
 86                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedAttribute_1"
 87                   xmi:type="uml:Property">
 88      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedAttribute_1-lowerValue"
 89                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedAttribute_1-lowerValue"
 90                  xmi:type="uml:LiteralInteger">
 91         <value>1</value>
 92      </lowerValue>
 93      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedAttribute_1-upperValue"
 94                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedAttribute_1-upperValue"
 95                  xmi:type="uml:LiteralUnlimitedNatural">
 96         <value>*</value>
 97      </upperValue>
 98      <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap_hasSource_Concept"/>
 99      <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Concept"/>
100   </ownedAttribute>
101   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedAttribute_2"
102                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedAttribute_2"
103                   xmi:type="uml:Property">
104      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedAttribute_2-lowerValue"
105                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedAttribute_2-lowerValue"
106                  xmi:type="uml:LiteralInteger">
107         <value>1</value>
108      </lowerValue>
109      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-ownedAttribute_2-upperValue"
110                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-ownedAttribute_2-upperValue"
111                  xmi:type="uml:LiteralUnlimitedNatural">
112         <value>*</value>
113      </upperValue>
114      <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap_hasTarget_Concept"/>
115      <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Concept"/>
116   </ownedAttribute>
117   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-usage"
118                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-usage"
119                   xmi:type="uml:Property">
120      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-usage-ownedComment"
121                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-usage-ownedComment"
122                    xmi:type="uml:Comment">
123         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-usage"/>
124         <body>Explanation of the ways in which the object is employed.</body>
125      </ownedComment>
126      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-usage-lowerValue"
127                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-usage-lowerValue"
128                  xmi:type="uml:LiteralInteger"/>
129      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-usage-upperValue"
130                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-usage-upperValue"
131                  xmi:type="uml:LiteralUnlimitedNatural">
132         <value>1</value>
133      </upperValue>
134      <name>usage</name>
135      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
136   </ownedAttribute>
137   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-validDates"
138                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-validDates"
139                   xmi:type="uml:Property">
140      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-validDates-ownedComment"
141                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-validDates-ownedComment"
142                    xmi:type="uml:Comment">
143         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-validDates"/>
144         <body>The dates describing the validity period of the object. The date from which the object became valid must be defined if the map belongs to a "floating" construct. The date at which the object became invalid must be defined if the map belongs to a "floating" construct and is no longer valid.</body>
145      </ownedComment>
146      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-validDates-lowerValue"
147                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-validDates-lowerValue"
148                  xmi:type="uml:LiteralInteger"/>
149      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap-validDates-upperValue"
150                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptMap-validDates-upperValue"
151                  xmi:type="uml:LiteralUnlimitedNatural">
152         <value>1</value>
153      </upperValue>
154      <name>validDates</name>
155      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-DateRange"/>
156   </ownedAttribute>
157</packagedElement>

Fragment for the class ConceptMap (entire XML Schema)

  1<xs:element name="ConceptMap"
  2            type="ConceptMapXsdType"
  3            xml:id="ConceptMap">
  4  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptMap -->
  5  <xs:annotation>
  6    <xs:documentation>Definition 
  7          ============ 
  8          Correspondence between concepts in a correspondence table.  
  9          
 10          Examples 
 11          ========== 
 12          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. 
 13          
 14          Explanatory notes 
 15          =================== 
 16          A concept 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.</xs:documentation>
 17  </xs:annotation>
 18</xs:element>
 19<xs:complexType name="ConceptMapXsdType"
 20                xml:id="ConceptMapXsdType">
 21  <xs:annotation>
 22    <xs:documentation>Definition 
 23          ============ 
 24          Correspondence between concepts in a correspondence table.  
 25          
 26          Examples 
 27          ========== 
 28          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. 
 29          
 30          Explanatory notes 
 31          =================== 
 32          A concept 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.</xs:documentation>
 33  </xs:annotation>
 34  <xs:sequence>
 35    <xs:element name="correspondence"
 36                type="CorrespondenceDefinitionXsdType"
 37                minOccurs="0"
 38                maxOccurs="1"
 39                xml:id="ConceptMap-correspondence">
 40      <xs:annotation>
 41        <xs:documentation>Type of correspondence in terms of commonalities and differences between two members.</xs:documentation>
 42      </xs:annotation>
 43    </xs:element>
 44    <xs:element name="displayLabel"
 45                type="LabelForDisplayXsdType"
 46                minOccurs="0"
 47                maxOccurs="1"
 48                xml:id="ConceptMap-displayLabel">
 49      <xs:annotation>
 50        <xs:documentation>A human-readable display label for the object. Supports the use of multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
 51      </xs:annotation>
 52    </xs:element>
 53    <xs:element name="identifier"
 54                type="IdentifierXsdType"
 55                minOccurs="0"
 56                maxOccurs="1"
 57                xml:id="ConceptMap-identifier">
 58      <xs:annotation>
 59        <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
 60      </xs:annotation>
 61    </xs:element>
 62    <xs:element name="usage"
 63                type="InternationalStringXsdType"
 64                minOccurs="0"
 65                maxOccurs="1"
 66                xml:id="ConceptMap-usage">
 67      <xs:annotation>
 68        <xs:documentation>Explanation of the ways in which the object is employed.</xs:documentation>
 69      </xs:annotation>
 70    </xs:element>
 71    <xs:element name="validDates"
 72                type="DateRangeXsdType"
 73                minOccurs="0"
 74                maxOccurs="1"
 75                xml:id="ConceptMap-validDates">
 76      <xs:annotation>
 77        <xs:documentation>The dates describing the validity period of the object. The date from which the object became valid must be defined if the map belongs to a "floating" construct. The date at which the object became invalid must be defined if the map belongs to a "floating" construct and is no longer valid.</xs:documentation>
 78      </xs:annotation>
 79    </xs:element>
 80    <xs:element name="ConceptMap_hasSource_Concept"
 81                minOccurs="1"
 82                maxOccurs="unbounded"
 83                xml:id="ConceptMap_hasSource_Concept">
 84      <xs:annotation>
 85        <xs:documentation>Concept map has one to many source concepts.</xs:documentation>
 86      </xs:annotation>
 87      <xs:complexType>
 88        <xs:complexContent>
 89          <xs:restriction base="AssociationReferenceXsdType">
 90            <xs:sequence>
 91              <xs:element name="ddiReference"
 92                          type="InternationalRegistrationDataIdentifierXsdType"
 93                          minOccurs="0"
 94                          maxOccurs="1"
 95                          xml:id="ConceptMap_hasSource_Concept-ddiReference"/>
 96              <xs:element name="validType"
 97                          minOccurs="0"
 98                          maxOccurs="unbounded"
 99                          xml:id="ConceptMap_hasSource_Concept-validType">
100                <xs:simpleType>
101                  <xs:restriction base="xs:NMTOKEN">
102                    <xs:enumeration value="Category"/>
103                    <xs:enumeration value="Concept"/>
104                    <xs:enumeration value="ConceptualValue"/>
105                    <xs:enumeration value="ConceptualVariable"/>
106                    <xs:enumeration value="DescriptorVariable"/>
107                    <xs:enumeration value="DimensionalKeyDefinitionMember"/>
108                    <xs:enumeration value="InstanceVariable"/>
109                    <xs:enumeration value="KeyDefinitionMember"/>
110                    <xs:enumeration value="Population"/>
111                    <xs:enumeration value="ReferenceVariable"/>
112                    <xs:enumeration value="RepresentedVariable"/>
113                    <xs:enumeration value="UnitType"/>
114                    <xs:enumeration value="Universe"/>
115                  </xs:restriction>
116                </xs:simpleType>
117              </xs:element>
118            </xs:sequence>
119          </xs:restriction>
120        </xs:complexContent>
121      </xs:complexType>
122    </xs:element>
123    <xs:element name="ConceptMap_hasTarget_Concept"
124                minOccurs="1"
125                maxOccurs="unbounded"
126                xml:id="ConceptMap_hasTarget_Concept">
127      <xs:annotation>
128        <xs:documentation>Concept map has one to many target concepts.</xs:documentation>
129      </xs:annotation>
130      <xs:complexType>
131        <xs:complexContent>
132          <xs:restriction base="AssociationReferenceXsdType">
133            <xs:sequence>
134              <xs:element name="ddiReference"
135                          type="InternationalRegistrationDataIdentifierXsdType"
136                          minOccurs="0"
137                          maxOccurs="1"
138                          xml:id="ConceptMap_hasTarget_Concept-ddiReference"/>
139              <xs:element name="validType"
140                          minOccurs="0"
141                          maxOccurs="unbounded"
142                          xml:id="ConceptMap_hasTarget_Concept-validType">
143                <xs:simpleType>
144                  <xs:restriction base="xs:NMTOKEN">
145                    <xs:enumeration value="Category"/>
146                    <xs:enumeration value="Concept"/>
147                    <xs:enumeration value="ConceptualValue"/>
148                    <xs:enumeration value="ConceptualVariable"/>
149                    <xs:enumeration value="DescriptorVariable"/>
150                    <xs:enumeration value="DimensionalKeyDefinitionMember"/>
151                    <xs:enumeration value="InstanceVariable"/>
152                    <xs:enumeration value="KeyDefinitionMember"/>
153                    <xs:enumeration value="Population"/>
154                    <xs:enumeration value="ReferenceVariable"/>
155                    <xs:enumeration value="RepresentedVariable"/>
156                    <xs:enumeration value="UnitType"/>
157                    <xs:enumeration value="Universe"/>
158                  </xs:restriction>
159                </xs:simpleType>
160              </xs:element>
161            </xs:sequence>
162          </xs:restriction>
163        </xs:complexContent>
164      </xs:complexType>
165    </xs:element>
166  </xs:sequence>
167</xs:complexType>

Fragment for the class ConceptMap (main ontology)

 1# class ConceptMap
 2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptMap
 3cdi:ConceptMap
 4  a rdfs:Class, owl:Class, ucmis:Class;
 5  rdfs:label "ConceptMap";
 6  rdfs:comment "Definition \n============ \nCorrespondence between concepts in a correspondence table.  \n\nExamples \n========== \nA 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. \n\nExplanatory notes \n=================== \nA concept 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."@en;
 7  
 8.
 9
10cdi:ConceptMap-correspondence
11  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12  rdfs:label "correspondence";
13  rdfs:comment "Type of correspondence in terms of commonalities and differences between two members."@en;
14  rdfs:domain cdi:ConceptMap;
15  rdfs:range cdi:CorrespondenceDefinition;
16.
17
18cdi:ConceptMap-displayLabel
19  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
20  rdfs:label "displayLabel";
21  rdfs:comment "A human-readable display label for the object. Supports the use of multiple languages. Repeat for labels with different content, for example, labels with differing length limitations."@en;
22  rdfs:domain cdi:ConceptMap;
23  rdfs:range cdi:LabelForDisplay;
24.
25
26cdi:ConceptMap-identifier
27  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
28  rdfs:label "identifier";
29  rdfs:comment "Identifier for objects requiring short- or long-lasting referencing and management."@en;
30  rdfs:domain cdi:ConceptMap;
31  rdfs:range cdi:Identifier;
32.
33
34cdi:ConceptMap-usage
35  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
36  rdfs:label "usage";
37  rdfs:comment "Explanation of the ways in which the object is employed."@en;
38  rdfs:domain cdi:ConceptMap;
39  rdfs:range cdi:InternationalString;
40.
41
42cdi:ConceptMap-validDates
43  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
44  rdfs:label "validDates";
45  rdfs:comment "The dates describing the validity period of the object. The date from which the object became valid must be defined if the map belongs to a \"floating\" construct. The date at which the object became invalid must be defined if the map belongs to a \"floating\" construct and is no longer valid."@en;
46  rdfs:domain cdi:ConceptMap;
47  rdfs:range cdi:DateRange;
48.
49
50
51cdi:ConceptMap_hasSource_Concept
52  a rdf:Property, owl:ObjectProperty, ucmis:Association;
53  # ASSOCIATION
54  rdfs:label "hasSource";
55  skos:altLabel "ConceptMap_hasSource_Concept";
56  rdfs:comment "Concept map has one to many source concepts."@en;
57  rdfs:domain cdi:ConceptMap;
58  rdfs:range cdi:Concept;
59.
60
61cdi:ConceptMap_hasTarget_Concept
62  a rdf:Property, owl:ObjectProperty, ucmis:Association;
63  # ASSOCIATION
64  rdfs:label "hasTarget";
65  skos:altLabel "ConceptMap_hasTarget_Concept";
66  rdfs:comment "Concept map has one to many target concepts."@en;
67  rdfs:domain cdi:ConceptMap;
68  rdfs:range cdi:Concept;
69.

Fragment for the class ConceptMap (main JSON-LD)

 1{
 2  "@context": [
 3    {
 4      "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
 5      "xsd": "http://www.w3.org/2001/XMLSchema#",
 6      "ConceptMap": "cdi:ConceptMap",
 7      "correspondence": {
 8        "@id": "cdi:ConceptMap-correspondence",
 9        "@type": "@id",
10        "@context": "CorrespondenceDefinition.jsonld"
11      },
12      "displayLabel": {
13        "@id": "cdi:ConceptMap-displayLabel",
14        "@type": "@id",
15        "@context": "LabelForDisplay.jsonld"
16      },
17      "identifier": {
18        "@id": "cdi:ConceptMap-identifier",
19        "@type": "@id",
20        "@context": "Identifier.jsonld"
21      },
22      "usage": {
23        "@id": "cdi:ConceptMap-usage",
24        "@type": "@id",
25        "@context": "InternationalString.jsonld"
26      },
27      "validDates": {
28        "@id": "cdi:ConceptMap-validDates",
29        "@type": "@id",
30        "@context": "DateRange.jsonld"
31      },
32      
33      "hasSource": {
34        "@id": "cdi:ConceptMap_hasSource_Concept",
35        "@type": "@id"      },
36      "hasTarget": {
37        "@id": "cdi:ConceptMap_hasTarget_Concept",
38        "@type": "@id"      },
39      "has_OF_ConceptSystemCorrespondence": {
40        "@reverse": "cdi:ConceptSystemCorrespondence_has_ConceptMap",
41        "@type": "@id"
42      },
43      "has_OF_CorrespondenceTable": {
44        "@reverse": "cdi:CorrespondenceTable_has_ConceptMap",
45        "@type": "@id"
46      },
47      " comment ": "tag:json-should-support-trailing-commas" 
48    }
49  ],
50  "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:04.",
51  "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptMap"
52}