Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 2.5
edited by Helena
on 2025/06/08 00:53
Change comment: There is no comment for this version
To version 3.3
edited by Helena
on 2025/06/08 00:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -192,29 +192,17 @@
192 192  | |(% style="width:297px" %)/items|(% style="width:583px" %)Association to the Items in the scheme.
193 193  |//Item//|(% style="width:297px" %)(((
194 194  Inherits from:
195 -
196 196  //NameableArtefact//
197 -
198 198  Direct sub classes are
199 -
200 200  Category
201 -
202 202  Concept
203 -
204 204  Code
205 -
206 206  ReportingCategory //Organisation//
207 -
208 208  Transformation
209 -
210 210  CustomType
211 -
212 212  NamePersonalisation
213 -
214 214  Ruleset
215 -
216 216  VtlMapping
217 -
218 218  UserDefinedOperator// //hierarchy
219 219  )))|(% style="width:583px" %)(((
220 220  The Item is an item of content in an Item Scheme. This may be a node in a taxonomy or ontology, a code in a code list etc. Node that at the conceptual level the Organisation is not hierarchic.
... ... @@ -227,8 +227,11 @@
227 227  
228 228  The Structure Pattern is a basic architectural pattern which allows the specification of complex tabular structures which are often found in statistical data (such as Data Structure Definition, and Metadata Structure Definition). A Structure is a set of ordered lists. A pattern to underpin this tabular structure has been developed, so that commonalities between these structure definitions can be supported by common software and common syntax structures.
229 229  
230 -===== 3.6.2 Class Diagrams [[image:1749246130548-601.jpeg]] =====
218 +=== 3.6.2 Class Diagrams ===
231 231  
220 +(% class="wikigeneratedid" %)
221 +[[image:1749246130548-601.jpeg]]
222 +
232 232  **Figure 14: The Structure Pattern**
233 233  
234 234  [[image:1749246130554-995.jpeg]]
... ... @@ -235,9 +235,9 @@
235 235  
236 236  **Figure 15: Representation within the Structure Pattern**
237 237  
238 -====== 3.6.3 Explanation of the Diagrams ======
229 +=== 3.6.3 Explanation of the Diagrams ===
239 239  
240 -3.6.3.1 Narrative
231 +==== 3.6.3.1 Narrative ====
241 241  
242 242  The //Structure// is an abstract class which contains a set of one or more //ComponentList//(s) (this class is also abstract). An example of a concrete //Structure// is DataStructureDefinition.
243 243  
... ... @@ -246,13 +246,9 @@
246 246  The //Component// is contained in a //ComponentList//. The type of //Component// in a //ComponentList// is dependent on the concrete class of the ComponentList as follows:
247 247  
248 248  DimensionDescriptor: Dimension, TimeDimension
249 -
250 250  GroupDimensionDescriptor: Dimension, TimeDimension
251 -
252 252  MeasureDescriptor: Measure
253 -
254 254  AttributeDescriptor: DataAttribute, MetadataAttributeRef
255 -
256 256  MetadataAttributeDescriptor: MetadataAttribute
257 257  
258 258  Each //Component// takes its semantic (and possibly also its representation) from a Concept in a ConceptScheme. This is represented by the conceptIdentity association to Concept.
... ... @@ -271,59 +271,41 @@
271 271  
272 272  The //Structure// may be used by one or more //StructureUsage//(s). An example of this, in terms of concrete classes, is that a Dataflow (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the Metadataflow (link to MetadataStructureDefinition).
273 273  
274 -3.6.3.2 Definitions
261 +==== 3.6.3.2 Definitions ====
275 275  
276 276  |**Class**|**Feature**|**Description**
277 277  |StructureUsage|(((
278 278  Inherits from:
279 -
280 280  //MaintainableArtefact//
281 -
282 282  Sub classes are:
283 -
284 284  Dataflow
285 -
286 286  Metadataflow
287 287  )))|An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow which is linked to a given structure – in this case the Data Structure Definition.
288 288  | |structure|An association to a Structure specifying the structure of the artefact.
289 289  |Structure|(((
290 290  Inherits from:
291 -
292 292  //MaintainableArtefact//
293 -
294 294  Sub classes are:
295 -
296 296  DataStructureDefinition MetadataStructureDefinit ion
297 297  )))|Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners.
298 298  | |grouping|A composite association to one or more component lists.
299 299  |//ComponentList//|(((
300 300  Inherits from:
301 -
302 302  //IdentifiableArtefact//
303 -
304 304  Sub classes are:
305 -
306 306  DimensionDescriptor
307 -
308 308  GroupDimensionDescriptor
309 -
310 310  MeasureDescriptor
311 -
312 312  AttributeDescriptor MetadataAttributeDescrip tor
313 313  )))|An abstract definition of a list of components. A concrete example is a Dimension Descriptor, which defines the list of Dimensions in a Data Structure Definition.
314 314  | |components|An aggregate association to one or more components which make up the list.
315 315  |//Component//|(((
316 316  Inherits from:
317 -
318 318  //IdentifiableArtefact//
319 -
320 320  Sub classes are:
321 -
322 322  Measure
323 -
324 -//AttributeComponent//
325 -
326 -//DimensionComponent//
294 +//AttributeComponent
295 +DimensionComponent//
327 327  )))|A Component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes.
328 328  | |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component.
329 329  | |localRepresentation|(((
... ... @@ -342,59 +342,55 @@
342 342  
343 343  The specification of the content and use of the sub classes to //ComponentList// and //Component// can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition). Moreover, the FacetType SentinelValues is explained in the datastructure representation diagram (see 5.3.2.2), since it only concerns DataStructureDefinitions.
344 344  
345 -3.6.3.3 Representation Constructs
314 +==== 3.6.3.3 Representation Constructs ====
346 346  
347 347  The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
348 348  
349 -|(((
350 -**SDMX Facet**
318 +|(% style="width:188px" %)(((
319 +**SDMX Facet Value Type**
320 +)))|(% style="width:203px" %)**XML Schema Data Type**|(% style="width:207px" %)**JSON Schema Data Type**|(% style="width:184px" %)(((
321 +**.NET Framework Type**
322 +)))|(% style="width:833px" %)**Java Data Type**
323 +|(% style="width:188px" %)String|(% style="width:203px" %)xsd:string|(% style="width:207px" %)string|(% style="width:184px" %)System.String|(% style="width:833px" %)java.lang.String
324 +|(% style="width:188px" %)Big Integer|(% style="width:203px" %)xsd:integer|(% style="width:207px" %)integer|(% style="width:184px" %)System.Decimal|(% style="width:833px" %)java.math.BigInteger
325 +|(% style="width:188px" %)Integer|(% style="width:203px" %)xsd:int|(% style="width:207px" %)integer|(% style="width:184px" %)System.Int32|(% style="width:833px" %)int
326 +|(% style="width:188px" %)Long|(% style="width:203px" %)xsd.long|(% style="width:207px" %)integer|(% style="width:184px" %)System.Int64|(% style="width:833px" %)long
327 +|(% style="width:188px" %)Short|(% style="width:203px" %)xsd:short|(% style="width:207px" %)integer|(% style="width:184px" %)System.Int16|(% style="width:833px" %)short
328 +|(% style="width:188px" %)Decimal|(% style="width:203px" %)xsd:decimal|(% style="width:207px" %)number|(% style="width:184px" %)System.Decimal|(% style="width:833px" %)java.math.BigDecimal
329 +|(% style="width:188px" %)Float|(% style="width:203px" %)xsd:float|(% style="width:207px" %)number|(% style="width:184px" %)System.Single|(% style="width:833px" %)float
330 +|(% style="width:188px" %)Double|(% style="width:203px" %)xsd:double|(% style="width:207px" %)number|(% style="width:184px" %)System.Double|(% style="width:833px" %)double
331 +|(% style="width:188px" %)Boolean|(% style="width:203px" %)xsd:boolean|(% style="width:207px" %)boolean|(% style="width:184px" %)System.Boolean|(% style="width:833px" %)boolean
332 +|(% style="width:188px" %)URI|(% style="width:203px" %)xsd:anyURI|(% style="width:207px" %)string:uri|(% style="width:184px" %)System.Uri|(% style="width:833px" %)Java.net.URI or java.lang.String
333 +|(% style="width:188px" %)DateTime|(% style="width:203px" %)xsd:dateTime|(% style="width:207px" %)string:datetime|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
334 +|(% style="width:188px" %)Time|(% style="width:203px" %)xsd:time|(% style="width:207px" %)string:time|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
335 +|(% style="width:188px" %)GregorianYear|(% style="width:203px" %)xsd:gYear|(% style="width:207px" %)string[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]]|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
336 +|(% style="width:188px" %)GregorianMonth|(% style="width:203px" %)xsd:gYearMonth|(% style="width:207px" %)string|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
337 +|(% style="width:188px" %)GregorianDay|(% style="width:203px" %)xsd:date|(% style="width:207px" %)string|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
338 +|(% style="width:188px" %)Day, MonthDay, Month|(% style="width:203px" %)xsd:g*|(% style="width:207px" %)string|(% style="width:184px" %)System.DateTime|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
339 +|(% style="width:188px" %)Duration|(% style="width:203px" %)xsd:duration|(% style="width:207px" %)string|(% style="width:184px" %)System.TimeSpan|(% style="width:833px" %)javax.xml.datatype.Dur ation
351 351  
352 -**Value Type**
353 -)))|**XML Schema Data Type**|**JSON Schema Data Type**|(((
354 -**.NET Framework**
355 -
356 -**Type**
357 -)))|**Java Data Type**
358 -|String|xsd:string|string|System.String|java.lang.String
359 -|Big Integer|xsd:integer|integer|System.Decimal|java.math.BigInteger
360 -|Integer|xsd:int|integer|System.Int32|int
361 -|Long|xsd.long|integer|System.Int64|long
362 -|Short|xsd:short|integer|System.Int16|short
363 -|Decimal|xsd:decimal|number|System.Decimal|java.math.BigDecimal
364 -|Float|xsd:float|number|System.Single|float
365 -|Double|xsd:double|number|System.Double|double
366 -|Boolean|xsd:boolean|boolean|System.Boolean|boolean
367 -|URI|xsd:anyURI|string:uri|System.Uri|Java.net.URI or java.lang.String
368 -|DateTime|xsd:dateTime|string:datetime|System.DateTime|javax.xml.datatype.XML GregorianCalendar
369 -|Time|xsd:time|string:time|System.DateTime|javax.xml.datatype.XML GregorianCalendar
370 -|GregorianYear|xsd:gYear|string[[(% class="wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]]|System.DateTime|javax.xml.datatype.XML GregorianCalendar
371 -|GregorianMonth|xsd:gYearMonth|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
372 -|GregorianDay|xsd:date|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
373 -|Day, MonthDay, Month|xsd:g*|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
374 -|Duration|xsd:duration|string|System.TimeSpan|javax.xml.datatype.Dur ation
375 -
376 376  There are also a number of SDMX data types which do not have these direct correspondences, often because they are composite representations or restrictions of a broader data type. These are detailed in Section 6 of the standards.
377 377  
378 378  The Representation is composed of Facets, each of which conveys characteristic information related to the definition of a value domain. Often a set of Facets are needed to convey the required semantic. For example, a sequence is defined by a minimum of two Facets: one to define the start value, and one to define the interval.
379 379  
345 +(% style="width:981.835px" %)
346 +|(% style="width:107px" %)**Facet Type**|(% style="width:872px" %)**Explanation**
347 +|(% style="width:107px" %)isSequence|(% style="width:872px" %)The isSequence facet indicates whether the values are intended to be ordered, and it may work in combination with the interval, startValue,and endValue facet or the timeInterval, startTime, and endTime, facets. If this attribute holds a value of true, a start value or time and a numeric or time interval must be supplied. If an end value is not given, then the sequence continues indefinitely.
348 +|(% style="width:107px" %)interval|(% style="width:872px" %)The interval attribute specifies the permitted interval (increment) in a sequence. In order for this to be used, the isSequence attribute must have a value of true.
349 +|(% style="width:107px" %)startValue|(% style="width:872px" %)The startValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet isused for a numeric sequence and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed.
350 +|(% style="width:107px" %)endValue|(% style="width:872px" %)The endValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet is used for a numeric sequence and indicates that ending point (if any) of the sequence.
351 +|(% style="width:107px" %)timeInterval|(% style="width:872px" %)The timeInterval facet indicates the permitted duration in a time sequence. In order for this to be used, the isSequence facet must have a value of true.
352 +|(% style="width:107px" %)startTime|(% style="width:872px" %)The startTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). Thisnattribute is used for a time sequence and indicates the start time of thensequence. This value is mandatory for a time sequence to be expressed.
353 +|(% style="width:107px" %)endTime|(% style="width:872px" %)The endTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). This facet is used for a time sequence and indicates that ending point (if any) ofnthe sequence.
354 +|(% style="width:107px" %)minLength|(% style="width:872px" %)The minLength facet specifies the minimum and length of the value in characters.
355 +|(% style="width:107px" %)maxLength|(% style="width:872px" %)The maxLength facet specifies the maximum length of the value in characters.
356 +|(% style="width:107px" %)minValue|(% style="width:872px" %)The minValue facet is used for inclusive and exclusive ranges, indicating what the lower bound of the range is. If this is used with an inclusive range, a valid value will be greater than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
357 +|(% style="width:107px" %)maxValue|(% style="width:872px" %)The maxValue facet is used for inclusive and exclusive ranges, indicating what the upper bound of the range is. If this is used with an inclusive range, a valid value will be less than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
358 +|(% style="width:107px" %)Decimals|(% style="width:872px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
359 +|(% style="width:107px" %)pattern|(% style="width:872px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
380 380  
381 -|**Facet Type**|**Explanation**
382 -|isSequence|The isSequence facet indicates whether the values are intended to be ordered, and it may work in combination with the interval, startValue,and endValue facet or the timeInterval, startTime, and endTime, facets. If this attribute holds a value of true, a start value or time and a numeric or time interval must be supplied. If an end value is not given, then the sequence continues indefinitely.
383 -|interval|The interval attribute specifies the permitted interval (increment) in a sequence. In order for this to be used, the isSequence attribute must have a value of true.
384 -|startValue|The startValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet isused for a numeric sequence and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed.
385 -|endValue|The endValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet is used for a numeric sequence and indicates that ending point (if any) of the sequence.
386 -|timeInterval|The timeInterval facet indicates the permitted duration in a time sequence. In order for this to be used, the isSequence facet must have a value of true.
387 -|startTime|The startTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). Thisnattribute is used for a time sequence and indicates the start time of thensequence. This value is mandatory for a time sequence to be expressed.
388 -|endTime|The endTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). This facet is used for a time sequence and indicates that ending point (if any) ofnthe sequence.
389 -|minLength|The minLength facet specifies the minimum and length of the value in characters.
390 -|maxLength|The maxLength facet specifies the maximum length of the value in characters.
391 -|minValue|The minValue facet is used for inclusive and exclusive ranges, indicating what the lower bound of the range is. If this is used with an inclusive range, a valid value will be greater than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
392 -|maxValue|The maxValue facet is used for inclusive and exclusive ranges, indicating what the upper bound of the range is. If this is used with an inclusive range, a valid value will be less than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
393 -|Decimals|The decimals facet indicates the number of characters allowed after the decimal separator.
394 -|pattern|The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
395 395  
396 396  
397 -
398 398  ----
399 399  
400 400  [[~[1~]>>path:#_ftnref1]] In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.