Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 4.1
edited by Helena
on 2025/05/19 23:53
Change comment: There is no comment for this version
To version 8.1
edited by Helena
on 2025/05/20 00:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,6 @@
1 -= {{id name="_Toc370967"/}}3 SDMX Base Package =
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 3  == {{id name="_Toc370968"/}}3.1 Introduction ==
4 4  
... ... @@ -6,9 +6,9 @@
6 6  
7 7  The motivation for establishing the SDMX Base package is as follows:
8 8  
9 -* it is accepted “Best Practise” to identify fundamental archetypes occurring in a model//  //
10 -* identification of commonly found structures or “patterns” leads to easier understanding//  //
11 -* identification of patterns encourages re-use//  //
11 +* it is accepted “Best Practise” to identify fundamental archetypes occurring in a model
12 +* identification of commonly found structures or “patterns” leads to easier understanding
13 +* identification of patterns encourages re-use
12 12  
13 13  Each of the class diagrams in this section views classes from the SDMX Base package from a different perspective. There are detailed views of specific patterns, plus overviews showing inheritance between classes, and relationships amongst classes.
14 14  
... ... @@ -24,10 +24,8 @@
24 24  
25 25  This group of classes forms the nucleus of the administration facets of SDMX objects. They provide features which are reusable by derived classes to support horizontal functionality such as identity, versioning etc.
26 26  
27 -All classes derived from the abstract class //AnnotableArtefact// may have Annotations (or notes): this supports the need to add notes to all SDMX-ML elements. The Annotation is used to convey extra information to describe any SDMX construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to
29 +All classes derived from the abstract class //AnnotableArtefact// may have Annotations (or notes): this supports the need to add notes to all SDMX-ML elements. The Annotation is used to convey extra information to describe any SDMX construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to InternationalString).
28 28  
29 -InternationalString).
30 -
31 31  The //IdentifiableArtefact// is an abstract class that comprises the basic attributes needed for identification. Concrete classes based on //IdentifiableArtefact// all inherit the ability to be uniquely identified.
32 32  
33 33  The //NamableArtefact// is an abstract class that inherits from //IdentifiableArtefact //and in addition the +description and +name roles support multilingual descriptions and names for all objects based on //NameableArtefact//. The InternationalString supports the representation of a description in multiple locales (locale is similar to language but includes geographic variations such as Canadian French, US English etc.). The //LocalisedString// supports the representation of a description in one locale.
... ... @@ -38,70 +38,62 @@
38 38  
39 39  The inheritance chain from //AnnotableArtefact// through to //MaintainableArtefact// allows SDMX classes to inherit the features they need, from simple annotation, through identity, naming, to versioning and maintenance.
40 40  
41 -**3.2.2.2 Definitions**
41 +==== 3.2.2.2 Definitions ====
42 42  
43 -|**Class**|**Feature**|**Description**
44 -|//AnnotableArtefact//|(((
43 +(% style="width:902.294px" %)
44 +|**Class**|(% style="width:246px" %)**Feature**|(% style="width:480px" %)**Description**
45 +|//AnnotableArtefact//|(% style="width:246px" %)(((
45 45  Base inheritance sub classes are:
46 -
47 47  //IdentifiableArtefact//
48 -)))|Objects of classes derived from this can have attached annotations.
49 -|Annotation||Additional descriptive information attached to an object.
50 -||id|(((
48 +)))|(% style="width:480px" %)Objects of classes derived from this can have attached annotations.
49 +|Annotation|(% style="width:246px" %) |(% style="width:480px" %)Additional descriptive information attached to an object.
50 +| |(% style="width:246px" %)id|(% style="width:480px" %)(((
51 51  Identifier for the Annotation.
52 -
53 53  It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
54 54  )))
55 -||title//    //|A title used to identify an annotation.
56 -||type|Specifies how the annotation is to be processed.
57 -||url|A link to external descriptive text.
58 -||+text|An International String provides the multilingual text content of the annotation via this role.
59 -|//IdentifiableArtefact//|(((
54 +| |(% style="width:246px" %)title|(% style="width:480px" %)A title used to identify an annotation.
55 +| |(% style="width:246px" %)type|(% style="width:480px" %)Specifies how the annotation is to be processed.
56 +| |(% style="width:246px" %)url|(% style="width:480px" %)A link to external descriptive text.
57 +| |(% style="width:246px" %)+text|(% style="width:480px" %)An International String provides the multilingual text content of the annotation via this role.
58 +|//IdentifiableArtefact//|(% style="width:246px" %)(((
60 60  Superclass is
61 -
62 62  //AnnotableArtefact//
63 -
64 -Base inheritance sub classes are~://    //
65 -
61 +Base inheritance sub classes are:
66 66  //NameableArtefact//
67 -)))|Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
68 -||id|The unique identifier of the object.
69 -||uri|Universal resource identifier that may or may not be resolvable.
70 -||urn|Universal resource name – this is for use in registries: all registered objects have a urn.
71 -|//NameableArtefact//|(((
63 +)))|(% style="width:480px" %)Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
64 +| |(% style="width:246px" %)id|(% style="width:480px" %)The unique identifier of the object.
65 +| |(% style="width:246px" %)uri|(% style="width:480px" %)Universal resource identifier that may or may not be resolvable.
66 +| |(% style="width:246px" %)urn|(% style="width:480px" %)Universal resource name – this is for use in registries: all registered objects have a urn.
67 +|//NameableArtefact//|(% style="width:246px" %)(((
72 72  Superclass is
73 -
74 74  //IdentifiableArtefact// Base inheritance sub classes are:
75 -
76 76  //VersionableArtefact//
77 -)))|Provides a Name and Description to all derived classes in addition to identification and annotations.
78 -||+description|A multi-lingual description is provided by this role via the International String class.
79 -||+name|A multi-lingual name is provided by this role via the International String class
80 -|InternationalString||The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
81 -|LocalisedString||The Localised String supports the representation of text in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
82 -||label|Label of the string.
83 -||locale|The geographic locale of the string e.g French, Canadian French.
84 -|//VersionableArtefact//|(((
71 +)))|(% style="width:480px" %)Provides a Name and Description to all derived classes in addition to identification and annotations.
72 +| |(% style="width:246px" %)+description|(% style="width:480px" %)A multi-lingual description is provided by this role via the International String class.
73 +| |(% style="width:246px" %)+name|(% style="width:480px" %)A multi-lingual name is provided by this role via the International String class
74 +|InternationalString|(% style="width:246px" %) |(% style="width:480px" %)The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
75 +|LocalisedString|(% style="width:246px" %) |(% style="width:480px" %)The Localised String supports the representation of text in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
76 +| |(% style="width:246px" %)label|(% style="width:480px" %)Label of the string.
77 +| |(% style="width:246px" %)locale|(% style="width:480px" %)The geographic locale of the string e.g French, Canadian French.
78 +|//VersionableArtefact//|(% style="width:246px" %)(((
85 85  Superclass is
86 -
87 87  //NameableArtefact// Base inheritance sub classes are:
88 -
89 89  //MaintainableArtefact//
90 -)))|Provides versioning information for all derived objects.
91 -||version|A version string following an agreed convention
92 -||validFrom|Date from which the version is valid
93 -||validTo|Date from which version is superceded
94 -|//MaintainableArtefact//|(((
82 +)))|(% style="width:480px" %)Provides versioning information for all derived objects.
83 +| |(% style="width:246px" %)version|(% style="width:480px" %)A version string following an agreed convention
84 +| |(% style="width:246px" %)validFrom|(% style="width:480px" %)Date from which the version is valid
85 +| |(% style="width:246px" %)validTo|(% style="width:480px" %)Date from which version is superceded
86 +|//MaintainableArtefact//|(% style="width:246px" %)(((
95 95  Inherits from
96 96  
97 97  //VersionableArtefact//
98 -)))|An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
99 -||final|Defines whether a maintained artefact is draft or final.
100 -||isExternalReference|If set to “true” it indicates that the content of the object is held externally.
101 -||structureURL|The URL of an SDMX-ML document containing the external object.
102 -||serviceURL|The URL of an SDMX-compliant web service from which the external object can be retrieved.
103 -||+maintainer//    //|Association to the Maintenance Agency responsible for maintaining the artefact.
104 -|Agency||See section on “Organisations”
90 +)))|(% style="width:480px" %)An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
91 +| |(% style="width:246px" %)final|(% style="width:480px" %)Defines whether a maintained artefact is draft or final.
92 +| |(% style="width:246px" %)isExternalReference|(% style="width:480px" %)If set to “true” it indicates that the content of the object is held externally.
93 +| |(% style="width:246px" %)structureURL|(% style="width:480px" %)The URL of an SDMX-ML document containing the external object.
94 +| |(% style="width:246px" %)serviceURL|(% style="width:480px" %)The URL of an SDMX-compliant web service from which the external object can be retrieved.
95 +| |(% style="width:246px" %)+maintainer|(% style="width:480px" %)Association to the Maintenance Agency responsible for maintaining the artefact.
96 +|Agency|(% style="width:246px" %) |(% style="width:480px" %)See section on “Organisations”
105 105  
106 106  == {{id name="_Toc370972"/}}3.3 Basic Inheritance ==
107 107  
... ... @@ -167,11 +167,12 @@
167 167  
168 168  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_a2879920.jpg||height="602" width="614"]]
169 169  
170 -====== Figure 12 The Item Scheme Pattern ======
162 +(% class="wikigeneratedid" id="HFigure12TheItemSchemePattern" %)
163 +**Figure 12 The Item Scheme Pattern**
171 171  
172 172  ===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
173 173  
174 -**3.5.3.1 Narrative**
167 +==== 3.5.3.1 Narrative ====
175 175  
176 176  The //ItemScheme// is an abstract class which defines a set of //Item// (this class is also abstract). Its main purpose is to define a mechanism which can be used to create taxonomies which can classify other parts of the SDMX Information Model. It inherits from //MaintainableArtefact// which gives it the ability to be annotated, have identity, naming, versioning and be associated with an Agency. An example of a concrete class is a CategoryScheme. The associated Category are //Items//.
177 177  
... ... @@ -185,81 +185,53 @@
185 185  
186 186  The purpose of a partial //ItemScheme// is to support the exchange and dissemination of a subset ItemScheme without the need to maintain multiple //ItemScheme//s which contain the same //Item//s. For instance, when a Codelist is used in a DataStructureDefinition it is sometimes the case that only a sub-set of the Codes in a Codelist are relevant. In this case a partial Codelist can be constructed using the Constraint mechanism explained later in this document.
187 187  
188 -//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn attributes, a name and a description in the form of an
181 +//Item// inherits from //NameableArtefact// which gives it the ability to be annotated and have identity, and therefore has id, uri and urn attributes, a name and a description in the form of an InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e. it implicitly has the same agency as the //ItemScheme//).
189 189  
190 -InternationalString. Unlike the parent //ItemScheme//, the //Item// itself is not a //MaintainableArtefact// and therefore cannot have an independent Agency (i.e. it implicitly has the same agency as the //ItemScheme//).
191 -
192 192  The //Item// can be hierarchic and so one //Item// can have child //Item//s. The restriction of the hierarchic association is that a child //Item// can have only parent //Item//.
193 193  
194 194  ==== 3.5.3.2 Definitions ====
195 195  
196 -|**Class**|**Feature**|**Description**
197 -|//ItemScheme//|(((
187 +(% style="width:911.294px" %)
188 +|**Class**|(% style="width:246px" %)**Feature**|(% style="width:478px" %)**Description**
189 +|//ItemScheme//|(% style="width:246px" %)(((
198 198  Inherits from:
199 -
200 200  //MaintainableArtefact//
201 -
202 202  Direct sub classes are:
203 -
204 204  CategoryScheme
205 -
206 206  ConceptScheme
207 -
208 208  Codelist
209 -)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
210 -||(((
196 +)))|(% style="width:478px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
197 +| |(% style="width:246px" %)(((
211 211  ReportingTaxonomy
212 -
213 213  //OrganisationScheme//
214 -
215 215  Transformation Scheme
216 -
217 217  CustomTypeScheme
218 -
219 219  NamePersonasationScheme
220 -
221 221  RuletScheme
222 -
223 223  VtlMappingScheme
224 -
225 225  UserDefinedOperatorScheme
226 -)))|
227 -||isPartial|Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme.
228 -||items|Association to the Items in the scheme.
229 -|//Item//|(((
206 +)))|(% style="width:478px" %)
207 +| |(% 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.
208 +| |(% style="width:246px" %)items|(% style="width:478px" %)Association to the Items in the scheme.
209 +|//Item//|(% style="width:246px" %)(((
230 230  Inherits from:
231 -
232 232  //NameableArtefact//
233 -
234 -Direct sub classes are
235 -
236 -Category
237 -
212 +Direct sub classes are Category
238 238  Concept
239 -
240 240  Code
241 -
242 242  ReportingCategory
243 -
244 244  //Organisation//
245 -
246 246  Transformation
247 -
248 248  CustomType
249 -
250 250  NamePersonlisation
251 -
252 252  Ruleset
253 -
254 254  VtlMapping
255 -
256 -UserDefinedOperator//    //
257 -)))|(((
222 +UserDefinedOperator
223 +)))|(% style="width:478px" %)(((
258 258  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.
259 -
260 260  Note that at the conceptual level the Organisation is not hierarchic
261 261  )))
262 -||hierarchy|This allows an Item optionally to have one or more child Items.
227 +| |(% style="width:246px" %)hierarchy|(% style="width:478px" %)This allows an Item optionally to have one or more child Items.
263 263  
264 264  == {{id name="_Toc370982"/}}3.6 The Structure Pattern ==
265 265  
... ... @@ -275,7 +275,8 @@
275 275  
276 276  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_b6478a73.png||height="774" width="556"]]
277 277  
278 -====== Figure 14: Representation within the Structure Pattern ======
243 +(% class="wikigeneratedid" id="HFigure14:RepresentationwithintheStructurePattern" %)
244 +**Figure 14: Representation within the Structure Pattern**
279 279  
280 280  === {{id name="_Toc370985"/}}3.6.3 Explanation of the Diagrams ===
281 281  
... ... @@ -299,7 +299,7 @@
299 299  
300 300  __ReportStructure__: MetadataAttribute
301 301  
302 -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.
268 +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.
303 303  
304 304  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.
305 305  
... ... @@ -314,140 +314,112 @@
314 314  
315 315  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).
316 316  
317 -**3.6.3.2 Definitions**
283 +==== 3.6.3.2 Definitions ====
318 318  
319 -|**Class**|**Feature**|**Description**
285 +(% style="width:1001.29px" %)
286 +|**Class**|**Feature**|(% style="width:537px" %)**Description**
320 320  |//StructureUsage//|(((
321 321  Inherits from:
322 -
323 323  //MaintainableArtefact//
324 -
325 325  Sub classes are:
326 -
327 327  DataflowDefinition
328 -
329 -MetadataflowDefinition//    //
330 -)))|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.
331 -||structure|An association to a Structure specifying the structure of the artefact.
292 +MetadataflowDefinition
293 +)))|(% 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.
294 +| |structure|(% style="width:537px" %)An association to a Structure specifying the structure of the artefact.
332 332  |//Structure//|(((
333 333  Inherits from:
334 -
335 335  //MaintainableArtefact//
336 -
337 337  Sub classes are:
338 -
339 339  DataStructure
340 -
341 341  Definition
342 -
343 343  MetadataStructure
344 -
345 345  Definition
346 -)))|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.
347 -||grouping|A composite association to one or more component lists.
303 +)))|(% 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.
304 +| |grouping|(% style="width:537px" %)A composite association to one or more component lists.
348 348  |//ComponentList//|(((
349 349  Inherits from:
350 -
351 351  //IdentifiableArtefact//
352 -
353 353  Sub classes are:
354 -
355 355  DimensionDescriptor
356 -
357 357  GroupDimension
358 -
359 359  Descriptor
360 -
361 361  MeasureDescriptor
362 -
363 363  AttributeDescriptor
364 -
365 365  MetadataTarget
366 -
367 367  ReportStructure
368 -)))|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.
369 -||components|An aggregate association to one or more components which make up the list.
316 +)))|(% 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.
317 +| |components|(% style="width:537px" %)An aggregate association to one or more components which make up the list.
370 370  |//Component//|(((
371 371  Inherits from:
372 -
373 373  //IdentifiableArtefact//
374 -
375 375  Sub classes are:
376 -
377 377  PrimaryMeasure
378 -
379 379  DataAttribute
380 -
381 -//DimensionComponent//
382 -
383 -//TargetObject//
384 -
324 +//DimensionComponent
325 +TargetObject//
385 385  MetadataAttribute
386 -)))|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.
387 -||conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
388 -||localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage)
389 -|Representation||The allowable value or format for Component or Concept
390 -||+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).
391 -||+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.
392 -|Facet||Defines the format for the content of the Component when reported in a data or metadata set.
393 -||facetType|A specific content type which is constrained by the FacetType enumeration
394 -||facetValueType|(((
327 +)))|(% 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.
328 +| |conceptIdentity|(% style="width:537px" %)Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
329 +| |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)
330 +|Representation| |(% style="width:537px" %)The allowable value or format for Component or Concept
331 +| |+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).
332 +| |+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.
333 +|Facet| |(% style="width:537px" %)Defines the format for the content of the Component when reported in a data or metadata set.
334 +| |facetType|(% style="width:537px" %)A specific content type which is constrained by the FacetType enumeration
335 +| |facetValueType|(% style="width:537px" %)(((
395 395  The format of the value of a Component when reported in a data or metadata set.
396 396  
397 397  This is contrained by the FacetValueType enumeration.
398 398  )))
399 -||+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.
400 -|ExtendedFacet||This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute
340 +| |+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.
341 +|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
401 401  
402 -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)
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)
403 403  
404 404  ==== 3.6.3.3 Representation Constructs ====
405 405  
406 406  The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, 818 and have equivalents in most current implementation platforms:
407 407  
408 -:
409 -
410 410  (((
411 -|**SDMX Facet Value Type**|**XML Schema Data Type     **|**.NET Framework Type**|**Java Data Type**
412 -|String|xsd:string|System.String|java.lang.String
413 -|Big Integer|xsd:integer|System.Decimal|java.math.BigInteger
414 -|Integer|xsd:int|System.Int32|int
415 -|Long|xsd.long|System.Int64|long
416 -|Short|xsd:short|System.Int16|short
417 -|Decimal|xsd:decimal|System.Decimal|java.math.BigDecimal
418 -|Float|xsd:float|System.Single|float
419 -|Double|xsd:double|System.Double|double
420 -|Boolean|xsd:boolean|System.Boolean|boolean
421 -|URI|xsd:anyURI|System.Uri|Java.net.URI or java.lang.String
422 -|DateTime|xsd:dateTime|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
423 -|Time|xsd:time|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
424 -|GregorianYear|xsd:gYear|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
425 -|GregorianMonth|xsd:gYearMonth|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
426 -|GregorianDay|xsd:date|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
427 -|Day, MonthDay, Month|xsd:g*|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
428 -|Duration|xsd:duration|System.TimeSpan|javax.xml.datatype.Dura tion
350 +(% style="width:1034.29px" %)
351 +|(% 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**
352 +|(% style="width:222px" %)String|(% style="width:229px" %)xsd:string|(% style="width:216px" %)System.String|(% style="width:354px" %)java.lang.String
353 +|(% style="width:222px" %)Big Integer|(% style="width:229px" %)xsd:integer|(% style="width:216px" %)System.Decimal|(% style="width:354px" %)java.math.BigInteger
354 +|(% style="width:222px" %)Integer|(% style="width:229px" %)xsd:int|(% style="width:216px" %)System.Int32|(% style="width:354px" %)int
355 +|(% style="width:222px" %)Long|(% style="width:229px" %)xsd.long|(% style="width:216px" %)System.Int64|(% style="width:354px" %)long
356 +|(% style="width:222px" %)Short|(% style="width:229px" %)xsd:short|(% style="width:216px" %)System.Int16|(% style="width:354px" %)short
357 +|(% style="width:222px" %)Decimal|(% style="width:229px" %)xsd:decimal|(% style="width:216px" %)System.Decimal|(% style="width:354px" %)java.math.BigDecimal
358 +|(% style="width:222px" %)Float|(% style="width:229px" %)xsd:float|(% style="width:216px" %)System.Single|(% style="width:354px" %)float
359 +|(% style="width:222px" %)Double|(% style="width:229px" %)xsd:double|(% style="width:216px" %)System.Double|(% style="width:354px" %)double
360 +|(% style="width:222px" %)Boolean|(% style="width:229px" %)xsd:boolean|(% style="width:216px" %)System.Boolean|(% style="width:354px" %)boolean
361 +|(% style="width:222px" %)URI|(% style="width:229px" %)xsd:anyURI|(% style="width:216px" %)System.Uri|(% style="width:354px" %)Java.net.URI or java.lang.String
362 +|(% style="width:222px" %)DateTime|(% style="width:229px" %)xsd:dateTime|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
363 +|(% style="width:222px" %)Time|(% style="width:229px" %)xsd:time|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
364 +|(% style="width:222px" %)GregorianYear|(% style="width:229px" %)xsd:gYear|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
365 +|(% style="width:222px" %)GregorianMonth|(% style="width:229px" %)xsd:gYearMonth|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
366 +|(% style="width:222px" %)GregorianDay|(% style="width:229px" %)xsd:date|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
367 +|(% style="width:222px" %)Day, MonthDay, Month|(% style="width:229px" %)xsd:g*|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar
368 +|(% style="width:222px" %)Duration|(% style="width:229px" %)xsd:duration|(% style="width:216px" %)System.TimeSpan|(% style="width:354px" %)javax.xml.datatype.Dura tion
429 429  )))
430 430  
431 -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.
371 +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.
432 432  
433 -The ,,Representation,, is composed of ,,Facet,,s, each of which conveys characteristic 826 information related to the definition of a value domain. Often a set of Facets are needed to 827 convey the required semantic. For example, a sequence is defined by a minimum of two 828 Facets: one to define the start value, and one to define the interval.
373 +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.
434 434  
435 -:
436 -
437 437  (((
438 -|**Facet Type**|**Explanation**|
439 -|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 supplied. If an end value is not given, then the sequence continues indefinitely.|
440 -|interval|The interval attribute specifies the permitted interval (increment) in a|
441 -||(% colspan="2" %)sequence. In order for this to be used, the isSequence attribute must have a value of true.
442 -|startValue|(% colspan="2" %)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 is used for a numeric sequence, and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed.
443 -|endValue|(% colspan="2" %)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.
444 -|timeInterval|(% colspan="2" %)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.
445 -|startTime|(% colspan="2" %)The startTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). This attribute is used for a time sequence, and indicates the start time of the sequence. This value is mandatory for a time sequence to be expressed.
446 -|endTime|(% colspan="2" %)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) of the sequence.
447 -|minLength|(% colspan="2" %)The minLength facet specifies the minimum and length of the value in characters.
448 -|maxLength|(% colspan="2" %)The maxLength facet specifies the maximum length of the value in characters.
449 -|minValue|(% colspan="2" %)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.
450 -|maxValue|(% colspan="2" %)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.
451 -|decimals|(% colspan="2" %)The decimals facet indicates the number of characters allowed after the decimal separator.
452 -|pattern|(% colspan="2" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g. W3C XML Schema).
376 +(% style="width:1043.29px" %)
377 +|(% style="width:179px" %)**Facet Type**|(% style="width:862px" %)**Explanation**
378 +|(% style="width:179px" %)isSequence|(% style="width:862px" %)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 supplied. If an end value is not given, then the sequence continues indefinitely.
379 +|(% style="width:179px" %)interval|(% style="width:862px" %)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.
380 +|(% style="width:179px" %)startValue|(% colspan="1" style="width:862px" %)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 is used for a numeric sequence, and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed.
381 +|(% style="width:179px" %)endValue|(% colspan="1" style="width:862px" %)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.
382 +|(% style="width:179px" %)timeInterval|(% colspan="1" style="width:862px" %)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.
383 +|(% style="width:179px" %)startTime|(% colspan="1" style="width:862px" %)The startTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). This attribute is used for a time sequence, and indicates the start time of the sequence. This value is mandatory for a time sequence to be expressed.
384 +|(% style="width:179px" %)endTime|(% colspan="1" style="width:862px" %)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) of the sequence.
385 +|(% style="width:179px" %)minLength|(% colspan="1" style="width:862px" %)The minLength facet specifies the minimum and length of the value in characters.
386 +|(% style="width:179px" %)maxLength|(% colspan="1" style="width:862px" %)The maxLength facet specifies the maximum length of the value in characters.
387 +|(% style="width:179px" %)minValue|(% colspan="1" style="width:862px" %)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.
388 +|(% style="width:179px" %)maxValue|(% colspan="1" style="width:862px" %)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.
389 +|(% style="width:179px" %)decimals|(% colspan="1" style="width:862px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
390 +|(% style="width:179px" %)pattern|(% colspan="1" style="width:862px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g. W3C XML Schema).
453 453  )))
SDMX_2-1_SECTION_2_InformationModel_2020-07_84176ba5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +158.3 KB
Content
SDMX_2-1_SECTION_2_InformationModel_2020-07_a2879920.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +207.8 KB
Content