Wiki source code of 3 SDMX Base Package

Version 3.1 by Helena on 2025/06/08 00:55

version	line-number	content
2.2	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
	4
1.1	5	== 3.1 Introduction ==
	6
	7	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).
	8
	9	The motivation for establishing the SDMX Base package is as follows:
	10
	11	it is accepted “Best Practise” to identify fundamental archetypes occurring in a model// //identification of commonly found structures or “patterns” leads to easier understanding// //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
2.3	15	== 3.2 Base Structures - Identification, Versioning, and Maintenance ==
1.1	16
2.3	17	=== 3.2.1 Class Diagram ===
1.1	18
	19	[[image:1749246130522-547.jpeg]]
	20
	21	Figure 10: SDMX Identification, Maintenance and Versioning
	22
2.3	23	=== 3.2.2 Explanation of the Diagram ===
1.1	24
2.3	25	==== 3.2.2.1 Narrative ====
1.1	26
	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
	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).
	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, as explained in the SDMX versioning rules in SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
	36
	37	//MaintainableArtefact// further adds the ability for derived classes to be maintained via its association to an //Organisation//, and adds locational information (i.e., from where the object can be retrieved).
	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
2.3	41	==== 3.2.2.2 Definitions ====
1.1	42
2.3	43	(% style="width:973.835px" %)
	44	\|Class\|(% style="width:262px" %)Feature\|(% style="width:543px" %)Description
	45	\|//AnnotableArtefact//\|(% style="width:262px" %)(((
1.1	46	Base inheritance sub classes are:
	47	//IdentifiableArtefact//
2.3	48	)))\|(% style="width:543px" %)Objects of classes derived from this can have attached annotations.
	49	\|Annotation\|(% style="width:262px" %)// //\|(% style="width:543px" %)Additional descriptive information attached to an object.
	50	\| \|(% style="width:262px" %)id\|(% style="width:543px" %)Identifier for the Annotation. It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
	51	\| \|(% style="width:262px" %)title\|(% style="width:543px" %)A title used to identify an annotation.
	52	\| \|(% style="width:262px" %)type\|(% style="width:543px" %)Specifies how the annotation is to be processed.
	53	\| \|(% style="width:262px" %)url\|(% style="width:543px" %)A link to external descriptive text.
	54	\| \|(% style="width:262px" %)value\|(% style="width:543px" %)A non-localised version of the Annotation content.
	55	\| \|(% style="width:262px" %)+url\|(% style="width:543px" %)An International URI provides a set of links that are language specific, via this role.
	56	\| \|(% style="width:262px" %)+text\|(% style="width:543px" %)An International String provides the multilingual text content of the annotation via this role.
	57	\|InternationalUri\|(% style="width:262px" %) \|(% style="width:543px" %)The International Uri is a collection of Localised URIs and supports linking to external descriptions in multiple locales.
	58	\|LocalisedUri\|(% style="width:262px" %) \|(% style="width:543px" %)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.).
	59	\|//IdentifiableArtefact//\|(% style="width:262px" %)(((
	60	Superclass is //AnnotableArtefact//
1.1	61	Base inheritance sub classes are:
	62	//NameableArtefact//
2.3	63	)))\|(% style="width:543px" %)Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
	64	\| \|(% style="width:262px" %)id\|(% style="width:543px" %)The unique identifier of the object.
	65	\| \|(% style="width:262px" %)uri\|(% style="width:543px" %)Universal resource identifier that may or may not be resolvable.
	66	\| \|(% style="width:262px" %)urn\|(% style="width:543px" %)Universal resource name – this is for use in registries: all registered objects have a urn.
	67	\|//NameableArtefact//\|(% style="width:262px" %)(((
	68	Superclass is //IdentifiableArtefact// Base inheritance sub classes are:
1.1	69	//VersionableArtefact//
2.3	70	)))\|(% style="width:543px" %)Provides a Name and Description to all derived classes in addition to identification and annotations.
	71	\| \|(% style="width:262px" %)+description\|(% style="width:543px" %)A multi-lingual description is provided by this role via the International String class.
	72	\| \|(% style="width:262px" %)+name\|(% style="width:543px" %)A multi-lingual name is provided by this role via the International String class
	73	\|InternationalString\|(% style="width:262px" %) \|(% style="width:543px" %)The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
	74	\|LocalisedString\|(% style="width:262px" %) \|(% style="width:543px" %)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.).
	75	\| \|(% style="width:262px" %)label\|(% style="width:543px" %)Label of the string.
	76	\| \|(% style="width:262px" %)locale\|(% style="width:543px" %)The geographic locale of the string e.g French, Canadian French.
	77	\|//VersionableArtefact//\|(% style="width:262px" %)(((
1.1	78	Superclass is
	79	//NameableArtefact//
	80	Base inheritance sub classes are:
	81	//MaintainableArtefact//
2.3	82	)))\|(% style="width:543px" %)Provides versioning information for all derived objects.
	83	\| \|(% style="width:262px" %)version\|(% style="width:543px" %)A version string following SDMX versioning rules.
	84	\| \|(% style="width:262px" %)validFrom\|(% style="width:543px" %)Date from which the version is valid
	85	\| \|(% style="width:262px" %)validTo\|(% style="width:543px" %)Date from which version is superseded
	86	\|//MaintainableArtefact//\|(% style="width:262px" %)(((
1.1	87	Inherits from
	88
	89	//VersionableArtefact//
2.3	90	)))\|(% style="width:543px" %)An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
	91	\| \|(% style="width:262px" %)isExternalReference\|(% style="width:543px" %)If set to “true” it indicates that the content of the object is held externally.
	92	\| \|(% style="width:262px" %)structureURL\|(% style="width:543px" %)The URL of an SDMX-ML document containing the external object.
	93	\| \|(% style="width:262px" %)serviceURL\|(% style="width:543px" %)The URL of an SDMX-compliant web service from which the external object can be retrieved.
	94	\| \|(% style="width:262px" %)+maintainer\|(% style="width:543px" %)Association to the Maintenance Agency responsible for maintaining the artefact.
	95	\|Agency\|(% style="width:262px" %) \|(% style="width:543px" %)See section on “Organisations”
1.1	96
2.3	97	== 3.3 Basic Inheritance ==
1.1	98
2.3	99	=== 3.3.1 Class Diagram – Basic Inheritance from the Base Inheritance Classes ===
1.1	100
	101	[[image:1749246130530-261.jpeg]]
	102
	103	Figure 11: Basic Inheritance from the Base Structures
	104
2.3	105	=== 3.3.2 Explanation of the Diagram ===
1.1	106
2.3	107	==== 3.3.2.1 Narrative ====
1.1	108
	109	The diagram above shows the inheritance within the base structures. The concrete classes are introduced and defined in the specific package to which they relate.
	110
2.3	111	== 3.4 Data Types ==
1.1	112
2.3	113	=== 3.4.1 Class Diagram ===
1.1	114
	115	[[image:1749246130536-128.jpeg]]
	116
	117	Figure 12: Class Diagram of Basic Data Types
	118
2.4	119	=== 3.4.2 Explanation of the Diagram ===
1.1	120
2.4	121	==== 3.4.2.1 Narrative ====
1.1	122
	123	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 chapter on ConceptScheme (section 4.5).
	124
	125	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:
	126
	127	* Append: 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.
	128	* Replace: Data/metadata is to be replaced and may also include additional data/metadata to be appended.
	129	* Delete: Data/Metadata is to be deleted.
	130	* Information: Data and metadata are for information purposes.
	131
	132	The ToValueType data type contains the attributes to support transformations defined in the StructureMap (see Section 0).
	133
	134	The ConstraintRoleType data type contains the attributes that identify the purpose of a Constraint (allowableContent, actualContent).
	135
	136	The ComponentRoleType data type contains the predefined Concept roles that can be assigned to any Component.
	137
	138	The CascadeValues data type contains the possible values for a MemberValue within a CubeRegion, in order to enable cascading to all children Codes of a selected Code, while including/excluding the latter in the selection.
	139
	140	The VersionType data types provides the details for versioning according to SDMX versioning rules, as explained in SDMX Standards Section 6, paragraph “4.3 Versioning”.
	141
2.4	142	== 3.5 The Item Scheme Pattern ==
1.1	143
2.4	144	=== 3.5.1 Context ===
1.1	145
	146	The Item Scheme is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
	147
	148	The //ItemScheme// is the basis for CategoryScheme, Codelist, ConceptScheme, ReportingTaxonomy, //OrganisationScheme//, TransformationScheme, CustomTypeScheme, NamePersonalisationScheme, RulesetScheme, VtlMappingScheme and UserDefinedOperatorScheme.
	149
2.4	150	=== 3.5.2 Class Diagram ===
1.1	151
	152	[[image:1749246130543-644.jpeg]]
	153
	154	Figure 13 The Item Scheme pattern
	155
2.4	156	=== 3.5.3 Explanation of the Diagram ===
1.1	157
2.4	158	==== 3.5.3.1 Narrative ====
1.1	159
	160	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 is derived 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 ConceptScheme. The associated Concepts are //Item//s.
	161
	162	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".
	163
	164	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//.
	165
	166	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.
	167
	168	//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 agencyId as the //ItemScheme//).
	169
	170	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//.
	171
2.4	172	==== 3.5.3.2 Definitions ====
1.1	173
2.4	174	(% style="width:989.835px" %)
	175	\|Class\|(% style="width:297px" %)Feature\|(% style="width:583px" %)Description
	176	\|//ItemScheme//\|(% style="width:297px" %)(((
1.1	177	Inherits from:
	178	//MaintainableArtefact//
	179	Direct sub classes are:
	180	CategoryScheme
	181	ConceptScheme
	182	Codelist
	183	ReportingTaxonomy
	184	//OrganisationScheme//
	185	TransformationScheme
	186	CustomTypeScheme NamePersonalisationSc heme
	187	RulesetScheme
2.4	188	VtlMappingScheme
	189	UserDefinedOperatorSc heme
	190	)))\|(% style="width:583px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
	191	\| \|(% style="width:297px" %)isPartial\|(% style="width:583px" %)Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
	192	\| \|(% style="width:297px" %)/items\|(% style="width:583px" %)Association to the Items in the scheme.
	193	\|//Item//\|(% style="width:297px" %)(((
1.1	194	Inherits from:
	195
	196	//NameableArtefact//
	197
	198	Direct sub classes are
	199
	200	Category
	201
	202	Concept
	203
	204	Code
	205
	206	ReportingCategory //Organisation//
	207
	208	Transformation
	209
	210	CustomType
	211
	212	NamePersonalisation
	213
	214	Ruleset
	215
	216	VtlMapping
	217
	218	UserDefinedOperator// //hierarchy
2.4	219	)))\|(% style="width:583px" %)(((
1.1	220	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.
	221	This allows an Item optionally to have one or more child Items
	222	)))
	223
2.5	224	== 3.6 The Structure Pattern ==
1.1	225
2.5	226	=== 3.6.1 Context ===
1.1	227
	228	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.
	229
3.1	230	=== 3.6.2 Class Diagrams ===
1.1	231
3.1	232	(% class="wikigeneratedid" %)
	233	[[image:1749246130548-601.jpeg]]
	234
1.1	235	Figure 14: The Structure Pattern
	236
	237	[[image:1749246130554-995.jpeg]]
	238
	239	Figure 15: Representation within the Structure Pattern
	240
3.1	241	=== 3.6.3 Explanation of the Diagrams ===
1.1	242
3.1	243	==== 3.6.3.1 Narrative ====
1.1	244
	245	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.
	246
	247	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 MetadataAttributeDescriptor of the MetadataStructureDefinition.
	248
	249	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:
	250
	251	DimensionDescriptor: Dimension, TimeDimension
	252
	253	GroupDimensionDescriptor: Dimension, TimeDimension
	254
	255	MeasureDescriptor: Measure
	256
	257	AttributeDescriptor: DataAttribute, MetadataAttributeRef
	258
	259	MetadataAttributeDescriptor: MetadataAttribute
	260
	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.
	262
	263	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.
	264
	265	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 Codelist, ValueList or //GeoCodelist//. The valid content of a non-enumerated representation is specified as one or more Facet(s) (for example, these may specify minimum and maximum values). For any Attribute this is achieved by one of more
	266
	267	ExtendedFacet(s), which allow the additional representation of XHTML.
	268
	269	The types of representation that are valid for specific components is expressed in the model as a constraint on the association:
	270
	271	* The Dimension, DataAttribute, Measure, MetadataAttribute may be enumerated and, if so, use an //EnumeratedList//.
	272	* The Dimension and Measure may be non-enumerated and, if so, use one or more Facet(s), note that the FacetValueType applicable to the TimeDimension is restricted to those that represent time.
	273	* The MetadataAttribute and DataAttribute may be non-enumerated and, if so, use one or more ExtendedFacet(s).
	274
	275	The //Structure// may be used by one or more //StructureUsage//(s). An example of this, in terms of concrete classes, is that a Dataflow (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the Metadataflow (link to MetadataStructureDefinition).
	276
3.1	277	==== 3.6.3.2 Definitions ====
1.1	278
	279	\|Class\|Feature\|Description
	280	\|StructureUsage\|(((
	281	Inherits from:
	282
	283	//MaintainableArtefact//
	284
	285	Sub classes are:
	286
	287	Dataflow
	288
	289	Metadataflow
	290	)))\|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.
	291	\| \|structure\|An association to a Structure specifying the structure of the artefact.
	292	\|Structure\|(((
	293	Inherits from:
	294
	295	//MaintainableArtefact//
	296
	297	Sub classes are:
	298
	299	DataStructureDefinition MetadataStructureDefinit ion
	300	)))\|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.
	301	\| \|grouping\|A composite association to one or more component lists.
	302	\|//ComponentList//\|(((
	303	Inherits from:
	304
	305	//IdentifiableArtefact//
	306
	307	Sub classes are:
	308
	309	DimensionDescriptor
	310
	311	GroupDimensionDescriptor
	312
	313	MeasureDescriptor
	314
	315	AttributeDescriptor MetadataAttributeDescrip tor
	316	)))\|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\|An aggregate association to one or more components which make up the list.
	318	\|//Component//\|(((
	319	Inherits from:
	320
	321	//IdentifiableArtefact//
	322
	323	Sub classes are:
	324
	325	Measure
	326
	327	//AttributeComponent//
	328
	329	//DimensionComponent//
	330	)))\|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.
	331	\| \|conceptIdentity\|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component.
	332	\| \|localRepresentation\|(((
	333	Association to the Representation of the Component if this is different from the coreRepresentation of the
	334
	335	Concept, which the Component uses (ConceptUsage).
	336	)))
	337	\|Representation\| \|The allowable value or format for Component or Concept
	338	\| \|+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.
	339	\| \|+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.
	340	\|Facet\| \|Defines the format for the content of the Component when reported in a data or metadata set.
	341	\| \|facetType\|A specific content type, which is constrained by the Facet Type enumeration.
	342	\| \|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.
	343	\| \|+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.
	344	\|ExtendedFacet\| \|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.
	345
	346	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.
	347
3.1	348	==== 3.6.3.3 Representation Constructs ====
1.1	349
	350	The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
	351
3.1	352	\|(% style="width:188px" %)(((
	353	SDMX Facet Value Type
	354	)))\|(% style="width:203px" %)XML Schema Data Type\|(% style="width:207px" %)JSON Schema Data Type\|(% style="width:184px" %)(((
	355	.NET Framework Type
	356	)))\|(% style="width:833px" %)Java Data Type
	357	\|(% style="width:188px" %)String\|(% style="width:203px" %)xsd:string\|(% style="width:207px" %)string\|(% style="width:184px" %)System.String\|(% style="width:833px" %)java.lang.String
	358	\|(% style="width:188px" %)Big Integer\|(% style="width:203px" %)xsd:integer\|(% style="width:207px" %)integer\|(% style="width:184px" %)System.Decimal\|(% style="width:833px" %)java.math.BigInteger
	359	\|(% style="width:188px" %)Integer\|(% style="width:203px" %)xsd:int\|(% style="width:207px" %)integer\|(% style="width:184px" %)System.Int32\|(% style="width:833px" %)int
	360	\|(% style="width:188px" %)Long\|(% style="width:203px" %)xsd.long\|(% style="width:207px" %)integer\|(% style="width:184px" %)System.Int64\|(% style="width:833px" %)long
	361	\|(% style="width:188px" %)Short\|(% style="width:203px" %)xsd:short\|(% style="width:207px" %)integer\|(% style="width:184px" %)System.Int16\|(% style="width:833px" %)short
	362	\|(% style="width:188px" %)Decimal\|(% style="width:203px" %)xsd:decimal\|(% style="width:207px" %)number\|(% style="width:184px" %)System.Decimal\|(% style="width:833px" %)java.math.BigDecimal
	363	\|(% style="width:188px" %)Float\|(% style="width:203px" %)xsd:float\|(% style="width:207px" %)number\|(% style="width:184px" %)System.Single\|(% style="width:833px" %)float
	364	\|(% style="width:188px" %)Double\|(% style="width:203px" %)xsd:double\|(% style="width:207px" %)number\|(% style="width:184px" %)System.Double\|(% style="width:833px" %)double
	365	\|(% style="width:188px" %)Boolean\|(% style="width:203px" %)xsd:boolean\|(% style="width:207px" %)boolean\|(% style="width:184px" %)System.Boolean\|(% style="width:833px" %)boolean
	366	\|(% style="width:188px" %)URI\|(% style="width:203px" %)xsd:anyURI\|(% style="width:207px" %)string:uri\|(% style="width:184px" %)System.Uri\|(% style="width:833px" %)Java.net.URI or java.lang.String
	367	\|(% style="width:188px" %)DateTime\|(% style="width:203px" %)xsd:dateTime\|(% style="width:207px" %)string:datetime\|(% style="width:184px" %)System.DateTime\|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	368	\|(% style="width:188px" %)Time\|(% style="width:203px" %)xsd:time\|(% style="width:207px" %)string:time\|(% style="width:184px" %)System.DateTime\|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	369	\|(% style="width:188px" %)GregorianYear\|(% style="width:203px" %)xsd:gYear\|(% style="width:207px" %)string[[(% class="wikiinternallink wikiinternallink" %)^^~[1~]^^>>path:#_ftn1]]\|(% style="width:184px" %)System.DateTime\|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	370	\|(% style="width:188px" %)GregorianMonth\|(% style="width:203px" %)xsd:gYearMonth\|(% style="width:207px" %)string\|(% style="width:184px" %)System.DateTime\|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	371	\|(% style="width:188px" %)GregorianDay\|(% style="width:203px" %)xsd:date\|(% style="width:207px" %)string\|(% style="width:184px" %)System.DateTime\|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	372	\|(% style="width:188px" %)Day, MonthDay, Month\|(% style="width:203px" %)xsd:g*\|(% style="width:207px" %)string\|(% style="width:184px" %)System.DateTime\|(% style="width:833px" %)javax.xml.datatype.XML GregorianCalendar
	373	\|(% style="width:188px" %)Duration\|(% style="width:203px" %)xsd:duration\|(% style="width:207px" %)string\|(% style="width:184px" %)System.TimeSpan\|(% style="width:833px" %)javax.xml.datatype.Dur ation
1.1	374
	375	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.
	376
	377	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.
	378
3.1	379	(% style="width:981.835px" %)
	380	\|(% style="width:107px" %)Facet Type\|(% style="width:872px" %)Explanation
	381	\|(% style="width:107px" %)isSequence\|(% style="width:872px" %)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.
	382	\|(% style="width:107px" %)interval\|(% style="width:872px" %)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.
	383	\|(% style="width:107px" %)startValue\|(% style="width:872px" %)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 isused for a numeric sequence and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed.
	384	\|(% style="width:107px" %)endValue\|(% style="width:872px" %)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.
	385	\|(% style="width:107px" %)timeInterval\|(% style="width:872px" %)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.
	386	\|(% style="width:107px" %)startTime\|(% style="width:872px" %)The startTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). Thisnattribute is used for a time sequence and indicates the start time of thensequence. This value is mandatory for a time sequence to be expressed.
	387	\|(% style="width:107px" %)endTime\|(% style="width:872px" %)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) ofnthe sequence.
	388	\|(% style="width:107px" %)minLength\|(% style="width:872px" %)The minLength facet specifies the minimum and length of the value in characters.
	389	\|(% style="width:107px" %)maxLength\|(% style="width:872px" %)The maxLength facet specifies the maximum length of the value in characters.
	390	\|(% style="width:107px" %)minValue\|(% style="width:872px" %)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.
	391	\|(% style="width:107px" %)maxValue\|(% style="width:872px" %)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.
	392	\|(% style="width:107px" %)Decimals\|(% style="width:872px" %)The decimals facet indicates the number of characters allowed after the decimal separator.
	393	\|(% style="width:107px" %)pattern\|(% style="width:872px" %)The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
1.1	394
	395
	396
	397	----
	398
	399	[[~[1~]>>path:#_ftnref1]] In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.