PhysicalRecordSegment¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalRecordSegment
Definition¶
Description of each physical storage segment required to completely cover a physical record representing the logical record.
Examples¶
The file below has four instance variables: PersonId, SegmentId, AgeYr, and HeightCm. The data for each person (identified by PersonId) is recorded in two segments (identified by SegmentId), “a” and “b”. AgeYr is on physical segment a, and HeightCm is on segment b. These are the same data as described in the unit segment layout documentation.
1 a 22
1 b 183
2 a 45
2 b 175
Explanatory notes¶
A logical record may be stored in one or more segments housed hierarchically in a single file or in separate data files. All logical records have at least one segment.
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. |
0..1 |
||
identifier |
- own class - |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
||
name |
- own class - |
Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage. |
0..* |
||
physicalFileName |
- own class - |
Use when each physical segment is stored in its own file. |
String |
0..1 |
|
purpose |
- own class - |
Intent or reason for the object/the description of the object. |
0..1 |
Associations
Direction |
Association |
Description |
Multiplicity of PhysicalRecordSegment |
Package of Other Class |
Other Class |
Multiplicity of other class |
Aggregation Kind |
Inherited from |
|---|---|---|---|---|---|---|---|---|
from |
PhysicalRecordSegment isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
- own class - |
||
from |
PhysicalRecordSegment represents Population |
A record segment may represent a specific population or sub-population within a larger set of segments. Allows for the identification of this filter for membership in the segment. |
0..* |
0..1 |
none |
- own class - |
||
from |
PhysicalRecordSegment has DataPoint |
0..* |
0..* |
shared |
- own class - |
|||
to |
PhysicalDataSet has PhysicalRecordSegment |
0..* |
- own package - |
0..* |
none |
- own class - |
||
from |
PhysicalRecordSegment has DataPointPosition |
1..1 |
- own package - |
0..* |
composite |
- own class - |
||
from |
PhysicalRecordSegment has PhysicalSegmentLayout |
0..* |
- own package - |
0..1 |
none |
- own class - |
||
from |
PhysicalRecordSegment mapsTo LogicalRecord |
Every data record has zero to many physical record segments. It is possible to describe a physical data product and its record segment(s) without reference to a data record. |
0..* |
- own package - |
0..1 |
none |
- own class - |
|
to |
PhysicalRecordSegmentPosition indexes PhysicalRecordSegment |
Assigns a position to a physical record segment within a physical record. |
1..1 |
- own package - |
0..* |
none |
- own class - |
|
to |
PhysicalRecordSegmentRelationship hasSource PhysicalRecordSegment |
0..1 |
- own package - |
0..* |
none |
- own class - |
||
to |
PhysicalRecordSegmentRelationship hasTarget PhysicalRecordSegment |
0..* |
- own package - |
0..* |
none |
- own class - |
||
to |
PhysicalRecordSegmentStructure structures PhysicalRecordSegment |
There may be cases where there is a more complex structure to a sequence of data points. A cell containing a list, for example, might be considered to have nested data points that are the elements of the list. (For simplicity’s sake, each element of the list should be modeled as a data point if this is possible.) |
0..1 |
- own package - |
0..* |
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 PhysicalRecordSegment (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-FormatDescription-PhysicalRecordSegment"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment"/>
11 <body>Definition
12==========
13Description of each physical storage segment required to completely cover a physical record representing the logical record.
14
15Examples
16========
17The file below has four instance variables: PersonId, SegmentId, AgeYr, and HeightCm. The data for each person (identified by PersonId) is recorded in two segments (identified by SegmentId), "a" and "b". AgeYr is on physical segment a, and HeightCm is on segment b. These are the same data as described in the unit segment layout documentation. ::
18
19 1 a 22
20 1 b 183
21 2 a 45
22 2 b 175
23
24Explanatory notes
25=================
26A logical record may be stored in one or more segments housed hierarchically in a single file or in separate data files. All logical records have at least one segment.</body>
27 </ownedComment>
28 <name>PhysicalRecordSegment</name>
29 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails"
30 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails"
31 xmi:type="uml:Property">
32 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails-ownedComment"
33 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails-ownedComment"
34 xmi:type="uml:Comment">
35 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails"/>
36 <body>Bundles the information useful for a data catalog entry.
37
38Examples would be creator, contributor, title, copyright, embargo, and license information
39
40A set of information useful for attribution, data discovery, and access.
41This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</body>
42 </ownedComment>
43 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails-lowerValue"
44 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails-lowerValue"
45 xmi:type="uml:LiteralInteger"/>
46 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails-upperValue"
47 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails-upperValue"
48 xmi:type="uml:LiteralUnlimitedNatural">
49 <value>1</value>
50 </upperValue>
51 <name>catalogDetails</name>
52 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
53 </ownedAttribute>
54 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier"
55 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier"
56 xmi:type="uml:Property">
57 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier-ownedComment"
58 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier-ownedComment"
59 xmi:type="uml:Comment">
60 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier"/>
61 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
62 </ownedComment>
63 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier-lowerValue"
64 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier-lowerValue"
65 xmi:type="uml:LiteralInteger"/>
66 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier-upperValue"
67 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier-upperValue"
68 xmi:type="uml:LiteralUnlimitedNatural">
69 <value>1</value>
70 </upperValue>
71 <name>identifier</name>
72 <isID>true</isID>
73 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
74 </ownedAttribute>
75 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name"
76 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name"
77 xmi:type="uml:Property">
78 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name-ownedComment"
79 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name-ownedComment"
80 xmi:type="uml:Comment">
81 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name"/>
82 <body>Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage.</body>
83 </ownedComment>
84 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name-lowerValue"
85 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name-lowerValue"
86 xmi:type="uml:LiteralInteger"/>
87 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name-upperValue"
88 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name-upperValue"
89 xmi:type="uml:LiteralUnlimitedNatural">
90 <value>*</value>
91 </upperValue>
92 <name>name</name>
93 <isOrdered>true</isOrdered>
94 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ObjectName"/>
95 </ownedAttribute>
96 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_1"
97 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_1"
98 xmi:type="uml:Property">
99 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_1-lowerValue"
100 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_1-lowerValue"
101 xmi:type="uml:LiteralInteger"/>
102 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_1-upperValue"
103 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_1-upperValue"
104 xmi:type="uml:LiteralUnlimitedNatural">
105 <value>1</value>
106 </upperValue>
107 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-PhysicalRecordSegment_represents_Population"/>
108 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Population"/>
109 </ownedAttribute>
110 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_2"
111 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_2"
112 xmi:type="uml:Property">
113 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_2-lowerValue"
114 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_2-lowerValue"
115 xmi:type="uml:LiteralInteger"/>
116 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_2-upperValue"
117 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_2-upperValue"
118 xmi:type="uml:LiteralUnlimitedNatural">
119 <value>*</value>
120 </upperValue>
121 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-PhysicalRecordSegment_isDefinedBy_Concept"/>
122 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Concept"/>
123 </ownedAttribute>
124 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_3"
125 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_3"
126 xmi:type="uml:Property">
127 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_3-lowerValue"
128 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_3-lowerValue"
129 xmi:type="uml:LiteralInteger"/>
130 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_3-upperValue"
131 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_3-upperValue"
132 xmi:type="uml:LiteralUnlimitedNatural">
133 <value>1</value>
134 </upperValue>
135 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment_has_PhysicalSegmentLayout"/>
136 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLayout"/>
137 </ownedAttribute>
138 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_4"
139 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_4"
140 xmi:type="uml:Property">
141 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_4-lowerValue"
142 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_4-lowerValue"
143 xmi:type="uml:LiteralInteger"/>
144 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_4-upperValue"
145 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_4-upperValue"
146 xmi:type="uml:LiteralUnlimitedNatural">
147 <value>1</value>
148 </upperValue>
149 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment_mapsTo_LogicalRecord"/>
150 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-LogicalRecord"/>
151 </ownedAttribute>
152 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_5"
153 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_5"
154 xmi:type="uml:Property">
155 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_5-lowerValue"
156 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_5-lowerValue"
157 xmi:type="uml:LiteralInteger"/>
158 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_5-upperValue"
159 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_5-upperValue"
160 xmi:type="uml:LiteralUnlimitedNatural">
161 <value>*</value>
162 </upperValue>
163 <aggregation>composite</aggregation>
164 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment_has_DataPointPosition"/>
165 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-DataPointPosition"/>
166 </ownedAttribute>
167 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_6"
168 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_6"
169 xmi:type="uml:Property">
170 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_6-lowerValue"
171 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_6-lowerValue"
172 xmi:type="uml:LiteralInteger"/>
173 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_6-upperValue"
174 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_6-upperValue"
175 xmi:type="uml:LiteralUnlimitedNatural">
176 <value>*</value>
177 </upperValue>
178 <aggregation>shared</aggregation>
179 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-PhysicalRecordSegment_has_DataPoint"/>
180 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-DataPoint"/>
181 </ownedAttribute>
182 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName"
183 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName"
184 xmi:type="uml:Property">
185 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName-ownedComment"
186 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName-ownedComment"
187 xmi:type="uml:Comment">
188 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName"/>
189 <body>Use when each physical segment is stored in its own file.</body>
190 </ownedComment>
191 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName-lowerValue"
192 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName-lowerValue"
193 xmi:type="uml:LiteralInteger"/>
194 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName-upperValue"
195 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName-upperValue"
196 xmi:type="uml:LiteralUnlimitedNatural">
197 <value>1</value>
198 </upperValue>
199 <name>physicalFileName</name>
200 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#String"
201 xmi:type="uml:PrimitiveType"/>
202 </ownedAttribute>
203 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose"
204 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose"
205 xmi:type="uml:Property">
206 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose-ownedComment"
207 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose-ownedComment"
208 xmi:type="uml:Comment">
209 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose"/>
210 <body>Intent or reason for the object/the description of the object.</body>
211 </ownedComment>
212 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose-lowerValue"
213 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose-lowerValue"
214 xmi:type="uml:LiteralInteger"/>
215 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose-upperValue"
216 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose-upperValue"
217 xmi:type="uml:LiteralUnlimitedNatural">
218 <value>1</value>
219 </upperValue>
220 <name>purpose</name>
221 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
222 </ownedAttribute>
223</packagedElement>
Fragment for the class PhysicalRecordSegment (entire XML Schema)
1<xs:element name="PhysicalRecordSegment"
2 type="PhysicalRecordSegmentXsdType"
3 xml:id="PhysicalRecordSegment">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalRecordSegment -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ==========
8 Description of each physical storage segment required to completely cover a physical record representing the logical record.
9
10 Examples
11 ========
12 The file below has four instance variables: PersonId, SegmentId, AgeYr, and HeightCm. The data for each person (identified by PersonId) is recorded in two segments (identified by SegmentId), "a" and "b". AgeYr is on physical segment a, and HeightCm is on segment b. These are the same data as described in the unit segment layout documentation. ::
13
14 1 a 22
15 1 b 183
16 2 a 45
17 2 b 175
18
19 Explanatory notes
20 =================
21 A logical record may be stored in one or more segments housed hierarchically in a single file or in separate data files. All logical records have at least one segment.</xs:documentation>
22 </xs:annotation>
23</xs:element>
24<xs:complexType name="PhysicalRecordSegmentXsdType"
25 xml:id="PhysicalRecordSegmentXsdType">
26 <xs:annotation>
27 <xs:documentation>Definition
28 ==========
29 Description of each physical storage segment required to completely cover a physical record representing the logical record.
30
31 Examples
32 ========
33 The file below has four instance variables: PersonId, SegmentId, AgeYr, and HeightCm. The data for each person (identified by PersonId) is recorded in two segments (identified by SegmentId), "a" and "b". AgeYr is on physical segment a, and HeightCm is on segment b. These are the same data as described in the unit segment layout documentation. ::
34
35 1 a 22
36 1 b 183
37 2 a 45
38 2 b 175
39
40 Explanatory notes
41 =================
42 A logical record may be stored in one or more segments housed hierarchically in a single file or in separate data files. All logical records have at least one segment.</xs:documentation>
43 </xs:annotation>
44 <xs:sequence>
45 <xs:element name="catalogDetails"
46 type="CatalogDetailsXsdType"
47 minOccurs="0"
48 maxOccurs="1"
49 xml:id="PhysicalRecordSegment-catalogDetails">
50 <xs:annotation>
51 <xs:documentation>Bundles the information useful for a data catalog entry.
52
53 Examples would be creator, contributor, title, copyright, embargo, and license information
54
55 A set of information useful for attribution, data discovery, and access.
56 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>
57 </xs:annotation>
58 </xs:element>
59 <xs:element name="identifier"
60 type="IdentifierXsdType"
61 minOccurs="0"
62 maxOccurs="1"
63 xml:id="PhysicalRecordSegment-identifier">
64 <xs:annotation>
65 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
66 </xs:annotation>
67 </xs:element>
68 <xs:element name="name"
69 type="ObjectNameXsdType"
70 minOccurs="0"
71 maxOccurs="unbounded"
72 xml:id="PhysicalRecordSegment-name">
73 <xs:annotation>
74 <xs:documentation>Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage.</xs:documentation>
75 </xs:annotation>
76 </xs:element>
77 <xs:element name="physicalFileName"
78 type="xs:string"
79 minOccurs="0"
80 maxOccurs="1"
81 xml:id="PhysicalRecordSegment-physicalFileName">
82 <xs:annotation>
83 <xs:documentation>Use when each physical segment is stored in its own file.</xs:documentation>
84 </xs:annotation>
85 </xs:element>
86 <xs:element name="purpose"
87 type="InternationalStringXsdType"
88 minOccurs="0"
89 maxOccurs="1"
90 xml:id="PhysicalRecordSegment-purpose">
91 <xs:annotation>
92 <xs:documentation>Intent or reason for the object/the description of the object.</xs:documentation>
93 </xs:annotation>
94 </xs:element>
95 <xs:element name="PhysicalRecordSegment_represents_Population"
96 minOccurs="0"
97 maxOccurs="1"
98 xml:id="PhysicalRecordSegment_represents_Population">
99 <xs:annotation>
100 <xs:documentation>A record segment may represent a specific population or sub-population within a larger set of segments. Allows for the identification of this filter for membership in the segment.</xs:documentation>
101 </xs:annotation>
102 <xs:complexType>
103 <xs:complexContent>
104 <xs:restriction base="AssociationReferenceXsdType">
105 <xs:sequence>
106 <xs:element name="ddiReference"
107 type="InternationalRegistrationDataIdentifierXsdType"
108 minOccurs="0"
109 maxOccurs="1"
110 xml:id="PhysicalRecordSegment_represents_Population-ddiReference"/>
111 <xs:element name="validType"
112 minOccurs="0"
113 maxOccurs="unbounded"
114 xml:id="PhysicalRecordSegment_represents_Population-validType">
115 <xs:simpleType>
116 <xs:restriction base="xs:NMTOKEN">
117 <xs:enumeration value="Population"/>
118 </xs:restriction>
119 </xs:simpleType>
120 </xs:element>
121 </xs:sequence>
122 </xs:restriction>
123 </xs:complexContent>
124 </xs:complexType>
125 </xs:element>
126 <xs:element name="PhysicalRecordSegment_isDefinedBy_Concept"
127 minOccurs="0"
128 maxOccurs="unbounded"
129 xml:id="PhysicalRecordSegment_isDefinedBy_Concept">
130 <xs:annotation>
131 <xs:documentation>The conceptual basis for the collection of members.</xs:documentation>
132 </xs:annotation>
133 <xs:complexType>
134 <xs:complexContent>
135 <xs:restriction base="AssociationReferenceXsdType">
136 <xs:sequence>
137 <xs:element name="ddiReference"
138 type="InternationalRegistrationDataIdentifierXsdType"
139 minOccurs="0"
140 maxOccurs="1"
141 xml:id="PhysicalRecordSegment_isDefinedBy_Concept-ddiReference"/>
142 <xs:element name="validType"
143 minOccurs="0"
144 maxOccurs="unbounded"
145 xml:id="PhysicalRecordSegment_isDefinedBy_Concept-validType">
146 <xs:simpleType>
147 <xs:restriction base="xs:NMTOKEN">
148 <xs:enumeration value="Category"/>
149 <xs:enumeration value="Concept"/>
150 <xs:enumeration value="ConceptualValue"/>
151 <xs:enumeration value="ConceptualVariable"/>
152 <xs:enumeration value="DescriptorVariable"/>
153 <xs:enumeration value="DimensionalKeyDefinitionMember"/>
154 <xs:enumeration value="InstanceVariable"/>
155 <xs:enumeration value="KeyDefinitionMember"/>
156 <xs:enumeration value="Population"/>
157 <xs:enumeration value="ReferenceVariable"/>
158 <xs:enumeration value="RepresentedVariable"/>
159 <xs:enumeration value="UnitType"/>
160 <xs:enumeration value="Universe"/>
161 </xs:restriction>
162 </xs:simpleType>
163 </xs:element>
164 </xs:sequence>
165 </xs:restriction>
166 </xs:complexContent>
167 </xs:complexType>
168 </xs:element>
169 <xs:element name="PhysicalRecordSegment_has_PhysicalSegmentLayout"
170 minOccurs="0"
171 maxOccurs="1"
172 xml:id="PhysicalRecordSegment_has_PhysicalSegmentLayout">
173 <xs:annotation>
174 <xs:documentation></xs:documentation>
175 </xs:annotation>
176 <xs:complexType>
177 <xs:complexContent>
178 <xs:restriction base="AssociationReferenceXsdType">
179 <xs:sequence>
180 <xs:element name="ddiReference"
181 type="InternationalRegistrationDataIdentifierXsdType"
182 minOccurs="0"
183 maxOccurs="1"
184 xml:id="PhysicalRecordSegment_has_PhysicalSegmentLayout-ddiReference"/>
185 <xs:element name="validType"
186 minOccurs="0"
187 maxOccurs="unbounded"
188 xml:id="PhysicalRecordSegment_has_PhysicalSegmentLayout-validType">
189 <xs:simpleType>
190 <xs:restriction base="xs:NMTOKEN">
191 <xs:enumeration value="PhysicalSegmentLayout"/>
192 <xs:enumeration value="UnitSegmentLayout"/>
193 </xs:restriction>
194 </xs:simpleType>
195 </xs:element>
196 </xs:sequence>
197 </xs:restriction>
198 </xs:complexContent>
199 </xs:complexType>
200 </xs:element>
201 <xs:element name="PhysicalRecordSegment_mapsTo_LogicalRecord"
202 minOccurs="0"
203 maxOccurs="1"
204 xml:id="PhysicalRecordSegment_mapsTo_LogicalRecord">
205 <xs:annotation>
206 <xs:documentation>Every data record has zero to many physical record segments. It is possible to describe a physical data product and its record segment(s) without reference to a data record.</xs:documentation>
207 </xs:annotation>
208 <xs:complexType>
209 <xs:complexContent>
210 <xs:restriction base="AssociationReferenceXsdType">
211 <xs:sequence>
212 <xs:element name="ddiReference"
213 type="InternationalRegistrationDataIdentifierXsdType"
214 minOccurs="0"
215 maxOccurs="1"
216 xml:id="PhysicalRecordSegment_mapsTo_LogicalRecord-ddiReference"/>
217 <xs:element name="validType"
218 minOccurs="0"
219 maxOccurs="unbounded"
220 xml:id="PhysicalRecordSegment_mapsTo_LogicalRecord-validType">
221 <xs:simpleType>
222 <xs:restriction base="xs:NMTOKEN">
223 <xs:enumeration value="LogicalRecord"/>
224 </xs:restriction>
225 </xs:simpleType>
226 </xs:element>
227 </xs:sequence>
228 </xs:restriction>
229 </xs:complexContent>
230 </xs:complexType>
231 </xs:element>
232 <xs:element name="PhysicalRecordSegment_has_DataPointPosition"
233 minOccurs="0"
234 maxOccurs="unbounded"
235 xml:id="PhysicalRecordSegment_has_DataPointPosition">
236 <xs:annotation>
237 <xs:documentation></xs:documentation>
238 </xs:annotation>
239 <xs:complexType>
240 <xs:complexContent>
241 <xs:restriction base="AssociationReferenceXsdType">
242 <xs:sequence>
243 <xs:element name="ddiReference"
244 type="InternationalRegistrationDataIdentifierXsdType"
245 minOccurs="0"
246 maxOccurs="1"
247 xml:id="PhysicalRecordSegment_has_DataPointPosition-ddiReference"/>
248 <xs:element name="validType"
249 minOccurs="1"
250 maxOccurs="1"
251 xml:id="PhysicalRecordSegment_has_DataPointPosition-validType">
252 <xs:simpleType>
253 <xs:restriction base="xs:NMTOKEN">
254 <xs:enumeration value="DataPointPosition"/>
255 </xs:restriction>
256 </xs:simpleType>
257 </xs:element>
258 </xs:sequence>
259 </xs:restriction>
260 </xs:complexContent>
261 </xs:complexType>
262 </xs:element>
263 <xs:element name="PhysicalRecordSegment_has_DataPoint"
264 minOccurs="0"
265 maxOccurs="unbounded"
266 xml:id="PhysicalRecordSegment_has_DataPoint">
267 <xs:annotation>
268 <xs:documentation></xs:documentation>
269 </xs:annotation>
270 <xs:complexType>
271 <xs:complexContent>
272 <xs:restriction base="AssociationReferenceXsdType">
273 <xs:sequence>
274 <xs:element name="ddiReference"
275 type="InternationalRegistrationDataIdentifierXsdType"
276 minOccurs="0"
277 maxOccurs="1"
278 xml:id="PhysicalRecordSegment_has_DataPoint-ddiReference"/>
279 <xs:element name="validType"
280 minOccurs="0"
281 maxOccurs="unbounded"
282 xml:id="PhysicalRecordSegment_has_DataPoint-validType">
283 <xs:simpleType>
284 <xs:restriction base="xs:NMTOKEN">
285 <xs:enumeration value="DataPoint"/>
286 </xs:restriction>
287 </xs:simpleType>
288 </xs:element>
289 </xs:sequence>
290 </xs:restriction>
291 </xs:complexContent>
292 </xs:complexType>
293 </xs:element>
294 </xs:sequence>
295</xs:complexType>
Fragment for the class PhysicalRecordSegment (main ontology)
1# class PhysicalRecordSegment
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalRecordSegment
3cdi:PhysicalRecordSegment
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "PhysicalRecordSegment";
6 rdfs:comment "Definition\n==========\nDescription of each physical storage segment required to completely cover a physical record representing the logical record.\n\nExamples\n========\nThe file below has four instance variables: PersonId, SegmentId, AgeYr, and HeightCm. The data for each person (identified by PersonId) is recorded in two segments (identified by SegmentId), \"a\" and \"b\". AgeYr is on physical segment a, and HeightCm is on segment b. These are the same data as described in the unit segment layout documentation. ::\n\n 1 a 22 \n 1 b 183 \n 2 a 45\n 2 b 175 \n\nExplanatory notes\n=================\nA logical record may be stored in one or more segments housed hierarchically in a single file or in separate data files. All logical records have at least one segment."@en;
7
8.
9
10cdi:PhysicalRecordSegment-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. \n\nExamples would be creator, contributor, title, copyright, embargo, and license information\n\nA set of information useful for attribution, data discovery, and access.\nThis 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:PhysicalRecordSegment;
15 rdfs:range cdi:CatalogDetails;
16.
17
18cdi:PhysicalRecordSegment-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:PhysicalRecordSegment;
23 rdfs:range cdi:Identifier;
24.
25
26cdi:PhysicalRecordSegment-name
27 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
28 rdfs:label "name";
29 rdfs:comment "Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage."@en;
30 rdfs:domain cdi:PhysicalRecordSegment;
31 rdfs:range cdi:ObjectName;
32.
33
34cdi:PhysicalRecordSegment-physicalFileName
35 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
36 rdfs:label "physicalFileName";
37 rdfs:comment "Use when each physical segment is stored in its own file."@en;
38 rdfs:domain cdi:PhysicalRecordSegment;
39 rdfs:range xsd:string;
40.
41
42cdi:PhysicalRecordSegment-purpose
43 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
44 rdfs:label "purpose";
45 rdfs:comment "Intent or reason for the object/the description of the object."@en;
46 rdfs:domain cdi:PhysicalRecordSegment;
47 rdfs:range cdi:InternationalString;
48.
49
50
51cdi:PhysicalRecordSegment_isDefinedBy_Concept
52 a rdf:Property, owl:ObjectProperty, ucmis:Association;
53 # ASSOCIATION
54 rdfs:label "isDefinedBy_Concept";
55 skos:altLabel "PhysicalRecordSegment_isDefinedBy_Concept";
56 rdfs:comment "The conceptual basis for the collection of members."@en;
57 rdfs:domain cdi:PhysicalRecordSegment;
58 rdfs:range cdi:Concept;
59.
60
61cdi:PhysicalRecordSegment_represents_Population
62 a rdf:Property, owl:ObjectProperty, ucmis:Association;
63 # ASSOCIATION
64 rdfs:label "represents";
65 skos:altLabel "PhysicalRecordSegment_represents_Population";
66 rdfs:comment "A record segment may represent a specific population or sub-population within a larger set of segments. Allows for the identification of this filter for membership in the segment."@en;
67 rdfs:domain cdi:PhysicalRecordSegment;
68 rdfs:range cdi:Population;
69.
70
71cdi:PhysicalRecordSegment_has_DataPoint
72 a rdf:Property, owl:ObjectProperty, ucmis:Association;
73 # ASSOCIATION
74 rdfs:label "has_DataPoint";
75 skos:altLabel "PhysicalRecordSegment_has_DataPoint";
76
77 rdfs:domain cdi:PhysicalRecordSegment;
78 rdfs:range cdi:DataPoint;
79.
80
81cdi:PhysicalRecordSegment_has_DataPointPosition
82 a rdf:Property, owl:ObjectProperty, ucmis:Association;
83 # ASSOCIATION
84 rdfs:label "has_DataPointPosition";
85 skos:altLabel "PhysicalRecordSegment_has_DataPointPosition";
86
87 rdfs:domain cdi:PhysicalRecordSegment;
88 rdfs:range cdi:DataPointPosition;
89.
90
91cdi:PhysicalRecordSegment_has_PhysicalSegmentLayout
92 a rdf:Property, owl:ObjectProperty, ucmis:Association;
93 # ASSOCIATION
94 rdfs:label "has_PhysicalSegmentLayout";
95 skos:altLabel "PhysicalRecordSegment_has_PhysicalSegmentLayout";
96
97 rdfs:domain cdi:PhysicalRecordSegment;
98 rdfs:range cdi:PhysicalSegmentLayout;
99.
100
101cdi:PhysicalRecordSegment_mapsTo_LogicalRecord
102 a rdf:Property, owl:ObjectProperty, ucmis:Association;
103 # ASSOCIATION
104 rdfs:label "mapsTo";
105 skos:altLabel "PhysicalRecordSegment_mapsTo_LogicalRecord";
106 rdfs:comment "Every data record has zero to many physical record segments. It is possible to describe a physical data product and its record segment(s) without reference to a data record."@en;
107 rdfs:domain cdi:PhysicalRecordSegment;
108 rdfs:range cdi:LogicalRecord;
109.
Fragment for the class PhysicalRecordSegment (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
7 "catalogDetails": {
8 "@id": "cdi:PhysicalRecordSegment-catalogDetails",
9 "@type": "@id",
10 "@context": "CatalogDetails.jsonld"
11 },
12 "identifier": {
13 "@id": "cdi:PhysicalRecordSegment-identifier",
14 "@type": "@id",
15 "@context": "Identifier.jsonld"
16 },
17 "name": {
18 "@id": "cdi:PhysicalRecordSegment-name",
19 "@type": "@id",
20 "@context": "ObjectName.jsonld"
21 },
22 "physicalFileName": {
23 "@id": "cdi:PhysicalRecordSegment-physicalFileName",
24 "@type": "xsd:string"
25 },
26 "purpose": {
27 "@id": "cdi:PhysicalRecordSegment-purpose",
28 "@type": "@id",
29 "@context": "InternationalString.jsonld"
30 },
31
32 "isDefinedBy_Concept": {
33 "@id": "cdi:PhysicalRecordSegment_isDefinedBy_Concept",
34 "@type": "@id",
35 "@context": "Concept.jsonld"
36 },
37 "represents": {
38 "@id": "cdi:PhysicalRecordSegment_represents_Population",
39 "@type": "@id",
40 "@context": "Population.jsonld"
41 },
42 "has_DataPoint": {
43 "@id": "cdi:PhysicalRecordSegment_has_DataPoint",
44 "@type": "@id",
45 "@context": "DataPoint.jsonld"
46 },
47 "has_DataPointPosition": {
48 "@id": "cdi:PhysicalRecordSegment_has_DataPointPosition",
49 "@type": "@id",
50 "@context": "DataPointPosition.jsonld"
51 },
52 "has_PhysicalSegmentLayout": {
53 "@id": "cdi:PhysicalRecordSegment_has_PhysicalSegmentLayout",
54 "@type": "@id",
55 "@context": "PhysicalSegmentLayout.jsonld"
56 },
57 "mapsTo": {
58 "@id": "cdi:PhysicalRecordSegment_mapsTo_LogicalRecord",
59 "@type": "@id",
60 "@context": "LogicalRecord.jsonld"
61 },
62 "has_PhysicalRecordSegment_OF_PhysicalDataSet": {
63 "@reverse": "cdi:PhysicalDataSet_has_PhysicalRecordSegment",
64 "@type": "@id",
65 "@context": "PhysicalDataSet.jsonld"
66 },
67 "indexes_OF_PhysicalRecordSegmentPosition": {
68 "@reverse": "cdi:PhysicalRecordSegmentPosition_indexes_PhysicalRecordSegment",
69 "@type": "@id",
70 "@context": "PhysicalRecordSegmentPosition.jsonld"
71 },
72 "hasSource_OF_PhysicalRecordSegmentRelationship": {
73 "@reverse": "cdi:PhysicalRecordSegmentRelationship_hasSource_PhysicalRecordSegment",
74 "@type": "@id",
75 "@context": "PhysicalRecordSegmentRelationship.jsonld"
76 },
77 "hasTarget_OF_PhysicalRecordSegmentRelationship": {
78 "@reverse": "cdi:PhysicalRecordSegmentRelationship_hasTarget_PhysicalRecordSegment",
79 "@type": "@id",
80 "@context": "PhysicalRecordSegmentRelationship.jsonld"
81 },
82 "structures_OF_PhysicalRecordSegmentStructure": {
83 "@reverse": "cdi:PhysicalRecordSegmentStructure_structures_PhysicalRecordSegment",
84 "@type": "@id",
85 "@context": "PhysicalRecordSegmentStructure.jsonld"
86 },
87 " comment ": "tag:json-should-support-trailing-commas"
88 }
89 ],
90 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2025-01-25 16:58:32.",
91 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalRecordSegment"
92}
