Last modified by Helena K. on 2026/06/08 15:16

From version 35.1
edited by Helena K.
on 2026/06/04 13:58
Change comment: There is no comment for this version
To version 33.3
edited by Helena K.
on 2026/06/04 13:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Adjustment|Artefact|Attribute|Bilateral exchange|Categorisation|Category|Category Scheme|Code|Codelist|Comment|Component|Concept|Concept Scheme|Constraint|Coverage|Cross-domain Concept|Currency|Data Consumer|Data Provider|Data Set|Data Source|Data Structure Definition|Data exchange|Dataflow|Dimension|Frequency of observation|Global Registry|Hierarchical Codelist|Hierarchy|Incremental update|Item Scheme|Language|Maintenance agency|Map|Measure|Metadata Set|Metadata Structure Definition|Metadata repository|Metadataflow|Notification|Provision Agreement|Reference metadata|Release policy - release calendar|Reporting Taxonomy|Representation|SDMX Information Model|SDMX Registry|SDMX Technical Specification|SDMX-CSV|SDMX-EDI|SDMX-JSON|SDMX-ML|Series|Statistical Data and Metadata eXchange|Statistical classification|Statistical subject-matter domain|Statistical unit|Structural metadata|Subscription|Timeliness|Validation and Transformation Language|Version
Content
... ... @@ -224,7 +224,7 @@
224 224  
225 225  Inherent in any statistical exchange – and in many dissemination activities – is a concept of "service level agreement", even if this is not formalized or made explicit. [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] incorporates this idea in objects termed "[[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]". [[Data providers>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] may provide data to many different [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]. [[Data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] may incorporate data coming from more than one [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]. [[Provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] are the objects which tell you which [[data providers>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] are supplying what data to which [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]. Similarly, metadata [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] for [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]].
226 226  
227 -[[Provision Agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] allow for data collection restrictions to be applied at the level of the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] in the context of the collection ([[data flow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]), this set of information is termed a ‘Data Constraint’ in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. Additionally, in a dissemination environment, data can be queried at the level of the [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], this can be a complete [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] as supplied by a specific [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] for the [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], a subset of data, or information about what data exists (Data Availability).
227 +[[Provision Agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] allow for data collection restrictions to be applied at the level of the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] in the context of the collection ([[data flow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]), this set of information is termed a ‘Data [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]’ in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. Additionally, in a dissemination environment, data can be queried at the level of the [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], this can be a complete [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] as supplied by a specific [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] for the [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], a subset of data, or information about what data exists (Data Availability).
228 228  
229 229  A brief summary of the objects described in the information model includes:
230 230  
... ... @@ -242,9 +242,9 @@
242 242  * //**[[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]: **//An organization which produces data is termed a [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]].
243 243  * //**Metadata Provider: **//An organization which produces [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] is termed a metadata provider.
244 244  * //**[[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] (Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]):**// The set of information which describes the way in which [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]] are provided by a data/metadata provider. A [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] can be constrained in much the same way as a data or [[metadata flow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] definition. Thus, a [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] can express the fact that it provides a particular [[data flow>>doc:sdmx:Glossary 2\.1.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 2\.1.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-level agreement”. In [[SDMX>>doc:sdmx:Glossary 2\.1.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 version 3.0, metadata [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] and data [[provision agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] are two separate [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]].
245 -* //**Data Constraint:**// Used to restrict content (such as enumerations) and are used by [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
246 -* //**Metadata Constraint:**// Used to restrict content (such as enumerations) and are used by metadata [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
247 -* //**Available Data Constraint:**// Used to report the set of [[Component>>doc:sdmx:Glossary 2\.1.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.
245 +* //**Data [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]:**// Used to restrict content (such as enumerations) and are used by [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
246 +* //**Metadata [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]:**// Used to restrict content (such as enumerations) and are used by metadata [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] in order to provide a set of reporting restrictions in the context of a collection
247 +* //**Available Data [[Constraint>>doc:sdmx:Glossary 2\.1.Constraint.WebHome]]:**// Used to report the set of [[Component>>doc:sdmx:Glossary 2\.1.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.
248 248  * //**Structure Map: **//Structure maps describes a mapping between [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] for the purpose of transforming a [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] into a different structure. The mapping rules are defined using one or more [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] maps which each map in turn describes how one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] from the source [[data structure definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] map to one or more [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] in that of the target. Represent maps act as lookup tables and specific provision is made for mapping dates and times.
249 249  * //**[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Map:**// [[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] 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 2\.1.Code list.WebHome]], value list or be of a certain type such as integer or string.
250 250  * //**[[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] Map:**// An [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] map describes mapping rules between any [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] with the exception of [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and value lists which use [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] maps. The version 3.0 information model provides four [[item scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] maps: organisation scheme map, [[concept scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]] map, [[category scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] map and [[reporting taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]] map. Organisation scheme map and reporting scheme map have been omitted from the information model schematic in Figure 1.
© Semantic R&D Group, 2026