ConceptSystemCorrespondence

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

Definition

Relationship between 2 or more concept systems described through mapping similarity relationships between their member concepts.

Examples

Correspondence between the concepts used to define the amount of salt dissolved in a body of water: the concepts “salinity” and “saltiness” might be described as equivalent, for example.

Explanatory notes

Describes correspondence with one or more maps which identify a source and target concept and defines their commonality and difference using descriptive text and controlled vocabularies.

Diagram

Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

catalogDetails

- own class -

Bundles the information useful for a data catalog entry. Examples would be creator, contributor, title, copyright, embargo, and license information. A set of information useful for attribution, data discovery, and access. This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.

CatalogDetails

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

identifier

- own class -

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

Identifier

0..1

purpose

- own class -

Intent or reason for the object/the description of the object.

InternationalString

0..1

usage

- own class -

Explanation of the ways in which the object is employed.

InternationalString

0..1

Associations

Direction

Association

Description

Multiplicity of ConceptSystemCorrespondence

Package of Other Class

Other Class

Multiplicity of other class

Aggregation Kind

Inherited from

from

ConceptSystemCorrespondence has ConceptMap

Concept system correspondence has zero to many concept maps.

0..1

- own package -

ConceptMap

0..*

composite

- own class -

from

ConceptSystemCorrespondence maps ConceptSystem

Concept system correspondence maps two to many concept systems. Realization of structures in symmetric relation. When concepts of a single concept system are mapped, the Concept has to appear twice as target.

0..*

- own package -

ConceptSystem

2..*

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 ConceptSystemCorrespondence (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-ConceptSystemCorrespondence"
  5                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence"
  6                 xmi:type="uml:Class">
  7   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedComment"
  8                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedComment"
  9                 xmi:type="uml:Comment">
 10      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence"/>
 11      <body>Definition 
 12============ 
 13Relationship between 2 or more concept systems described through mapping similarity relationships between their member concepts.  
 14
 15Examples 
 16========== 
 17Correspondence between the concepts used to define the amount of salt dissolved in a body of water: the concepts "salinity" and "saltiness" might be described as equivalent, for example.
 18
 19Explanatory notes 
 20=================== 
 21Describes correspondence with one or more maps which identify a source and target concept and defines their commonality and difference using descriptive text and controlled vocabularies.</body>
 22   </ownedComment>
 23   <name>ConceptSystemCorrespondence</name>
 24   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-catalogDetails"
 25                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-catalogDetails"
 26                   xmi:type="uml:Property">
 27      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-catalogDetails-ownedComment"
 28                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-catalogDetails-ownedComment"
 29                    xmi:type="uml:Comment">
 30         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-catalogDetails"/>
 31         <body>Bundles the information useful for a data catalog entry. Examples would be creator, contributor, title, copyright, embargo, and license information. A set of information useful for attribution, data discovery, and access. This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</body>
 32      </ownedComment>
 33      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-catalogDetails-lowerValue"
 34                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-catalogDetails-lowerValue"
 35                  xmi:type="uml:LiteralInteger"/>
 36      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-catalogDetails-upperValue"
 37                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-catalogDetails-upperValue"
 38                  xmi:type="uml:LiteralUnlimitedNatural">
 39         <value>1</value>
 40      </upperValue>
 41      <name>catalogDetails</name>
 42      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
 43   </ownedAttribute>
 44   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-displayLabel"
 45                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-displayLabel"
 46                   xmi:type="uml:Property">
 47      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-displayLabel-ownedComment"
 48                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-displayLabel-ownedComment"
 49                    xmi:type="uml:Comment">
 50         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-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-ConceptSystemCorrespondence-displayLabel-lowerValue"
 54                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-displayLabel-lowerValue"
 55                  xmi:type="uml:LiteralInteger"/>
 56      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-displayLabel-upperValue"
 57                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-displayLabel-upperValue"
 58                  xmi:type="uml:LiteralUnlimitedNatural">
 59         <value>*</value>
 60      </upperValue>
 61      <name>displayLabel</name>
 62      <isOrdered>true</isOrdered>
 63      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-LabelForDisplay"/>
 64   </ownedAttribute>
 65   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-identifier"
 66                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-identifier"
 67                   xmi:type="uml:Property">
 68      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-identifier-ownedComment"
 69                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-identifier-ownedComment"
 70                    xmi:type="uml:Comment">
 71         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-identifier"/>
 72         <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
 73      </ownedComment>
 74      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-identifier-lowerValue"
 75                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-identifier-lowerValue"
 76                  xmi:type="uml:LiteralInteger"/>
 77      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-identifier-upperValue"
 78                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-identifier-upperValue"
 79                  xmi:type="uml:LiteralUnlimitedNatural">
 80         <value>1</value>
 81      </upperValue>
 82      <name>identifier</name>
 83      <isID>true</isID>
 84      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
 85   </ownedAttribute>
 86   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedAttribute_1"
 87                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedAttribute_1"
 88                   xmi:type="uml:Property">
 89      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedAttribute_1-lowerValue"
 90                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedAttribute_1-lowerValue"
 91                  xmi:type="uml:LiteralInteger">
 92         <value>2</value>
 93      </lowerValue>
 94      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedAttribute_1-upperValue"
 95                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedAttribute_1-upperValue"
 96                  xmi:type="uml:LiteralUnlimitedNatural">
 97         <value>*</value>
 98      </upperValue>
 99      <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence_maps_ConceptSystem"/>
100      <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystem"/>
101   </ownedAttribute>
102   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedAttribute_2"
103                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedAttribute_2"
104                   xmi:type="uml:Property">
105      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedAttribute_2-lowerValue"
106                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedAttribute_2-lowerValue"
107                  xmi:type="uml:LiteralInteger"/>
108      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-ownedAttribute_2-upperValue"
109                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-ownedAttribute_2-upperValue"
110                  xmi:type="uml:LiteralUnlimitedNatural">
111         <value>*</value>
112      </upperValue>
113      <aggregation>composite</aggregation>
114      <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence_has_ConceptMap"/>
115      <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptMap"/>
116   </ownedAttribute>
117   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-purpose"
118                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-purpose"
119                   xmi:type="uml:Property">
120      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-purpose-ownedComment"
121                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-purpose-ownedComment"
122                    xmi:type="uml:Comment">
123         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-purpose"/>
124         <body>Intent or reason for the object/the description of the object.</body>
125      </ownedComment>
126      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-purpose-lowerValue"
127                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-purpose-lowerValue"
128                  xmi:type="uml:LiteralInteger"/>
129      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-purpose-upperValue"
130                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-purpose-upperValue"
131                  xmi:type="uml:LiteralUnlimitedNatural">
132         <value>1</value>
133      </upperValue>
134      <name>purpose</name>
135      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
136   </ownedAttribute>
137   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-usage"
138                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-usage"
139                   xmi:type="uml:Property">
140      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-usage-ownedComment"
141                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-usage-ownedComment"
142                    xmi:type="uml:Comment">
143         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-usage"/>
144         <body>Explanation of the ways in which the object is employed.</body>
145      </ownedComment>
146      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-usage-lowerValue"
147                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-usage-lowerValue"
148                  xmi:type="uml:LiteralInteger"/>
149      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-ConceptSystemCorrespondence-usage-upperValue"
150                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ConceptSystemCorrespondence-usage-upperValue"
151                  xmi:type="uml:LiteralUnlimitedNatural">
152         <value>1</value>
153      </upperValue>
154      <name>usage</name>
155      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
156   </ownedAttribute>
157</packagedElement>

Fragment for the class ConceptSystemCorrespondence (entire XML Schema)

  1<xs:element name="ConceptSystemCorrespondence"
  2            type="ConceptSystemCorrespondenceXsdType"
  3            xml:id="ConceptSystemCorrespondence">
  4  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptSystemCorrespondence -->
  5  <xs:annotation>
  6    <xs:documentation>Definition 
  7          ============ 
  8          Relationship between 2 or more concept systems described through mapping similarity relationships between their member concepts.  
  9          
 10          Examples 
 11          ========== 
 12          Correspondence between the concepts used to define the amount of salt dissolved in a body of water: the concepts "salinity" and "saltiness" might be described as equivalent, for example.
 13          
 14          Explanatory notes 
 15          =================== 
 16          Describes correspondence with one or more maps which identify a source and target concept and defines their commonality and difference using descriptive text and controlled vocabularies.</xs:documentation>
 17  </xs:annotation>
 18</xs:element>
 19<xs:complexType name="ConceptSystemCorrespondenceXsdType"
 20                xml:id="ConceptSystemCorrespondenceXsdType">
 21  <xs:annotation>
 22    <xs:documentation>Definition 
 23          ============ 
 24          Relationship between 2 or more concept systems described through mapping similarity relationships between their member concepts.  
 25          
 26          Examples 
 27          ========== 
 28          Correspondence between the concepts used to define the amount of salt dissolved in a body of water: the concepts "salinity" and "saltiness" might be described as equivalent, for example.
 29          
 30          Explanatory notes 
 31          =================== 
 32          Describes correspondence with one or more maps which identify a source and target concept and defines their commonality and difference using descriptive text and controlled vocabularies.</xs:documentation>
 33  </xs:annotation>
 34  <xs:sequence>
 35    <xs:element name="catalogDetails"
 36                type="CatalogDetailsXsdType"
 37                minOccurs="0"
 38                maxOccurs="1"
 39                xml:id="ConceptSystemCorrespondence-catalogDetails">
 40      <xs:annotation>
 41        <xs:documentation>Bundles the information useful for a data catalog entry. Examples would be creator, contributor, title, copyright, embargo, and license information. A set of information useful for attribution, data discovery, and access. This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</xs:documentation>
 42      </xs:annotation>
 43    </xs:element>
 44    <xs:element name="displayLabel"
 45                type="LabelForDisplayXsdType"
 46                minOccurs="0"
 47                maxOccurs="unbounded"
 48                xml:id="ConceptSystemCorrespondence-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="ConceptSystemCorrespondence-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="purpose"
 63                type="InternationalStringXsdType"
 64                minOccurs="0"
 65                maxOccurs="1"
 66                xml:id="ConceptSystemCorrespondence-purpose">
 67      <xs:annotation>
 68        <xs:documentation>Intent or reason for the object/the description of the object.</xs:documentation>
 69      </xs:annotation>
 70    </xs:element>
 71    <xs:element name="usage"
 72                type="InternationalStringXsdType"
 73                minOccurs="0"
 74                maxOccurs="1"
 75                xml:id="ConceptSystemCorrespondence-usage">
 76      <xs:annotation>
 77        <xs:documentation>Explanation of the ways in which the object is employed.</xs:documentation>
 78      </xs:annotation>
 79    </xs:element>
 80    <xs:element name="ConceptSystemCorrespondence_maps_ConceptSystem"
 81                minOccurs="2"
 82                maxOccurs="unbounded"
 83                xml:id="ConceptSystemCorrespondence_maps_ConceptSystem">
 84      <xs:annotation>
 85        <xs:documentation>Concept system correspondence maps two to many concept systems. Realization of structures in symmetric relation. When concepts of a single concept system are mapped, the Concept has to appear twice as target.</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="ConceptSystemCorrespondence_maps_ConceptSystem-ddiReference"/>
 96              <xs:element name="validType"
 97                          minOccurs="0"
 98                          maxOccurs="unbounded"
 99                          xml:id="ConceptSystemCorrespondence_maps_ConceptSystem-validType">
100                <xs:simpleType>
101                  <xs:restriction base="xs:NMTOKEN">
102                    <xs:enumeration value="CategorySet"/>
103                    <xs:enumeration value="ConceptSystem"/>
104                  </xs:restriction>
105                </xs:simpleType>
106              </xs:element>
107            </xs:sequence>
108          </xs:restriction>
109        </xs:complexContent>
110      </xs:complexType>
111    </xs:element>
112    <xs:element name="ConceptSystemCorrespondence_has_ConceptMap"
113                minOccurs="0"
114                maxOccurs="unbounded"
115                xml:id="ConceptSystemCorrespondence_has_ConceptMap">
116      <xs:annotation>
117        <xs:documentation>Concept system correspondence has zero to many concept maps.</xs:documentation>
118      </xs:annotation>
119      <xs:complexType>
120        <xs:complexContent>
121          <xs:restriction base="AssociationReferenceXsdType">
122            <xs:sequence>
123              <xs:element name="ddiReference"
124                          type="InternationalRegistrationDataIdentifierXsdType"
125                          minOccurs="0"
126                          maxOccurs="1"
127                          xml:id="ConceptSystemCorrespondence_has_ConceptMap-ddiReference"/>
128              <xs:element name="validType"
129                          minOccurs="0"
130                          maxOccurs="1"
131                          xml:id="ConceptSystemCorrespondence_has_ConceptMap-validType">
132                <xs:simpleType>
133                  <xs:restriction base="xs:NMTOKEN">
134                    <xs:enumeration value="ConceptMap"/>
135                  </xs:restriction>
136                </xs:simpleType>
137              </xs:element>
138            </xs:sequence>
139          </xs:restriction>
140        </xs:complexContent>
141      </xs:complexType>
142    </xs:element>
143  </xs:sequence>
144</xs:complexType>

Fragment for the class ConceptSystemCorrespondence (main ontology)

 1# class ConceptSystemCorrespondence
 2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptSystemCorrespondence
 3cdi:ConceptSystemCorrespondence
 4  a rdfs:Class, owl:Class, ucmis:Class;
 5  rdfs:label "ConceptSystemCorrespondence";
 6  rdfs:comment "Definition \n============ \nRelationship between 2 or more concept systems described through mapping similarity relationships between their member concepts.  \n\nExamples \n========== \nCorrespondence between the concepts used to define the amount of salt dissolved in a body of water: the concepts \"salinity\" and \"saltiness\" might be described as equivalent, for example.\n\nExplanatory notes \n=================== \nDescribes correspondence with one or more maps which identify a source and target concept and defines their commonality and difference using descriptive text and controlled vocabularies."@en;
 7  
 8.
 9
10cdi:ConceptSystemCorrespondence-catalogDetails
11  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12  rdfs:label "catalogDetails";
13  rdfs:comment "Bundles the information useful for a data catalog entry. Examples would be creator, contributor, title, copyright, embargo, and license information. A set of information useful for attribution, data discovery, and access. This is information that is tied to the identity of the object. If this information changes the version of the associated object changes."@en;
14  rdfs:domain cdi:ConceptSystemCorrespondence;
15  rdfs:range cdi:CatalogDetails;
16.
17
18cdi:ConceptSystemCorrespondence-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:ConceptSystemCorrespondence;
23  rdfs:range cdi:LabelForDisplay;
24.
25
26cdi:ConceptSystemCorrespondence-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:ConceptSystemCorrespondence;
31  rdfs:range cdi:Identifier;
32.
33
34cdi:ConceptSystemCorrespondence-purpose
35  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
36  rdfs:label "purpose";
37  rdfs:comment "Intent or reason for the object/the description of the object."@en;
38  rdfs:domain cdi:ConceptSystemCorrespondence;
39  rdfs:range cdi:InternationalString;
40.
41
42cdi:ConceptSystemCorrespondence-usage
43  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
44  rdfs:label "usage";
45  rdfs:comment "Explanation of the ways in which the object is employed."@en;
46  rdfs:domain cdi:ConceptSystemCorrespondence;
47  rdfs:range cdi:InternationalString;
48.
49
50
51cdi:ConceptSystemCorrespondence_has_ConceptMap
52  a rdf:Property, owl:ObjectProperty, ucmis:Association;
53  # ASSOCIATION
54  rdfs:label "has";
55  skos:altLabel "ConceptSystemCorrespondence_has_ConceptMap";
56  rdfs:comment "Concept system correspondence has zero to many concept maps."@en;
57  rdfs:domain cdi:ConceptSystemCorrespondence;
58  rdfs:range cdi:ConceptMap;
59.
60
61cdi:ConceptSystemCorrespondence_maps_ConceptSystem
62  a rdf:Property, owl:ObjectProperty, ucmis:Association;
63  # ASSOCIATION
64  rdfs:label "maps";
65  skos:altLabel "ConceptSystemCorrespondence_maps_ConceptSystem";
66  rdfs:comment "Concept system correspondence maps two to many concept systems. Realization of structures in symmetric relation. When concepts of a single concept system are mapped, the Concept has to appear twice as target."@en;
67  rdfs:domain cdi:ConceptSystemCorrespondence;
68  rdfs:range cdi:ConceptSystem;
69.

Fragment for the class ConceptSystemCorrespondence (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      "ConceptSystemCorrespondence": "cdi:ConceptSystemCorrespondence",
 7      "catalogDetails": {
 8        "@id": "cdi:ConceptSystemCorrespondence-catalogDetails",
 9        "@type": "@id",
10        "@context": "CatalogDetails.jsonld"
11      },
12      "displayLabel": {
13        "@id": "cdi:ConceptSystemCorrespondence-displayLabel",
14        "@type": "@id",
15        "@context": "LabelForDisplay.jsonld"
16      },
17      "identifier": {
18        "@id": "cdi:ConceptSystemCorrespondence-identifier",
19        "@type": "@id",
20        "@context": "Identifier.jsonld"
21      },
22      "purpose": {
23        "@id": "cdi:ConceptSystemCorrespondence-purpose",
24        "@type": "@id",
25        "@context": "InternationalString.jsonld"
26      },
27      "usage": {
28        "@id": "cdi:ConceptSystemCorrespondence-usage",
29        "@type": "@id",
30        "@context": "InternationalString.jsonld"
31      },
32      
33      "has": {
34        "@id": "cdi:ConceptSystemCorrespondence_has_ConceptMap",
35        "@type": "@id"      },
36      "maps": {
37        "@id": "cdi:ConceptSystemCorrespondence_maps_ConceptSystem",
38        "@type": "@id"      },
39      " comment ": "tag:json-should-support-trailing-commas" 
40    }
41  ],
42  "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-09-23 21:52:55.",
43  "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Conceptual::ConceptSystemCorrespondence"
44}