Changes for page 3 SDMX Base Package

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,0 +1,1 @@
	1	+3 SDMX Base Package

Content

...	...	@@ -1,0 +1,423 @@
	1	+= 3 SDMX Base Package =
	2	+
	3	+== 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	+
	11	+identification of commonly found structures or “patterns” leads to easier understanding
	12	+
	13	+identification of patterns encourages re-use
	14	+
	15	+Each of the class diagrams in this section views classes from the SDMX Base package from a different perspective. There are detailed views of specific patterns, plus overviews showing inheritance between classes, and relationships amongst classes.
	16	+
	17	+== 3.2 Base Structures - Identification, Versioning, and Maintenance ==
	18	+
	19	+=== 3.2.1 Class Diagram ===
	20	+
	21	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_1683f36a.jpg||height="675" width="576"]]
	22	+
	23	+**Figure 10: SDMX Identification, Maintenance and Versioning**
	24	+
	25	+=== 3.2.2 Explanation of the Diagram ===
	26	+
	27	+==== 3.2.2.1 Narrative ====
	28	+
	29	+This group of classes forms the nucleus of the administration facets of SDMX objects. They provide features which are reusable by derived classes to support horizontal functionality such as identity, versioning etc.
	30	+
	31	+All classes derived from the abstract class //AnnotableArtefact// may have Annotations (or notes): this supports the need to add notes to all SDMX-ML elements. The Annotation is used to convey extra information to describe any SDMX construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to
	32	+
	33	+InternationalString).
	34	+
	35	+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.
	36	+
	37	+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	+
	39	+//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”.
	40	+
	41	+//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).
	42	+
	43	+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.
	44	+
	45	+==== 3.2.2.2 Definitions ====
	46	+
	47	+|**Class**|**Feature**|**Description**
	48	+|//AnnotableArtefact//|(((
	49	+Base inheritance sub classes are:
	50	+
	51	+//IdentifiableArtefact//
	52	+)))|Objects of classes derived from this can have attached annotations.
	53	+|Annotation||Additional descriptive information attached to an object.
	54	+||id|Identifier for the Annotation. It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object.
	55	+||title//    //|A title used to identify an annotation.
	56	+||type|Specifies how the annotation is to be processed.
	57	+||url|A link to external descriptive text.
	58	+||value|A non-localised version of the Annotation content.
	59	+||+url|An International URI provides a set of links that are language specific, via this role.
	60	+||+text|An International String provides the multilingual text content of the annotation via this role.
	61	+|InternationalUri||The International Uri is a collection of Localised URIs and supports linking to external descriptions in multiple locales.
	62	+|LocalisedUri||The Localised URI supports the link to an external description in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
	63	+|//IdentifiableArtefact//|(((
	64	+Superclass is
	65	+
	66	+//AnnotableArtefact//
	67	+
	68	+Base inheritance sub classes are~://    //
	69	+
	70	+//NameableArtefact//
	71	+)))|Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact.
	72	+||id|The unique identifier of the object.
	73	+||uri|Universal resource identifier that may or may not be resolvable.
	74	+||urn|Universal resource name – this is for use in registries: all registered objects have a urn.
	75	+|//NameableArtefact//|(((
	76	+Superclass is
	77	+
	78	+//IdentifiableArtefact// Base inheritance sub classes are:
	79	+
	80	+//VersionableArtefact//
	81	+)))|Provides a Name and Description to all derived classes in addition to identification and annotations.
	82	+||+description|(((
	83	+A multi-lingual description is provided by this role via the
	84	+
	85	+International String class.
	86	+)))
	87	+||+name|A multi-lingual name is provided by this role via the International String class
	88	+|InternationalString||The International String is a collection of Localised Strings and supports the representation of text in multiple locales.
	89	+|LocalisedString||The Localised String supports the representation of text in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.).
	90	+||label|Label of the string.
	91	+||locale|The geographic locale of the string e.g French, Canadian French.
	92	+|//VersionableArtefact//|(((
	93	+Superclass is
	94	+
	95	+//NameableArtefact//
	96	+
	97	+Base inheritance sub classes are:
	98	+
	99	+//MaintainableArtefact//
	100	+)))|Provides versioning information for all derived objects.
	101	+||version|A version string following SDMX versioning rules.
	102	+||validFrom|Date from which the version is valid
	103	+||validTo|Date from which version is superseded
	104	+|//MaintainableArtefact//|(((
	105	+Inherits from
	106	+
	107	+//VersionableArtefact//
	108	+)))|An abstract class to group together primary structural metadata artefacts that are maintained by an Agency.
	109	+||isExternalReference|If set to “true” it indicates that the content of the object is held externally.
	110	+||structureURL|The URL of an SDMX-ML document containing the external object.
	111	+||serviceURL|The URL of an SDMX-compliant web service from which the external object can be retrieved.
	112	+||+maintainer//    //|Association to the Maintenance Agency responsible for maintaining the artefact.
	113	+|Agency||See section on “Organisations”
	114	+
	115	+== 3.3 Basic Inheritance ==
	116	+
	117	+=== 3.3.1 Class Diagram – Basic Inheritance from the Base Inheritance Classes ===
	118	+
	119	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_b6346072.jpg||height="697" width="622"]]
	120	+
	121	+**Figure 11: Basic Inheritance from the Base Structures**
	122	+
	123	+=== 3.3.2 Explanation of the Diagram ===
	124	+
	125	+==== 3.3.2.1 Narrative ====
	126	+
	127	+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.
	128	+
	129	+== 3.4 Data Types ==
	130	+
	131	+=== 3.4.1 Class Diagram ===
	132	+
	133	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_ec1b8edc.jpg||height="711" width="540"]]
	134	+
	135	+**Figure 12: Class Diagram of Basic Data Types**
	136	+
	137	+=== 3.4.2 Explanation of the Diagram ===
	138	+
	139	+==== 3.4.2.1 Narrative ====
	140	+
	141	+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).
	142	+
	143	+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:
	144	+
	145	+* 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.
	146	+* Replace: Data/metadata is to be replaced and may also include additional data/metadata to be appended.
	147	+* Delete: Data/Metadata is to be deleted.
	148	+* Information: Data and metadata are for information purposes.
	149	+
	150	+The ToValueType data type contains the attributes to support transformations defined in the StructureMap (see Section 0).
	151	+
	152	+The ConstraintRoleType data type contains the attributes that identify the purpose of a Constraint (allowableContent, actualContent).
	153	+
	154	+The ComponentRoleType data type contains the predefined Concept roles that can be assigned to any Component.
	155	+
	156	+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.
	157	+
	158	+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”.
	159	+
	160	+== 3.5 The Item Scheme Pattern ==
	161	+
	162	+=== 3.5.1 Context ===
	163	+
	164	+The Item Scheme is a basic architectural pattern that allows the creation of list schemes for use in simple taxonomies, for example.
	165	+
	166	+The //ItemScheme// is the basis for CategoryScheme, Codelist, ConceptScheme, ReportingTaxonomy, //OrganisationScheme//, TransformationScheme, CustomTypeScheme, NamePersonalisationScheme, RulesetScheme, VtlMappingScheme and UserDefinedOperatorScheme.
	167	+
	168	+=== 3.5.2 Class Diagram ===
	169	+
	170	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_6afb5cc3.jpg||height="570" width="594"]]
	171	+
	172	+**Figure 13 The Item Scheme pattern**
	173	+
	174	+=== 3.5.3 Explanation of the Diagram ===
	175	+
	176	+==== 3.5.3.1 Narrative ====
	177	+
	178	+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.
	179	+
	180	+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".
	181	+
	182	+A[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_99fcc5a.gif||alt="Shape28" height="36" width="31"]] “partial” //ItemScheme// cannot be maintained independently in its partial form i.e., it cannot contain //Item//s that are not present in the full //ItemScheme// and the content of any one //Item //(e.g., names and descriptions) cannot deviate from the content in the full //ItemScheme//. Furthermore, the id of the //ItemScheme// where isPartial is set to "true" is the same as the id of the full //ItemScheme// (agencyId, id, version). This is important as this is the id that that is referenced in other structures (e.g., a Codelist referenced in a DSD) and this id is always the same, regardless of whether the disseminated //ItemScheme// is the full //ItemScheme// or a partial //ItemScheme//.
	183	+
	184	+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.
	185	+
	186	+//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//).
	187	+
	188	+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//.
	189	+
	190	+==== 3.5.3.2 Definitions ====
	191	+
	192	+|**Class**|**Feature**|**Description**
	193	+|//ItemScheme//|(((
	194	+Inherits from:
	195	+
	196	+//MaintainableArtefact//
	197	+
	198	+Direct sub classes are:
	199	+
	200	+CategoryScheme
	201	+
	202	+ConceptScheme
	203	+
	204	+Codelist
	205	+
	206	+ReportingTaxonomy
	207	+
	208	+//OrganisationScheme//
	209	+
	210	+TransformationScheme
	211	+
	212	+CustomTypeScheme NamePersonalisationSc heme
	213	+
	214	+RulesetScheme
	215	+
	216	+VtlMappingScheme UserDefinedOperatorSc heme
	217	+)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common.
	218	+||isPartial|Denotes whether the Item Scheme contains a subset of the full set of Items in the maintained scheme.
	219	+||/items|Association to the Items in the scheme.
	220	+|//Item//|(((
	221	+Inherits from:
	222	+
	223	+//NameableArtefact//
	224	+
	225	+Direct sub classes are
	226	+
	227	+Category
	228	+
	229	+Concept
	230	+
	231	+Code
	232	+
	233	+ReportingCategory
	234	+
	235	+//Organisation//
	236	+
	237	+Transformation
	238	+
	239	+CustomType
	240	+
	241	+NamePersonalisation
	242	+
	243	+Ruleset
	244	+
	245	+VtlMapping
	246	+
	247	+UserDefinedOperator//    //
	248	+)))|The Item is an item of content in an Item Scheme. This may be a node in a taxonomy or ontology, a code in a code list etc. Node that at the conceptual level the Organisation is not hierarchic.
	249	+||hierarchy|This allows an Item optionally to have one or more child Items.
	250	+
	251	+== 3.6 The Structure Pattern ==
	252	+
	253	+=== 3.6.1 Context ===
	254	+
	255	+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.
	256	+
	257	+=== 3.6.2 Class Diagrams ===
	258	+
	259	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_828a9828.jpg||height="726" width="607"]]
	260	+
	261	+**Figure 14: The Structure Pattern**
	262	+
	263	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_1513ed19.jpg||height="459" width="602"]]
	264	+
	265	+**Figure 15: Representation within the Structure Pattern**
	266	+
	267	+=== 3.6.3 Explanation of the Diagrams ===
	268	+
	269	+==== 3.6.3.1 Narrative ====
	270	+
	271	+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.
	272	+
	273	+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.
	274	+
	275	+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:
	276	+
	277	+DimensionDescriptor: Dimension, TimeDimension
	278	+
	279	+GroupDimensionDescriptor: Dimension, TimeDimension
	280	+
	281	+MeasureDescriptor: Measure
	282	+
	283	+AttributeDescriptor: DataAttribute, MetadataAttributeRef
	284	+
	285	+MetadataAttributeDescriptor: MetadataAttribute
	286	+
	287	+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.
	288	+
	289	+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.
	290	+
	291	+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 ExtendedFacet(s), which allow the additional representation of XHTML.
	292	+
	293	+The types of representation that are valid for specific components is expressed in the model as a constraint on the association:
	294	+
	295	+* The Dimension, DataAttribute, Measure, MetadataAttribute may be enumerated and, if so, use an //EnumeratedList//.
	296	+* 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.
	297	+* The MetadataAttribute and DataAttribute may be non-enumerated and, if so, use one or more ExtendedFacet(s).
	298	+
	299	+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).
	300	+
	301	+==== 3.6.3.2 Definitions ====
	302	+
	303	+|**Class**|**Feature**|**Description**
	304	+|StructureUsage|(((
	305	+Inherits from:
	306	+
	307	+//MaintainableArtefact//
	308	+
	309	+Sub classes are:
	310	+
	311	+Dataflow
	312	+
	313	+Metadataflow
	314	+)))|An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow which is linked to a given structure – in this case the Data Structure Definition.
	315	+||structure|An association to a Structure specifying the structure of the artefact.
	316	+|Structure|(((
	317	+Inherits from:
	318	+
	319	+//MaintainableArtefact//
	320	+
	321	+Sub classes are:
	322	+
	323	+DataStructureDefinition MetadataStructureDefinit ion
	324	+)))|Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners.
	325	+||grouping|A composite association to one or more component lists.
	326	+|//ComponentList//|(((
	327	+Inherits from:
	328	+
	329	+//IdentifiableArtefact//
	330	+
	331	+Sub classes are:
	332	+
	333	+DimensionDescriptor
	334	+
	335	+GroupDimensionDescriptor
	336	+
	337	+MeasureDescriptor
	338	+
	339	+AttributeDescriptor MetadataAttributeDescriptor
	340	+)))|An abstract definition of a list of components. A concrete example is a Dimension Descriptor, which defines the list of Dimensions in a Data Structure Definition.
	341	+||components|An aggregate association to one or more components which make up the list.
	342	+|//Component//|(((
	343	+Inherits from:
	344	+
	345	+//IdentifiableArtefact//
	346	+
	347	+Sub classes are:
	348	+
	349	+Measure
	350	+
	351	+//AttributeComponent//
	352	+
	353	+//DimensionComponent//
	354	+)))|A Component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes.
	355	+||conceptIdentity|(((
	356	+Association to a Concept in a Concept Scheme that identifies and defines the
	357	+
	358	+semantic of the Component.
	359	+)))
	360	+||localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept, which the Component uses (ConceptUsage).
	361	+|Representation||The allowable value or format for Component or Concept
	362	+||+enumerated|Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association.
	363	+||+nonEnumerated|Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set.
	364	+|Facet||Defines the format for the content of the Component when reported in a data or metadata set.
	365	+||facetType|A specific content type, which is constrained by the Facet Type enumeration.
	366	+||facetValueType|The format of the value of a Component when reported in a data or metadata set. This is constrained by the Facet Value Type enumeration.
	367	+|||Defines the format of the identifiers in an Item Scheme used by a Component. Typically, this would define the number of characters (length) of the identifier.
	368	+|ExtendedFacet|+itemSchemeFacet|This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute and a Data Attribute.
	369	+
	370	+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.
	371	+
	372	+==== 3.6.3.3 Representation Constructs ====
	373	+
	374	+The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, and have equivalents in most current implementation platforms:
	375	+
	376	+|**SDMX Facet Value Type**|**XML Schema Data Type**|**JSON Schema Data Type**|**.NET Framework Type**|**Java Data Type**
	377	+|String|xsd:string|string|System.String|java.lang.String
	378	+|Big Integer|xsd:integer|integer|System.Decimal|java.math.BigInteger
	379	+|Integer|xsd:int|integer|System.Int32|int
	380	+|Long|xsd.long|integer|System.Int64|long
	381	+|Short|xsd:short|integer|System.Int16|short
	382	+|Decimal|xsd:decimal|number|System.Decimal|java.math.BigDecimal
	383	+|Float|xsd:float|number|System.Single|float
	384	+|Double|xsd:double|number|System.Double|double
	385	+|Boolean|xsd:boolean|boolean|System.Boolean|boolean
	386	+|URI|xsd:anyURI|string:uri|System.Uri|Java.net.URI or java.lang.String
	387	+|DateTime|xsd:dateTime|string:datetime|System.DateTime|javax.xml.datatype.XML GregorianCalendar
	388	+|Time|xsd:time|string:time|System.DateTime|javax.xml.datatype.XML GregorianCalendar
	389	+|GregorianYear|xsd:gYear|(((
	390	+2
	391	+
	392	+string
	393	+)))|System.DateTime|javax.xml.datatype.XML GregorianCalendar
	394	+|GregorianMonth|xsd:gYearMonth|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
	395	+|GregorianDay|xsd:date|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
	396	+|Day, MonthDay, Month|xsd:g*|string|System.DateTime|javax.xml.datatype.XML GregorianCalendar
	397	+|Duration|xsd:duration|string|System.TimeSpan|javax.xml.datatype.Dur ation
	398	+
	399	+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.
	400	+
	401	+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.
	402	+
	403	+|**Facet Type**||**Explanation**
	404	+|isSequence||The isSequence facet indicates whether the values are intended to be ordered, and it may work in combination with the interval, startValue, and endValue facet or the timeInterval, startTime, and endTime, facets. If this attribute holds a value of true, a start value or time and a numeric or time interval must be supplied. If an end value is not given, then the sequence continues indefinitely.
	405	+|interval||The interval attribute specifies the permitted interval (increment) in a sequence. In order for this to be used, the isSequence attribute must have a value of true.
	406	+|startValue||The startValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet is used for a numeric sequence and indicates the starting point of the sequence. This value is mandatory for a numeric sequence to be expressed
	407	+|endValue||The endValue facet is used in conjunction with the isSequence and interval facets (which must be set in order to use this facet). This facet is used for a numeric sequence and indicates that ending point (if any) of the sequence.
	408	+|timeInterval||The timeInterval facet indicates the permitted duration in a time sequence. In order for this to be used, the isSequence facet must have a value of true.
	409	+|startTime||The startTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). This attribute is used for a time sequence and indicates the start time of the sequence. This value is mandatory for a time sequence to be expressed.
	410	+|endTime||The endTime facet is used in conjunction with the isSequence and timeInterval facets (which must be set in order to use this facet). This facet is used for a time sequence and indicates that ending point (if any) of the sequence.
	411	+|minLength||The minLength facet specifies the minimum and length of the value in characters.
	412	+|maxLength||The maxLength facet specifies the maximum length of the value in characters.
	413	+|minValue||The minValue facet is used for inclusive and exclusive ranges, indicating what the lower bound of the range is. If this is used with an inclusive range, a valid value will be greater than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
	414	+|minLength||The minLength facet specifies the minimum and length of the value in characters.
	415	+|maxLength||The maxLength facet specifies the maximum length of the value in characters.
	416	+|minValue||The minValue facet is used for inclusive and exclusive ranges, indicating what the lower bound of the range is. If this is used with an inclusive range, a valid value will be greater than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
	417	+|maxValue||The maxValue facet is used for inclusive and exclusive ranges, indicating what the upper bound of the range is. If this is used with an inclusive range, a valid value will be less than or equal to the value specified here. If the inclusive and exclusive data type is not specified (e.g., this facet is used with an integer data type), the value is assumed to be inclusive.
	418	+|decimals||The decimals facet indicates the number of characters allowed after the decimal separator.
	419	+|pattern||The pattern attribute holds any regular expression permitted in the implementation syntax (e.g., W3C XML Schema).
	420	+
	421	+[[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_59eee18f.gif||alt="Shape29" height="1" width="192"]]
	422	+
	423	+^^2^^ In the JSON schemas, more complex data types are complemented with regular expressions, whenever no direct mapping to a standard type exists.