Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 6.7
edited by Helena
on 2025/05/20 00:28
Change comment: There is no comment for this version
To version 6.5
edited by Helena
on 2025/05/20 00:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -242,8 +242,7 @@
242 242  
243 243  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_b6478a73.png||height="774" width="556"]]
244 244  
245 -(% class="wikigeneratedid" id="HFigure14:RepresentationwithintheStructurePattern" %)
246 -**Figure 14: Representation within the Structure Pattern**
245 +====== Figure 14: Representation within the Structure Pattern ======
247 247  
248 248  === {{id name="_Toc370985"/}}3.6.3 Explanation of the Diagrams ===
249 249  
... ... @@ -267,7 +267,7 @@
267 267  
268 268  __ReportStructure__: MetadataAttribute
269 269  
270 -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.
269 +Each Component takes its semantic (and possibly also its representation) from a Concept in 773 a ConceptScheme. This is represented by the conceptIdentity association to Concept.
271 271  
272 272  The //Component// may also have a localRepresentation, This allows a concrete class, such as Dimension, to specify its representation which is local to the //Structure// in which it is contained (for Dimension this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the Concept.
273 273  
... ... @@ -282,92 +282,118 @@
282 282  
283 283  The //Structure// may be used by one or more //StructureUsage//. An example of this in terms of concrete classes is that a DataflowDefinition (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the MetadataflowDefinition (link to MetadataStructureDefinition).
284 284  
285 -==== 3.6.3.2 Definitions ====
284 +**3.6.3.2 Definitions**
286 286  
287 -(% style="width:1001.29px" %)
288 -|**Class**|**Feature**|(% style="width:537px" %)**Description**
286 +|**Class**|**Feature**|**Description**
289 289  |//StructureUsage//|(((
290 290  Inherits from:
289 +
291 291  //MaintainableArtefact//
291 +
292 292  Sub classes are:
293 +
293 293  DataflowDefinition
294 -MetadataflowDefinition
295 -)))|(% style="width:537px" %)An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow Definition which is linked to a given structure – in this case the Data Structure Definition.
296 -| |structure|(% style="width:537px" %)An association to a Structure specifying the structure of the artefact.
295 +
296 +MetadataflowDefinition//    //
297 +)))|An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow Definition which is linked to a given structure – in this case the Data Structure Definition.
298 +| |structure|An association to a Structure specifying the structure of the artefact.
297 297  |//Structure//|(((
298 298  Inherits from:
301 +
299 299  //MaintainableArtefact//
303 +
300 300  Sub classes are:
305 +
301 301  DataStructure
307 +
302 302  Definition
309 +
303 303  MetadataStructure
311 +
304 304  Definition
305 -)))|(% style="width:537px" %)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.
306 -| |grouping|(% style="width:537px" %)A composite association to one or more component lists.
313 +)))|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.
314 +| |grouping|A composite association to one or more component lists.
307 307  |//ComponentList//|(((
308 308  Inherits from:
317 +
309 309  //IdentifiableArtefact//
319 +
310 310  Sub classes are:
321 +
311 311  DimensionDescriptor
323 +
312 312  GroupDimension
325 +
313 313  Descriptor
327 +
314 314  MeasureDescriptor
329 +
315 315  AttributeDescriptor
331 +
316 316  MetadataTarget
333 +
317 317  ReportStructure
318 -)))|(% style="width:537px" %)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.
319 -| |components|(% style="width:537px" %)An aggregate association to one or more components which make up the list.
335 +)))|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.
336 +| |components|An aggregate association to one or more components which make up the list.
320 320  |//Component//|(((
321 321  Inherits from:
339 +
322 322  //IdentifiableArtefact//
341 +
323 323  Sub classes are:
343 +
324 324  PrimaryMeasure
345 +
325 325  DataAttribute
326 -//DimensionComponent
327 -TargetObject//
347 +
348 +//DimensionComponent//
349 +
350 +//TargetObject//
351 +
328 328  MetadataAttribute
329 -)))|(% style="width:537px" %)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.
330 -| |conceptIdentity|(% style="width:537px" %)Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
331 -| |localRepresentation|(% style="width:537px" %)Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage)
332 -|Representation| |(% style="width:537px" %)The allowable value or format for Component or Concept
333 -| |+enumerated|(% style="width:537px" %)Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association (e.g. Identifier Component can have any of the sub classes of Item Scheme, whereas Measure Dimension must have a Concept Scheme).
334 -| |+nonEnumerated|(% style="width:537px" %)Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set.
335 -|Facet| |(% style="width:537px" %)Defines the format for the content of the Component when reported in a data or metadata set.
336 -| |facetType|(% style="width:537px" %)A specific content type which is constrained by the FacetType enumeration
337 -| |facetValueType|(% style="width:537px" %)(((
353 +)))|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.
354 +| |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
355 +| |localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage)
356 +|Representation| |The allowable value or format for Component or Concept
357 +| |+enumerated|Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association (e.g. Identifier Component can have any of the sub classes of Item Scheme, whereas Measure Dimension must have a Concept Scheme).
358 +| |+nonEnumerated|Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set.
359 +|Facet| |Defines the format for the content of the Component when reported in a data or metadata set.
360 +| |facetType|A specific content type which is constrained by the FacetType enumeration
361 +| |facetValueType|(((
338 338  The format of the value of a Component when reported in a data or metadata set.
339 339  
340 340  This is contrained by the FacetValueType enumeration.
341 341  )))
342 -| |+itemSchemeFacet|(% style="width:537px" %)Defines the format of the identifiers in an Item Scheme used by a Component. Typically this would define the number of characters (length) of the identifier.
343 -|ExtendedFacet| |(% style="width:537px" %)This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute
366 +| |+itemSchemeFacet|Defines the format of the identifiers in an Item Scheme used by a Component. Typically this would define the number of characters (length) of the identifier.
367 +|ExtendedFacet| |This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute
344 344  
345 -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)
369 +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)
346 346  
347 347  ==== 3.6.3.3 Representation Constructs ====
348 348  
349 349  The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, 818 and have equivalents in most current implementation platforms:
350 350  
375 +:
376 +
351 351  (((
352 -(% style="width:1034.29px" %)
353 -|(% style="width:222px" %)**SDMX Facet Value Type**|(% style="width:229px" %)**XML Schema Data Type**|(% style="width:216px" %)**.NET Framework Type**|(% style="width:354px" %)**Java Data Type**
354 -|(% style="width:222px" %)String|(% style="width:229px" %)xsd:string|(% style="width:216px" %)System.String|(% style="width:354px" %)java.lang.String
355 -|(% style="width:222px" %)Big Integer|(% style="width:229px" %)xsd:integer|(% style="width:216px" %)System.Decimal|(% style="width:354px" %)java.math.BigInteger
356 -|(% style="width:222px" %)Integer|(% style="width:229px" %)xsd:int|(% style="width:216px" %)System.Int32|(% style="width:354px" %)int
357 -|(% style="width:222px" %)Long|(% style="width:229px" %)xsd.long|(% style="width:216px" %)System.Int64|(% style="width:354px" %)long
358 -|(% style="width:222px" %)Short|(% style="width:229px" %)xsd:short|(% style="width:216px" %)System.Int16|(% style="width:354px" %)short
359 -|(% style="width:222px" %)Decimal|(% style="width:229px" %)xsd:decimal|(% style="width:216px" %)System.Decimal|(% style="width:354px" %)java.math.BigDecimal
360 -|(% style="width:222px" %)Float|(% style="width:229px" %)xsd:float|(% style="width:216px" %)System.Single|(% style="width:354px" %)float
361 -|(% style="width:222px" %)Double|(% style="width:229px" %)xsd:double|(% style="width:216px" %)System.Double|(% style="width:354px" %)double
362 -|(% style="width:222px" %)Boolean|(% style="width:229px" %)xsd:boolean|(% style="width:216px" %)System.Boolean|(% style="width:354px" %)boolean
363 -|(% style="width:222px" %)URI|(% style="width:229px" %)xsd:anyURI|(% style="width:216px" %)System.Uri|(% style="width:354px" %)Java.net.URI or java.lang.String
364 -|(% style="width:222px" %)DateTime|(% style="width:229px" %)xsd:dateTime|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
365 -|(% style="width:222px" %)Time|(% style="width:229px" %)xsd:time|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
366 -|(% style="width:222px" %)GregorianYear|(% style="width:229px" %)xsd:gYear|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
367 -|(% style="width:222px" %)GregorianMonth|(% style="width:229px" %)xsd:gYearMonth|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
368 -|(% style="width:222px" %)GregorianDay|(% style="width:229px" %)xsd:date|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
369 -|(% style="width:222px" %)Day, MonthDay, Month|(% style="width:229px" %)xsd:g*|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
370 -|(% style="width:222px" %)Duration|(% style="width:229px" %)xsd:duration|(% style="width:216px" %)System.TimeSpan|(% style="width:354px" %)javax.xml.datatype.Dura tion
378 +|**SDMX Facet Value Type**|**XML Schema Data Type     **|**.NET Framework Type**|**Java Data Type**
379 +|String|xsd:string|System.String|java.lang.String
380 +|Big Integer|xsd:integer|System.Decimal|java.math.BigInteger
381 +|Integer|xsd:int|System.Int32|int
382 +|Long|xsd.long|System.Int64|long
383 +|Short|xsd:short|System.Int16|short
384 +|Decimal|xsd:decimal|System.Decimal|java.math.BigDecimal
385 +|Float|xsd:float|System.Single|float
386 +|Double|xsd:double|System.Double|double
387 +|Boolean|xsd:boolean|System.Boolean|boolean
388 +|URI|xsd:anyURI|System.Uri|Java.net.URI or java.lang.String
389 +|DateTime|xsd:dateTime|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
390 +|Time|xsd:time|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
391 +|GregorianYear|xsd:gYear|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
392 +|GregorianMonth|xsd:gYearMonth|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
393 +|GregorianDay|xsd:date|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
394 +|Day, MonthDay, Month|xsd:g*|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
395 +|Duration|xsd:duration|System.TimeSpan|javax.xml.datatype.Dura tion
371 371  )))
372 372  
373 373  There are also a number of SDMX data types which do not have these direct 822 correspondences, often because they are composite representations or restrictions of a 823 broader data type. These are detailed in Section 6 of the standards.