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 |
|---|---|---|---|---|---|
allowsDuplicates |
- own class - |
If value is False, the members are unique within the collection - if True, there may be duplicates. (Note that a mathematical “bag” permits duplicates and is unordered - a “set” does not have duplicates and may be ordered.) |
Boolean |
1..1 |
|
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-allowsDuplicates"
30 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-allowsDuplicates"
31 xmi:type="uml:Property">
32 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-allowsDuplicates-ownedComment"
33 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-allowsDuplicates-ownedComment"
34 xmi:type="uml:Comment">
35 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-allowsDuplicates"/>
36 <body>If value is False, the members are unique within the collection - if True, there may be duplicates. (Note that a mathematical “bag” permits duplicates and is unordered - a “set” does not have duplicates and may be ordered.)</body>
37 </ownedComment>
38 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-allowsDuplicates-lowerValue"
39 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-allowsDuplicates-lowerValue"
40 xmi:type="uml:LiteralInteger">
41 <value>1</value>
42 </lowerValue>
43 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-allowsDuplicates-upperValue"
44 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-allowsDuplicates-upperValue"
45 xmi:type="uml:LiteralUnlimitedNatural">
46 <value>1</value>
47 </upperValue>
48 <name>allowsDuplicates</name>
49 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#Boolean"
50 xmi:type="uml:PrimitiveType"/>
51 </ownedAttribute>
52 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails"
53 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails"
54 xmi:type="uml:Property">
55 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails-ownedComment"
56 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails-ownedComment"
57 xmi:type="uml:Comment">
58 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails"/>
59 <body>Bundles the information useful for a data catalog entry.
60
61Examples would be creator, contributor, title, copyright, embargo, and license information
62
63A set of information useful for attribution, data discovery, and access.
64This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</body>
65 </ownedComment>
66 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails-lowerValue"
67 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails-lowerValue"
68 xmi:type="uml:LiteralInteger"/>
69 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-catalogDetails-upperValue"
70 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-catalogDetails-upperValue"
71 xmi:type="uml:LiteralUnlimitedNatural">
72 <value>1</value>
73 </upperValue>
74 <name>catalogDetails</name>
75 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
76 </ownedAttribute>
77 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier"
78 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier"
79 xmi:type="uml:Property">
80 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier-ownedComment"
81 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier-ownedComment"
82 xmi:type="uml:Comment">
83 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier"/>
84 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
85 </ownedComment>
86 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier-lowerValue"
87 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier-lowerValue"
88 xmi:type="uml:LiteralInteger"/>
89 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-identifier-upperValue"
90 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-identifier-upperValue"
91 xmi:type="uml:LiteralUnlimitedNatural">
92 <value>1</value>
93 </upperValue>
94 <name>identifier</name>
95 <isID>true</isID>
96 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
97 </ownedAttribute>
98 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name"
99 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name"
100 xmi:type="uml:Property">
101 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name-ownedComment"
102 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name-ownedComment"
103 xmi:type="uml:Comment">
104 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name"/>
105 <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>
106 </ownedComment>
107 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name-lowerValue"
108 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name-lowerValue"
109 xmi:type="uml:LiteralInteger"/>
110 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-name-upperValue"
111 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-name-upperValue"
112 xmi:type="uml:LiteralUnlimitedNatural">
113 <value>*</value>
114 </upperValue>
115 <name>name</name>
116 <isOrdered>true</isOrdered>
117 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ObjectName"/>
118 </ownedAttribute>
119 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_1"
120 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_1"
121 xmi:type="uml:Property">
122 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_1-lowerValue"
123 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_1-lowerValue"
124 xmi:type="uml:LiteralInteger"/>
125 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_1-upperValue"
126 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_1-upperValue"
127 xmi:type="uml:LiteralUnlimitedNatural">
128 <value>1</value>
129 </upperValue>
130 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-PhysicalRecordSegment_represents_Population"/>
131 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Population"/>
132 </ownedAttribute>
133 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_2"
134 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_2"
135 xmi:type="uml:Property">
136 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_2-lowerValue"
137 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_2-lowerValue"
138 xmi:type="uml:LiteralInteger"/>
139 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_2-upperValue"
140 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_2-upperValue"
141 xmi:type="uml:LiteralUnlimitedNatural">
142 <value>*</value>
143 </upperValue>
144 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-PhysicalRecordSegment_isDefinedBy_Concept"/>
145 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Concept"/>
146 </ownedAttribute>
147 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_3"
148 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_3"
149 xmi:type="uml:Property">
150 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_3-lowerValue"
151 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_3-lowerValue"
152 xmi:type="uml:LiteralInteger"/>
153 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_3-upperValue"
154 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_3-upperValue"
155 xmi:type="uml:LiteralUnlimitedNatural">
156 <value>1</value>
157 </upperValue>
158 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment_has_PhysicalSegmentLayout"/>
159 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLayout"/>
160 </ownedAttribute>
161 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_4"
162 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_4"
163 xmi:type="uml:Property">
164 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_4-lowerValue"
165 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_4-lowerValue"
166 xmi:type="uml:LiteralInteger"/>
167 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_4-upperValue"
168 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_4-upperValue"
169 xmi:type="uml:LiteralUnlimitedNatural">
170 <value>1</value>
171 </upperValue>
172 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment_mapsTo_LogicalRecord"/>
173 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-LogicalRecord"/>
174 </ownedAttribute>
175 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_5"
176 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_5"
177 xmi:type="uml:Property">
178 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_5-lowerValue"
179 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_5-lowerValue"
180 xmi:type="uml:LiteralInteger"/>
181 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_5-upperValue"
182 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_5-upperValue"
183 xmi:type="uml:LiteralUnlimitedNatural">
184 <value>*</value>
185 </upperValue>
186 <aggregation>composite</aggregation>
187 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment_has_DataPointPosition"/>
188 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-DataPointPosition"/>
189 </ownedAttribute>
190 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_6"
191 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_6"
192 xmi:type="uml:Property">
193 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_6-lowerValue"
194 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_6-lowerValue"
195 xmi:type="uml:LiteralInteger"/>
196 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-ownedAttribute_6-upperValue"
197 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-ownedAttribute_6-upperValue"
198 xmi:type="uml:LiteralUnlimitedNatural">
199 <value>*</value>
200 </upperValue>
201 <aggregation>shared</aggregation>
202 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-PhysicalRecordSegment_has_DataPoint"/>
203 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-DataPoint"/>
204 </ownedAttribute>
205 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName"
206 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName"
207 xmi:type="uml:Property">
208 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName-ownedComment"
209 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName-ownedComment"
210 xmi:type="uml:Comment">
211 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName"/>
212 <body>Use when each physical segment is stored in its own file.</body>
213 </ownedComment>
214 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName-lowerValue"
215 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName-lowerValue"
216 xmi:type="uml:LiteralInteger"/>
217 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-physicalFileName-upperValue"
218 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-physicalFileName-upperValue"
219 xmi:type="uml:LiteralUnlimitedNatural">
220 <value>1</value>
221 </upperValue>
222 <name>physicalFileName</name>
223 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#String"
224 xmi:type="uml:PrimitiveType"/>
225 </ownedAttribute>
226 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose"
227 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose"
228 xmi:type="uml:Property">
229 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose-ownedComment"
230 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose-ownedComment"
231 xmi:type="uml:Comment">
232 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose"/>
233 <body>Intent or reason for the object/the description of the object.</body>
234 </ownedComment>
235 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose-lowerValue"
236 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose-lowerValue"
237 xmi:type="uml:LiteralInteger"/>
238 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalRecordSegment-purpose-upperValue"
239 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalRecordSegment-purpose-upperValue"
240 xmi:type="uml:LiteralUnlimitedNatural">
241 <value>1</value>
242 </upperValue>
243 <name>purpose</name>
244 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
245 </ownedAttribute>
246</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="allowsDuplicates"
46 type="xs:boolean"
47 minOccurs="1"
48 maxOccurs="1"
49 xml:id="PhysicalRecordSegment-allowsDuplicates">
50 <xs:annotation>
51 <xs:documentation>If value is False, the members are unique within the collection - if True, there may be duplicates. (Note that a mathematical “bag” permits duplicates and is unordered - a “set” does not have duplicates and may be ordered.)</xs:documentation>
52 </xs:annotation>
53 </xs:element>
54 <xs:element name="catalogDetails"
55 type="CatalogDetailsXsdType"
56 minOccurs="0"
57 maxOccurs="1"
58 xml:id="PhysicalRecordSegment-catalogDetails">
59 <xs:annotation>
60 <xs:documentation>Bundles the information useful for a data catalog entry.
61
62 Examples would be creator, contributor, title, copyright, embargo, and license information
63
64 A set of information useful for attribution, data discovery, and access.
65 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>
66 </xs:annotation>
67 </xs:element>
68 <xs:element name="identifier"
69 type="IdentifierXsdType"
70 minOccurs="0"
71 maxOccurs="1"
72 xml:id="PhysicalRecordSegment-identifier">
73 <xs:annotation>
74 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
75 </xs:annotation>
76 </xs:element>
77 <xs:element name="name"
78 type="ObjectNameXsdType"
79 minOccurs="0"
80 maxOccurs="unbounded"
81 xml:id="PhysicalRecordSegment-name">
82 <xs:annotation>
83 <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>
84 </xs:annotation>
85 </xs:element>
86 <xs:element name="physicalFileName"
87 type="xs:string"
88 minOccurs="0"
89 maxOccurs="1"
90 xml:id="PhysicalRecordSegment-physicalFileName">
91 <xs:annotation>
92 <xs:documentation>Use when each physical segment is stored in its own file.</xs:documentation>
93 </xs:annotation>
94 </xs:element>
95 <xs:element name="purpose"
96 type="InternationalStringXsdType"
97 minOccurs="0"
98 maxOccurs="1"
99 xml:id="PhysicalRecordSegment-purpose">
100 <xs:annotation>
101 <xs:documentation>Intent or reason for the object/the description of the object.</xs:documentation>
102 </xs:annotation>
103 </xs:element>
104 <xs:element name="PhysicalRecordSegment_represents_Population"
105 minOccurs="0"
106 maxOccurs="1"
107 xml:id="PhysicalRecordSegment_represents_Population">
108 <xs:annotation>
109 <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>
110 </xs:annotation>
111 <xs:complexType>
112 <xs:complexContent>
113 <xs:restriction base="AssociationReferenceXsdType">
114 <xs:sequence>
115 <xs:element name="ddiReference"
116 type="InternationalRegistrationDataIdentifierXsdType"
117 minOccurs="0"
118 maxOccurs="1"
119 xml:id="PhysicalRecordSegment_represents_Population-ddiReference"/>
120 <xs:element name="validType"
121 minOccurs="0"
122 maxOccurs="unbounded"
123 xml:id="PhysicalRecordSegment_represents_Population-validType">
124 <xs:simpleType>
125 <xs:restriction base="xs:NMTOKEN">
126 <xs:enumeration value="Population"/>
127 </xs:restriction>
128 </xs:simpleType>
129 </xs:element>
130 </xs:sequence>
131 </xs:restriction>
132 </xs:complexContent>
133 </xs:complexType>
134 </xs:element>
135 <xs:element name="PhysicalRecordSegment_isDefinedBy_Concept"
136 minOccurs="0"
137 maxOccurs="unbounded"
138 xml:id="PhysicalRecordSegment_isDefinedBy_Concept">
139 <xs:annotation>
140 <xs:documentation>The conceptual basis for the collection of members.</xs:documentation>
141 </xs:annotation>
142 <xs:complexType>
143 <xs:complexContent>
144 <xs:restriction base="AssociationReferenceXsdType">
145 <xs:sequence>
146 <xs:element name="ddiReference"
147 type="InternationalRegistrationDataIdentifierXsdType"
148 minOccurs="0"
149 maxOccurs="1"
150 xml:id="PhysicalRecordSegment_isDefinedBy_Concept-ddiReference"/>
151 <xs:element name="validType"
152 minOccurs="0"
153 maxOccurs="unbounded"
154 xml:id="PhysicalRecordSegment_isDefinedBy_Concept-validType">
155 <xs:simpleType>
156 <xs:restriction base="xs:NMTOKEN">
157 <xs:enumeration value="Category"/>
158 <xs:enumeration value="Concept"/>
159 <xs:enumeration value="ConceptualValue"/>
160 <xs:enumeration value="ConceptualVariable"/>
161 <xs:enumeration value="DescriptorVariable"/>
162 <xs:enumeration value="DimensionalKeyDefinitionMember"/>
163 <xs:enumeration value="InstanceVariable"/>
164 <xs:enumeration value="KeyDefinitionMember"/>
165 <xs:enumeration value="Population"/>
166 <xs:enumeration value="ReferenceVariable"/>
167 <xs:enumeration value="RepresentedVariable"/>
168 <xs:enumeration value="UnitType"/>
169 <xs:enumeration value="Universe"/>
170 </xs:restriction>
171 </xs:simpleType>
172 </xs:element>
173 </xs:sequence>
174 </xs:restriction>
175 </xs:complexContent>
176 </xs:complexType>
177 </xs:element>
178 <xs:element name="PhysicalRecordSegment_has_PhysicalSegmentLayout"
179 minOccurs="0"
180 maxOccurs="1"
181 xml:id="PhysicalRecordSegment_has_PhysicalSegmentLayout">
182 <xs:annotation>
183 <xs:documentation></xs:documentation>
184 </xs:annotation>
185 <xs:complexType>
186 <xs:complexContent>
187 <xs:restriction base="AssociationReferenceXsdType">
188 <xs:sequence>
189 <xs:element name="ddiReference"
190 type="InternationalRegistrationDataIdentifierXsdType"
191 minOccurs="0"
192 maxOccurs="1"
193 xml:id="PhysicalRecordSegment_has_PhysicalSegmentLayout-ddiReference"/>
194 <xs:element name="validType"
195 minOccurs="0"
196 maxOccurs="unbounded"
197 xml:id="PhysicalRecordSegment_has_PhysicalSegmentLayout-validType">
198 <xs:simpleType>
199 <xs:restriction base="xs:NMTOKEN">
200 <xs:enumeration value="PhysicalSegmentLayout"/>
201 <xs:enumeration value="UnitSegmentLayout"/>
202 </xs:restriction>
203 </xs:simpleType>
204 </xs:element>
205 </xs:sequence>
206 </xs:restriction>
207 </xs:complexContent>
208 </xs:complexType>
209 </xs:element>
210 <xs:element name="PhysicalRecordSegment_mapsTo_LogicalRecord"
211 minOccurs="0"
212 maxOccurs="1"
213 xml:id="PhysicalRecordSegment_mapsTo_LogicalRecord">
214 <xs:annotation>
215 <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>
216 </xs:annotation>
217 <xs:complexType>
218 <xs:complexContent>
219 <xs:restriction base="AssociationReferenceXsdType">
220 <xs:sequence>
221 <xs:element name="ddiReference"
222 type="InternationalRegistrationDataIdentifierXsdType"
223 minOccurs="0"
224 maxOccurs="1"
225 xml:id="PhysicalRecordSegment_mapsTo_LogicalRecord-ddiReference"/>
226 <xs:element name="validType"
227 minOccurs="0"
228 maxOccurs="unbounded"
229 xml:id="PhysicalRecordSegment_mapsTo_LogicalRecord-validType">
230 <xs:simpleType>
231 <xs:restriction base="xs:NMTOKEN">
232 <xs:enumeration value="LogicalRecord"/>
233 </xs:restriction>
234 </xs:simpleType>
235 </xs:element>
236 </xs:sequence>
237 </xs:restriction>
238 </xs:complexContent>
239 </xs:complexType>
240 </xs:element>
241 <xs:element name="PhysicalRecordSegment_has_DataPointPosition"
242 minOccurs="0"
243 maxOccurs="unbounded"
244 xml:id="PhysicalRecordSegment_has_DataPointPosition">
245 <xs:annotation>
246 <xs:documentation></xs:documentation>
247 </xs:annotation>
248 <xs:complexType>
249 <xs:complexContent>
250 <xs:restriction base="AssociationReferenceXsdType">
251 <xs:sequence>
252 <xs:element name="ddiReference"
253 type="InternationalRegistrationDataIdentifierXsdType"
254 minOccurs="0"
255 maxOccurs="1"
256 xml:id="PhysicalRecordSegment_has_DataPointPosition-ddiReference"/>
257 <xs:element name="validType"
258 minOccurs="1"
259 maxOccurs="1"
260 xml:id="PhysicalRecordSegment_has_DataPointPosition-validType">
261 <xs:simpleType>
262 <xs:restriction base="xs:NMTOKEN">
263 <xs:enumeration value="DataPointPosition"/>
264 </xs:restriction>
265 </xs:simpleType>
266 </xs:element>
267 </xs:sequence>
268 </xs:restriction>
269 </xs:complexContent>
270 </xs:complexType>
271 </xs:element>
272 <xs:element name="PhysicalRecordSegment_has_DataPoint"
273 minOccurs="0"
274 maxOccurs="unbounded"
275 xml:id="PhysicalRecordSegment_has_DataPoint">
276 <xs:annotation>
277 <xs:documentation></xs:documentation>
278 </xs:annotation>
279 <xs:complexType>
280 <xs:complexContent>
281 <xs:restriction base="AssociationReferenceXsdType">
282 <xs:sequence>
283 <xs:element name="ddiReference"
284 type="InternationalRegistrationDataIdentifierXsdType"
285 minOccurs="0"
286 maxOccurs="1"
287 xml:id="PhysicalRecordSegment_has_DataPoint-ddiReference"/>
288 <xs:element name="validType"
289 minOccurs="0"
290 maxOccurs="unbounded"
291 xml:id="PhysicalRecordSegment_has_DataPoint-validType">
292 <xs:simpleType>
293 <xs:restriction base="xs:NMTOKEN">
294 <xs:enumeration value="DataPoint"/>
295 </xs:restriction>
296 </xs:simpleType>
297 </xs:element>
298 </xs:sequence>
299 </xs:restriction>
300 </xs:complexContent>
301 </xs:complexType>
302 </xs:element>
303 </xs:sequence>
304</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-allowsDuplicates
11 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
12 rdfs:label "allowsDuplicates";
13 rdfs:comment "If value is False, the members are unique within the collection - if True, there may be duplicates. (Note that a mathematical “bag” permits duplicates and is unordered - a “set” does not have duplicates and may be ordered.)"@en;
14 rdfs:domain cdi:PhysicalRecordSegment;
15 rdfs:range xsd:boolean;
16.
17
18cdi:PhysicalRecordSegment-catalogDetails
19 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
20 rdfs:label "catalogDetails";
21 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;
22 rdfs:domain cdi:PhysicalRecordSegment;
23 rdfs:range cdi:CatalogDetails;
24.
25
26cdi:PhysicalRecordSegment-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:PhysicalRecordSegment;
31 rdfs:range cdi:Identifier;
32.
33
34cdi:PhysicalRecordSegment-name
35 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
36 rdfs:label "name";
37 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;
38 rdfs:domain cdi:PhysicalRecordSegment;
39 rdfs:range cdi:ObjectName;
40.
41
42cdi:PhysicalRecordSegment-physicalFileName
43 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
44 rdfs:label "physicalFileName";
45 rdfs:comment "Use when each physical segment is stored in its own file."@en;
46 rdfs:domain cdi:PhysicalRecordSegment;
47 rdfs:range xsd:string;
48.
49
50cdi:PhysicalRecordSegment-purpose
51 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
52 rdfs:label "purpose";
53 rdfs:comment "Intent or reason for the object/the description of the object."@en;
54 rdfs:domain cdi:PhysicalRecordSegment;
55 rdfs:range cdi:InternationalString;
56.
57
58
59cdi:PhysicalRecordSegment_isDefinedBy_Concept
60 a rdf:Property, owl:ObjectProperty, ucmis:Association;
61 # ASSOCIATION
62 rdfs:label "isDefinedBy";
63 skos:altLabel "PhysicalRecordSegment_isDefinedBy_Concept";
64 rdfs:comment "The conceptual basis for the collection of members."@en;
65 rdfs:domain cdi:PhysicalRecordSegment;
66 rdfs:range cdi:Concept;
67.
68
69cdi:PhysicalRecordSegment_represents_Population
70 a rdf:Property, owl:ObjectProperty, ucmis:Association;
71 # ASSOCIATION
72 rdfs:label "represents";
73 skos:altLabel "PhysicalRecordSegment_represents_Population";
74 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;
75 rdfs:domain cdi:PhysicalRecordSegment;
76 rdfs:range cdi:Population;
77.
78
79cdi:PhysicalRecordSegment_has_DataPoint
80 a rdf:Property, owl:ObjectProperty, ucmis:Association;
81 # ASSOCIATION
82 rdfs:label "has";
83 skos:altLabel "PhysicalRecordSegment_has_DataPoint";
84
85 rdfs:domain cdi:PhysicalRecordSegment;
86 rdfs:range cdi:DataPoint;
87.
88
89cdi:PhysicalRecordSegment_has_DataPointPosition
90 a rdf:Property, owl:ObjectProperty, ucmis:Association;
91 # ASSOCIATION
92 rdfs:label "has";
93 skos:altLabel "PhysicalRecordSegment_has_DataPointPosition";
94
95 rdfs:domain cdi:PhysicalRecordSegment;
96 rdfs:range cdi:DataPointPosition;
97.
98
99cdi:PhysicalRecordSegment_has_PhysicalSegmentLayout
100 a rdf:Property, owl:ObjectProperty, ucmis:Association;
101 # ASSOCIATION
102 rdfs:label "has";
103 skos:altLabel "PhysicalRecordSegment_has_PhysicalSegmentLayout";
104
105 rdfs:domain cdi:PhysicalRecordSegment;
106 rdfs:range cdi:PhysicalSegmentLayout;
107.
108
109cdi:PhysicalRecordSegment_mapsTo_LogicalRecord
110 a rdf:Property, owl:ObjectProperty, ucmis:Association;
111 # ASSOCIATION
112 rdfs:label "mapsTo";
113 skos:altLabel "PhysicalRecordSegment_mapsTo_LogicalRecord";
114 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;
115 rdfs:domain cdi:PhysicalRecordSegment;
116 rdfs:range cdi:LogicalRecord;
117.
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 "PhysicalRecordSegment": "cdi:PhysicalRecordSegment",
7 "allowsDuplicates": {
8 "@id": "cdi:PhysicalRecordSegment-allowsDuplicates",
9 "@type": "xsd:boolean"
10 },
11 "catalogDetails": {
12 "@id": "cdi:PhysicalRecordSegment-catalogDetails",
13 "@type": "@id",
14 "@context": "CatalogDetails.jsonld"
15 },
16 "identifier": {
17 "@id": "cdi:PhysicalRecordSegment-identifier",
18 "@type": "@id",
19 "@context": "Identifier.jsonld"
20 },
21 "name": {
22 "@id": "cdi:PhysicalRecordSegment-name",
23 "@type": "@id",
24 "@context": "ObjectName.jsonld"
25 },
26 "physicalFileName": {
27 "@id": "cdi:PhysicalRecordSegment-physicalFileName",
28 "@type": "xsd:string"
29 },
30 "purpose": {
31 "@id": "cdi:PhysicalRecordSegment-purpose",
32 "@type": "@id",
33 "@context": "InternationalString.jsonld"
34 },
35
36 "isDefinedBy": {
37 "@id": "cdi:PhysicalRecordSegment_isDefinedBy_Concept",
38 "@type": "@id" },
39 "represents": {
40 "@id": "cdi:PhysicalRecordSegment_represents_Population",
41 "@type": "@id" },
42 "has": {
43 "@id": "cdi:PhysicalRecordSegment_has_DataPoint",
44 "@type": "@id" },
45 "has": {
46 "@id": "cdi:PhysicalRecordSegment_has_DataPointPosition",
47 "@type": "@id" },
48 "has": {
49 "@id": "cdi:PhysicalRecordSegment_has_PhysicalSegmentLayout",
50 "@type": "@id" },
51 "mapsTo": {
52 "@id": "cdi:PhysicalRecordSegment_mapsTo_LogicalRecord",
53 "@type": "@id" },
54 "has_OF_PhysicalDataSet": {
55 "@reverse": "cdi:PhysicalDataSet_has_PhysicalRecordSegment",
56 "@type": "@id"
57 },
58 "indexes_OF_PhysicalRecordSegmentPosition": {
59 "@reverse": "cdi:PhysicalRecordSegmentPosition_indexes_PhysicalRecordSegment",
60 "@type": "@id"
61 },
62 "hasSource_OF_PhysicalRecordSegmentRelationship": {
63 "@reverse": "cdi:PhysicalRecordSegmentRelationship_hasSource_PhysicalRecordSegment",
64 "@type": "@id"
65 },
66 "hasTarget_OF_PhysicalRecordSegmentRelationship": {
67 "@reverse": "cdi:PhysicalRecordSegmentRelationship_hasTarget_PhysicalRecordSegment",
68 "@type": "@id"
69 },
70 "structures_OF_PhysicalRecordSegmentStructure": {
71 "@reverse": "cdi:PhysicalRecordSegmentStructure_structures_PhysicalRecordSegment",
72 "@type": "@id"
73 },
74 " comment ": "tag:json-should-support-trailing-commas"
75 }
76 ],
77 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:10.",
78 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalRecordSegment"
79}
