Changes for page SDMX 3.1 Standards. Section 1. Framework

Summary

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

Details

Page properties

Content

...	...	@@ -242,15 +242,15 @@
242	242	* //**[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] (Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]):**// The set of information which describes the way in which [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] are provided by a data/metadata provider. A [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] can be constrained in much the same way as a data or [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] definition. Thus, a [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] can express the fact that it provides a particular [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] covering a specific set of countries and topics, Importantly, the actual source of registered data or metadata is attached to the [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] (in terms of a URL). The term “agreement” is used because this information can be understood as the basis of a “service-(% style="color:#e74c3c" %)level(%%) agreement”. In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], however, this is informational metadata to support the technical systems, as opposed to any sort of contractual information (which is outside the scope of a technical specification). In (% style="color:#e74c3c" %)version(%%) 3.0, metadata [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] and data [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] are two separate artefacts.
243	243	* //**Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to restrict content (such as enumerations) and are used by [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
244	244	* //**Metadata (% style="color:#e74c3c" %)Constraint(%%):**// Used to restrict content (such as enumerations) and are used by metadata [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
245		-* //**Available Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to report the set of [[Component>>doc:sdmx:Glossary.Component.WebHome]] values that have data reported against them in the context of a Data Query. This structure allows a user to know what valid filters can be applied to a cube of data, such that the resulting cube will contain data.
246		-* //**Structure (% style="color:#e74c3c" %)Map(%%): **//Structure (% style="color:#e74c3c" %)maps(%%) describes a mapping between [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)maps(%%) which each (% style="color:#e74c3c" %)map(%%) in turn describes how one or more [[components>>doc:sdmx:Glossary.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] (% style="color:#e74c3c" %)map(%%) to one or more [[components>>doc:sdmx:Glossary.Component.WebHome]] in that of the target. Represent (% style="color:#e74c3c" %)maps(%%) act as lookup tables and specific provision is made for mapping dates and times.
247		-* //**[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%) describe mappings between source value(s) and target value(s) where the values are restricted to those in a [[code list>>doc:sdmx:Glossary.Code list.WebHome]], value list or be of a certain type such as integer or string.
248		-* //**[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// An [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) describes mapping rules between any [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%). The (% style="color:#e74c3c" %)version(%%) 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)maps(%%): organisation scheme (% style="color:#e74c3c" %)map(%%), [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)map(%%), [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) and [[reporting taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)map(%%). Organisation scheme (% style="color:#e74c3c" %)map(%%) and reporting scheme (% style="color:#e74c3c" %)map(%%) have been omitted from the information model schematic in Figure 1.
249		-* //**[[Reporting Taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]]: **//A [[reporting taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]] allows an organisation to link (possibly in a hierarchical way) a number of cube or [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] definitions which together form a complete “report” of data or metadata. This supports primary reporting which often comprises multiple cubes of heterogeneous data, but may also support other collection and reporting functions. It also supports the specification of publications such as a yearbook, in terms of the data or metadata contained in the publication.
250		-* //**Process:**// The process class provides a way to model statistical processes as a set of interconnected //process steps.// Although not central to the exchange and dissemination of statistical data and metadata, having a shared description of processing allows for the interoperable exchange and dissemination of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets which describe processes-related (% style="color:#e74c3c" %)concepts(%%).
251		-* //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]**//: Describes complex [[code>>doc:sdmx:Glossary.Code.WebHome]] [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] principally for data discovery purposes. The [[codes>>doc:sdmx:Glossary.Code.WebHome]] themselves are referenced from the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] in which they are maintained.
252		-* //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association**//: A [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association links a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] to something that needs it like a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. Furthermore, the linking can be specified in the context of another object such as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the context of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. Thus, a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in a [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] could have different [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] depending on the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
253		-* //**Transformation Scheme:**// A transformation scheme is a set of [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]) transformations aimed at obtaining some meaningful results for the user (e.g., the validation of one or more [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]). The set of transformations is meant to be executed together (in the same run) and may contain 597 any number of transformations in order to produce any number of results. Thus, a transformation scheme can be considered as a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ‘program’.
	245	+* • //**Available Data (% style="color:#e74c3c" %)Constraint(%%):**// Used to report the set of [[Component>>doc:sdmx:Glossary.Component.WebHome]] values that have data reported against them in the context of a Data Query. This structure allows a user to know what valid filters can be applied to a cube of data, such that the resulting cube will contain data.
	246	+* • //**Structure (% style="color:#e74c3c" %)Map(%%): **//Structure (% style="color:#e74c3c" %)maps(%%) describes a mapping between [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)maps(%%) which each (% style="color:#e74c3c" %)map(%%) in turn describes how one or more [[components>>doc:sdmx:Glossary.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] (% style="color:#e74c3c" %)map(%%) to one or more [[components>>doc:sdmx:Glossary.Component.WebHome]] in that of the target. Represent (% style="color:#e74c3c" %)maps(%%) act as lookup tables and specific provision is made for mapping dates and times.
	247	+* • //**[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%) describe mappings between source value(s) and target value(s) where the values are restricted to those in a [[code list>>doc:sdmx:Glossary.Code list.WebHome]], value list or be of a certain type such as integer or string.
	248	+* • //**[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map(%%):**// An [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) describes mapping rules between any [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%). The (% style="color:#e74c3c" %)version(%%) 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)maps(%%): organisation scheme (% style="color:#e74c3c" %)map(%%), [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)map(%%), [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)map(%%) and [[reporting taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)map(%%). Organisation scheme (% style="color:#e74c3c" %)map(%%) and reporting scheme (% style="color:#e74c3c" %)map(%%) have been omitted from the information model schematic in Figure 1.
	249	+* • //**[[Reporting Taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]]: **//A [[reporting taxonomy>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]] allows an organisation to link (possibly in a hierarchical way) a number of cube or [[data flow>>doc:sdmx:Glossary.Dataflow.WebHome]] definitions which together form a complete “report” of data or metadata. This supports primary reporting which often comprises multiple cubes of heterogeneous data, but may also support other collection and reporting functions. It also supports the specification of publications such as a yearbook, in terms of the data or metadata contained in the publication.
	250	+* • //**Process:**// The process class provides a way to model statistical processes as a set of interconnected //process steps.// Although not central to the exchange and dissemination of statistical data and metadata, having a shared description of processing allows for the interoperable exchange and dissemination of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets which describe processes-related (% style="color:#e74c3c" %)concepts(%%).
	251	+* • //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]**//: Describes complex [[code>>doc:sdmx:Glossary.Code.WebHome]] [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] principally for data discovery purposes. The [[codes>>doc:sdmx:Glossary.Code.WebHome]] themselves are referenced from the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] in which they are maintained.
	252	+* • //**[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association**//: A [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association links a [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] to something that needs it like a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. Furthermore, the linking can be specified in the context of another object such as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in the context of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. Thus, a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] in a [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] could have different [[hierarchies>>doc:sdmx:Glossary.Hierarchy.WebHome]] depending on the [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]].
	253	+* • //**Transformation Scheme:**// A transformation scheme is a set of [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]) transformations aimed at obtaining some meaningful results for the user (e.g., the validation of one or more [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]). The set of transformations is meant to be executed together (in the same run) and may contain 597 any number of transformations in order to produce any number of results. Thus, a transformation scheme can be considered as a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ‘program’.
254	254
255	255	== 3.5 SDMX Registry Services ==
256	256