Datum¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::DataDescription::Datum
Definition¶
Correspondence of a data instance to the concept it represents.
Examples¶
A systolic blood pressure of 122 is measured. The single data instance (instance value) for that measurement is the character string “122”. The datum in this case is the association of the conceptual value, i.e. the underlying measured concept (a blood pressure at that level), with the instance value. if a datum represents the conceptual value “married” with a code “M,” it is not the same datum where that conceptual value is represented with a code “1”. If the datum which uses the code “M” is present in more than one data set, it is still the same datum.
Explanatory notes¶
The datum is a reification of the association between instance value and conceptual value. It is a designation (a representation of a concept by a sign) in the signification pattern. The data instance (instance value) is the signifier and the concept it represents (conceptual value) is the signified. The datum has an association with an instance variable which allows the attachment of a unit of measurement, a datatype, and a population. These instance variable attributes are critical for interpreting the signifier. NOTE: This is NOT datum as defined in The Data Documentation Initiative Lifecycle specification, which is more limited in breadth. This specification takes a little more formal (semiotic) description of a datum using the signification pattern. The datum is reusable, and may appear in more than one data set, carrying with it its full contextualized meaning and identity. The instance variables and instance values with which it is associated will therefore be functionally similar or identical across its appearance in different data instances. Instance variable and instance value are specific to a single data set instance – datum is not.
Diagram
Inheritance
DataDescription::Datum
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. |
0..1 |
||
identifier |
- own class - |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
Associations
Direction |
Association |
Description |
Multiplicity of Datum |
Package of Other Class |
Other Class |
Multiplicity of other class |
Aggregation Kind |
Inherited from |
|---|---|---|---|---|---|---|---|---|
from |
Datum isBoundedBy InstanceVariable |
A datum is bounded by an instance variable. The datum is drawn from a set of values, either substantive or sentinel described by the value domain of the instance variable. |
0..* |
1..* |
none |
- own class - |
||
from |
Datum denotes ConceptualValue |
0..* |
- own package - |
1..1 |
none |
- own class - |
||
from |
Datum uses InstanceValue |
0..* |
- own package - |
1..* |
none |
- own class - |
||
from |
Datum uses Notation |
0..* |
- own package - |
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 Datum (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-DataDescription-Datum"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum"/>
11 <body>Definition
12============
13Correspondence of a data instance to the concept it represents.
14
15Examples
16==========
17A systolic blood pressure of 122 is measured. The single data instance (instance value) for that measurement is the character string "122". The datum in this case is the association of the conceptual value, i.e. the underlying measured concept (a blood pressure at that level), with the instance value.
18if a datum represents the conceptual value “married” with a code “M,” it is not the same datum where that conceptual value is represented with a code “1”. If the datum which uses the code “M” is present in more than one data set, it is still the same datum.
19
20Explanatory notes
21===================
22The datum is a reification of the association between instance value and conceptual value. It is a designation (a representation of a concept by a sign) in the signification pattern. The data instance (instance value) is the signifier and the concept it represents (conceptual value) is the signified. The datum has an association with an instance variable which allows the attachment of a unit of measurement, a datatype, and a population. These instance variable attributes are critical for interpreting the signifier. NOTE: This is NOT datum as defined in The Data Documentation Initiative Lifecycle specification, which is more limited in breadth. This specification takes a little more formal (semiotic) description of a datum using the signification pattern.
23The datum is reusable, and may appear in more than one data set, carrying with it its full contextualized meaning and identity. The instance variables and instance values with which it is associated will therefore be functionally similar or identical across its appearance in different data instances. Instance variable and instance value are specific to a single data set instance – datum is not.</body>
24 </ownedComment>
25 <name>Datum</name>
26 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-catalogDetails"
27 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-catalogDetails"
28 xmi:type="uml:Property">
29 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-catalogDetails-ownedComment"
30 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-catalogDetails-ownedComment"
31 xmi:type="uml:Comment">
32 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-catalogDetails"/>
33 <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>
34 </ownedComment>
35 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-catalogDetails-lowerValue"
36 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-catalogDetails-lowerValue"
37 xmi:type="uml:LiteralInteger"/>
38 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-catalogDetails-upperValue"
39 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-catalogDetails-upperValue"
40 xmi:type="uml:LiteralUnlimitedNatural">
41 <value>1</value>
42 </upperValue>
43 <name>catalogDetails</name>
44 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
45 </ownedAttribute>
46 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-identifier"
47 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-identifier"
48 xmi:type="uml:Property">
49 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-identifier-ownedComment"
50 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-identifier-ownedComment"
51 xmi:type="uml:Comment">
52 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-identifier"/>
53 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
54 </ownedComment>
55 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-identifier-lowerValue"
56 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-identifier-lowerValue"
57 xmi:type="uml:LiteralInteger"/>
58 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-identifier-upperValue"
59 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-identifier-upperValue"
60 xmi:type="uml:LiteralUnlimitedNatural">
61 <value>1</value>
62 </upperValue>
63 <name>identifier</name>
64 <isID>true</isID>
65 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
66 </ownedAttribute>
67 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_1"
68 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_1"
69 xmi:type="uml:Property">
70 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_1-lowerValue"
71 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_1-lowerValue"
72 xmi:type="uml:LiteralInteger"/>
73 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_1-upperValue"
74 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_1-upperValue"
75 xmi:type="uml:LiteralUnlimitedNatural">
76 <value>1</value>
77 </upperValue>
78 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum_uses_Notation"/>
79 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Notation"/>
80 </ownedAttribute>
81 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_2"
82 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_2"
83 xmi:type="uml:Property">
84 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_2-lowerValue"
85 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_2-lowerValue"
86 xmi:type="uml:LiteralInteger">
87 <value>1</value>
88 </lowerValue>
89 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_2-upperValue"
90 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_2-upperValue"
91 xmi:type="uml:LiteralUnlimitedNatural">
92 <value>1</value>
93 </upperValue>
94 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum_denotes_ConceptualValue"/>
95 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-ConceptualValue"/>
96 </ownedAttribute>
97 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_3"
98 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_3"
99 xmi:type="uml:Property">
100 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_3-lowerValue"
101 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_3-lowerValue"
102 xmi:type="uml:LiteralInteger">
103 <value>1</value>
104 </lowerValue>
105 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_3-upperValue"
106 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_3-upperValue"
107 xmi:type="uml:LiteralUnlimitedNatural">
108 <value>*</value>
109 </upperValue>
110 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum_uses_InstanceValue"/>
111 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-InstanceValue"/>
112 </ownedAttribute>
113 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_4"
114 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_4"
115 xmi:type="uml:Property">
116 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_4-lowerValue"
117 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_4-lowerValue"
118 xmi:type="uml:LiteralInteger">
119 <value>1</value>
120 </lowerValue>
121 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Datum-ownedAttribute_4-upperValue"
122 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Datum-ownedAttribute_4-upperValue"
123 xmi:type="uml:LiteralUnlimitedNatural">
124 <value>*</value>
125 </upperValue>
126 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Datum_isBoundedBy_InstanceVariable"/>
127 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-InstanceVariable"/>
128 </ownedAttribute>
129</packagedElement>
Fragment for the class Datum (entire XML Schema)
1<xs:element name="Datum"
2 type="DatumXsdType"
3 xml:id="Datum">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::DataDescription::Datum -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ============
8 Correspondence of a data instance to the concept it represents.
9
10 Examples
11 ==========
12 A systolic blood pressure of 122 is measured. The single data instance (instance value) for that measurement is the character string "122". The datum in this case is the association of the conceptual value, i.e. the underlying measured concept (a blood pressure at that level), with the instance value.
13 if a datum represents the conceptual value “married” with a code “M,” it is not the same datum where that conceptual value is represented with a code “1”. If the datum which uses the code “M” is present in more than one data set, it is still the same datum.
14
15 Explanatory notes
16 ===================
17 The datum is a reification of the association between instance value and conceptual value. It is a designation (a representation of a concept by a sign) in the signification pattern. The data instance (instance value) is the signifier and the concept it represents (conceptual value) is the signified. The datum has an association with an instance variable which allows the attachment of a unit of measurement, a datatype, and a population. These instance variable attributes are critical for interpreting the signifier. NOTE: This is NOT datum as defined in The Data Documentation Initiative Lifecycle specification, which is more limited in breadth. This specification takes a little more formal (semiotic) description of a datum using the signification pattern.
18 The datum is reusable, and may appear in more than one data set, carrying with it its full contextualized meaning and identity. The instance variables and instance values with which it is associated will therefore be functionally similar or identical across its appearance in different data instances. Instance variable and instance value are specific to a single data set instance – datum is not.</xs:documentation>
19 </xs:annotation>
20</xs:element>
21<xs:complexType name="DatumXsdType"
22 xml:id="DatumXsdType">
23 <xs:annotation>
24 <xs:documentation>Definition
25 ============
26 Correspondence of a data instance to the concept it represents.
27
28 Examples
29 ==========
30 A systolic blood pressure of 122 is measured. The single data instance (instance value) for that measurement is the character string "122". The datum in this case is the association of the conceptual value, i.e. the underlying measured concept (a blood pressure at that level), with the instance value.
31 if a datum represents the conceptual value “married” with a code “M,” it is not the same datum where that conceptual value is represented with a code “1”. If the datum which uses the code “M” is present in more than one data set, it is still the same datum.
32
33 Explanatory notes
34 ===================
35 The datum is a reification of the association between instance value and conceptual value. It is a designation (a representation of a concept by a sign) in the signification pattern. The data instance (instance value) is the signifier and the concept it represents (conceptual value) is the signified. The datum has an association with an instance variable which allows the attachment of a unit of measurement, a datatype, and a population. These instance variable attributes are critical for interpreting the signifier. NOTE: This is NOT datum as defined in The Data Documentation Initiative Lifecycle specification, which is more limited in breadth. This specification takes a little more formal (semiotic) description of a datum using the signification pattern.
36 The datum is reusable, and may appear in more than one data set, carrying with it its full contextualized meaning and identity. The instance variables and instance values with which it is associated will therefore be functionally similar or identical across its appearance in different data instances. Instance variable and instance value are specific to a single data set instance – datum is not.</xs:documentation>
37 </xs:annotation>
38 <xs:sequence>
39 <xs:element name="catalogDetails"
40 type="CatalogDetailsXsdType"
41 minOccurs="0"
42 maxOccurs="1"
43 xml:id="Datum-catalogDetails">
44 <xs:annotation>
45 <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>
46 </xs:annotation>
47 </xs:element>
48 <xs:element name="identifier"
49 type="IdentifierXsdType"
50 minOccurs="0"
51 maxOccurs="1"
52 xml:id="Datum-identifier">
53 <xs:annotation>
54 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
55 </xs:annotation>
56 </xs:element>
57 <xs:element name="Datum_uses_Notation"
58 minOccurs="0"
59 maxOccurs="1"
60 xml:id="Datum_uses_Notation">
61 <xs:annotation>
62 <xs:documentation></xs:documentation>
63 </xs:annotation>
64 <xs:complexType>
65 <xs:complexContent>
66 <xs:restriction base="AssociationReferenceXsdType">
67 <xs:sequence>
68 <xs:element name="ddiReference"
69 type="InternationalRegistrationDataIdentifierXsdType"
70 minOccurs="0"
71 maxOccurs="1"
72 xml:id="Datum_uses_Notation-ddiReference"/>
73 <xs:element name="validType"
74 minOccurs="0"
75 maxOccurs="unbounded"
76 xml:id="Datum_uses_Notation-validType">
77 <xs:simpleType>
78 <xs:restriction base="xs:NMTOKEN">
79 <xs:enumeration value="Notation"/>
80 </xs:restriction>
81 </xs:simpleType>
82 </xs:element>
83 </xs:sequence>
84 </xs:restriction>
85 </xs:complexContent>
86 </xs:complexType>
87 </xs:element>
88 <xs:element name="Datum_denotes_ConceptualValue"
89 minOccurs="1"
90 maxOccurs="1"
91 xml:id="Datum_denotes_ConceptualValue">
92 <xs:annotation>
93 <xs:documentation></xs:documentation>
94 </xs:annotation>
95 <xs:complexType>
96 <xs:complexContent>
97 <xs:restriction base="AssociationReferenceXsdType">
98 <xs:sequence>
99 <xs:element name="ddiReference"
100 type="InternationalRegistrationDataIdentifierXsdType"
101 minOccurs="0"
102 maxOccurs="1"
103 xml:id="Datum_denotes_ConceptualValue-ddiReference"/>
104 <xs:element name="validType"
105 minOccurs="0"
106 maxOccurs="unbounded"
107 xml:id="Datum_denotes_ConceptualValue-validType">
108 <xs:simpleType>
109 <xs:restriction base="xs:NMTOKEN">
110 <xs:enumeration value="ConceptualValue"/>
111 <xs:enumeration value="DimensionalKeyDefinitionMember"/>
112 <xs:enumeration value="KeyDefinitionMember"/>
113 </xs:restriction>
114 </xs:simpleType>
115 </xs:element>
116 </xs:sequence>
117 </xs:restriction>
118 </xs:complexContent>
119 </xs:complexType>
120 </xs:element>
121 <xs:element name="Datum_uses_InstanceValue"
122 minOccurs="1"
123 maxOccurs="unbounded"
124 xml:id="Datum_uses_InstanceValue">
125 <xs:annotation>
126 <xs:documentation></xs:documentation>
127 </xs:annotation>
128 <xs:complexType>
129 <xs:complexContent>
130 <xs:restriction base="AssociationReferenceXsdType">
131 <xs:sequence>
132 <xs:element name="ddiReference"
133 type="InternationalRegistrationDataIdentifierXsdType"
134 minOccurs="0"
135 maxOccurs="1"
136 xml:id="Datum_uses_InstanceValue-ddiReference"/>
137 <xs:element name="validType"
138 minOccurs="0"
139 maxOccurs="unbounded"
140 xml:id="Datum_uses_InstanceValue-validType">
141 <xs:simpleType>
142 <xs:restriction base="xs:NMTOKEN">
143 <xs:enumeration value="Descriptor"/>
144 <xs:enumeration value="DimensionalKeyMember"/>
145 <xs:enumeration value="InstanceValue"/>
146 <xs:enumeration value="KeyMember"/>
147 <xs:enumeration value="LongMainKeyMember"/>
148 <xs:enumeration value="MainKeyMember"/>
149 <xs:enumeration value="ReferenceValue"/>
150 <xs:enumeration value="WideKeyMember"/>
151 </xs:restriction>
152 </xs:simpleType>
153 </xs:element>
154 </xs:sequence>
155 </xs:restriction>
156 </xs:complexContent>
157 </xs:complexType>
158 </xs:element>
159 <xs:element name="Datum_isBoundedBy_InstanceVariable"
160 minOccurs="1"
161 maxOccurs="unbounded"
162 xml:id="Datum_isBoundedBy_InstanceVariable">
163 <xs:annotation>
164 <xs:documentation>A datum is bounded by an instance variable. The datum is drawn from a set of values, either substantive or sentinel described by the value domain of the instance variable.</xs:documentation>
165 </xs:annotation>
166 <xs:complexType>
167 <xs:complexContent>
168 <xs:restriction base="AssociationReferenceXsdType">
169 <xs:sequence>
170 <xs:element name="ddiReference"
171 type="InternationalRegistrationDataIdentifierXsdType"
172 minOccurs="0"
173 maxOccurs="1"
174 xml:id="Datum_isBoundedBy_InstanceVariable-ddiReference"/>
175 <xs:element name="validType"
176 minOccurs="0"
177 maxOccurs="unbounded"
178 xml:id="Datum_isBoundedBy_InstanceVariable-validType">
179 <xs:simpleType>
180 <xs:restriction base="xs:NMTOKEN">
181 <xs:enumeration value="InstanceVariable"/>
182 </xs:restriction>
183 </xs:simpleType>
184 </xs:element>
185 </xs:sequence>
186 </xs:restriction>
187 </xs:complexContent>
188 </xs:complexType>
189 </xs:element>
190 </xs:sequence>
191</xs:complexType>
Fragment for the class Datum (main ontology)
1# class Datum
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::DataDescription::Datum
3cdi:Datum
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "Datum";
6 rdfs:comment "Definition \n============ \nCorrespondence of a data instance to the concept it represents. \n\nExamples \n========== \nA systolic blood pressure of 122 is measured. The single data instance (instance value) for that measurement is the character string \"122\". The datum in this case is the association of the conceptual value, i.e. the underlying measured concept (a blood pressure at that level), with the instance value. \nif a datum represents the conceptual value “married” with a code “M,” it is not the same datum where that conceptual value is represented with a code “1”. If the datum which uses the code “M” is present in more than one data set, it is still the same datum.\n\nExplanatory notes \n=================== \nThe datum is a reification of the association between instance value and conceptual value. It is a designation (a representation of a concept by a sign) in the signification pattern. The data instance (instance value) is the signifier and the concept it represents (conceptual value) is the signified. The datum has an association with an instance variable which allows the attachment of a unit of measurement, a datatype, and a population. These instance variable attributes are critical for interpreting the signifier. NOTE: This is NOT datum as defined in The Data Documentation Initiative Lifecycle specification, which is more limited in breadth. This specification takes a little more formal (semiotic) description of a datum using the signification pattern.\nThe datum is reusable, and may appear in more than one data set, carrying with it its full contextualized meaning and identity. The instance variables and instance values with which it is associated will therefore be functionally similar or identical across its appearance in different data instances. Instance variable and instance value are specific to a single data set instance – datum is not."@en;
7
8.
9
10cdi:Datum-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:Datum;
15 rdfs:range cdi:CatalogDetails;
16.
17
18cdi:Datum-identifier
19 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
20 rdfs:label "identifier";
21 rdfs:comment "Identifier for objects requiring short- or long-lasting referencing and management."@en;
22 rdfs:domain cdi:Datum;
23 rdfs:range cdi:Identifier;
24.
25
26
27cdi:Datum_isBoundedBy_InstanceVariable
28 a rdf:Property, owl:ObjectProperty, ucmis:Association;
29 # ASSOCIATION
30 rdfs:label "isBoundedBy";
31 skos:altLabel "Datum_isBoundedBy_InstanceVariable";
32 rdfs:comment "A datum is bounded by an instance variable. The datum is drawn from a set of values, either substantive or sentinel described by the value domain of the instance variable."@en;
33 rdfs:domain cdi:Datum;
34 rdfs:range cdi:InstanceVariable;
35.
36
37cdi:Datum_denotes_ConceptualValue
38 a rdf:Property, owl:ObjectProperty, ucmis:Association;
39 # ASSOCIATION
40 rdfs:label "denotes";
41 skos:altLabel "Datum_denotes_ConceptualValue";
42
43 rdfs:domain cdi:Datum;
44 rdfs:range cdi:ConceptualValue;
45.
46
47cdi:Datum_uses_InstanceValue
48 a rdf:Property, owl:ObjectProperty, ucmis:Association;
49 # ASSOCIATION
50 rdfs:label "uses";
51 skos:altLabel "Datum_uses_InstanceValue";
52
53 rdfs:domain cdi:Datum;
54 rdfs:range cdi:InstanceValue;
55.
56
57cdi:Datum_uses_Notation
58 a rdf:Property, owl:ObjectProperty, ucmis:Association;
59 # ASSOCIATION
60 rdfs:label "uses";
61 skos:altLabel "Datum_uses_Notation";
62
63 rdfs:domain cdi:Datum;
64 rdfs:range cdi:Notation;
65.
Fragment for the class Datum (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 "Datum": "cdi:Datum",
7 "catalogDetails": {
8 "@id": "cdi:Datum-catalogDetails",
9 "@type": "@id",
10 "@context": "CatalogDetails.jsonld"
11 },
12 "identifier": {
13 "@id": "cdi:Datum-identifier",
14 "@type": "@id",
15 "@context": "Identifier.jsonld"
16 },
17
18 "isBoundedBy": {
19 "@id": "cdi:Datum_isBoundedBy_InstanceVariable",
20 "@type": "@id" },
21 "denotes": {
22 "@id": "cdi:Datum_denotes_ConceptualValue",
23 "@type": "@id" },
24 "uses": {
25 "@id": "cdi:Datum_uses_InstanceValue",
26 "@type": "@id" },
27 "uses": {
28 "@id": "cdi:Datum_uses_Notation",
29 "@type": "@id" },
30 " comment ": "tag:json-should-support-trailing-commas"
31 }
32 ],
33 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:09.",
34 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::DataDescription::Datum"
35}
