Changes for page 3 SDMX Base Package

Last modified by Helena on 2025/09/10 11:19

From version 8.1
edited by Helena
on 2025/05/20 00:30
Change comment: There is no comment for this version
To version 6.2
edited by Helena
on 2025/05/20 00:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,8 +26,10 @@
26 26  
27 27  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.
28 28  
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).
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
30 30  
31 +InternationalString).
32 +
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,62 +38,70 @@
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 ====
43 +**3.2.2.2 Definitions**
42 42  
43 -(% style="width:902.294px" %)
44 -|**Class**|(% style="width:246px" %)**Feature**|(% style="width:480px" %)**Description**
45 -|//AnnotableArtefact//|(% style="width:246px" %)(((
45 +|**Class**|**Feature**|**Description**
46 +|//AnnotableArtefact//|(((
46 46  Base inheritance sub classes are:
48 +
47 47  //IdentifiableArtefact//
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" %)(((
50 +)))|Objects of classes derived from this can have attached annotations.
51 +|Annotation| |Additional descriptive information attached to an object.
52 +| |id|(((
51 51  Identifier for the Annotation.
54 +
52 52  It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
53 53  )))
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" %)(((
57 +| |title//    //|A title used to identify an annotation.
58 +| |type|Specifies how the annotation is to be processed.
59 +| |url|A link to external descriptive text.
60 +| |+text|An International String provides the multilingual text content of the annotation via this role.
61 +|//IdentifiableArtefact//|(((
59 59  Superclass is
63 +
60 60  //AnnotableArtefact//
61 -Base inheritance sub classes are:
65 +
66 +Base inheritance sub classes are~://    //
67 +
62 62  //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" %)(((
69 +)))|Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
70 +| |id|The unique identifier of the object.
71 +| |uri|Universal resource identifier that may or may not be resolvable.
72 +| |urn|Universal resource name – this is for use in registries: all registered objects have a urn.
73 +|//NameableArtefact//|(((
68 68  Superclass is
75 +
69 69  //IdentifiableArtefact// Base inheritance sub classes are:
77 +
70 70  //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" %)(((
79 +)))|Provides a Name and Description to all derived classes in addition to identification and annotations.
80 +| |+description|A multi-lingual description is provided by this role via the International String class.
81 +| |+name|A multi-lingual name is provided by this role via the International String class
82 +|InternationalString| |The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
83 +|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.).
84 +| |label|Label of the string.
85 +| |locale|The geographic locale of the string e.g French, Canadian French.
86 +|//VersionableArtefact//|(((
79 79  Superclass is
88 +
80 80  //NameableArtefact// Base inheritance sub classes are:
90 +
81 81  //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" %)(((
92 +)))|Provides versioning information for all derived objects.
93 +| |version|A version string following an agreed convention
94 +| |validFrom|Date from which the version is valid
95 +| |validTo|Date from which version is superceded
96 +|//MaintainableArtefact//|(((
87 87  Inherits from
88 88  
89 89  //VersionableArtefact//
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”
100 +)))|An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
101 +| |final|Defines whether a maintained artefact is draft or final.
102 +| |isExternalReference|If set to “true” it indicates that the content of the object is held externally.
103 +| |structureURL|The URL of an SDMX-ML document containing the external object.
104 +| |serviceURL|The URL of an SDMX-compliant web service from which the external object can be retrieved.
105 +| |+maintainer//    //|Association to the Maintenance Agency responsible for maintaining the artefact.
106 +|Agency| |See section on “Organisations”
97 97  
98 98  == {{id name="_Toc370972"/}}3.3 Basic Inheritance ==
99 99  
... ... @@ -159,12 +159,11 @@
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**
172 +====== Figure 12 The Item Scheme Pattern ======
164 164  
165 165  ===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
166 166  
167 -==== 3.5.3.1 Narrative ====
176 +**3.5.3.1 Narrative**
168 168  
169 169  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//.
170 170  
... ... @@ -178,53 +178,81 @@
178 178  
179 179  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.
180 180  
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//).
190 +//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
182 182  
192 +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//).
193 +
183 183  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//.
184 184  
185 185  ==== 3.5.3.2 Definitions ====
186 186  
187 -(% style="width:911.294px" %)
188 -|**Class**|(% style="width:246px" %)**Feature**|(% style="width:478px" %)**Description**
189 -|//ItemScheme//|(% style="width:246px" %)(((
198 +|**Class**|**Feature**|**Description**
199 +|//ItemScheme//|(((
190 190  Inherits from:
201 +
191 191  //MaintainableArtefact//
203 +
192 192  Direct sub classes are:
205 +
193 193  CategoryScheme
207 +
194 194  ConceptScheme
209 +
195 195  Codelist
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 +)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
212 +| |(((
198 198  ReportingTaxonomy
214 +
199 199  //OrganisationScheme//
216 +
200 200  Transformation Scheme
218 +
201 201  CustomTypeScheme
220 +
202 202  NamePersonasationScheme
222 +
203 203  RuletScheme
224 +
204 204  VtlMappingScheme
226 +
205 205  UserDefinedOperatorScheme
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" %)(((
228 +)))|
229 +| |isPartial|Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme.
230 +| |items|Association to the Items in the scheme.
231 +|//Item//|(((
210 210  Inherits from:
233 +
211 211  //NameableArtefact//
212 -Direct sub classes are Category
235 +
236 +Direct sub classes are
237 +
238 +Category
239 +
213 213  Concept
241 +
214 214  Code
243 +
215 215  ReportingCategory
245 +
216 216  //Organisation//
247 +
217 217  Transformation
249 +
218 218  CustomType
251 +
219 219  NamePersonlisation
253 +
220 220  Ruleset
255 +
221 221  VtlMapping
222 -UserDefinedOperator
223 -)))|(% style="width:478px" %)(((
257 +
258 +UserDefinedOperator//    //
259 +)))|(((
224 224  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.
261 +
225 225  Note that at the conceptual level the Organisation is not hierarchic
226 226  )))
227 -| |(% style="width:246px" %)hierarchy|(% style="width:478px" %)This allows an Item optionally to have one or more child Items.
264 +| |hierarchy|This allows an Item optionally to have one or more child Items.
228 228  
229 229  == {{id name="_Toc370982"/}}3.6 The Structure Pattern ==
230 230  
... ... @@ -240,8 +240,7 @@
240 240  
241 241  [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_b6478a73.png||height="774" width="556"]]
242 242  
243 -(% class="wikigeneratedid" id="HFigure14:RepresentationwithintheStructurePattern" %)
244 -**Figure 14: Representation within the Structure Pattern**
280 +====== Figure 14: Representation within the Structure Pattern ======
245 245  
246 246  === {{id name="_Toc370985"/}}3.6.3 Explanation of the Diagrams ===
247 247  
... ... @@ -265,7 +265,7 @@
265 265  
266 266  __ReportStructure__: MetadataAttribute
267 267  
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.
304 +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.
269 269  
270 270  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.
271 271  
... ... @@ -280,112 +280,140 @@
280 280  
281 281  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).
282 282  
283 -==== 3.6.3.2 Definitions ====
319 +**3.6.3.2 Definitions**
284 284  
285 -(% style="width:1001.29px" %)
286 -|**Class**|**Feature**|(% style="width:537px" %)**Description**
321 +|**Class**|**Feature**|**Description**
287 287  |//StructureUsage//|(((
288 288  Inherits from:
324 +
289 289  //MaintainableArtefact//
326 +
290 290  Sub classes are:
328 +
291 291  DataflowDefinition
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.
330 +
331 +MetadataflowDefinition//    //
332 +)))|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.
333 +| |structure|An association to a Structure specifying the structure of the artefact.
295 295  |//Structure//|(((
296 296  Inherits from:
336 +
297 297  //MaintainableArtefact//
338 +
298 298  Sub classes are:
340 +
299 299  DataStructure
342 +
300 300  Definition
344 +
301 301  MetadataStructure
346 +
302 302  Definition
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 +)))|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.
349 +| |grouping|A composite association to one or more component lists.
305 305  |//ComponentList//|(((
306 306  Inherits from:
352 +
307 307  //IdentifiableArtefact//
354 +
308 308  Sub classes are:
356 +
309 309  DimensionDescriptor
358 +
310 310  GroupDimension
360 +
311 311  Descriptor
362 +
312 312  MeasureDescriptor
364 +
313 313  AttributeDescriptor
366 +
314 314  MetadataTarget
368 +
315 315  ReportStructure
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 +)))|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.
371 +| |components|An aggregate association to one or more components which make up the list.
318 318  |//Component//|(((
319 319  Inherits from:
374 +
320 320  //IdentifiableArtefact//
376 +
321 321  Sub classes are:
378 +
322 322  PrimaryMeasure
380 +
323 323  DataAttribute
324 -//DimensionComponent
325 -TargetObject//
382 +
383 +//DimensionComponent//
384 +
385 +//TargetObject//
386 +
326 326  MetadataAttribute
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" %)(((
388 +)))|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.
389 +| |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
390 +| |localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage)
391 +|Representation| |The allowable value or format for Component or Concept
392 +| |+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).
393 +| |+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.
394 +|Facet| |Defines the format for the content of the Component when reported in a data or metadata set.
395 +| |facetType|A specific content type which is constrained by the FacetType enumeration
396 +| |facetValueType|(((
336 336  The format of the value of a Component when reported in a data or metadata set.
337 337  
338 338  This is contrained by the FacetValueType enumeration.
339 339  )))
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 +| |+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.
402 +|ExtendedFacet| |This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute
342 342  
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)
404 +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)
344 344  
345 345  ==== 3.6.3.3 Representation Constructs ====
346 346  
347 347  The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, 818 and have equivalents in most current implementation platforms:
348 348  
410 +:
411 +
349 349  (((
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
413 +|**SDMX Facet Value Type**|**XML Schema Data Type     **|**.NET Framework Type**|**Java Data Type**
414 +|String|xsd:string|System.String|java.lang.String
415 +|Big Integer|xsd:integer|System.Decimal|java.math.BigInteger
416 +|Integer|xsd:int|System.Int32|int
417 +|Long|xsd.long|System.Int64|long
418 +|Short|xsd:short|System.Int16|short
419 +|Decimal|xsd:decimal|System.Decimal|java.math.BigDecimal
420 +|Float|xsd:float|System.Single|float
421 +|Double|xsd:double|System.Double|double
422 +|Boolean|xsd:boolean|System.Boolean|boolean
423 +|URI|xsd:anyURI|System.Uri|Java.net.URI or java.lang.String
424 +|DateTime|xsd:dateTime|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
425 +|Time|xsd:time|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
426 +|GregorianYear|xsd:gYear|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
427 +|GregorianMonth|xsd:gYearMonth|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
428 +|GregorianDay|xsd:date|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
429 +|Day, MonthDay, Month|xsd:g*|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
430 +|Duration|xsd:duration|System.TimeSpan|javax.xml.datatype.Dura tion
369 369  )))
370 370  
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.
433 +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.
372 372  
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.
435 +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.
374 374  
437 +:
438 +
375 375  (((
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).
440 +|**Facet Type**|**Explanation**|
441 +|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.|
442 +|interval|The interval attribute specifies the permitted interval (increment) in a|
443 +| |(% colspan="2" %)sequence. In order for this to be used, the isSequence attribute must have a value of true.
444 +|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.
445 +|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.
446 +|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.
447 +|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.
448 +|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.
449 +|minLength|(% colspan="2" %)The minLength facet specifies the minimum and length of the value in characters.
450 +|maxLength|(% colspan="2" %)The maxLength facet specifies the maximum length of the value in characters.
451 +|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.
452 +|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.
453 +|decimals|(% colspan="2" %)The decimals facet indicates the number of characters allowed after the decimal separator.
454 +|pattern|(% colspan="2" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g. W3C XML Schema).
391 391  )))