Skip to Content

Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19
From version 11.3
edited by Helena
on 2025/05/16 13:37
Change comment: There is no comment for this version
To version 5.1
edited by Helena
on 2025/05/15 09:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,4 @@
1 -{{box title="**Contents**"}}
2 -{{toc/}}
3 -{{/box}}
1 += 3 SDMX Base Package =
4 4  
5 5  == 3.1 Introduction ==
6 6  
... ... @@ -9,7 +9,9 @@
9 9  The motivation for establishing the SDMX Base package is as follows:
10 10  
11 11  it is accepted “Best Practise” to identify fundamental archetypes occurring in a model
10 +
12 12  identification of commonly found structures or “patterns” leads to easier understanding
12 +
13 13  identification of patterns encourages re-use
14 14  
15 15  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.
... ... @@ -28,8 +28,10 @@
28 28  
29 29  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.
30 30  
31 -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).
31 +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
32 32  
33 +InternationalString).
34 +
33 33  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.
34 34  
35 35  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.
... ... @@ -42,53 +42,52 @@
42 42  
43 43  ==== 3.2.2.2 Definitions ====
44 44  
45 -(% style="width:914.039px" %)
46 -|**Class**|(% style="width:244px" %)**Feature**|(% style="width:514px" %)**Description**
47 -|//AnnotableArtefact//|(% style="width:244px" %)(((
47 +|**Class**|**Feature**|**Description**
48 +|//AnnotableArtefact//|(((
48 48  Base inheritance sub classes are:
49 49  
50 50  //IdentifiableArtefact//
51 -)))|(% style="width:514px" %)Objects of classes derived from this can have attached annotations.
52 -|Annotation|(% style="width:244px" %) |(% style="width:514px" %)Additional descriptive information attached to an object.
53 -| |(% style="width:244px" %)id|(% style="width:514px" %)Identifier for the Annotation. It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
54 -| |(% style="width:244px" %)title|(% style="width:514px" %)A title used to identify an annotation.
55 -| |(% style="width:244px" %)type|(% style="width:514px" %)Specifies how the annotation is to be processed.
56 -| |(% style="width:244px" %)url|(% style="width:514px" %)A link to external descriptive text.
57 -| |(% style="width:244px" %)value|(% style="width:514px" %)A non-localised version of the Annotation content.
58 -| |(% style="width:244px" %)+url|(% style="width:514px" %)An International URI provides a set of links that are language specific, via this role.
59 -| |(% style="width:244px" %)+text|(% style="width:514px" %)An International String provides the multilingual text content of the annotation via this role.
60 -|InternationalUri|(% style="width:244px" %) |(% style="width:514px" %)The International Uri is a collection of Localised URIs and supports linking to external descriptions in multiple locales.
61 -|LocalisedUri|(% style="width:244px" %) |(% style="width:514px" %)The Localised URI supports the link to an external description in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
62 -|//IdentifiableArtefact//|(% style="width:244px" %)(((
52 +)))|Objects of classes derived from this can have attached annotations.
53 +|Annotation||Additional descriptive information attached to an object.
54 +||id|Identifier for the Annotation. It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
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 +||value|A non-localised version of the Annotation content.
59 +||+url|An International URI provides a set of links that are language specific, via this role.
60 +||+text|An International String provides the multilingual text content of the annotation via this role.
61 +|InternationalUri||The International Uri is a collection of Localised URIs and supports linking to external descriptions in multiple locales.
62 +|LocalisedUri||The Localised URI supports the link to an external description in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
63 +|//IdentifiableArtefact//|(((
63 63  Superclass is
64 64  
65 65  //AnnotableArtefact//
66 66  
67 -Base inheritance sub classes are:
68 +Base inheritance sub classes are~://    //
68 68  
69 69  //NameableArtefact//
70 -)))|(% style="width:514px" %)Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
71 -| |(% style="width:244px" %)id|(% style="width:514px" %)The unique identifier of the object.
72 -| |(% style="width:244px" %)uri|(% style="width:514px" %)Universal resource identifier that may or may not be resolvable.
73 -| |(% style="width:244px" %)urn|(% style="width:514px" %)Universal resource name – this is for use in registries: all registered objects have a urn.
74 -|//NameableArtefact//|(% style="width:244px" %)(((
71 +)))|Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
72 +||id|The unique identifier of the object.
73 +||uri|Universal resource identifier that may or may not be resolvable.
74 +||urn|Universal resource name – this is for use in registries: all registered objects have a urn.
75 +|//NameableArtefact//|(((
75 75  Superclass is
76 76  
77 77  //IdentifiableArtefact// Base inheritance sub classes are:
78 78  
79 79  //VersionableArtefact//
80 -)))|(% style="width:514px" %)Provides a Name and Description to all derived classes in addition to identification and annotations.
81 -| |(% style="width:244px" %)+description|(% style="width:514px" %)(((
81 +)))|Provides a Name and Description to all derived classes in addition to identification and annotations.
82 +||+description|(((
82 82  A multi-lingual description is provided by this role via the
83 83  
84 84  International String class.
85 85  )))
86 -| |(% style="width:244px" %)+name|(% style="width:514px" %)A multi-lingual name is provided by this role via the International String class
87 -|InternationalString|(% style="width:244px" %) |(% style="width:514px" %)The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
88 -|LocalisedString|(% style="width:244px" %) |(% style="width:514px" %)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.).
89 -| |(% style="width:244px" %)label|(% style="width:514px" %)Label of the string.
90 -| |(% style="width:244px" %)locale|(% style="width:514px" %)The geographic locale of the string e.g French, Canadian French.
91 -|//VersionableArtefact//|(% style="width:244px" %)(((
87 +||+name|A multi-lingual name is provided by this role via the International String class
88 +|InternationalString||The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
89 +|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.).
90 +||label|Label of the string.
91 +||locale|The geographic locale of the string e.g French, Canadian French.
92 +|//VersionableArtefact//|(((
92 92  Superclass is
93 93  
94 94  //NameableArtefact//
... ... @@ -96,20 +96,20 @@
96 96  Base inheritance sub classes are:
97 97  
98 98  //MaintainableArtefact//
99 -)))|(% style="width:514px" %)Provides versioning information for all derived objects.
100 -| |(% style="width:244px" %)version|(% style="width:514px" %)A version string following SDMX versioning rules.
101 -| |(% style="width:244px" %)validFrom|(% style="width:514px" %)Date from which the version is valid
102 -| |(% style="width:244px" %)validTo|(% style="width:514px" %)Date from which version is superseded
103 -|//MaintainableArtefact//|(% style="width:244px" %)(((
100 +)))|Provides versioning information for all derived objects.
101 +||version|A version string following SDMX versioning rules.
102 +||validFrom|Date from which the version is valid
103 +||validTo|Date from which version is superseded
104 +|//MaintainableArtefact//|(((
104 104  Inherits from
105 105  
106 106  //VersionableArtefact//
107 -)))|(% style="width:514px" %)An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
108 -| |(% style="width:244px" %)isExternalReference|(% style="width:514px" %)If set to “true” it indicates that the content of the object is held externally.
109 -| |(% style="width:244px" %)structureURL|(% style="width:514px" %)The URL of an SDMX-ML document containing the external object.
110 -| |(% style="width:244px" %)serviceURL|(% style="width:514px" %)The URL of an SDMX-compliant web service from which the external object can be retrieved.
111 -| |(% style="width:244px" %)+maintainer|(% style="width:514px" %)Association to the Maintenance Agency responsible for maintaining the artefact.
112 -|Agency|(% style="width:244px" %) |(% style="width:514px" %)See section on “Organisations”
108 +)))|An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
109 +||isExternalReference|If set to “true” it indicates that the content of the object is held externally.
110 +||structureURL|The URL of an SDMX-ML document containing the external object.
111 +||serviceURL|The URL of an SDMX-compliant web service from which the external object can be retrieved.
112 +||+maintainer//    //|Association to the Maintenance Agency responsible for maintaining the artefact.
113 +|Agency||See section on “Organisations”
113 113  
114 114  == 3.3 Basic Inheritance ==
115 115  
... ... @@ -178,7 +178,7 @@
178 178  
179 179  In an exchange environment an //ItemScheme// is allowed to contain a sub-set of the //Item//s in the maintained //ItemScheme//. If such an ItemScheme is disseminated with a sub-set of the //Item//s then the fact that this is a sub-set is denoted by setting the isPartial attribute to "true".
180 180  
181 -A “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, version). This is important as this is the id that that is referenced in other structures (e.g., a Codelist referenced in a DSD) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
182 +A[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_99fcc5a.gif||alt="Shape28" height="36" width="31"]] “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, version). This is important as this is the id that that is referenced in other structures (e.g., a Codelist referenced in a DSD) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
182 182  
183 183  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.
184 184  
... ... @@ -188,44 +188,65 @@
188 188  
189 189  ==== 3.5.3.2 Definitions ====
190 190  
191 -(% style="width:800.039px" %)
192 -|**Class**|(% style="width:272px" %)**Feature**|(% style="width:422px" %)**Description**
193 -|//ItemScheme//|(% style="width:272px" %)(((
192 +|**Class**|**Feature**|**Description**
193 +|//ItemScheme//|(((
194 194  Inherits from:
195 +
195 195  //MaintainableArtefact//
197 +
196 196  Direct sub classes are:
199 +
197 197  CategoryScheme
201 +
198 198  ConceptScheme
203 +
199 199  Codelist
205 +
200 200  ReportingTaxonomy
207 +
201 201  //OrganisationScheme//
209 +
202 202  TransformationScheme
203 -CustomTypeScheme
204 -NamePersonalisationSc heme
211 +
212 +CustomTypeScheme NamePersonalisationSc heme
213 +
205 205  RulesetScheme
215 +
206 206  VtlMappingScheme UserDefinedOperatorSc heme
207 -)))|(% style="width:422px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
208 -| |(% style="width:272px" %)isPartial|(% style="width:422px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
209 -| |(% style="width:272px" %)/items|(% style="width:422px" %)Association to the Items in the scheme.
210 -|//Item//|(% style="width:272px" %)(((
217 +)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
218 +||isPartial|Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
219 +||/items|Association to the Items in the scheme.
220 +|//Item//|(((
211 211  Inherits from:
212 212  
213 213  //NameableArtefact//
224 +
214 214  Direct sub classes are
226 +
215 215  Category
228 +
216 216  Concept
230 +
217 217  Code
232 +
218 218  ReportingCategory
234 +
219 219  //Organisation//
236 +
220 220  Transformation
238 +
221 221  CustomType
240 +
222 222  NamePersonalisation
242 +
223 223  Ruleset
244 +
224 224  VtlMapping
225 -UserDefinedOperator
226 -)))|(% style="width:422px" %)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 -| |(% style="width:272px" %)hierarchy|(% style="width:422px" %)This allows an Item optionally to have one or more child Items.
228 228  
247 +UserDefinedOperator//    //
248 +)))|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.
249 +||hierarchy|This allows an Item optionally to have one or more child Items.
250 +
229 229  == 3.6 The Structure Pattern ==
230 230  
231 231  === 3.6.1 Context ===
... ... @@ -253,9 +253,13 @@
253 253  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:
254 254  
255 255  DimensionDescriptor: Dimension, TimeDimension
278 +
256 256  GroupDimensionDescriptor: Dimension, TimeDimension
280 +
257 257  MeasureDescriptor: Measure
282 +
258 258  AttributeDescriptor: DataAttribute, MetadataAttributeRef
284 +
259 259  MetadataAttributeDescriptor: MetadataAttribute
260 260  
261 261  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.
... ... @@ -274,59 +274,72 @@
274 274  
275 275  ==== 3.6.3.2 Definitions ====
276 276  
277 -(% style="width:756.039px" %)
278 -|**Class**|(% style="width:284px" %)**Feature**|(% style="width:353px" %)**Description**
279 -|StructureUsage|(% style="width:284px" %)(((
303 +|**Class**|**Feature**|**Description**
304 +|StructureUsage|(((
280 280  Inherits from:
306 +
281 281  //MaintainableArtefact//
282 282  
283 283  Sub classes are:
310 +
284 284  Dataflow
312 +
285 285  Metadataflow
286 -)))|(% style="width:353px" %)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.
287 -| |(% style="width:284px" %)structure|(% style="width:353px" %)An association to a Structure specifying the structure of the artefact.
288 -|Structure|(% style="width:284px" %)(((
314 +)))|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.
315 +||structure|An association to a Structure specifying the structure of the artefact.
316 +|Structure|(((
289 289  Inherits from:
318 +
290 290  //MaintainableArtefact//
291 291  
292 292  Sub classes are:
322 +
293 293  DataStructureDefinition MetadataStructureDefinit ion
294 -)))|(% style="width:353px" %)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.
295 -| |(% style="width:284px" %)grouping|(% style="width:353px" %)A composite association to one or more component lists.
296 -|//ComponentList//|(% style="width:284px" %)(((
324 +)))|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.
325 +||grouping|A composite association to one or more component lists.
326 +|//ComponentList//|(((
297 297  Inherits from:
328 +
298 298  //IdentifiableArtefact//
299 299  
300 300  Sub classes are:
332 +
301 301  DimensionDescriptor
334 +
302 302  GroupDimensionDescriptor
336 +
303 303  MeasureDescriptor
338 +
304 304  AttributeDescriptor MetadataAttributeDescriptor
305 -)))|(% style="width:353px" %)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.
306 -| |(% style="width:284px" %)components|(% style="width:353px" %)An aggregate association to one or more components which make up the list.
307 -|//Component//|(% style="width:284px" %)(((
340 +)))|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.
341 +||components|An aggregate association to one or more components which make up the list.
342 +|//Component//|(((
308 308  Inherits from:
344 +
309 309  //IdentifiableArtefact//
310 310  
311 311  Sub classes are:
348 +
312 312  Measure
313 -//AttributeComponent
314 -DimensionComponent//
315 -)))|(% style="width:353px" %)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.
316 -| |(% style="width:284px" %)conceptIdentity|(% style="width:353px" %)(((
350 +
351 +//AttributeComponent//
352 +
353 +//DimensionComponent//
354 +)))|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.
355 +||conceptIdentity|(((
317 317  Association to a Concept in a Concept Scheme that identifies and defines the
318 318  
319 319  semantic of the Component.
320 320  )))
321 -| |(% style="width:284px" %)localRepresentation|(% style="width:353px" %)Association to the Representation of the Component if this is different from the coreRepresentation of the Concept, which the Component uses (ConceptUsage).
322 -|Representation|(% style="width:284px" %) |(% style="width:353px" %)The allowable value or format for Component or Concept
323 -| |(% style="width:284px" %)+enumerated|(% style="width:353px" %)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.
324 -| |(% style="width:284px" %)+nonEnumerated|(% style="width:353px" %)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.
325 -|Facet|(% style="width:284px" %) |(% style="width:353px" %)Defines the format for the content of the Component when reported in a data or metadata set.
326 -| |(% style="width:284px" %)facetType|(% style="width:353px" %)A specific content type, which is constrained by the Facet Type enumeration.
327 -| |(% style="width:284px" %)facetValueType|(% style="width:353px" %)The format of the value of a Component when reported in a data or metadata set. This is constrained by the Facet Value Type enumeration.
328 -| |(% style="width:284px" %) |(% style="width:353px" %)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.
329 -|ExtendedFacet|(% style="width:284px" %)+itemSchemeFacet|(% style="width:353px" %)This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute and a Data Attribute.
360 +||localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept, which the Component uses (ConceptUsage).
361 +|Representation||The allowable value or format for Component or Concept
362 +||+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.
363 +||+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.
364 +|Facet||Defines the format for the content of the Component when reported in a data or metadata set.
365 +||facetType|A specific content type, which is constrained by the Facet Type enumeration.
366 +||facetValueType|The format of the value of a Component when reported in a data or metadata set. This is constrained by the Facet Value Type enumeration.
367 +|||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.
368 +|ExtendedFacet|+itemSchemeFacet|This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute and a Data Attribute.
330 330  
331 331  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.
332 332  
... ... @@ -334,53 +334,51 @@
334 334  
335 335  The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
336 336  
337 -(% style="width:923.039px" %)
338 -|(% style="width:167px" %)**SDMX Facet Value Type**|(% style="width:148px" %)**XML Schema Data Type**|(% style="width:158px" %)**JSON Schema Data Type**|(% style="width:161px" %)**.NET Framework Type**|(% style="width:285px" %)**Java Data Type**
339 -|(% style="width:167px" %)String|(% style="width:148px" %)xsd:string|(% style="width:158px" %)string|(% style="width:161px" %)System.String|(% style="width:285px" %)java.lang.String
340 -|(% style="width:167px" %)Big Integer|(% style="width:148px" %)xsd:integer|(% style="width:158px" %)integer|(% style="width:161px" %)System.Decimal|(% style="width:285px" %)java.math.BigInteger
341 -|(% style="width:167px" %)Integer|(% style="width:148px" %)xsd:int|(% style="width:158px" %)integer|(% style="width:161px" %)System.Int32|(% style="width:285px" %)int
342 -|(% style="width:167px" %)Long|(% style="width:148px" %)xsd.long|(% style="width:158px" %)integer|(% style="width:161px" %)System.Int64|(% style="width:285px" %)long
343 -|(% style="width:167px" %)Short|(% style="width:148px" %)xsd:short|(% style="width:158px" %)integer|(% style="width:161px" %)System.Int16|(% style="width:285px" %)short
344 -|(% style="width:167px" %)Decimal|(% style="width:148px" %)xsd:decimal|(% style="width:158px" %)number|(% style="width:161px" %)System.Decimal|(% style="width:285px" %)java.math.BigDecimal
345 -|(% style="width:167px" %)Float|(% style="width:148px" %)xsd:float|(% style="width:158px" %)number|(% style="width:161px" %)System.Single|(% style="width:285px" %)float
346 -|(% style="width:167px" %)Double|(% style="width:148px" %)xsd:double|(% style="width:158px" %)number|(% style="width:161px" %)System.Double|(% style="width:285px" %)double
347 -|(% style="width:167px" %)Boolean|(% style="width:148px" %)xsd:boolean|(% style="width:158px" %)boolean|(% style="width:161px" %)System.Boolean|(% style="width:285px" %)boolean
348 -|(% style="width:167px" %)URI|(% style="width:148px" %)xsd:anyURI|(% style="width:158px" %)string:uri|(% style="width:161px" %)System.Uri|(% style="width:285px" %)Java.net.URI or java.lang.String
349 -|(% style="width:167px" %)DateTime|(% style="width:148px" %)xsd:dateTime|(% style="width:158px" %)string:datetime|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
350 -|(% style="width:167px" %)Time|(% style="width:148px" %)xsd:time|(% style="width:158px" %)string:time|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
351 -|(% style="width:167px" %)GregorianYear|(% style="width:148px" %)xsd:gYear|(% style="width:158px" %)(((
352 -string{{footnote}}In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.{{/footnote}}
353 -)))|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
354 -|(% style="width:167px" %)GregorianMonth|(% style="width:148px" %)xsd:gYearMonth|(% style="width:158px" %)string|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
355 -|(% style="width:167px" %)GregorianDay|(% style="width:148px" %)xsd:date|(% style="width:158px" %)string|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
356 -|(% style="width:167px" %)Day, MonthDay, Month|(% style="width:148px" %)xsd:g*|(% style="width:158px" %)string|(% style="width:161px" %)System.DateTime|(% style="width:285px" %)javax.xml.datatype.XML GregorianCalendar
357 -|(% style="width:167px" %)Duration|(% style="width:148px" %)xsd:duration|(% style="width:158px" %)string|(% style="width:161px" %)System.TimeSpan|(% style="width:285px" %)javax.xml.datatype.Dur ation
376 +|**SDMX Facet Value Type**|**XML Schema Data Type**|**JSON Schema Data Type**|**.NET Framework Type**|**Java Data Type**
377 +|String|xsd:string|string|System.String|java.lang.String
378 +|Big Integer|xsd:integer|integer|System.Decimal|java.math.BigInteger
379 +|Integer|xsd:int|integer|System.Int32|int
380 +|Long|xsd.long|integer|System.Int64|long
381 +|Short|xsd:short|integer|System.Int16|short
382 +|Decimal|xsd:decimal|number|System.Decimal|java.math.BigDecimal
383 +|Float|xsd:float|number|System.Single|float
384 +|Double|xsd:double|number|System.Double|double
385 +|Boolean|xsd:boolean|boolean|System.Boolean|boolean
386 +|URI|xsd:anyURI|string:uri|System.Uri|Java.net.URI or java.lang.String
387 +|DateTime|xsd:dateTime|string:datetime|System.DateTime|javax.xml.datatype.XML GregorianCalendar
388 +|Time|xsd:time|string:time|System.DateTime|javax.xml.datatype.XML GregorianCalendar
389 +|GregorianYear|xsd:gYear|(((
390 +2
358 358  
392 +string
393 +)))|System.DateTime|javax.xml.datatype.XML GregorianCalendar
394 +|GregorianMonth|xsd:gYearMonth|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
395 +|GregorianDay|xsd:date|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
396 +|Day, MonthDay, Month|xsd:g*|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
397 +|Duration|xsd:duration|string|System.TimeSpan|javax.xml.datatype.Dur ation
398 +
359 359  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.
360 360  
361 361  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.
362 362  
363 -(% style="width:921.039px" %)
364 -|**Facet Type**|(% style="width:827px" %)**Explanation**
365 -|isSequence|(% style="width:827px" %)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.
366 -|interval|(% style="width:827px" %)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.
367 -|startValue|(% style="width:827px" %)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
368 -|endValue|(% style="width:827px" %)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.
369 -|timeInterval|(% style="width:827px" %)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.
370 -|startTime|(% style="width:827px" %)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.
371 -|endTime|(% style="width:827px" %)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.
372 -|minLength|(% style="width:827px" %)The minLength facet specifies the minimum and length of the value in characters.
373 -|maxLength|(% style="width:827px" %)The maxLength facet specifies the maximum length of the value in characters.
374 -|minValue|(% style="width:827px" %)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.
375 -|minLength|(% style="width:827px" %)The minLength facet specifies the minimum and length of the value in characters.
376 -|maxLength|(% style="width:827px" %)The maxLength facet specifies the maximum length of the value in characters.
377 -|minValue|(% style="width:827px" %)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.
378 -|maxValue|(% style="width:827px" %)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.
379 -|decimals|(% style="width:827px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
380 -|pattern|(% style="width:827px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
403 +|**Facet Type**||**Explanation**
404 +|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.
405 +|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.
406 +|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 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
407 +|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.
408 +|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.
409 +|startTime||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.
410 +|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) of the sequence.
411 +|minLength||The minLength facet specifies the minimum and length of the value in characters.
412 +|maxLength||The maxLength facet specifies the maximum length of the value in characters.
413 +|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.
414 +|minLength||The minLength facet specifies the minimum and length of the value in characters.
415 +|maxLength||The maxLength facet specifies the maximum length of the value in characters.
416 +|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.
417 +|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.
418 +|decimals||The decimals facet indicates the number of characters allowed after the decimal separator.
419 +|pattern||The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
381 381  
382 382  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_59eee18f.gif||alt="Shape29" height="1" width="192"]]
383 383  
384 384  ^^2^^ In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.
385 -
386 -{{putFootnotes/}}
SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_1513ed19.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -243.7 KB
Content
SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_59eee18f.gif
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -851 bytes
Content
SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_828a9828.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -217.9 KB
Content
SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_b6346072.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -332.9 KB
Content
SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_ec1b8edc.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -159.6 KB
Content