Skip to Content

Wiki source code of 3 SDMX Base Package

Version 2.2 by Helena on 2025/05/19 23:53
Show last authors
1 = {{id name="_Toc370967"/}}3 SDMX Base Package =
2
3 == {{id name="_Toc370968"/}}3.1 Introduction ==
4
5 The constructs in the SDMX Base package comprise the fundamental building blocks that support many of the other structures in the model. For this reason, many of the classes in this package are abstract (i.e. only derived sub-classes can exist in an implementation).
6
7 The motivation for establishing the SDMX Base package is as follows:
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//  //
12
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
15 == {{id name="_Toc370969"/}}3.2 Base Structures - Identification, Versioning, and Maintenance ==
16
17 === {{id name="_Toc370970"/}}3.2.1 Class Diagram ===
18
19 **Figure 9: SDMX Identification, Maintenance and Versioning**
20
21 === {{id name="_Toc370971"/}}3.2.2 Explanation of the Diagram ===
22
23 ==== 3.2.2.1 Narrative ====
24
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
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
28
29 InternationalString).
30
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
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.
34
35 //VersionableArtefact// is an abstract class which inherits from //NameableArtefact// and adds versioning ability to all classes derived from it.
36
37 //MaintainableArtefact// further adds the ability for derived classes to be maintained via its association to //Agency, //and adds locational information (i.e. from where the object can be retrieved). It is possible to define whether the artefact is draft or final with the final attribute.
38
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
41 **3.2.2.2 Definitions**
42
43 |**Class**|**Feature**|**Description**
44 |//AnnotableArtefact//|(((
45 Base inheritance sub classes are:
46
47 //IdentifiableArtefact//
48 )))|Objects of classes derived from this can have attached annotations.
49 |Annotation||Additional descriptive information attached to an object.
50 ||id|(((
51 Identifier for the Annotation.
52
53 It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
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//|(((
60 Superclass is
61
62 //AnnotableArtefact//
63
64 Base inheritance sub classes are~://    //
65
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//|(((
72 Superclass is
73
74 //IdentifiableArtefact// Base inheritance sub classes are:
75
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//|(((
85 Superclass is
86
87 //NameableArtefact// Base inheritance sub classes are:
88
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//|(((
95 Inherits from
96
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”
105
106 == {{id name="_Toc370972"/}}3.3 Basic Inheritance ==
107
108 === {{id name="_Toc370973"/}}3.3.1 Class Diagram– Basic Inheritance from the Base Inheritance Classes ===
109
110 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_84176ba5.png||height="709" width="514"]]
111
112 **Figure 10: Basic Inheritance from the Base Structures**
113
114 === {{id name="_Toc370974"/}}3.3.2 Explanation of the Diagram ===
115
116 ==== 3.3.2.1 Narrative ====
117
118 The diagram above shows the inheritance within the base structures. The concrete classes 642 are introduced and defined in the specific package to which they relate.
119
120 == {{id name="_Toc370975"/}}3.4 Data Types ==
121
122 === {{id name="_Toc370976"/}}3.4.1 Class Diagram ===
123
124 **Figure 11: Class Diagram of Basic Data Types**
125
126 === {{id name="_Toc370977"/}}3.4.2 Explanation of the Diagram ===
127
128 ==== 3.4.2.1 Narrative ====
129
130 The UsageStatus enumeration is used as a data type on a DataAttribute where the value of the attribute in an instance of the class must take one of the values in the UsageStatus (i.e. mandatory, conditional).
131
132 The FacetType and FacetValueType enumerations are used to specify the valid format of the content of a non enumerated Concept or the usage of a Concept when specified for use on a //Component// on a //Structure// (such as a Dimension in a DataStructureDefinition). The description of the various types can be found in the section on //ConceptScheme// (section 4.4).
133
134 The ActionType enumeration is used to specify the action that a receiving system should take when processing the content that is the object of the action. It is enumerated as follows:
135
136 * Append
137
138 Data or metadata is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards
139
140 * Replace
141
142 Data/metadata is to be replaced, and may also include additional data/metadata to be appended.
143
144 * Delete
145
146 Data/Metadata is to be deleted.
147
148 * Information
149
150 Data and metadata are for information purposes.
151
152 The IdentifiableObjectType enumeration is used to specify an object type whose class is a sub class of IdentifiableArtefact either directly of via NameableArtefact, VersionableArtefact or MaintainableArtefact.
153
154 The ToValueType,, ,,data type contains the attributes to support transformations defined in the StructureMap (see Section 9).
155
156 The ConstraintRoleType,, ,,data type contains the attributes that identify the purpose of a Constraint (allowableContent, actualContent).
157
158 == {{id name="_Toc370978"/}}3.5 The Item Scheme Pattern ==
159
160 === {{id name="_Toc370979"/}}3.5.1 Context ===
161
162 The Item Scheme is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
163
164 The ItemScheme is the basis for CategoryScheme, Codelist, ConceptScheme, ReportingTaxonomy, and //OrganisationScheme//.
165
166 === {{id name="_Toc370980"/}}3.5.2 Class Diagram ===
167
168 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_a2879920.jpg||height="602" width="614"]]
169
170 ====== Figure 12 The Item Scheme Pattern ======
171
172 ===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram =====
173
174 **3.5.3.1 Narrative**
175
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
178 In an exchange environment an ItemScheme is allowed to contain a sub-set of the Items in the maintained //ItemScheme//. If such an //ItemScheme// is disseminated with a sub-set of the Items then the fact that this is a sub-set is denoted by setting the isPartial attribute to
179
180 “true”.
181
182 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//.
183
184 Furthermore, the Id of the //ItemScheme// where isPartial is set to “true” is the same as the Id of the full //ItemScheme// (maintenance agency, 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//.
185
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
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
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 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
194 ==== 3.5.3.2 Definitions ====
195
196 |**Class**|**Feature**|**Description**
197 |//ItemScheme//|(((
198 Inherits from:
199
200 //MaintainableArtefact//
201
202 Direct sub classes are:
203
204 CategoryScheme
205
206 ConceptScheme
207
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 ||(((
211 ReportingTaxonomy
212
213 //OrganisationScheme//
214
215 Transformation Scheme
216
217 CustomTypeScheme
218
219 NamePersonasationScheme
220
221 RuletScheme
222
223 VtlMappingScheme
224
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//|(((
230 Inherits from:
231
232 //NameableArtefact//
233
234 Direct sub classes are
235
236 Category
237
238 Concept
239
240 Code
241
242 ReportingCategory
243
244 //Organisation//
245
246 Transformation
247
248 CustomType
249
250 NamePersonlisation
251
252 Ruleset
253
254 VtlMapping
255
256 UserDefinedOperator//    //
257 )))|(((
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 Note that at the conceptual level the Organisation is not hierarchic
261 )))
262 ||hierarchy|This allows an Item optionally to have one or more child Items.
263
264 == {{id name="_Toc370982"/}}3.6 The Structure Pattern ==
265
266 === {{id name="_Toc370983"/}}3.6.1 Context ===
267
268 The Structure Pattern is a basic architectural pattern which allows the specification of complex tabular structures which are often found in statistical data (such as Data Structure Definition, and Metadata Structure Definition). A Structure is a set of ordered lists. A pattern to underpin this tabular structure has been developed, so that commonalities between these structure definitions can be supported by common software and common syntax structures.
269
270 === {{id name="_Toc370984"/}}3.6.2 Class Diagrams ===
271
272 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_1645dbd1.png||height="441" width="578"]]
273
274 **Figure 13: The Structure Pattern**
275
276 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_b6478a73.png||height="774" width="556"]]
277
278 ====== Figure 14: Representation within the Structure Pattern ======
279
280 === {{id name="_Toc370985"/}}3.6.3 Explanation of the Diagrams ===
281
282 ==== 3.6.3.1 Narrative ====
283
284 The //Structure// is an abstract class which contains a set of one or more //ComponentList//(s) (this class is also abstract). An example of a concrete //Structure// is DataStructureDefinition.
285
286 The //ComponentList// is a list of one or more //Component//(s//)//. The //ComponentList// has several concrete descriptor classes based on it: DimensionDescriptor, GroupDimensionDescriptor, MeasureDescriptor, and AttributeDescriptor of the DataStructureDefinition and MetadataTarget, and ReportStructure of the MetaDataStructureDefinition.
287
288 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:
289
290 __DimensionDescripto__r: Dimension, Measure Dimension, Time Dimension
291
292 __GroupDimensionDescriptor__: Dimension, Measure Dimension, Time Dimension
293
294 MeasureDescriptor: PrimaryMeasure
295
296 __AttributeDescriptor:__ Data Attribute
297
298 __MetadataTarget__: //TargetObject //and its sub classes
299
300 __ReportStructure__: MetadataAttribute
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.
303
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
306 The Representation can be enumerated or non-enumerated. The valid content of an enumerated representation is specified either in an //ItemScheme// which can be one of ConceptScheme, Codelist, //OrganisationScheme//, CategoryScheme, and ReportingTaxonomy. The valid content of a non-enumerated representation is specified as one or more Facet (for example these may specify minimum and maximum values). For a MetadataAttribute this is achieved by one of more Extended Facet which allows the additional representation of XHTML.
307
308 The types of representation that are valid for specific components is expressed in the model as a constraint on the association viz:
309
310 * The MeasureDimension must be enumerated and use a ConceptScheme The Dimension (but not MeasureDimension), DataAttribute, PrimaryMeasure, MetadataAttribute may be enumerated and, if so, use a Codelist
311 * The //TargetObject// may be enumerated and, if so, can use any ItemScheme (Codelist, ConceptScheme, //OrganisationScheme//, CategoryScheme, ReportingTaxonomy)
312 * The Dimension (but ot MeasureDimension), Data Attribute, PrimaryMeasure, //TargetObject// may be non-enumerated and, if so, use one of more Facet, note that the FacetValueType applicable to the TimeDimension is restricted to those that represent time
313 * The MetadataAttribute may be non-enumerated and, if so, uses one or more ExtendedFacet
314
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
317 **3.6.3.2 Definitions**
318
319 |**Class**|**Feature**|**Description**
320 |//StructureUsage//|(((
321 Inherits from:
322
323 //MaintainableArtefact//
324
325 Sub classes are:
326
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.
332 |//Structure//|(((
333 Inherits from:
334
335 //MaintainableArtefact//
336
337 Sub classes are:
338
339 DataStructure
340
341 Definition
342
343 MetadataStructure
344
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.
348 |//ComponentList//|(((
349 Inherits from:
350
351 //IdentifiableArtefact//
352
353 Sub classes are:
354
355 DimensionDescriptor
356
357 GroupDimension
358
359 Descriptor
360
361 MeasureDescriptor
362
363 AttributeDescriptor
364
365 MetadataTarget
366
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.
370 |//Component//|(((
371 Inherits from:
372
373 //IdentifiableArtefact//
374
375 Sub classes are:
376
377 PrimaryMeasure
378
379 DataAttribute
380
381 //DimensionComponent//
382
383 //TargetObject//
384
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|(((
395 The format of the value of a Component when reported in a data or metadata set.
396
397 This is contrained by the FacetValueType enumeration.
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
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)
403
404 ==== 3.6.3.3 Representation Constructs ====
405
406 The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, 818 and have equivalents in most current implementation platforms:
407
408 :
409
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
429 )))
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.
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.
434
435 :
436
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).
453 )))