PhysicalLayoutRelationStructure¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalLayoutRelationStructure
Definition¶
Realization of relation structure that is used to describe the sequence of value mappings in a physical layout.
Examples¶
The W3C Tabular Data on the Web specification section 4.5 Cells (https://www.w3.org/TR/tabular-data-model/#content-type) allows for a list datatype within cells. In the example below there are three top level instance variables: PersonID - the person identifier; AgeYr - age in years; BpSys_Dia - blood pressure (a list containing Systolic and Diastolic values). There are two variables at a secondary level of the hierarchy: Systolic - the systolic pressure; Diastolic - the diastolic pressure. The delimited file below uses the comma to separate “columns” and forward slash to separate elements of a blood pressure list.
PersonID, AgeYr, BpSys_Dia
1,22,119/67
2,68,122/70
The physical relation structure in this case would describe a BpSys_Dia list variable as containing an ordered sequence of the Systolic and Diastolic instance variables.
Explanatory notes¶
This can be more complex than a simple sequence.
Diagram
Attributes
Name |
Inherited from |
Description |
Data Type |
Multiplicity |
Default value |
|---|---|---|---|---|---|
criteria |
- own class - |
Intentional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.). |
0..1 |
||
identifier |
- own class - |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
||
name |
- own class - |
A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided then a context to differentiate usage must be provided as well. |
0..* |
||
purpose |
- own class - |
Intent or reason for the object/the description of the object. |
0..1 |
||
semantics |
- own class - |
Specifies the semantics of the object in reference to a vocabulary, ontology, etc. |
0..1 |
||
specification |
- own class - |
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumerated list. Use if all relations within this relation structure are of the same specification. |
0..1 |
||
topology |
- own class - |
Indicates the form of the associations among members of the collection. Specifies the way in which constituent parts are interrelated or arranged. |
1..1 |
||
totality |
- own class - |
Indicates whether the related collections are comprehensive in terms of their coverage. |
0..1 |
Associations
Direction |
Association |
Description |
Multiplicity of PhysicalLayoutRelationStructure |
Package of Other Class |
Other Class |
Multiplicity of other class |
Aggregation Kind |
Inherited from |
|---|---|---|---|---|---|---|---|---|
from |
PhysicalLayoutRelationStructure has ValueMappingRelationship |
1..1 |
- own package - |
0..* |
composite |
- own class - |
||
from |
PhysicalLayoutRelationStructure structures PhysicalSegmentLayout |
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 PhysicalLayoutRelationStructure (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-PhysicalLayoutRelationStructure"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure"/>
11 <body>Definition
12==========
13Realization of relation structure that is used to describe the sequence of value mappings in a physical layout.
14
15Examples
16========
17The W3C Tabular Data on the Web specification section 4.5 Cells (https://www.w3.org/TR/tabular-data-model/#content-type) allows for a list datatype within cells. In the example below there are three top level instance variables: PersonID - the person identifier; AgeYr - age in years; BpSys_Dia - blood pressure (a list containing Systolic and Diastolic values). There are two variables at a secondary level of the hierarchy: Systolic - the systolic pressure; Diastolic - the diastolic pressure. The delimited file below uses the comma to separate "columns" and forward slash to separate elements of a blood pressure list. ::
18
19 PersonID, AgeYr, BpSys_Dia
20 1,22,119/67
21 2,68,122/70
22
23The physical relation structure in this case would describe a BpSys_Dia list variable as containing an ordered sequence of the Systolic and Diastolic instance variables.
24
25Explanatory notes
26=================
27This can be more complex than a simple sequence.</body>
28 </ownedComment>
29 <name>PhysicalLayoutRelationStructure</name>
30 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-criteria"
31 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-criteria"
32 xmi:type="uml:Property">
33 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-criteria-ownedComment"
34 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-criteria-ownedComment"
35 xmi:type="uml:Comment">
36 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-criteria"/>
37 <body>Intentional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.).</body>
38 </ownedComment>
39 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-criteria-lowerValue"
40 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-criteria-lowerValue"
41 xmi:type="uml:LiteralInteger"/>
42 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-criteria-upperValue"
43 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-criteria-upperValue"
44 xmi:type="uml:LiteralUnlimitedNatural">
45 <value>1</value>
46 </upperValue>
47 <name>criteria</name>
48 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
49 </ownedAttribute>
50 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-identifier"
51 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-identifier"
52 xmi:type="uml:Property">
53 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-identifier-ownedComment"
54 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-identifier-ownedComment"
55 xmi:type="uml:Comment">
56 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-identifier"/>
57 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
58 </ownedComment>
59 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-identifier-lowerValue"
60 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-identifier-lowerValue"
61 xmi:type="uml:LiteralInteger"/>
62 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-identifier-upperValue"
63 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-identifier-upperValue"
64 xmi:type="uml:LiteralUnlimitedNatural">
65 <value>1</value>
66 </upperValue>
67 <name>identifier</name>
68 <isID>true</isID>
69 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
70 </ownedAttribute>
71 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-name"
72 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-name"
73 xmi:type="uml:Property">
74 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-name-ownedComment"
75 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-name-ownedComment"
76 xmi:type="uml:Comment">
77 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-name"/>
78 <body>A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided then a context to differentiate usage must be provided as well.</body>
79 </ownedComment>
80 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-name-lowerValue"
81 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-name-lowerValue"
82 xmi:type="uml:LiteralInteger"/>
83 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-name-upperValue"
84 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-name-upperValue"
85 xmi:type="uml:LiteralUnlimitedNatural">
86 <value>*</value>
87 </upperValue>
88 <name>name</name>
89 <isOrdered>true</isOrdered>
90 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ObjectName"/>
91 </ownedAttribute>
92 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedAttribute_1"
93 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedAttribute_1"
94 xmi:type="uml:Property">
95 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedAttribute_1-lowerValue"
96 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedAttribute_1-lowerValue"
97 xmi:type="uml:LiteralInteger"/>
98 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedAttribute_1-upperValue"
99 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedAttribute_1-upperValue"
100 xmi:type="uml:LiteralUnlimitedNatural">
101 <value>1</value>
102 </upperValue>
103 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout"/>
104 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLayout"/>
105 </ownedAttribute>
106 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedAttribute_2"
107 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedAttribute_2"
108 xmi:type="uml:Property">
109 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedAttribute_2-lowerValue"
110 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedAttribute_2-lowerValue"
111 xmi:type="uml:LiteralInteger"/>
112 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-ownedAttribute_2-upperValue"
113 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-ownedAttribute_2-upperValue"
114 xmi:type="uml:LiteralUnlimitedNatural">
115 <value>*</value>
116 </upperValue>
117 <aggregation>composite</aggregation>
118 <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure_has_ValueMappingRelationship"/>
119 <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-ValueMappingRelationship"/>
120 </ownedAttribute>
121 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-purpose"
122 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-purpose"
123 xmi:type="uml:Property">
124 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-purpose-ownedComment"
125 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-purpose-ownedComment"
126 xmi:type="uml:Comment">
127 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-purpose"/>
128 <body>Intent or reason for the object/the description of the object.</body>
129 </ownedComment>
130 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-purpose-lowerValue"
131 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-purpose-lowerValue"
132 xmi:type="uml:LiteralInteger"/>
133 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-purpose-upperValue"
134 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-purpose-upperValue"
135 xmi:type="uml:LiteralUnlimitedNatural">
136 <value>1</value>
137 </upperValue>
138 <name>purpose</name>
139 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
140 </ownedAttribute>
141 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-semantics"
142 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-semantics"
143 xmi:type="uml:Property">
144 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-semantics-ownedComment"
145 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-semantics-ownedComment"
146 xmi:type="uml:Comment">
147 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-semantics"/>
148 <body>Specifies the semantics of the object in reference to a vocabulary, ontology, etc.</body>
149 </ownedComment>
150 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-semantics-lowerValue"
151 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-semantics-lowerValue"
152 xmi:type="uml:LiteralInteger"/>
153 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-semantics-upperValue"
154 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-semantics-upperValue"
155 xmi:type="uml:LiteralUnlimitedNatural">
156 <value>1</value>
157 </upperValue>
158 <name>semantics</name>
159 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ControlledVocabularyEntry"/>
160 </ownedAttribute>
161 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-specification"
162 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-specification"
163 xmi:type="uml:Property">
164 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-specification-ownedComment"
165 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-specification-ownedComment"
166 xmi:type="uml:Comment">
167 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-specification"/>
168 <body>Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumerated list. Use if all relations within this relation structure are of the same specification.</body>
169 </ownedComment>
170 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-specification-lowerValue"
171 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-specification-lowerValue"
172 xmi:type="uml:LiteralInteger"/>
173 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-specification-upperValue"
174 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-specification-upperValue"
175 xmi:type="uml:LiteralUnlimitedNatural">
176 <value>1</value>
177 </upperValue>
178 <name>specification</name>
179 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-StructureSpecification"/>
180 </ownedAttribute>
181 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-topology"
182 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-topology"
183 xmi:type="uml:Property">
184 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-topology-ownedComment"
185 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-topology-ownedComment"
186 xmi:type="uml:Comment">
187 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-topology"/>
188 <body>Indicates the form of the associations among members of the collection. Specifies the way in which constituent parts are interrelated or arranged.</body>
189 </ownedComment>
190 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-topology-lowerValue"
191 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-topology-lowerValue"
192 xmi:type="uml:LiteralInteger">
193 <value>1</value>
194 </lowerValue>
195 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-topology-upperValue"
196 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-topology-upperValue"
197 xmi:type="uml:LiteralUnlimitedNatural">
198 <value>1</value>
199 </upperValue>
200 <name>topology</name>
201 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ControlledVocabularyEntry"/>
202 </ownedAttribute>
203 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-totality"
204 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-totality"
205 xmi:type="uml:Property">
206 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-totality-ownedComment"
207 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-totality-ownedComment"
208 xmi:type="uml:Comment">
209 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-totality"/>
210 <body>Indicates whether the related collections are comprehensive in terms of their coverage.</body>
211 </ownedComment>
212 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-totality-lowerValue"
213 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-totality-lowerValue"
214 xmi:type="uml:LiteralInteger"/>
215 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalLayoutRelationStructure-totality-upperValue"
216 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalLayoutRelationStructure-totality-upperValue"
217 xmi:type="uml:LiteralUnlimitedNatural">
218 <value>1</value>
219 </upperValue>
220 <name>totality</name>
221 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-Enumerations-StructureExtent"/>
222 </ownedAttribute>
223</packagedElement>
Fragment for the class PhysicalLayoutRelationStructure (entire XML Schema)
1<xs:element name="PhysicalLayoutRelationStructure"
2 type="PhysicalLayoutRelationStructureXsdType"
3 xml:id="PhysicalLayoutRelationStructure">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalLayoutRelationStructure -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ==========
8 Realization of relation structure that is used to describe the sequence of value mappings in a physical layout.
9
10 Examples
11 ========
12 The W3C Tabular Data on the Web specification section 4.5 Cells (https://www.w3.org/TR/tabular-data-model/#content-type) allows for a list datatype within cells. In the example below there are three top level instance variables: PersonID - the person identifier; AgeYr - age in years; BpSys_Dia - blood pressure (a list containing Systolic and Diastolic values). There are two variables at a secondary level of the hierarchy: Systolic - the systolic pressure; Diastolic - the diastolic pressure. The delimited file below uses the comma to separate "columns" and forward slash to separate elements of a blood pressure list. ::
13
14 PersonID, AgeYr, BpSys_Dia
15 1,22,119/67
16 2,68,122/70
17
18 The physical relation structure in this case would describe a BpSys_Dia list variable as containing an ordered sequence of the Systolic and Diastolic instance variables.
19
20 Explanatory notes
21 =================
22 This can be more complex than a simple sequence.</xs:documentation>
23 </xs:annotation>
24</xs:element>
25<xs:complexType name="PhysicalLayoutRelationStructureXsdType"
26 xml:id="PhysicalLayoutRelationStructureXsdType">
27 <xs:annotation>
28 <xs:documentation>Definition
29 ==========
30 Realization of relation structure that is used to describe the sequence of value mappings in a physical layout.
31
32 Examples
33 ========
34 The W3C Tabular Data on the Web specification section 4.5 Cells (https://www.w3.org/TR/tabular-data-model/#content-type) allows for a list datatype within cells. In the example below there are three top level instance variables: PersonID - the person identifier; AgeYr - age in years; BpSys_Dia - blood pressure (a list containing Systolic and Diastolic values). There are two variables at a secondary level of the hierarchy: Systolic - the systolic pressure; Diastolic - the diastolic pressure. The delimited file below uses the comma to separate "columns" and forward slash to separate elements of a blood pressure list. ::
35
36 PersonID, AgeYr, BpSys_Dia
37 1,22,119/67
38 2,68,122/70
39
40 The physical relation structure in this case would describe a BpSys_Dia list variable as containing an ordered sequence of the Systolic and Diastolic instance variables.
41
42 Explanatory notes
43 =================
44 This can be more complex than a simple sequence.</xs:documentation>
45 </xs:annotation>
46 <xs:sequence>
47 <xs:element name="criteria"
48 type="InternationalStringXsdType"
49 minOccurs="0"
50 maxOccurs="1"
51 xml:id="PhysicalLayoutRelationStructure-criteria">
52 <xs:annotation>
53 <xs:documentation>Intentional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.).</xs:documentation>
54 </xs:annotation>
55 </xs:element>
56 <xs:element name="identifier"
57 type="IdentifierXsdType"
58 minOccurs="0"
59 maxOccurs="1"
60 xml:id="PhysicalLayoutRelationStructure-identifier">
61 <xs:annotation>
62 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
63 </xs:annotation>
64 </xs:element>
65 <xs:element name="name"
66 type="ObjectNameXsdType"
67 minOccurs="0"
68 maxOccurs="unbounded"
69 xml:id="PhysicalLayoutRelationStructure-name">
70 <xs:annotation>
71 <xs:documentation>A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided then a context to differentiate usage must be provided as well.</xs:documentation>
72 </xs:annotation>
73 </xs:element>
74 <xs:element name="purpose"
75 type="InternationalStringXsdType"
76 minOccurs="0"
77 maxOccurs="1"
78 xml:id="PhysicalLayoutRelationStructure-purpose">
79 <xs:annotation>
80 <xs:documentation>Intent or reason for the object/the description of the object.</xs:documentation>
81 </xs:annotation>
82 </xs:element>
83 <xs:element name="semantics"
84 type="ControlledVocabularyEntryXsdType"
85 minOccurs="0"
86 maxOccurs="1"
87 xml:id="PhysicalLayoutRelationStructure-semantics">
88 <xs:annotation>
89 <xs:documentation>Specifies the semantics of the object in reference to a vocabulary, ontology, etc.</xs:documentation>
90 </xs:annotation>
91 </xs:element>
92 <xs:element name="specification"
93 type="StructureSpecificationXsdType"
94 minOccurs="0"
95 maxOccurs="1"
96 xml:id="PhysicalLayoutRelationStructure-specification">
97 <xs:annotation>
98 <xs:documentation>Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumerated list. Use if all relations within this relation structure are of the same specification.</xs:documentation>
99 </xs:annotation>
100 </xs:element>
101 <xs:element name="topology"
102 type="ControlledVocabularyEntryXsdType"
103 minOccurs="1"
104 maxOccurs="1"
105 xml:id="PhysicalLayoutRelationStructure-topology">
106 <xs:annotation>
107 <xs:documentation>Indicates the form of the associations among members of the collection. Specifies the way in which constituent parts are interrelated or arranged.</xs:documentation>
108 </xs:annotation>
109 </xs:element>
110 <xs:element name="totality"
111 type="StructureExtentXsdType"
112 minOccurs="0"
113 maxOccurs="1"
114 xml:id="PhysicalLayoutRelationStructure-totality">
115 <xs:annotation>
116 <xs:documentation>Indicates whether the related collections are comprehensive in terms of their coverage.</xs:documentation>
117 </xs:annotation>
118 </xs:element>
119 <xs:element name="PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout"
120 minOccurs="0"
121 maxOccurs="1"
122 xml:id="PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout">
123 <xs:annotation>
124 <xs:documentation></xs:documentation>
125 </xs:annotation>
126 <xs:complexType>
127 <xs:complexContent>
128 <xs:restriction base="AssociationReferenceXsdType">
129 <xs:sequence>
130 <xs:element name="ddiReference"
131 type="InternationalRegistrationDataIdentifierXsdType"
132 minOccurs="0"
133 maxOccurs="1"
134 xml:id="PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout-ddiReference"/>
135 <xs:element name="validType"
136 minOccurs="0"
137 maxOccurs="unbounded"
138 xml:id="PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout-validType">
139 <xs:simpleType>
140 <xs:restriction base="xs:NMTOKEN">
141 <xs:enumeration value="PhysicalSegmentLayout"/>
142 <xs:enumeration value="UnitSegmentLayout"/>
143 </xs:restriction>
144 </xs:simpleType>
145 </xs:element>
146 </xs:sequence>
147 </xs:restriction>
148 </xs:complexContent>
149 </xs:complexType>
150 </xs:element>
151 <xs:element name="PhysicalLayoutRelationStructure_has_ValueMappingRelationship"
152 minOccurs="0"
153 maxOccurs="unbounded"
154 xml:id="PhysicalLayoutRelationStructure_has_ValueMappingRelationship">
155 <xs:annotation>
156 <xs:documentation></xs:documentation>
157 </xs:annotation>
158 <xs:complexType>
159 <xs:complexContent>
160 <xs:restriction base="AssociationReferenceXsdType">
161 <xs:sequence>
162 <xs:element name="ddiReference"
163 type="InternationalRegistrationDataIdentifierXsdType"
164 minOccurs="0"
165 maxOccurs="1"
166 xml:id="PhysicalLayoutRelationStructure_has_ValueMappingRelationship-ddiReference"/>
167 <xs:element name="validType"
168 minOccurs="1"
169 maxOccurs="1"
170 xml:id="PhysicalLayoutRelationStructure_has_ValueMappingRelationship-validType">
171 <xs:simpleType>
172 <xs:restriction base="xs:NMTOKEN">
173 <xs:enumeration value="ValueMappingRelationship"/>
174 </xs:restriction>
175 </xs:simpleType>
176 </xs:element>
177 </xs:sequence>
178 </xs:restriction>
179 </xs:complexContent>
180 </xs:complexType>
181 </xs:element>
182 </xs:sequence>
183</xs:complexType>
Fragment for the class PhysicalLayoutRelationStructure (main ontology)
1# class PhysicalLayoutRelationStructure
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalLayoutRelationStructure
3cdi:PhysicalLayoutRelationStructure
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "PhysicalLayoutRelationStructure";
6 rdfs:comment "Definition\n==========\nRealization of relation structure that is used to describe the sequence of value mappings in a physical layout. \n\nExamples\n======== \nThe W3C Tabular Data on the Web specification section 4.5 Cells (https://www.w3.org/TR/tabular-data-model/#content-type) allows for a list datatype within cells. In the example below there are three top level instance variables: PersonID - the person identifier; AgeYr - age in years; BpSys_Dia - blood pressure (a list containing Systolic and Diastolic values). There are two variables at a secondary level of the hierarchy: Systolic - the systolic pressure; Diastolic - the diastolic pressure. The delimited file below uses the comma to separate \"columns\" and forward slash to separate elements of a blood pressure list. ::\n\n PersonID, AgeYr, BpSys_Dia \n 1,22,119/67 \n 2,68,122/70 \n\nThe physical relation structure in this case would describe a BpSys_Dia list variable as containing an ordered sequence of the Systolic and Diastolic instance variables. \n\nExplanatory notes\n=================\nThis can be more complex than a simple sequence."@en;
7
8.
9
10cdi:PhysicalLayoutRelationStructure-criteria
11 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12 rdfs:label "criteria";
13 rdfs:comment "Intentional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.)."@en;
14 rdfs:domain cdi:PhysicalLayoutRelationStructure;
15 rdfs:range cdi:InternationalString;
16.
17
18cdi:PhysicalLayoutRelationStructure-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:PhysicalLayoutRelationStructure;
23 rdfs:range cdi:Identifier;
24.
25
26cdi:PhysicalLayoutRelationStructure-name
27 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
28 rdfs:label "name";
29 rdfs:comment "A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided then a context to differentiate usage must be provided as well."@en;
30 rdfs:domain cdi:PhysicalLayoutRelationStructure;
31 rdfs:range cdi:ObjectName;
32.
33
34cdi:PhysicalLayoutRelationStructure-purpose
35 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
36 rdfs:label "purpose";
37 rdfs:comment "Intent or reason for the object/the description of the object."@en;
38 rdfs:domain cdi:PhysicalLayoutRelationStructure;
39 rdfs:range cdi:InternationalString;
40.
41
42cdi:PhysicalLayoutRelationStructure-semantics
43 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
44 rdfs:label "semantics";
45 rdfs:comment "Specifies the semantics of the object in reference to a vocabulary, ontology, etc."@en;
46 rdfs:domain cdi:PhysicalLayoutRelationStructure;
47 rdfs:range cdi:ControlledVocabularyEntry;
48.
49
50cdi:PhysicalLayoutRelationStructure-specification
51 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
52 rdfs:label "specification";
53 rdfs:comment "Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumerated list. Use if all relations within this relation structure are of the same specification."@en;
54 rdfs:domain cdi:PhysicalLayoutRelationStructure;
55 rdfs:range cdi:StructureSpecification;
56.
57
58cdi:PhysicalLayoutRelationStructure-topology
59 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
60 rdfs:label "topology";
61 rdfs:comment "Indicates the form of the associations among members of the collection. Specifies the way in which constituent parts are interrelated or arranged."@en;
62 rdfs:domain cdi:PhysicalLayoutRelationStructure;
63 rdfs:range cdi:ControlledVocabularyEntry;
64.
65
66cdi:PhysicalLayoutRelationStructure-totality
67 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
68 rdfs:label "totality";
69 rdfs:comment "Indicates whether the related collections are comprehensive in terms of their coverage."@en;
70 rdfs:domain cdi:PhysicalLayoutRelationStructure;
71 rdfs:range cdi:StructureExtent;
72.
73
74
75cdi:PhysicalLayoutRelationStructure_has_ValueMappingRelationship
76 a rdf:Property, owl:ObjectProperty, ucmis:Association;
77 # ASSOCIATION
78 rdfs:label "has";
79 skos:altLabel "PhysicalLayoutRelationStructure_has_ValueMappingRelationship";
80
81 rdfs:domain cdi:PhysicalLayoutRelationStructure;
82 rdfs:range cdi:ValueMappingRelationship;
83.
84
85cdi:PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout
86 a rdf:Property, owl:ObjectProperty, ucmis:Association;
87 # ASSOCIATION
88 rdfs:label "structures";
89 skos:altLabel "PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout";
90
91 rdfs:domain cdi:PhysicalLayoutRelationStructure;
92 rdfs:range cdi:PhysicalSegmentLayout;
93.
Fragment for the class PhysicalLayoutRelationStructure (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 "PhysicalLayoutRelationStructure": "cdi:PhysicalLayoutRelationStructure",
7 "criteria": {
8 "@id": "cdi:PhysicalLayoutRelationStructure-criteria",
9 "@type": "@id",
10 "@context": "InternationalString.jsonld"
11 },
12 "identifier": {
13 "@id": "cdi:PhysicalLayoutRelationStructure-identifier",
14 "@type": "@id",
15 "@context": "Identifier.jsonld"
16 },
17 "name": {
18 "@id": "cdi:PhysicalLayoutRelationStructure-name",
19 "@type": "@id",
20 "@context": "ObjectName.jsonld"
21 },
22 "purpose": {
23 "@id": "cdi:PhysicalLayoutRelationStructure-purpose",
24 "@type": "@id",
25 "@context": "InternationalString.jsonld"
26 },
27 "semantics": {
28 "@id": "cdi:PhysicalLayoutRelationStructure-semantics",
29 "@type": "@id",
30 "@context": "ControlledVocabularyEntry.jsonld"
31 },
32 "specification": {
33 "@id": "cdi:PhysicalLayoutRelationStructure-specification",
34 "@type": "@id",
35 "@context": "StructureSpecification.jsonld"
36 },
37 "topology": {
38 "@id": "cdi:PhysicalLayoutRelationStructure-topology",
39 "@type": "@id",
40 "@context": "ControlledVocabularyEntry.jsonld"
41 },
42 "totality": {
43 "@id": "cdi:PhysicalLayoutRelationStructure-totality",
44 "@type": "@vocab",
45 "@context": {
46 "Partial": "cdi:Partial",
47 "Total": "cdi:Total",
48 " comment ": "tag:json-should-support-trailing-commas"
49 }
50 },
51
52 "has": {
53 "@id": "cdi:PhysicalLayoutRelationStructure_has_ValueMappingRelationship",
54 "@type": "@id" },
55 "structures": {
56 "@id": "cdi:PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout",
57 "@type": "@id" },
58 " comment ": "tag:json-should-support-trailing-commas"
59 }
60 ],
61 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:10.",
62 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalLayoutRelationStructure"
63}
