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.3
edited by Helena
on 2025/05/20 00:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -159,8 +159,7 @@
159 159  
160 160  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_a2879920.jpg||height="602" width="614"]]
161 161  
162 -(% class="wikigeneratedid" id="HFigure12TheItemSchemePattern" %)
163 -**Figure 12 The Item Scheme Pattern**
162 +====== Figure 12 The Item Scheme Pattern ======
164 164  
165 165  ===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
166 166  
... ... @@ -186,47 +186,73 @@
186 186  
187 187  ==== 3.5.3.2 Definitions ====
188 188  
189 -(% style="width:911.294px" %)
190 -|**Class**|(% style="width:246px" %)**Feature**|(% style="width:478px" %)**Description**
191 -|//ItemScheme//|(% style="width:246px" %)(((
188 +|**Class**|**Feature**|**Description**
189 +|//ItemScheme//|(((
192 192  Inherits from:
191 +
193 193  //MaintainableArtefact//
193 +
194 194  Direct sub classes are:
195 +
195 195  CategoryScheme
197 +
196 196  ConceptScheme
199 +
197 197  Codelist
198 -)))|(% style="width:478px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
199 -| |(% style="width:246px" %)(((
201 +)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
202 +| |(((
200 200  ReportingTaxonomy
204 +
201 201  //OrganisationScheme//
206 +
202 202  Transformation Scheme
208 +
203 203  CustomTypeScheme
210 +
204 204  NamePersonasationScheme
212 +
205 205  RuletScheme
214 +
206 206  VtlMappingScheme
216 +
207 207  UserDefinedOperatorScheme
208 -)))|(% style="width:478px" %)
209 -| |(% style="width:246px" %)isPartial|(% style="width:478px" %)Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme.
210 -| |(% style="width:246px" %)items|(% style="width:478px" %)Association to the Items in the scheme.
211 -|//Item//|(% style="width:246px" %)(((
218 +)))|
219 +| |isPartial|Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme.
220 +| |items|Association to the Items in the scheme.
221 +|//Item//|(((
212 212  Inherits from:
223 +
213 213  //NameableArtefact//
214 -Direct sub classes are Category
225 +
226 +Direct sub classes are
227 +
228 +Category
229 +
215 215  Concept
231 +
216 216  Code
233 +
217 217  ReportingCategory
235 +
218 218  //Organisation//
237 +
219 219  Transformation
239 +
220 220  CustomType
241 +
221 221  NamePersonlisation
243 +
222 222  Ruleset
245 +
223 223  VtlMapping
224 -UserDefinedOperator
225 -)))|(% style="width:478px" %)(((
247 +
248 +UserDefinedOperator//    //
249 +)))|(((
226 226  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.
251 +
227 227  Note that at the conceptual level the Organisation is not hierarchic
228 228  )))
229 -| |(% style="width:246px" %)hierarchy|(% style="width:478px" %)This allows an Item optionally to have one or more child Items.
254 +| |hierarchy|This allows an Item optionally to have one or more child Items.
230 230  
231 231  == {{id name="_Toc370982"/}}3.6 The Structure Pattern ==
232 232  
... ... @@ -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**
270 +====== 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.
294 +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 ====
309 +**3.6.3.2 Definitions**
286 286  
287 -(% style="width:1001.29px" %)
288 -|**Class**|**Feature**|(% style="width:537px" %)**Description**
311 +|**Class**|**Feature**|**Description**
289 289  |//StructureUsage//|(((
290 290  Inherits from:
314 +
291 291  //MaintainableArtefact//
316 +
292 292  Sub classes are:
318 +
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.
320 +
321 +MetadataflowDefinition//    //
322 +)))|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.
323 +| |structure|An association to a Structure specifying the structure of the artefact.
297 297  |//Structure//|(((
298 298  Inherits from:
326 +
299 299  //MaintainableArtefact//
328 +
300 300  Sub classes are:
330 +
301 301  DataStructure
332 +
302 302  Definition
334 +
303 303  MetadataStructure
336 +
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.
338 +)))|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.
339 +| |grouping|A composite association to one or more component lists.
307 307  |//ComponentList//|(((
308 308  Inherits from:
342 +
309 309  //IdentifiableArtefact//
344 +
310 310  Sub classes are:
346 +
311 311  DimensionDescriptor
348 +
312 312  GroupDimension
350 +
313 313  Descriptor
352 +
314 314  MeasureDescriptor
354 +
315 315  AttributeDescriptor
356 +
316 316  MetadataTarget
358 +
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.
360 +)))|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.
361 +| |components|An aggregate association to one or more components which make up the list.
320 320  |//Component//|(((
321 321  Inherits from:
364 +
322 322  //IdentifiableArtefact//
366 +
323 323  Sub classes are:
368 +
324 324  PrimaryMeasure
370 +
325 325  DataAttribute
326 -//DimensionComponent
327 -TargetObject//
372 +
373 +//DimensionComponent//
374 +
375 +//TargetObject//
376 +
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" %)(((
378 +)))|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.
379 +| |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
380 +| |localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage)
381 +|Representation| |The allowable value or format for Component or Concept
382 +| |+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).
383 +| |+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.
384 +|Facet| |Defines the format for the content of the Component when reported in a data or metadata set.
385 +| |facetType|A specific content type which is constrained by the FacetType enumeration
386 +| |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
391 +| |+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.
392 +|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)
394 +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  
400 +:
401 +
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
403 +|**SDMX Facet Value Type**|**XML Schema Data Type     **|**.NET Framework Type**|**Java Data Type**
404 +|String|xsd:string|System.String|java.lang.String
405 +|Big Integer|xsd:integer|System.Decimal|java.math.BigInteger
406 +|Integer|xsd:int|System.Int32|int
407 +|Long|xsd.long|System.Int64|long
408 +|Short|xsd:short|System.Int16|short
409 +|Decimal|xsd:decimal|System.Decimal|java.math.BigDecimal
410 +|Float|xsd:float|System.Single|float
411 +|Double|xsd:double|System.Double|double
412 +|Boolean|xsd:boolean|System.Boolean|boolean
413 +|URI|xsd:anyURI|System.Uri|Java.net.URI or java.lang.String
414 +|DateTime|xsd:dateTime|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
415 +|Time|xsd:time|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
416 +|GregorianYear|xsd:gYear|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
417 +|GregorianMonth|xsd:gYearMonth|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
418 +|GregorianDay|xsd:date|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
419 +|Day, MonthDay, Month|xsd:g*|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
420 +|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.