Professionalism - code of conduct
type: Concept
comment: This metadata element is used to describe the policies promoting the recruitment and promotion of staff based on relevant aptitude; providing guidelines for staff behaviour and procedures to make these guidelines known to staff; and prescribing other practices that provide assurances of the independence, integrity, and accountability of the statistical agency.
term status: upload
alternative label: Professionalism code of conduct
broader: Professionalism
definition: Provisions for assuring the qualifications of staff and allowing staff to perform their functions without intervention motivated by non-statistical objectives.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROF_COND
related: Professionalism - methodology
related: Professionalism - impartiality
related: Professionalism - statistical commentary
related: Professionalism
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Reporting agency
type: Concept
term status: upload
definition: Organisation that supplies the data for a given instance of the statistics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REP_AGENCY
top concept of: SDMX Glossary 2.1
codelist ID: CL_ORGANISATION
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Metadata repository
type: Concept
comment: In SDMX reference metadata often relate to objects of the SDMX Information Model. These can be structural objects such as Dataflow, Code, Concept or Data Set objects such as partial keys (e.g. the value of a specific Dimension such as a country in the context of the Data Set) or even Observations. These metadata need to be managed and made accessible not only to systems disseminating the metadata but often also to systems concerned with data discovery, query, and data visualisation. Many dissemination systems unite the reference metadata with the data to which they pertain, even though these metadata are collected by different mechanisms, by different systems, and stored in different databases from the data.
term status: upload
broader: Code
broader: Statistical Data and Metadata eXchange
broader: Dimension
broader: SDMX Information Model
broader: Dataflow
broader: Data Set
broader: Reference metadata
definition: Place where logically organised statistical metadata are stored that allows for querying, editing and managing of metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_REPO
related: Code
related: Concept
related: Statistical Data and Metadata eXchange
related: Dimension
related: SDMX Information Model
related: Dataflow
related: Data Set
related: Reference metadata
top concept of: SDMX Glossary 2.1

Release policy
type: Concept
comment: This metadata element is used to describe the policy for release of the data to the public, how the public is informed that the data are being released, and whether the data are disseminated to all interested parties at the same time.
term status: upload
definition: Rules for disseminating statistical data to interested parties.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REL_POLICY
related: Release policy - user access
related: Release policy - release calendar
related: Release policy - transparency
related: Release policy - release calendar access
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Series Key
type: Concept
comment: Most Series Keys are combined with a time value in a Data Set in order to identify uniquely an observation. There may be particular Series Keys that do not require a time value in order to achieve this, so the "Time Dimension" is not obligatory in an SDMX Data Structure Definition. In an SDMX Data Set there must be a value for all of the Dimensions specified in the Data Structure Definition when reporting data for a Series Key. The combination of the semantic of the names of the concepts used by the Dimension (excluding time) describes a Series Key. Unless the Data Structure Definition contains multiple measures this semantic is often the semantic of the observation.
requires: Dimension
term status: upload
broader: Sibling group
definition: Cross product of values of Dimensions where either the cross product or the cross product combined with a time value identifies uniquely an observation.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SERIES_KEY
related: Concept
related: Sibling group
related: Statistical Data and Metadata eXchange
related: Data Structure Definition
related: Dimension
related: Measure
related: Data Set
top concept of: SDMX Glossary 2.1

Metadata Key Set
type: Concept
comment: A typical usage is to constrain a Metadataflow or Provision Agreement in order to validate the metadata exchange.
requires: Reference metadata
term status: upload
definition: Group of keys that identify items in a collection of reference metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_KEY_SET
related: Provision Agreement
related: Metadataflow
related: Constraint
top concept of: SDMX Glossary 2.1

Relevance - completeness
type: Concept
comment: The measurement of the availability of statistics normally refers to Data Sets and compares the required Data Set to the available one.
term status: upload
alternative label: Relevance completeness
broader: Relevance
definition: Extent to which all statistics that are needed are available.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMPLETENESS
related: Relevance - user needs
related: Relevance
related: Relevance - user satisfaction
related: Data Set
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Recommended uses and limitations
type: Concept
comment: This metadata element describes the type of indicators that can be constructed, the validity of inferences that can be made, the types of analyses that can be performed, and the type of policy questions it can help answer. It should mention what type of calculations and derivations should be avoided.
term status: newTerm
definition: Guidance for users on the correct usage and known caveats of the statistics.
in scheme: SDMX Glossary 2.1
related: Statistical indicator
related: Technical information
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Time transformation
type: Concept
comment: Examples of such time transformations are growth rates, cumulative sums over N periods and moving averages. Operations on time series not entailing a "time" component (e.g. ratios) are not to be considered as time transformations.
requires: Series
term status: upload
broader: Component
definition: Time-related operation performed on a time series, solely involving observations of that time series.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TRANSFORMATION
related: Component
top concept of: SDMX Glossary 2.1
codelist ID: CL_TRANSFORMATION
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Component
type: Concept
comment: In the SDMX Information Model it is an abstract super class whose sub classes are the content of a Data Structure Definition or Metadata Structure Definition such as a Dimension or Attribute. A "Component List" is an abstract super class whose sub classes are the lists of Dimensions, Attributes, and Measures defined in a content of a Data Structure Definition key family or Metadata Structure Definition. The Component specification includes its Representation which can be enumerated or non-enumerated. An enumerated Representation of a Component links to a Codelist and a non-enumerated Representation is specified in terms of Facets which define characteristics such as "string", "integer", "Observational Time Period" etc.
requires: Metadata Set
requires: Artefact
term status: upload
broader: Codelist
broader: Metadata Structure Definition
broader: Data Structure Definition
broader: Dimension
broader: SDMX Information Model
broader: Measure
broader: Facet
broader: Representation
broader: Metadata Set
broader: Artefact
broader: Attribute
definition: Structural artefact used to define the structure of a Data or Metadata Set.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMPONENT
related: Codelist
related: Time period
related: Metadata Structure Definition
related: Data Structure Definition
related: Dimension
related: SDMX Information Model
related: Measure
related: Facet
related: Representation
related: Attribute
top concept of: SDMX Glossary 2.1

Data revision - practice
type: Concept
comment: This metadata element is used to provide documentation regarding the source data used and the way they are adjusted, in order to give compilers the possibility of incorporating new and more accurate information into estimates, thus improving their accuracy without introducing breaks in the time series. It also describes the revision status of available data. Data may also be subject to regular or ad hoc revisions as a result of the introduction of new classifications, compilation frameworks and methodologies which result in the compilation of historical data that replace previously released data. Whether or not such changes constitute an actual "revision" or the compilation of a "new" series is a matter of judgment to be done by the statistical agency.
term status: upload
alternative label: Data revision practice
broader: Data revision
definition: Information on the data revision practice.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REV_PRACTICE
related: Data revision
related: Series
related: Statistical classification
related: Data revision - policy
related: Data revision - studies
related: Accuracy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Embargo time
type: Concept
comment: Usually, there is a time delay between the finalisation of the production process of statistical data and the moment when the data produced are released and made available to the users. This point in time where data are made publicly available is called "embargo time".
term status: upload
definition: Exact time at which the data can be made available to the public.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).EMBARGO_TIME
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Measurement error
type: Concept
comment: Measurement errors occur when the response provided differs from the real value. Such errors may be attributable to the respondent, the interviewer, the questionnaire, the collection method or the respondent's record-keeping system. Errors may be random or they may result in a systematic bias if they are not random. Measurement error in a survey response may result from respondents' confusion, ignorance, carelessness or dishonesty; error attributable to the interviewer, may be a consequence of poor or inadequate training, prior expectations regarding respondents' responses, or deliberate errors; and error attributable to the wording of the questions in the questionnaire, the order or context in which the questions are presented, and the method used to obtain the responses.
term status: upload
definition: Error in reading, calculating or recording a numerical value.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MEASUREMENT_ERR
related: Model assumption error
related: Coverage error
related: Processing error
related: Non-sampling error
related: Non-response error
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Relevance
type: Concept
comment: Relevance is concerned with whether the available information sheds light on the issues that are important to users. Assessing relevance is subjective and depends upon the varying needs of users. The Agency's challenge is to weight and balance the conflicting needs of current and potential users to produce statistics that satisfy the most important needs within given resource constraints. In assessing relevance, one approach is to gauge relevance directly, by polling users about the data. Indirect evidence of relevance may be found by ascertaining where there are processes in place to determine the uses of data and the views of their users or to use the data in-house for research and other analysis. Relevance refers to the processes for monitoring the relevance and practical usefulness of existing statistics in meeting users' needs and how these processes impact the development of statistical programmes.
term status: upload
definition: Degree to which statistical information meets the real or perceived needs of clients.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).RELEVANCE
related: Relevance - user needs
related: Relevance - completeness
related: Relevance - user satisfaction
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Statistical classification
type: Concept
comment: The categories at each level of the classification structure must be mutually exclusive and jointly exhaustive of all objects/units in the population of interest. They are defined with reference to one or more characteristics of a particular population of units of observation. A statistical classification may have a flat, linear structure or may be hierarchically structured, such that all categories at lower levels are sub-categories of categories at the next level up.
requires: Statistical variable
requires: Category
term status: newTerm
alternative label: Classification
definition: Set of categories (in the Generic Statistical Information Model sense) which may be assigned to one or more variables registered in statistical surveys or administrative files, and used in the production and dissemination of statistics.
in scheme: SDMX Glossary 2.1
related: Category
related: Classification system
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Statistical unit
type: Concept
comment: The statistical unit is the object of a statistical survey and the bearer of statistical characteristics. Statistical units can also be categorised into basic statistical units, i.e. those for which data are collected (also known as observation units), and derived statistical units, i.e. those which are constructed during the statistical production process (also known as analytical units). A basic statistical unit is the most detailed level to which the obtained characteristics can be attached. Statistical units for economic statistics comprise the enterprise, enterprise group, kind-of-activity unit (KAU), local unit, establishment, homogeneous unit of production, etc. In other statistical domains, statistical units can include persons, households, geographical areas, events etc.
term status: upload
alternative label: Unit
definition: Entity for which information is sought and for which statistics are ultimately compiled.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STAT_UNIT
related: Statistical subject-matter domain
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Provision Agreement
type: Concept
comment: An artefact that links the Data Provider to the relevant Structure Usage (e.g. Dataflow Definition or Metadataflow Definition) for which the provider supplies data or metadata. The agreement may constrain the scope of the data or metadata that can be provided.
term status: upload
broader: Data Provider
broader: Metadataflow
broader: Dataflow
definition: Arrangement within which the information provider supplies data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROVISION_AGR
related: Data Provider
related: Metadataflow
related: Dataflow
related: Artefact
top concept of: SDMX Glossary 2.1

Price adjustment
type: Concept
comment: Various economic aggregates (e.g. GDP, investment, household consumption) are calculated so that changes in value terms can be divided up into a factor that reflects the underlying price changes and a factor which reflects the volume changes. As a result of this sub-division, one can get an idea of how these aggregates develop after adjustment for price changes. For example, in order to measure the volume growth of GDP and its components, it is therefore necessary to remove the effect of price changes from the changes in value, by keeping prices "constant" as it were.
requires: Series
term status: upload
broader: Component
broader: Adjustment
definition: Statistical technique used to remove the effects of price influences operating on a data series.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PRICE_ADJUST
related: Component
related: Seasonal adjustment
related: Adjustment
top concept of: SDMX Glossary 2.1
codelist ID: CL_PRICE_ADJUST
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Confidentiality - redistribution authorisation policy
type: Concept
comment: This concept is used in the exchange of restricted data in cases where the sender explicitly allows subsequent forwarding of these data to other organisations.
term status: upload
alternative label: Confidentiality redistribution authorisation policy
broader: Confidentiality
definition: Secondary recipient(s) to whom the sender allows the primary recipient to forward restricted data.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONF_REDIST
related: Confidentiality - policy
related: Concept
related: Confidentiality - data treatment
related: Confidentiality - status
related: Confidentiality
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Organisation Unit Scheme
type: Concept
comment: In SDMX an Organisation Unit Scheme comprises a flat or hierarchical list of Organisation Units. Each maintenance agency can have multiple Organisation Unit Schemes, and may have none. The identity of the Organisation Unit is a combination of the identity of the Organisation Unit Scheme (which includes the maintenance agency) in which it resides and the identity of the Organisation Unit in that scheme. The Organisation Unit plays no direct role in support of the functionality of SDMX systems as documented in the technical standards (whereas Agency, Data Provider, and Data Consumer do play a distinct role). Therefore, this type of organisation can play any role and have any behaviour that is internal to the systems that use it.
requires: Statistical unit
term status: upload
broader: Data Provider
broader: Data Consumer
broader: Statistical Data and Metadata eXchange
broader: Maintenance agency
definition: Maintained collection of Organisation Units.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ORG_UNIT_SCH
related: Data Provider
related: Data Consumer
related: Statistical Data and Metadata eXchange
related: Maintenance agency
related: Statistical unit
top concept of: SDMX Glossary 2.1

Contact
type: Concept
comment: "Contact" describes contact points for the data or metadata, including how to reach the contact points.
term status: upload
definition: Individual or organisational contact points for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT
related: Contact phone number
related: Contact name
related: Contact person function
related: Contact email address
related: Contact mail address
related: Contact organisation unit
related: Contact organisation
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Concept Scheme
type: Concept
comment: Structural definitions of both data and reference metadata associate specific statistical concepts with their representations, whether textual, coded, etc. In SDMX these Concepts are taken from a "Concept Scheme" which is maintained by a specific Agency. Concept Schemes group a set of Concepts, provide their definitions and names. It is possible for a single Concept Scheme to be used both for data structures and metadata structures. A core Representation of each Concept can be specified (e.g. Codelist, or other Representations such as "date").
requires: Concept
requires: Metadata Structure Definition
requires: Data Structure Definition
term status: upload
broader: Concept
definition: Set of Concepts that are used in a Data Structure Definition or Metadata Structure Definition.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONCEPT_SCH
related: Codelist
related: Item Scheme
related: Concept
related: Statistical Data and Metadata eXchange
related: Representation
related: Reference metadata
top concept of: SDMX Glossary 2.1

Economic activity
type: Concept
comment: An activity can be said to take place when resources such as equipment, labour, manufacturing techniques or products are combined, leading to specific goods or services. Thus, an activity is characterised by an input of resources, a production process and an output of products.
term status: upload
definition: Combination of actions that result in the production, distribution and consumption of goods or services.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ACTIVITY
related: Economic sector
top concept of: SDMX Glossary 2.1
codelist ID: CL_ACTIVITY
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Code
type: Concept
comment: The Code in SDMX contains the Id (the code), and a name and description either or both of which can be multi-lingual.
requires: Concept
requires: Language
term status: upload
broader: Statistical Data and Metadata eXchange
definition: Language-independent set of letters, numbers or symbols that represent a Concept whose meaning is described in a natural language.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CODE
related: Coding Format
related: Constraint
related: Statistical Data and Metadata eXchange
top concept of: SDMX Glossary 2.1

Timeliness
type: Concept
comment: Timeliness refers to the speed of data availability, whether for dissemination or for further processing, and it is measured with respect to the time lag between the end of the reference period and the release of data. Timeliness is a crucial element of data quality: adequate timeliness corresponds to a situation where policy-makers can take informed decisions in time for achieving the targeted results. In quality assessment, timeliness is often associated with punctuality, which refers to the time lag between the release date of data and the target date announced in some official release calendar.
term status: upload
broader: Release policy - release calendar
broader: Quality management - quality assessment
broader: Punctuality
broader: Reference period
definition: Length of time between data availability and the event or phenomenon they describe.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TIMELINESS
related: Release policy - release calendar
related: Quality management - quality assessment
related: Punctuality
related: Time lag
related: Timeliness - source data
related: Reference period
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Compiling agency
type: Concept
comment: The concept is needed as two agencies might be compiling the exact same data but using different sources or concepts (the latter would be partially captured by the Dimensions). The provider ID may not be sufficient, as one provider could disseminate the data compiled by different compiling agencies.
term status: upload
broader: Dimension
definition: Organisation collecting and/or elaborating the data being reported.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMPILING_ORG
related: Concept
related: Dimension
top concept of: SDMX Glossary 2.1
codelist ID: CL_ORGANISATION
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Mode of transport
type: Concept
term status: newTerm
alternative label: Transport mode
definition: Way in which passengers and/or goods can be transported.
in scheme: SDMX Glossary 2.1
top concept of: SDMX Glossary 2.1
codelist ID: CL_TRANSPORT_MODE
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Action type
type: Concept
comment: The "Action type" specifies, for a data or a structure message, the action to be performed, e.g. append new data, replace or delete the data, as specified in the technical specifications.
requires: Statistical Data and Metadata eXchange
term status: upload
broader: Statistical Data and Metadata eXchange
definition: Behaviour to be undertaken by a system processing the information contained in a SDMX message.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ACTION_TYPE
top concept of: SDMX Glossary 2.1

Dissemination format - microdata access
type: Concept
comment: This metadata element indicates if and how the Data Set is accessible as micro-data (e.g. for researchers). Also the micro-data anonymisation rules should be described in short.
term status: upload
broader: Dissemination format
definition: Information on whether microdata are also disseminated.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MICRO_DAT_ACC
related: Dissemination format - news release
related: Dissemination format
related: Dissemination format - other formats
related: Dissemination format - online database
related: Data Set
related: Dissemination format - publications
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Group Key
type: Concept
comment: A Group Key is derived from the dimensionality of the Series Key for the purpose of attaching data attributes.
term status: upload
broader: Series Key
broader: Attribute
definition: Set of key values that comprise a partial key.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).GROUP_KEY
related: Series Key
related: Attribute
top concept of: SDMX Glossary 2.1

SDMX-CSV
type: Concept
comment: CSV is a widely used standardised and simple format to exchange data supported by many analytical and statistical software solutions. It is thus the most appropriate for general public data dissemination purposes. But it also offers clear advantages in special use cases linked to data collection and to system integration especially when third party database solutions are involved, such as relational databases. The SDMX-CSV Data Message format supports the SDMX 2.1 Information Model and works together with the SDMX 2.1 RESTful Web Services API for data queries. The SDMX-CSV format is streamable from a supporting web service in order to limit the amount of server resources.
requires: Data exchange
term status: newTerm
definition: Comma-Separated Values (CSV) based data exchange message format designed for and therefore responding to the main use case of public data dissemination. It fully respects the RFC 4180 specification (Common Format and MIME Type for CSV Files).
in scheme: SDMX Glossary 2.1
related: SDMX-JSON
related: SDMX-EDI
related: Statistical Data and Metadata eXchange
related: SDMX Technical Specification
related: SDMX-ML
top concept of: SDMX Glossary 2.1

Geographical coverage
type: Concept
comment: The geographical coverage specifies the relation of the statistical observation to a kind of area like macro regions, countries, sub-regions, localities, and/or types of cities covered. This concept is usually reference metadata, therefore modelled as an attribute in a DSD, or an MSD concept. Here is an example showing geographical coverage and reference area usage from Statistics on Income and Living Conditions (SILC): Geographical coverage (MSD concept): May exclude small parts of the national territory amounting to no more than 2% of the national population and the national territories. Reference area (DSD Dimension): FR – France. Another example from the 2014 household survey of Argentina: Geographical coverage (DSD attribute): Main cities or metropolitan areas. Reference area (DSD Dimension): AR – Argentina.
requires: Statistical unit
term status: newTerm
definition: Characterisation of the statistical units according to geographical criteria.
in scheme: SDMX Glossary 2.1
related: Concept
related: Sector coverage
related: Metadata Structure Definition
related: Time coverage
related: Data Structure Definition
related: Reference area
related: Dimension
related: Coverage
related: Attribute
related: Population coverage
related: Reference metadata
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Seasonal adjustment
type: Concept
comment: Seasonal adjustment removes the effects of events that follow a more or less regular pattern each year. These adjustments make it easier to observe the cyclical and other non-seasonal movements in a data series.
requires: Series
term status: upload
broader: Adjustment
definition: Statistical technique used to remove the effects of seasonal and calendar influences operating on a data series.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SEASONAL_ADJUST
related: Price adjustment
related: Series
related: Adjustment
top concept of: SDMX Glossary 2.1
codelist ID: CL_SEASONAL_ADJUST
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Institutional sector
type: Concept
comment: A sector is divided into sub-sectors according to the criteria relevant to that sector; this permits a more precise description of the economic behaviour of the units. The institutional sectors combine institutional units with broadly similar characteristics and behaviour: households and non-profit institutions serving households (NPISHs), non-financial corporations, financial corporations, and the government. Transactions with non-residents and the financial claims of residents on non-residents, or vice versa, are recorded in the "rest of the world" account.
requires: Statistical unit
term status: newTerm
definition: Aggregation of institutional units on the basis of the type of producer and depending on their principal activity and function, which are considered to be indicative of their economic behaviour.
in scheme: SDMX Glossary 2.1
related: Sector
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_INST_SECTOR
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Dissemination format - online database
type: Concept
comment: This metadata element provides a description of and link to the online database where the data are available, with a summary identification of domain names as released on the website, as well as the related access conditions.
term status: upload
alternative label: Dissemination format for online database
broader: Dissemination format
definition: Information about online databases in which the disseminated data can be accessed.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ONLINE_DB
related: Dissemination format - news release
related: Dissemination format
related: Dissemination format - other formats
related: Dissemination format - microdata access
related: Dissemination format - publications
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

SDMX Glossary 2.1
type: ConceptScheme
comment: The glossary is implemented as a concept set, enriched with lexical notes, cross-references, comments, examples, and semantic relationships between terms. While not intended to cover the full range of statistical terminology, the glossary focuses on terms central to metadata design and the implementation of SDMX-based exchange frameworks. As part of the Interoperability Basis initiative, we carried out substantial semantic enrichment of the glossary. This included: Introducing formal semantic links between terms using SKOS and DCTERMS Aligning glossary entries with the concept scheme from the SDMX Content-Oriented Guidelines (2009), ensuring skos:exactMatch where applicable Enhancing the glossary's internal coherence and machine-readability to support integration into linked data environments This enrichment strengthens the glossary’s role as a semantic backbone for SDMX metadata systems and improves its interoperability across platforms and statistical domains. This glossary is based on version 2.1, represented in HTML format, but not available in a machine-readable form and not integrated into the Registry. This version supports "Cross-domain concepts", which in the SDMX framework are Concepts relevant to several, if not all, statistical domains. SDMX recommends the use of these concepts, whenever feasible, in SDMX data and metadata structures and messages in order to promote re-usability and exchange of statistical information and their related metadata between organisations. Whenever used, these Concepts should conform to the specified names, ID, Representations and Codelists defined in the SDMX Content-Oriented Guidelines. Cross-Domain Concepts (CDCs) are useful for exchanging data and metadata between multiple agencies and statistical subject-matter domains. The CDCs, if adhered to by international organisations and national institutions, promote the: efficient and automated exchange of data and related structural and reference metadata by interlinking statist…
issued: 2025-03-19T00:00:00Z
replaces: concept#
version info: 45.1
definition: The SDMX Glossary is an SDMX guideline containing concepts and related definitions that are useful for building and understanding data and metadata exchange arrangements based on SDMX. The Glossary provides definition of terms found in the SDMX Information Model, Data Structure Definitions (DSDs), and Metadata Structure Definitions (MSDs) at the time of the present release. It is recommended as a single entry point to a common SDMX terminology to be used in order to facilitate communication and understanding of the standard.
has top concept: Professionalism - code of conduct
has top concept: Reporting agency
has top concept: Metadata repository
has top concept: Series Key
has top concept: Release policy
has top concept: Metadata Key Set
has top concept: Relevance - completeness
has top concept: Recommended uses and limitations
has top concept: Component
has top concept: Time transformation
has top concept: Data revision - practice
has top concept: Embargo time
has top concept: Measurement error
has top concept: Relevance
has top concept: Statistical classification
has top concept: Statistical unit
has top concept: Provision Agreement
has top concept: Price adjustment
has top concept: Confidentiality - redistribution authorisation policy
has top concept: Organisation Unit Scheme
has top concept: Contact
has top concept: Concept Scheme
has top concept: Economic activity
has top concept: Code
has top concept: Timeliness
has top concept: Compiling agency
has top concept: Mode of transport
has top concept: Dissemination format - microdata access
has top concept: Action type
has top concept: Group Key
has top concept: SDMX-CSV
has top concept: Geographical coverage
has top concept: Seasonal adjustment
has top concept: Institutional sector
has top concept: Dissemination format - online database
has top concept: Contact fax number
has top concept: Agency Scheme
has top concept: Accounting conventions
has top concept: Statistical indicator
has top concept: Observation Value
has top concept: Metadata update - last certified
has top concept: Confidentiality
has top concept: Structural metadata
has top concept: Accuracy
has top concept: Release policy - release calendar
has top concept: Dissemination format - news release
has top concept: Cost and burden - efficiency management
has top concept: Currency
has top concept: Confidentiality - data treatment
has top concept: Time coverage
has top concept: Contact person function
has top concept: Facet
has top concept: Non-response error
has top concept: Fast-track change
has top concept: Concept
has top concept: Data Consumer
has top concept: Notification
has top concept: Metadata Structure Definition
has top concept: Language
has top concept: Data revision
has top concept: Metadata update
has top concept: Multilateral exchange
has top concept: Maintenance agency
has top concept: Contact phone number
has top concept: Comment
has top concept: Frequency of dissemination
has top concept: Coherence - cross domain
has top concept: Comparability
has top concept: Data Source
has top concept: Map
has top concept: Decimals
has top concept: Annotable Artefact
has top concept: Data compilation

Contact fax number
type: Concept
term status: upload
broader: Contact
definition: Fax number of the contact points for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_FAX
related: Contact phone number
related: Contact name
related: Contact email address
related: Contact person function
related: Contact mail address
related: Contact organisation unit
related: Contact
related: Contact organisation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Agency Scheme
type: Concept
comment: In SDMX the Agency Scheme contains a non-hierarchic list of maintenance agencies. Each maintenance agency can have a single Agency Scheme, and may have none. The agencies in the Agency Scheme are deemed to be sub agencies of the maintenance agency of the scheme in which they reside. The top-level Agency Scheme is the scheme for which SDMX is the maintenance agency (SDMX Agency Scheme), and every Agency in every Agency Scheme must be related directly or indirectly via intervening Agency Schemes, to an Agency registered in the SDMX Agency Scheme. In this way each Agency can be identified uniquely by the combination of Agencies in the path from the SDMX Agency Scheme to the Agency Scheme in which it resides, plus its own identity in that scheme.
requires: Maintenance agency
term status: upload
broader: Statistical Data and Metadata eXchange
broader: Maintenance agency
definition: Maintained collection of maintenance agencies.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).AGENCY_SCH
related: Item Scheme
related: Statistical Data and Metadata eXchange
related: Maintenance agency
related: Data Consumer Scheme
related: Data Provider Scheme
top concept of: SDMX Glossary 2.1

Accounting conventions
type: Concept
comment: This metadata element refers to descriptions of the types of prices used to value flows and stocks, or other units of measurements used for recording the phenomena being observed; the time of recording of the flows and stocks or the time of recording of other phenomena that are measured, including the reference period employed; and the grossing/netting procedures that are used. Accounting conventions may refer to whether the data are recorded on a cash/accrual or mixed accounting basis, the time of their recording and the reference period (fiscal or calendar year) employed. The description could also include how consistent the practices used are with internationally accepted standards - such as the Balance of Payments Manual (BPM) or the System of National Accounts (SNA) - or good practices.
term status: upload
broader: Unit of measure
broader: Reference period
definition: Practical procedures, standards and other aspects used when compiling data from diverse sources under a common methodological framework.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ACC_CONV
related: Unit of measure
related: Reference period
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Statistical indicator
type: Concept
comment: An aggregation such as the number of accidents, total income or female members of parliament, are not in themselves indicators for comparison across countries, as they are not comparable between populations. However, if a transformation is applied to make the data comparable, e.g. number of accidents per thousand of population, average income, or female members of parliament as a percentage of the total, the result meets the criteria for an indicator. Indicators can be used to reveal relative positions and/or show positive or negative change. In an SDMX data modelling exercise, the modeller may typically decompose existing statistical indicators (say, from an existing exchange framework) into standard, normalised concepts such as Unit of Measure and other characteristics. An example is to take an indicator of Average weekly wage rate, and decompose it into the following concepts including Measure and its ancillary concepts: Measure: Wage rate; Unit of Measure: Currency per person; Aggregation operation: Mean; Indicator period: Weekly. The terms "Measure" and "Statistical indicator" have often been used interchangeably, therefore the existing uses of the terms may differ from the definitions described here.
term status: upload
alternative label: Indicator
broader: Dimension
definition: Data element that represents statistical data for a set of characteristics, one of which allows for meaningful comparisons of the data.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).INDICATOR
related: Unit of measure
related: Concept
related: Currency
related: Statistical Data and Metadata eXchange
related: Measure
top concept of: SDMX Glossary 2.1

Observation Value
type: Concept
comment: "Observation Value" is the field which holds the data.
requires: Statistical variable
term status: upload
definition: Value of a particular variable.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).OBS_VALUE
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: AlphaNumericDatatype

Metadata update - last certified
type: Concept
comment: In statistical agencies the domain manager is often asked to certify that the metadata are checked and updated at regular time intervals. The date of the latest certification is to be retained. Such a certification can also be done if the contents of the metadata file have not been amended. The concept is relevant for metadata reporting from countries to international organisations within metadata standards initiatives.
term status: upload
alternative label: Last certified metadata update
broader: Metadata update
definition: Date of the latest certification to confirm that the metadata posted are still up-to-date, even if the content has not been amended.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_CERTIFIED
related: Concept
related: Metadata update
related: Metadata update - last update
related: Metadata update - last posted
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Confidentiality
type: Concept
comment: Data are protected by confidentiality in cases where unauthorised disclosure could be prejudicial or harmful to the interest of the source or other relevant parties. For instance, data allowing the identification of a physical or legal person, either directly or indirectly, may be characterised as confidential according to the relevant national or international legislation. Unauthorised disclosure of data that are restricted or confidential is not permitted and even legislative measures or other formal provisions may be used to prevent disclosure. Often, there are procedures in place to prevent disclosure of restricted or confidential data, including rules applying to staff, aggregation rules when disseminating data, provision of unit records, etc.
term status: upload
broader: Measure
definition: Property of data indicating whether they are subject to dissemination restrictions.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONF
related: Confidentiality - policy
related: Confidentiality - data treatment
related: Confidentiality - status
related: Confidentiality - redistribution authorisation policy
related: Measure
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Structural metadata
type: Concept
comment: Structural metadata are needed to identify, use, and process data matrixes and data cubes, e.g. names of columns or Dimensions of statistical cubes. Structural metadata must be associated with the statistical data and reference metadata, otherwise it becomes impossible to identify, retrieve and navigate the data or reference metadata. In SDMX structural metadata are not limited to describing the structure of data and reference metadata. The structural metadata in SDMX include many of the other constructs to be found in the SDMX Information Model including data discovery, data and metadata Constraints (used for both data validation and data discovery), data and structure mapping, data and metadata reporting, statistical processes.
requires: Reference metadata
term status: upload
broader: Reference metadata
definition: Metadata that identify and describe data and reference metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STRUCT_META
related: Data validation
related: Statistical Data and Metadata eXchange
related: Dimension
related: SDMX Information Model
related: Reference metadata
related: Cross-domain Concept
related: Structural validation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept

Accuracy
type: Concept
comment: The accuracy of statistical information is the degree to which the information correctly describes the phenomena it was designed to measure. It is usually characterised in terms of error in statistical estimates and is often decomposed into bias (systematic error) and variance (random error) components. Accuracy can be expressed as either measures of accuracy (numerical results of the methods for assessing the accuracy of data) or qualitative assessment indicators. It may also be described in terms of the major sources of error that potentially cause inaccuracy (e.g. accuracy is associated with the "reliability" of the data, which is defined as the closeness of the initial estimated value to the subsequent estimated value).
term status: upload
broader: Component
broader: Measure
definition: Closeness of computations or estimates to the unknown exact or true values that the statistics were intended to measure.-
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ACCURACY
related: Component
related: Accuracy - overall
related: Statistical indicator
related: Non-sampling error
related: Measure
related: Sampling error
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Release policy - release calendar
type: Concept
comment: An advance release calendar is the schedule for release of data, which are publicly disseminated so as to provide prior notice of the precise release dates on which a national statistical agency, other national agency, or international organisation undertakes to release specified statistical information to the public. Such information may be provided for statistical releases in the coming week, month, quarter or year.
term status: upload
alternative label: Release calendar
broader: Release policy
definition: Schedule of statistical release dates.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REL_CAL_POLICY
related: Release policy - user access
related: Release policy - transparency
related: Release policy - release calendar access
related: Release policy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Dissemination format - news release
type: Concept
comment: This metadata element covers press releases or other kind of similar releases linked to data or metadata.
term status: upload
alternative label: Dissemination format for news release
broader: Dissemination format
definition: Regular or ad hoc press releases linked to the data.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).NEWS_REL
related: Dissemination format
related: Dissemination format - other formats
related: Dissemination format - online database
related: Dissemination format - microdata access
related: Dissemination format - publications
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Cost and burden - efficiency management
type: Concept
term status: upload
alternative label: Cost and burden efficiency management
broader: Cost and burden
definition: Cost-benefit analysis, effectiveness of execution of medium term statistical programmes, and ensuring efficient use of resources.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COST_BURDEN_EFF
related: Cost and burden
related: Cost and burden - resources
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Currency
type: Concept
term status: upload
definition: Monetary denomination of the object being measured.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CURRENCY
top concept of: SDMX Glossary 2.1
codelist ID: CL_CURRENCY
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Confidentiality - data treatment
type: Concept
comment: This metadata element is used to describe the rules applied when treating the data with regard to statistical confidentiality (e.g. controlled rounding, cell suppression, aggregation of disclosive information, aggregation rules on aggregated confidential data, primary confidentiality with regard to single data values, etc.).
requires: Statistical unit
requires: Data Set
term status: upload
alternative label: Data treatment for confidentiality
broader: Confidentiality
definition: Rules applied for treating the Data Set to ensure that private information from individual units cannot be accessed and to prevent unauthorised disclosure.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONF_DATA_TR
related: Confidentiality - policy
related: Confidentiality - status
related: Confidentiality - redistribution authorisation policy
related: Confidentiality
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Time coverage
type: Concept
comment: This metadata element describes the time period(s) covered by the data set. The time period covered can be indicated as a time interval, e.g. "1985 to 2006" for annual time series data, or as several intervals or values of time.
term status: upload
broader: Time period
broader: Reference metadata
definition: Period of time for which data are provided.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COVERAGE_TIME
related: Geographical coverage
related: Time period
related: Sector coverage
related: Series
related: Coverage
related: Population coverage
related: Data Set
top concept of: SDMX Glossary 2.1
codelist ID: CL_COVERAGE_TIME
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Contact person function
type: Concept
term status: upload
broader: Contact
definition: Area of technical responsibility of the contact, such as "methodology", "database management" or "dissemination".
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_FUNCT
related: Contact phone number
related: Contact name
related: Contact email address
related: Contact mail address
related: Contact organisation unit
related: Contact organisation
related: Contact
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Facet
type: Concept
comment: This specifies the valid format for a non-enumerated domain for a Component.
requires: Component
requires: Metadata Set
term status: upload
broader: Component
definition: Format specification of a Component's content when reported in a Data or Metadata Set.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).FACET
related: Component
top concept of: SDMX Glossary 2.1

Non-response error
type: Concept
comment: Non-response errors result from a failure to collect complete information on all units in the selected sample. These are known as "unit non-response" and "item non-response". Non-response errors affect survey results in two ways. First, the decrease in sample size or in the amount of information collected in response to a particular question results in larger standard errors. Second, and perhaps more important, a bias is introduced to the extent that non-respondents differ from respondents within a selected sample. Non-response errors are determined by collecting any or all of the following: unit response rate, weighted unit response rate, item response rate, item coverage rate, refusal rate, distribution of reason for non-response, comparison of data across contacts, link to administrative data for non- respondents, estimate of non-response bias.
term status: upload
definition: Error that occurs when the survey fails to get a response to one, or possibly all, of the questions.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).NONRESPONSE_ERR
related: Model assumption error
related: Coverage error
related: Processing error
related: Non-sampling error
related: Measurement error
related: Coverage
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Fast-track change
type: Concept
comment: A fast-track change request can be triggered by any of the organisations in the ownership group. Only changes not breaking backwards compatibility can be issued as fast-track. Fast-track changes follow the same change management process as normal changes but are applied with immediate effect if approved and do not need to wait until the next annual maintenance cycle.
requires: Statistical Data and Metadata eXchange
requires: Artefact
term status: upload
broader: Codelist
broader: Ownership group
broader: Statistical Data and Metadata eXchange
broader: Artefact
definition: Procedure followed to update at short notice an SDMX artefact.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).FAST_TRACK
related: Ownership group
top concept of: SDMX Glossary 2.1

Concept
comment: At an abstract level, a Concept is defined in the Generic Statistical Information Model (GSIM) as a "unit of thought differentiated by characteristics". Concepts are used in different ways throughout the statistical lifecycle, and each role of a Concept is described using different information objects (which are subtypes of Concept). A Concept can be used in these situations: (a) As a characteristic. The Concept is used by a Variable to describe the particular characteristic that is to be measured about a Population. For example, to measure the Concept of gender in a population of adults in Spain, the Variable combines this Concept with the Unit Type "person". (b) As a Unit Type or a Population. To describe the set of objects that information is to be obtained about in a statistical survey. For example, the Population of adults in the Netherlands based on the Unit Type of persons. (c) As a Category to further define details about a Concept. For example, Male and Female for the Concept of Gender. Codes can be linked to a Category via a Node (i.e. a Code Item or Classification Item), for use within a Codelist or Statistical Classification. In SDMX the Concept can be given a core Representation such as a reference to a Codelist for an enumerated Representation or other values such as "integer" or "string" for a non-enumerated Representation. This Representation can be overridden in the data structure when the Concept is used as a Dimension or Attribute. A Concept with a core Representation could be regarded as a represented variable.
requires: Statistical unit
term status: upload
broader: Codelist
broader: Code
broader: Category
broader: Statistical Data and Metadata eXchange
broader: Dimension
broader: Representation
broader: Attribute
definition: Unit of thought created by a unique combination of characteristics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONCEPT
related: Concept Scheme
related: Codelist
related: Code
related: Statistical variable
related: Category
related: Statistical Data and Metadata eXchange
related: Metadata Structure Definition
related: Dimension
related: Representation
related: Statistical classification
related: Attribute
related: Statistical unit
top concept of: SDMX Glossary 2.1

Data Consumer
type: Concept
comment: An organisation can play a number of organisation roles. In the SDMX Information Model three roles are identified at present: Data Provider; Data Consumer; Maintenance Agency. The Data Consumer is relevant for data and reference metadata dissemination. Such systems may require access control. The Data Consumer can be linked to the Dataflows and Metadataflows via a Provision Agreement thus enabling a dissemination system to validate which consumers have access to which data and reference metadata.
term status: upload
broader: Provision Agreement
broader: Data Provider
broader: Metadataflow
broader: SDMX Information Model
broader: Maintenance agency
broader: Dataflow
broader: Reference metadata
definition: Entity that uses data.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_CONSUM
related: Data Provider
related: Provision Agreement
related: Item Scheme
related: Metadataflow
related: SDMX Information Model
related: Maintenance agency
related: Dataflow
related: Reference metadata
top concept of: SDMX Glossary 2.1

Notification
type: Concept
comment: The SDMX Global Registry has the ability to send a Notification message either by means of an e-mail or by an SDMX message to a URL of a service that will process the Notification. The sending of a Notification is triggered by an event in the registry that affects a structural metadata object in the registry, such as a change to a Codelist, a deletion of a Codelist, or the addition of a new Codelist. The Notification is only created if there is one or more Subscriptions held for the object in question and it is sent only to the email addresses and URLs specified in the Subscriptions.
requires: SDMX Registry
term status: upload
broader: SDMX Registry
definition: Information sent to a person or application as a result of an event in an SDMX registry.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).NOTIFICATION
related: Codelist
related: Global Registry
related: SDMX Registry
related: Statistical Data and Metadata eXchange
related: Structural metadata
related: Subscription
top concept of: SDMX Glossary 2.1

Metadata Structure Definition
type: Concept
comment: An MSD defines the reference metadata to be collected or reported by specifying the concepts required, how these relate to each other, their presentational structure and to which objects they are to be attached.
requires: Metadata Set
requires: Attribute
term status: upload
alternative label: MSD
broader: Metadata Set
definition: Specification of the allowed content of a Metadata Set in terms of attributes for which content is to be provided and to which type of object the metadata pertain.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MSD
related: Component
related: Concept
related: Metadata Set
related: Attribute
related: Reference metadata
top concept of: SDMX Glossary 2.1

Language
type: Concept
comment: In some cases, although they are called in the same way, languages have some variations between different communities or countries which are locales in the SDMX information model. The most common used standards to classify languages are ISO 639-1, ISO 639-2/T, ISO 639-2/B, ISO-639-3; ISO 639-1 use two letters codes and the others use three letters. The language Concept could be used with two purposes: To describe which is the communication system adopted by a particular community or Country; To select the correct set of descriptions in a Codelist. The Codes used by statistical classifications are language independent but they are described by labels which can be written in multiple languages. In order to select the correct description for a specific context, it is needed to specify which language will be used to present those descriptions to a group of communities or countries.
term status: newTerm
definition: System of communication used by a particular community or Country.
in scheme: SDMX Glossary 2.1
related: Codelist
related: Code
related: Concept
related: SDMX Information Model
related: International String
related: Statistical classification
top concept of: SDMX Glossary 2.1
codelist ID: CL_LANGUAGE

Multilateral exchange
type: Concept
comment: This exchange process has the effect of reducing the burden of a sending organisation of managing multiple unique bilateral exchanges of statistics and / or metadata with several receiving organisations. This is also a very common exchange process in the statistical area, where communities of national and international institutes agree on ways to gain efficiencies within the scope of their collective responsibilities. Apart from multilateral exchange, the SDMX initiative identifies two other basic forms of exchange of statistics and metadata between organisations, i.e. bilateral exchange and data-sharing exchange.
requires: Dataflow
term status: newTerm
definition: Exchange of statistics and / or metadata between a sending and several receiving organisations for a specific Dataflow where all parties agree on all aspects of the exchange (including the mechanism for exchange, the formats, the frequency or schedule).
in scheme: SDMX Glossary 2.1
related: Bilateral exchange
related: Statistical Data and Metadata eXchange
related: Data sharing
related: Data exchange
top concept of: SDMX Glossary 2.1
recommended representation: StringDatatype

Data revision
type: Concept
comment: Preliminary data are revised when more and better source data become available, or due to a change in methodology. "Data revision" describes the policy and practice for identifying the revision status of the data, as well as the availability of revision studies and analyses.
term status: upload
definition: Change in a value of a statistic released to the public.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_REV
related: Data revision - practice
related: Data revision - policy
related: Data revision - studies
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Metadata update
type: Concept
comment: The date of the metadata update may refer to the update of a whole Metadata Set or to the update of any single metadata item. The update can refer to the file update (with or without change in the content) or to the date on which the metadata have been posted on the web.
term status: upload
broader: Metadata Set
definition: Date on which the metadata element was created or modified.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_UPDATE
related: Metadata update - last certified
related: Metadata update - last update
related: Metadata update - last posted
related: Metadata Set
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Maintenance agency
type: Concept
comment: The maintenance agency is responsible for all administrative and operational issues relating to an artefact or set of artefacts. It is the point of contact for all stakeholders for all issues related to the artefact(s) under its responsibility. The maintenance agency is not a decision-making body. Decisions are made collaboratively among the owners of the artefact. Each identifiable SDMX artefact must have a single maintenance agency (though the maintenance agency could actually consist of several organisations or bodies), either directly (such as Codelist or a Data Structure Definition) or via the container in which it is maintained such as a code (maintained artefact is a Codelist) or a Dimension (maintained artefact is a Data Structure Definition).
requires: Artefact
term status: upload
broader: Codelist
broader: Code
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Dimension
broader: Artefact
definition: Organisation or other expert body responsible for the operational maintenance of commonly used metadata artefacts.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).AGENCY
related: Codelist
related: Ownership group
related: Code
related: Agency Scheme
related: Statistical Data and Metadata eXchange
related: Dimension
related: Data Structure Definition
related: Data Consumer Scheme
related: Artefact
top concept of: SDMX Glossary 2.1
codelist ID: CL_AGENCY
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Contact phone number
type: Concept
term status: upload
alternative label: Telephone number
alternative label: Phone number
broader: Contact
definition: Telephone number of the contact points for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_PHONE
related: Contact name
related: Contact email address
related: Contact person function
related: Contact mail address
related: Contact organisation unit
related: Contact
related: Contact organisation
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Comment
type: Concept
comment: In data messages, a comment may be defined as an Attribute and can contain a descriptive text which can be attached to any construct specified in the Attribute Relationship. In Metadata Sets a comment can be attached to any object in the SDMX Information Model that can be identified (known as an "Identifiable Artefact" in the model). For example Agency, Provision Agreement, Dataflow, Code, Concept. In both of these types of messages the relevant Concept (e.g. COMMENT) must be declared in the structure definition (Data Structure Definition or Metadata Structure Definition) together with the object to which it is allowed to be attached in the Data Set or Metadata Set. Note that in a data structure (version 2.1 onwards) it is possible to define the "Attribute Relationship" of any Concept used as an Attribute to more than one of Data Set, group, series, observation. This is not possible using version 2.0. In version 2.0 it is necessary to declare multiple Concepts (e.g. COMMENT_TS, COMMENT_OBS) to achieve this.
term status: upload
broader: Provision Agreement
broader: Metadata Structure Definition
broader: Data Structure Definition
broader: Identifiable Artefact
broader: SDMX Information Model
broader: Metadata Set
broader: Dataflow
broader: Attribute Relationship
broader: Attribute
broader: Data Set
definition: Descriptive text which can be attached to data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMMENT
related: Provision Agreement
related: Concept
related: Metadata Structure Definition
related: SDMX Information Model
related: Identifiable Artefact
related: Attribute Relationship
related: Data Set
related: Code
related: Data Structure Definition
related: Series
related: Dataflow
related: Metadata Set
related: Attribute
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Frequency of dissemination
type: Concept
comment: The frequencies with which data are released, which could be different from the frequency of data collection.
requires: Time period
term status: upload
broader: Time period
broader: Frequency of data collection
definition: Time interval at which the statistics are disseminated over a given time period.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).FREQ_DISS
related: Frequency of observation
related: Frequency of data collection
top concept of: SDMX Glossary 2.1
codelist ID: CL_FREQ
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Coherence - cross domain
type: Concept
comment: This metadata element is used to describe the differences in the statistical results calculated on the basis of different statistical domains, or surveys based on different methodologies (e.g. between annual and short-term statistics or between social statistics and national accounts).
requires: Data Source
requires: Statistical subject-matter domain
term status: upload
alternative label: Cross-domain coherence
broader: Coherence
definition: Extent to which statistics are reconcilable with those obtained through other Data Sources or statistical domains.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COHER_X_DOM
related: Coherence
related: Statistical subject-matter domain
related: Coherence - internal
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Comparability
type: Concept
comment: Comparability aims at measuring the impact of differences in applied statistical concepts and definitions on the comparison of statistics between geographical areas, non-geographical dimensions, or over time. Comparability of statistics, i.e. their usefulness in drawing comparisons and contrast among different populations, is a complex concept, difficult to assess in precise or absolute terms. In general terms, it means that statistics for different populations can be legitimately aggregated, compared and interpreted in relation to each other or against some common standard. Metadata must convey such information that will help any interested party in evaluating comparability of the data, which is the result of a multitude of factors. In some quality assurance frameworks, e.g. the European Statistics Code of Practice, comparability is strictly associated with the coherence of statistics.
requires: Attribute
term status: upload
broader: Coherence
broader: Dimension
broader: Quality management - quality assurance
broader: Statistical concepts and definitions
broader: Attribute
definition: Extent to which differences between statistics can be attributed to differences between the true values of the statistical characteristics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMPARABILITY
related: Concept
related: Coherence
related: Quality management - quality assurance
related: Comparability - geographical
related: Dimension
related: Statistical concepts and definitions
related: Comparability - over time
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Map
type: Concept
comment: In SDMX there are several different types of correspondence that are contained in StructureSet artefacts and have different types: StructureMap: Used for mapping Codes in a Codelist; ItemSchemeMap: Used for mapping different schemes such as ConceptSchemeMap, CategorySchemeMap, CodelistMap; HybridCodelistMap: Associates a Codelist and a Hierarchical Codelist. Each map is a correspondence between the items in one scheme or list and the items in second scheme or list, where the schemes or lists must be of the same type (e.g. Codelists to Codelists). The map can be specified at the level of the Dataflow or Data Structure, or the Metadataflow or Metadata Structure. The Map takes into account the Constraints that are attached to the structural artefact that is mapped.
term status: upload
broader: Data Provider
broader: Codelist
broader: Item Scheme
broader: Metadataflow
broader: Category Scheme
broader: Data Consumer
broader: Category
broader: Statistical Data and Metadata eXchange
broader: Concept Scheme
broader: Component
broader: Code
broader: Dataflow
broader: Artefact
definition: Correspondence between two or more objects.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MAP
related: Structure Set
related: Codelist
related: Metadataflow
related: Code
related: Statistical Data and Metadata eXchange
related: Dataflow
related: Artefact
top concept of: SDMX Glossary 2.1

Data Source
type: Concept
comment: The location includes a resolvable URL which may download a file or be a query (that may be in the SDMX REST format) that returns data. Data citation (citation text) or DOI (Digital Object Identifier) may also be included alongside the URL.
term status: upload
definition: Location or service from where data or metadata can be obtained.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_SOURCE
related: Statistical Data and Metadata eXchange
top concept of: SDMX Glossary 2.1

Decimals
type: Concept
comment: A decimal is a fraction that has a denominator of a power of ten, the power depending on or deciding the decimal place. It is indicated by a decimal point to the left of the numerator, the denominator being omitted. Zeros are inserted between the point and the numerator, if necessary, to obtain the correct decimal place. Examples of decimals are 0.04 = 4/100 or 0.126 = 126/1000.
term status: upload
definition: Number of digits of an observation to the right of a decimal point.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DECIMALS
top concept of: SDMX Glossary 2.1
codelist ID: CL_DECIMALS
concept type: CrossDomainConcept
recommended representation: CodeListDatatype
recommended representation: IntegerDatatype

Annotable Artefact
type: Concept
comment: The Annotation in SDMX is way of extending the functionality of SDMX structural metadata.
requires: Annotation
term status: upload
broader: Annotation
definition: Construct capable of defining Annotations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ANNOTABLE_ART
related: Annotation
related: Maintainable Artefact
related: Statistical Data and Metadata eXchange
related: Identifiable Artefact
related: Versionable Artefact
related: Structural metadata
related: Artefact
related: Nameable Artefact
top concept of: SDMX Glossary 2.1

Data compilation
type: Concept
comment: In quality assurance frameworks, "Data compilation" refers to the description of statistical procedures used for producing intermediate data and final statistical outputs. Data compilation covers, among other things, the use of weighting schemes, methods for imputing missing values or source data, statistical adjustment, balancing/cross-checking techniques, and relevant characteristics of the specific methods applied.
term status: upload
broader: Quality management - quality assurance
broader: Adjustment
definition: Operations performed on data to derive new information according to a given set of rules.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_COMP
related: Data validation
related: Quality management - quality assurance
related: Adjustment
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

SDMX-ML
type: Concept
comment: SDMX-ML (SDMX markup language) is an XML implementation of the SDMX Information Model. In addition to supporting the collection and dissemination of statistical multi-dimensional arrays in a generic but standardised way, the SDMX-ML supports constructs that aid data validation, data discovery, mapping (of Data Sets) reference metadata, and process. The markup language uses the XML syntax and the allowable markup is specified and documented in Section 3 of the SDMX technical standards (Schema and Documentation).
requires: Statistical Data and Metadata eXchange
term status: upload
alternative label: SDMX markup language
broader: Data validation
broader: Statistical Data and Metadata eXchange
broader: SDMX Information Model
broader: Reference metadata
broader: Data Set
definition: XML format for the exchange of SDMX-structured data and metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_ML
related: Data validation
related: Statistical Data and Metadata eXchange
related: Language
related: SDMX Information Model
related: Reference metadata
related: SDMX Registry Interface (in the context of registry)
related: Data Set
top concept of: SDMX Glossary 2.1

Data Set
type: Concept
comment: Within SDMX, a Data Set can be understood as a collection of similar data, sharing a structure, which extends over a period of time. The Data Set can be represented physically in three fundamental forms: - Generic Data Set: this format allows the representation of data structured according to any Data Structure Definition; - Structure Specific Data Set: this format allows the representation of data structured according to a specific Data Structure Definition; - SDMX-EDI Data Set: a specific case of generic using the UN/EDIFACT syntax and which has limitations on what can be represented. It supports time series only. The Structure Specific format is new to SDMX version 2.1 and combines the functionalities of the version 2.0 Compact and Cross Sectional formats.
requires: Data Structure Definition
term status: upload
alternative label: Dataset
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Representation
definition: Organised collection of data defined by a Data Structure Definition (DSD).
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_SET
related: SDMX-EDI
related: Statistical Data and Metadata eXchange
related: Data Structure Definition
related: Series
related: Representation
related: Dataflow
top concept of: SDMX Glossary 2.1

Cross-domain Concept
type: Concept
comment: Cross-domain Concepts are envisaged to cover various elements describing statistical data and their quality. When exchanging statistics, institutions can select from a standard set of content-oriented concepts. The list of concepts and their definitions reflects recommended practices and can be the basis for mapping between internal systems when data and metadata are exchanged or shared between and among institutions.
requires: Concept
requires: Statistical subject-matter domain
requires: Reference metadata
term status: upload
alternative label: CDC
broader: Content-Oriented Guidelines
definition: Standard Concept, covering structural and reference metadata, which should be used in several statistical domains wherever possible to enhance possibilities of the exchange of data and metadata between organisations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CDC
related: Concept
related: Content-Oriented Guidelines
related: Structural metadata
related: Reference metadata
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept

Preferred scale
type: Concept
comment: For example, PREFERRED_SCALE=6 indicates that observations should be displayed in millions rather than the unit scale. The main use case for this concept is to render the data in a client that consumes SDMX data (e.g. as a graph generator) where it is very useful to have a default scale preference already stated by the provider. It is intended that the value may be overridden by the consumer.
requires: Statistical unit
term status: newTerm
definition: Exponent in base 10 recommended for displaying the data when the data is in unit scale.
in scheme: SDMX Glossary 2.1
related: Unit multiplier
related: Concept
related: Statistical Data and Metadata eXchange
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: IntegerDatatype

Hierarchical Code
type: Concept
comment: The Hierarchical Code references a Code in a Codelist and can have child Hierarchical Codes. It can also reference a Level in a Hierarchical Codelist.
requires: Code
requires: Hierarchy
term status: upload
broader: Codelist
broader: Code
broader: Hierarchy
broader: Hierarchical Codelist
definition: Code reference that is part of a hierarchy.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).HIERARCHIC_CODE
related: Codelist
related: Code
related: Hierarchical Codelist
top concept of: SDMX Glossary 2.1

Dimension
type: Concept
comment: In SDMX, "Dimension" is a statistical concept used (most probably together with other statistical concepts) to identify a series, e.g. a statistical concept indicating a particular economic activity or a geographical reference area.
requires: Concept
requires: Series
term status: upload
broader: Data Structure Definition
definition: Statistical concept used in combination with other statistical concepts to identify a statistical series or individual observations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DIMENSION
related: Economic activity
related: Concept
related: Statistical Data and Metadata eXchange
related: Data Structure Definition
related: Reference area
related: Series Key
related: Series
top concept of: SDMX Glossary 2.1

Quality management - quality documentation
type: Concept
comment: This metadata element is used to document the methods and standards for assessing data quality, based on standard quality criteria such as relevance, accuracy and reliability, timeliness and punctuality, accessibility and clarity, comparability, and coherence.
requires: Quality management - quality assessment
requires: Quality management
term status: upload
alternative label: Quality documentation
broader: Quality management
definition: Documentation on procedures applied for quality management and quality assessment.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).QUALITY_DOC
related: Quality management - quality assessment
related: Quality management
related: Punctuality
related: Comparability
related: Coherence
related: Quality management - quality assurance
related: Timeliness
related: Relevance
related: Accuracy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

isExternalReference
type: Concept
comment: This is used in structural metadata where the object is not contained in the structural metadata made available (e.g. in a structure message or in an SDMX Registry), but has a URI reference from where it can be obtained. Note that this is only available for maintainable objects such as a Codelist, and not for individual Codes.
term status: upload
broader: Codelist
broader: Code
broader: SDMX Registry
broader: Structural metadata
definition: Construct that indicates whether an object is available in the metadata source that contains its identifier or whether the object itself is available elsewhere.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).IS_EXT_REF
related: Codelist
related: Code
related: SDMX Registry
related: Structural metadata
top concept of: SDMX Glossary 2.1

Categorisation
type: Concept
comment: A Categorisation consists of a source property and a target property which define a relationship. The source describes the identifiable object (e.g. a Dataflow), and the target describes the Category.
requires: Concept
requires: Category
requires: Structural metadata
term status: newTerm
definition: Structural metadata concept that links an identifiable object to a Category.
in scheme: SDMX Glossary 2.1
related: Metadataflow
related: Category Scheme
related: Category
related: Dataflow
top concept of: SDMX Glossary 2.1

Local Data Structure Definition
type: Concept
comment: An example is a structure for use in internal production processes.
requires: Data Structure Definition
term status: upload
alternative label: local DSD
broader: Data Structure Definition
definition: Data Structure Definition DSD developed for the specific needs of one organisation only.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DSD_LOCAL
related: Data Structure Definition for global use
top concept of: SDMX Glossary 2.1

Metadata Set
type: Concept
comment: In SDMX the Metadata Set must conform to the specification in a Metadata Structure Definition. The Metadata Set contains one or more reports, each report comprising the metadata content (a set of attributes and corresponding content), and the identification of the precise object to which the metadata are to be attached. The metadata can be attached to any SDMX artefact that can be identified (e.g. structural artefact such as a Code, Concept, Dimension or a part of a Data Set such as a partial Series Key or Observation). In SDMX the type of report defined in a Metadata Structure Definition is known as "reference metadata" which are typified by quality metadata but can contain any type of metadata. These metadata are generally not reported with the data (as data attributes in a Data Set) and are often collected to a different schedule to the data, are derived from separate (from the data) repositories and collected from/reported by systems different from the statistical data warehouse.
requires: Reference metadata
term status: upload
broader: Reference metadata
definition: Organised collection of reference metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_SET
related: Code
related: Concept
related: Statistical Data and Metadata eXchange
related: Metadata Structure Definition
related: Series Key
related: Dimension
related: Attribute
related: Data Set
related: Reference metadata
related: Artefact
top concept of: SDMX Glossary 2.1

Institutional mandate - data sharing
type: Concept
term status: upload
alternative label: Institutional mandate for data sharing
broader: Institutional mandate
definition: Arrangements or procedures for data sharing and coordination between data producing agencies.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).INST_MAN_SHAR
related: Institutional mandate
related: Institutional mandate - legal acts and other agreements
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Release policy - transparency
type: Concept
comment: This statement does not describe the release policy itself.
requires: Release policy
term status: upload
alternative label: Release policy transparency
broader: Release policy
definition: Statement describing whether and how the release policy is disseminated to the public.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REL_POL_TRA
related: Release policy - user access
related: Release policy - release calendar
related: Release policy - release calendar access
related: Release policy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Data update - last update
type: Concept
comment: This concept will typically be used as an Attribute in SDMX data exchanges, usually automatically generated as a timestamp. It may also be used as a metadata Attribute in SDMX metadata exchanges, with a value as defined by the user. It covers the observation value and attributes that determine the measured value (e.g. Unit of Measure and Unit Multiplier). In the case that "Metadata update – Last update" is not implemented, then this concept may also be used to indicate changes to the metadata.
term status: newTerm
definition: Date of the most recent change of the measured value.
in scheme: SDMX Glossary 2.1
related: Observation Value
related: Unit of measure
related: Concept
related: Statistical Data and Metadata eXchange
related: Data exchange
related: Metadata update
related: Metadata update - last update
related: Data update - last certified
related: Attribute
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Subscription
type: Concept
comment: The SDMX Global Registry has a facility that enables a user to subscribe to events in the registry such as a change to a Codelist, a deletion of a Codelist, or the addition of a new Codelist. When such an event takes place the registry will send an SDMX Notification message to the email or URL address in the Subscription.
requires: SDMX Registry
term status: upload
broader: Codelist
broader: Global Registry
broader: SDMX Registry
broader: Statistical Data and Metadata eXchange
broader: Notification
definition: Indication that a person or application is to be notified when a predefined event occurs in an SDMX registry.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SUBSCRIPT
related: Codelist
related: Global Registry
related: Statistical Data and Metadata eXchange
related: Notification
top concept of: SDMX Glossary 2.1

SDMX Registry Interface (in the context of registry)
type: Concept
comment: The SDMX Registry must comply with the Registry Interface API and web services specification for query. An SDMX Registry is not obliged to implement all of the APIs.
requires: SDMX Registry
requires: SDMX-ML
term status: upload
broader: SDMX Registry
definition: SDMX-ML specification of the allowable constructs that an SDMX registry must consume or output in its response.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_REG_INTERFACE
related: SDMX Registry
related: SDMX-ML
top concept of: SDMX Glossary 2.1

Group key structure
type: Concept
comment: The Group Key's structure that comprises the subset of Dimensions that specifies the structure of the partial key.
requires: Concept
requires: Dimension
requires: Data Structure Definition
term status: upload
broader: Dimension
broader: Data Structure Definition
definition: Set of metadata concepts that define a partial key derived from the Dimension Descriptor in a Data Structure Definition.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).GROUP_KEY_STRUCT
related: Dimension
top concept of: SDMX Glossary 2.1

Institutional mandate
type: Concept
comment: The institutional mandate also includes arrangements or procedures to facilitate data sharing and coordination between data producing agencies.
term status: upload
definition: Set of rules or other formal set of instructions assigning responsibility as well as the authority to an organisation for the collection, processing, and dissemination of statistics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).INST_MANDATE
related: Institutional mandate - legal acts and other agreements
related: Institutional mandate - data sharing
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Source data type
type: Concept
comment: This metadata element is used to indicate whether the Data Set is based on a survey, on administrative Data Sources, on a mix of multiple Data Sources or on data from other statistical activities. If sample surveys are used, some sample characteristics should also be given (e.g. population size, gross and net sample size, type of sampling design, reporting domain). If administrative registers are used, the description of registers should be given (e.g. source, primary purpose, etc.).
requires: Component
term status: upload
broader: Component
broader: Data Source
broader: Data Set
definition: Characteristics and components of the raw statistical data used for compiling statistical aggregates.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SOURCE_TYPE
related: Data Source
related: Data Set
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Professionalism - statistical commentary
type: Concept
requires: Comment
term status: upload
alternative label: Professionalism statistical commentary
broader: Professionalism
definition: Elements providing assurances that the statistical entity is entitled to comment on erroneous interpretation and misuse of statistics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROF_STAT_COM
related: Professionalism - code of conduct
related: Professionalism - methodology
related: Professionalism - impartiality
related: Professionalism
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Imputation
type: Concept
comment: Imputation is the process used to determine and assign replacement values for missing, invalid or inconsistent data. This can be done by changing some of the responses or assigning values when they are missing on the record being edited to ensure that estimates are of high quality and that a plausible, internally consistent record is created.
term status: upload
definition: Procedure for entering a value for a specific data item where the response is missing or unusable.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).IMPUTATION
related: Imputation rate
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Documentation on methodology
type: Concept
comment: This metadata element refers to the availability of documentation related to various aspects of the data, such as methodological documents, summary notes or papers covering concepts, scope, classifications and statistical techniques.
term status: upload
definition: Descriptive text and references to methodological documents available.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DOC_METHOD
related: Concept
related: Documentation on methodology - advance notice
related: Statistical classification
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Imputation rate
type: Concept
comment: The un-weighted rate shows, for a particular variable, the proportion of units for which a value has been imputed due to the original value being a missing, implausible, or inconsistent value in comparison with the number of units with a value for this variable. The weighted rate shows, for a particular variable, the relative contribution of imputed values to the estimate of this item/variable.
requires: Statistical variable
term status: upload
definition: Ratio of the number of replaced values to the total number of values for a given variable.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).IMPUTATION_RATE
related: Statistical variable
related: Imputation
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Dataflow
type: Concept
comment: In SDMX, Data Sets are reported or disseminated according to a Dataflow Definition. The Dataflow Definition identifies the Data Structure Definition and may be associated with one or more subject-matter domains. This facilitates the search for data according to organised Category Schemes. A "Dataflow", in this context, is an abstract Concept of the Data Sets, i.e. a structure without any data. While a Data Structure Definition defines Dimensions, Attributes, Measures and associated representation that comprise the valid structure of data and related metadata contained in a Data Set, the Dataflow Definition associates a Data Structure Definition with one or more Category. This gives a system the ability to state which Data Sets are to be reported for a given Category and which Data Sets can be reported using the Data Structure Definition. The Dataflow Definition may also have additional metadata attached, defining qualitative information and Constraints on the use of the Data Structure Definition, in terms of reporting periodicity or specifying the subset of Codes to be used in a Dimension.
requires: Reference period
requires: Data Set
term status: upload
alternative label: Data flow
broader: Code
broader: Category Scheme
broader: Category
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Dimension
broader: Measure
broader: Representation
broader: Reference period
broader: Attribute
broader: Data Set
definition: Structure which describes, categorises and constrains the allowable content of a Data Set that providers will supply for different reference periods.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATAFLOW
related: Metadataflow
related: Code
related: Concept
related: Category
related: Statistical Data and Metadata eXchange
related: Dimension
related: Data Structure Definition
related: Measure
related: Frequency of observation
related: Representation
related: Attribute
related: Data Set
top concept of: SDMX Glossary 2.1

Civil status
type: Concept
comment: The civil status is often referred to as marital status and represented through codes of the respective Codelist.
term status: upload
broader: Codelist
broader: Code
definition: Legal, conjugal status of each individual in relation to the marriage laws or customs of the country.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CIVIL_STATUS
related: Codelist
related: Code
top concept of: SDMX Glossary 2.1
codelist ID: CL_CIVIL_STATUS
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Dissemination format - publications
type: Concept
comment: This metadata element provides references to the most important data dissemination done through paper or online publications, including a summary identification and information on availability of the publication means.
term status: upload
alternative label: Dissemination format for publications
broader: Dissemination format
definition: Regular or ad hoc publications in which the data are made available to the public.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PUBLICATIONS
related: Dissemination format - news release
related: Dissemination format
related: Dissemination format - other formats
related: Dissemination format - online database
related: Dissemination format - microdata access
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Unit multiplier
type: Concept
comment: For example, UNIT_MULT=6 indicates that observations are in millions. In some databases, it is referred to as scale, magnitude or power.
requires: Unit of measure
term status: upload
broader: Unit of measure
definition: Exponent in base 10 used for calculating the actual value in the unit of measure.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).UNIT_MULT
related: Preferred scale
top concept of: SDMX Glossary 2.1
codelist ID: CL_UNIT_MULT
concept type: CrossDomainConcept
recommended representation: CodeListDatatype
recommended representation: IntegerDatatype

Version
type: Concept
comment: In SDMX this construct is a part of the unique identification of the object if it is of the type "VersionableArtefact".
term status: upload
broader: Statistical Data and Metadata eXchange
definition: Construct that enables a system to distinguish between one state of an object and another where the contents of the object have changed.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).VERSION
related: Statistical Data and Metadata eXchange
related: Versionable Artefact
top concept of: SDMX Glossary 2.1

Degree of urbanisation
type: Concept
comment: The degree of urbanisation combines population size and population density thresholds to capture the full settlement hierarchy. It is applied in a two-step process: First, 1 km² grid cells are classified based on population density, contiguity and population size. Subsequently, local units are classified based on the type of grid cells their population resides in.
requires: Statistical classification
term status: newTerm
definition: Classification of the entire territory of a country along the urban-rural continuum.
in scheme: SDMX Glossary 2.1
related: Hierarchy
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_DEG_URB
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Content-Oriented Guidelines
type: Concept
comment: The SDMX Content-Oriented Guidelines comprise the Cross-Domain Concepts; Cross-Domain Codelists; Statistical Subject-Matter Domains; and the SDMX Glossary. The Guidelines focus on the harmonisation of specific concepts and terminology that are common to a large number of statistical domains. Such harmonisation is useful for the efficient exchange of comparable data and metadata.
requires: Statistical Data and Metadata eXchange
requires: SDMX Technical Specification
term status: upload
alternative label: COG
broader: Statistical Data and Metadata eXchange
broader: Cross-domain Codelist
broader: SDMX Technical Specification
broader: Statistical subject-matter domain
broader: Cross-domain Concept
definition: Practices for creating interoperable elements in the SDMX model using the SDMX Technical Specifications.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COG
related: Concept
related: Statistical Data and Metadata eXchange
related: Cross-domain Codelist
related: Statistical subject-matter domain
related: Cross-domain Concept
top concept of: SDMX Glossary 2.1

Coherence
type: Concept
comment: When originating from different sources, and in particular from statistical surveys using different methodology, statistics are often not completely identical, but show differences in results due to different collection methodology concepts, classifications and methodological standards. There are several areas where the assessment of coherence is regularly conducted: between provisional and final statistics, between annual and short-term statistics, between statistics from the same socio-economic domain, and between survey statistics and national accounts. The concept of coherence is closely related to the concept of comparability between statistical domains. Both coherence and comparability refer to a Data Set with respect to another. The difference between the two is that comparability refers to comparisons between statistics based on usually unrelated statistical populations and coherence refers to comparisons between statistics for the same or largely similar populations. In the Data Quality Assessment Framework (DQAF) of the International Monetary Fund (IMF), the term "consistency" is used for indicating "logical and numerical coherence". In that framework, "internal consistency" and "intersectoral and cross-domain consistency" can be mapped to "internal coherence" and "cross-domain coherence" respectively.
term status: upload
broader: Quality management - quality assessment
broader: Statistical population
broader: Comparability
broader: Statistical subject-matter domain
broader: Data Set
definition: Adequacy of statistics to be reliably combined in different ways and for various uses.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COHERENCE
related: Quality management - quality assessment
related: Coherence - cross domain
related: Concept
related: Comparability
related: Statistical population
related: Statistical subject-matter domain
related: Statistical classification
related: Coherence - internal
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Job
type: Concept
comment: A set of jobs whose main tasks and duties are characterised by a high degree of similarity constitutes an occupation.
term status: newTerm
definition: Set of tasks and duties performed, or meant to be performed, by one person, including for an employer or in self-employment
in scheme: SDMX Glossary 2.1
related: Occupation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept

Pull (reporting method)
type: Concept
comment: In a SDMX registry environment the Data Provider will fulfil its data reporting requirements when the registry has accepted the registration. The URL should be checked by the registry as being valid and the registry may check that the data service or Data Set are valid.
requires: Reference metadata
term status: upload
broader: Data Provider
broader: SDMX Registry
broader: Data Set
broader: Reference metadata
definition: Data or reference metadata reporting method that requires the provider to make the information available at an accessible web location.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PULL_METHOD
related: Data Provider
related: Push (reporting method)
related: SDMX Registry
related: Hub (dissemination architecture)
related: Data Set
top concept of: SDMX Glossary 2.1

Data Provider Scheme
type: Concept
comment: In SDMX a Data Provider Scheme contains a non-hierarchic list of Data Providers. Each maintenance agency can have a single Data Provider Scheme, and may have none. The identity of the Data Provider is a combination of the identity of the Data Provider Scheme (which includes the maintenance agency) in which it resides and the identity of the Data Provider in that scheme. The Data Provider is the owning organisation of data and reference metadata. These data and reference metadata are reported, exchanged, or disseminated as SDMX Data Sets and SDMX Metadata Sets. The type of data and metadata that are available are specified in a Dataflow and Metadataflow. The union of one Data Provider and one Dataflow or Metadataflow is known as a Provision Agreement. In a data collection scenario the Data Provider is the organisation reporting the data or reference metadata and information can be linked with the Provision Agreement. Information linked to the Provision Agreement can specify where the data or reference metadata are located (data registration) and the data collector (as the Agency of the Provision Agreement) can specify validation Constraints such as allowable dimension values or Series Keys for which data can be reported. In a data dissemination scenario information linked to the Provision Agreement can specify the location of the Data Source and the content of the Data Source in terms of Series Keys available (Constraint).
requires: Data Provider
term status: upload
broader: Data Provider
definition: Maintained collection of Data Providers.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_PROV_SCH
related: Provision Agreement
related: Data Provider
related: Metadataflow
related: Item Scheme
related: Data Source
related: Statistical Data and Metadata eXchange
related: Series Key
related: Maintenance agency
related: Reference metadata
related: Data Set
related: Agency Scheme
related: Dimension
related: Data Consumer Scheme
related: Metadata Set
related: Dataflow
top concept of: SDMX Glossary 2.1

Institutional mandate - legal acts and other agreements
type: Concept
comment: The concept covers provision in law assigning responsibility to specific organisations for collection, processing, and dissemination of statistics in one or several statistical domains. In addition, non-legal measures such as formal or informal administrative arrangements employed to specific organisations for collection, processing, and dissemination of statistics in one or several statistical domains should also be described.
term status: upload
alternative label: Institutional mandate for legal acts and other agreements
broader: Institutional mandate
definition: Legal acts or other formal or informal agreements that assign responsibility as well as the authority to an Agency for the collection, processing, and dissemination of statistics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).INST_MAN_LA_OA
related: Institutional mandate
related: Concept
related: Institutional mandate - data sharing
related: Statistical subject-matter domain
related: Measure
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Data sharing
type: Concept
comment: In data sharing exchange, any organisation or individual can use any counterparty's data and metadata (assuming they are permitted access to it). This model requires no bilateral agreement, but only requires that data and metadata providers and consumers adhere to the standards. Apart from data-sharing, SDMX identifies two other basic forms of exchange of statistics and metadata between organisations, i.e. bilateral exchange and multilateral exchange.
term status: newTerm
definition: Exchange of data and/or metadata in a situation involving the use of open, freely available data formats and where process patterns are known and standard.
in scheme: SDMX Glossary 2.1
related: Bilateral exchange
related: Statistical Data and Metadata eXchange
related: Data exchange
related: Multilateral exchange
top concept of: SDMX Glossary 2.1

Data update - last certified
type: Concept
comment: The date of the latest certification is to be retained. Such a certification can also be done if the contents of the data have not been amended.
term status: newTerm
definition: Date of the latest certification to confirm that the data posted are still up-to-date.
in scheme: SDMX Glossary 2.1
related: Data update - last update
related: Metadata update - last update
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Relevance - user needs
type: Concept
comment: With respect to the statistical data to be provided, the main users (e.g. official authorities, the public or others) and user needs should be stated, e.g. official authorities with the needs for policy indicators, national users, etc.
term status: upload
alternative label: Relevance user needs
broader: Relevance
definition: Description of requirements with respect to the statistical output.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).USER_NEEDS
related: Statistical indicator
related: Relevance
related: Relevance - completeness
related: Relevance - user satisfaction
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Professionalism - impartiality
type: Concept
term status: upload
alternative label: Professionalism impartiality
broader: Professionalism
definition: Elements providing assurances that statistics are developed, produced and disseminated in a neutral (impartial) manner, and that all users are given equal treatment.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROF_IMP
related: Professionalism - code of conduct
related: Professionalism - methodology
related: Professionalism - statistical commentary
related: Professionalism
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

SDMX-EDI
type: Concept
comment: SDMX-EDI is a message designed for the exchange of statistical information between organisations in a platform independent manner. The SDMX-EDI format is drawn from the GESMES/TS version 3.0 implementation guide, published as a standard of the SDMX initiative. GESMES (Generic Statistical Message) is a United Nations standard (EDIFACT message) allowing partner institutions to exchange statistical multi-dimensional arrays in a generic but standardised way. GESMES/TS (TS stands for "time series" and the specification is limited to supporting time series data) is an Implementation Guide specifying the use of GESMES for time series data and related metadata, and structural metadata; it can be regarded as a profile of GESMES. In the SDMX standard the GESMES/TS profile is known as SDMX-EDI. It defines the structures of GESMES that are available for use in SDMX-EDI thus allowing partner institutions to design and to build the applications needed to "read" and "write" SDMX-EDI messages.
requires: Statistical Data and Metadata eXchange
requires: Series
term status: upload
broader: Statistical Data and Metadata eXchange
broader: Structural metadata
definition: UN/EDIFACT format for exchange of SDMX-structured data and metadata for time series.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_EDI
related: Statistical Data and Metadata eXchange
related: SDMX Information Model
related: Series
related: Structural metadata
top concept of: SDMX Glossary 2.1

International String
type: Concept
comment: This is associated with the Name and Description of a structural metadata artefact. The text has an associated language therefore it is possible to define multi-lingual names and descriptions for any one structural metadata object such as a Code or Concept.
requires: Concept
term status: upload
broader: Code
broader: Structural metadata
broader: Artefact
definition: Construct defining multi-lingual text for the same underlying Concept.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).INTERNAT_STRING
related: Code
related: Concept
related: Language
related: Structural metadata
related: Artefact
top concept of: SDMX Glossary 2.1

Counterpart reference area
type: Concept
comment: The "counterpart area" (also known as "vis-a-vis area") is related to statistics on foreign trade, migration or other domains. It determines, from the point of view of the reporting country, the corresponding area to which the economic or other flows are related to (e.g., in statistics on imports, the counterpart reference area is the area of origin of the goods). A categorisation of IDs per attachment level (COUNTERPART_AREA_DSET for dataset, COUNTERPART_AREA_GRP for group) is recommended.
requires: Reference area
term status: upload
alternative label: Vis-a-vis area
broader: Reference area
definition: Secondary area, as opposed to reference area, to which the measured data are in relation.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COUNTERPART_AREA
related: Reference area
related: Categorisation
related: Attachment level
related: Data Set
top concept of: SDMX Glossary 2.1
codelist ID: CL_AREA
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Hierarchy
type: Concept
comment: Each level of the classification is defined in terms of the categories at the next lower level of the classification. In SDMX this is known as a level based hierarchy. SDMX also has the concept of the value based hierarchy where the hierarchy of categories are not organised into formal levels.
requires: Statistical classification
term status: upload
broader: Category
broader: Statistical Data and Metadata eXchange
definition: Classification structure arranged in levels of detail from the broadest to the most detailed level.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).HIERARCHY
related: Concept
related: Category
related: Statistical Data and Metadata eXchange
related: Level
related: Statistical classification
top concept of: SDMX Glossary 2.1

Observation pre-break value
type: Concept
comment: At a time series break period, two observations may be recorded: the pre-break value produced on the basis of the old methodology and the post-break value, as measured by the new methodology. SDMX allows for a pre-break value in the case of a series break, where one would use the Observation Value to show the post-break value.
requires: Series
term status: upload
broader: Observation Value
broader: Statistical Data and Metadata eXchange
definition: Observation, at a time series break period, that was calculated using the old methodology.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PRE_BREAK_VALUE
related: Observation Value
related: Statistical Data and Metadata eXchange
related: Series
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: AlphaNumericDatatype

Metadata Key
type: Concept
comment: For instance, for a Code or a Concept the Metadata Key would be their Id, such as the URN. For a specific key or partial key there would be two objects, the Data Structure Definition and the Series Key. This is a conceptual structure as it is probable that the Metadata Key would combine the value of all of the individual Object Ids, as this would be necessary in order to find metadata quickly. Metadata keys can be grouped into Metadata Key Sets.
requires: Reference metadata
term status: newTerm
definition: Construct comprised of one or more Object Type/Object Id(s) in order to uniquely identify an item in a collection of reference metadata.
in scheme: SDMX Glossary 2.1
related: Code
related: Concept
related: Series Key
related: Data Structure Definition
related: Metadata Key Set
top concept of: SDMX Glossary 2.1

Metadata update - last update
type: Concept
comment: The last update of the content of metadata should be retained. It covers reference metadata and attributes that do not determine the measured value.
term status: upload
alternative label: Last metadata update
broader: Metadata update
definition: Date of the most recent change of the metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_LAST_UPDATE
related: Metadata update - last certified
related: Data update - last update
related: Metadata update
related: Metadata update - last posted
related: Reference metadata
related: Attribute
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Versionable Artefact
type: Concept
comment: The version is mandatory and other attributes (such as "to" and "from" validity dates) are optional. Versionable Artefacts inherit the capability of having names, identity and Annotations.
term status: upload
broader: Annotation
broader: Attribute
definition: Construct that contains structures capable of providing a version to an object.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).VERSIONABLE_ART
related: Annotation
related: Maintainable Artefact
related: Version
related: Identifiable Artefact
related: Annotable Artefact
related: Attribute
related: Artefact
related: Nameable Artefact
top concept of: SDMX Glossary 2.1

Metadata update - last posted
type: Concept
comment: The date of the last posting (dissemination) of the metadata on the web site should be retained. This date will normally be inserted automatically by the metadata production system.
term status: upload
alternative label: Last posted metadata update
broader: Metadata update
definition: Date of the latest dissemination of the metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_POSTED
related: Metadata update - last certified
related: Metadata update
related: Metadata update - last update
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: BasicTimePeriodDatatype

Representation
type: Concept
comment: The Representation can be enumerated or non-enumerated. An enumerated Representation can be a Codelist, Concept Scheme, Category Scheme, Organisation Unit Scheme, Data Provider Scheme, Data Consumer Scheme, Agency Scheme. A non-enumerated Representation is a specification of the valid content in terms of data types such as boolean, string, integer, and the time formats within the Observational Time Period hierarchy such as Standard Time Period and Time Range.
requires: Component
requires: Concept
term status: upload
broader: Concept Scheme
broader: Codelist
broader: Component
broader: Agency Scheme
broader: Category Scheme
broader: Data Consumer Scheme
broader: Organisation Unit Scheme
broader: Data Provider Scheme
definition: Allowable value or format for Component or Concept when reported.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REPRESENT
related: Concept Scheme
related: Codelist
related: Component
related: Agency Scheme
related: Concept
related: Hierarchy
related: Category Scheme
related: Time period
related: Time format
related: Data Consumer Scheme
related: Organisation Unit Scheme
related: Data Provider Scheme
top concept of: SDMX Glossary 2.1

Hub (dissemination architecture)
type: Concept
comment: The hub architecture supports the "pull" method only, i.e. a group of partners agree on providing access to their data directly from their database according to standard processes, formats and technologies (e.g. web service). From the data management point of view, the hub is also based on pre-specified datasets, which are not kept locally at the central hub system. The query process operates as follows: a user identifies a dataset through the graphical user interface (GUI) of the hub using the structural metadata, and requests it; the hub translates the user request in one or more queries and sends them to the related Data Providers' systems; Data Providers' systems process the query and send the result to the hub in standard format (e.g. SDMX-ML 2.1); the hub puts together all the results originated in all implicated Data Providers' systems and presents them in the requested format. This could be a human-readable, non-SDMX format such as a table.
requires: Reference metadata
term status: upload
alternative label: Hub
broader: Data Provider
broader: Statistical Data and Metadata eXchange
broader: SDMX-ML
broader: Structural metadata
broader: Reference metadata
broader: Data Set
definition: Method of registering, querying, and disseminating data or reference metadata by means of a central, service-based platform (the hub).
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).HUB
related: Data Provider
related: Statistical Data and Metadata eXchange
related: Pull (reporting method)
related: SDMX-ML
related: Structural metadata
related: Data Set
top concept of: SDMX Glossary 2.1

Cost and burden - resources
type: Concept
comment: It may include the contribution of respondent time in supplying information (burden) as a distinct subject under this heading.
term status: upload
alternative label: Cost and burden resources
broader: Cost and burden
definition: Metadata element providing assurances that staff, facilities, computing resources, and financing to undertake statistical production are commensurate with statistical programs.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COST_BURDEN_RES
related: Cost and burden - efficiency management
related: Cost and burden
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Nameable Artefact
type: Concept
comment: The name is mandatory and the description is optional. Each can have multilingual variants. Nameable Artefacts inherit the capability of having identity and Annotations.
term status: upload
broader: Annotation
definition: Construct that contains structures capable of providing a name and a description to an object.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).NAMEABLE_ART
related: Annotation
related: Maintainable Artefact
related: Identifiable Artefact
related: Versionable Artefact
related: Annotable Artefact
related: Artefact
top concept of: SDMX Glossary 2.1

Constraint
type: Concept
comment: There are two types of Constraints: Content Constraints and Attachment Constraints. A Content Constraint specifies either the "allowable content" (used to restrict the values allowed when data or metadata are reported or exchanged), or the "actual" content (Series Keys and/or Dimension and Attribute Values present in a Data Source). In each of these cases the Constraint specifies a sub set of the full cube of data that could theoretically be present according to the specification of the Data Structure Definition or Metadata Structure Definition. An Attachment Constraint describes subsets of the content of a Data or Metadata Set in terms of the content regions or in terms of the set of key combinations to which attributes or reference metadata (as defined by structure definitions) may be attached.
requires: Codelist
term status: upload
broader: Codelist
definition: Specification of a subset of the possible content of data or metadata that can be derived from the Codelists used in a data or metadata structure.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONSTRAINT
related: Codelist
related: Member Value
related: Data Source
related: Series Key
related: Metadata key value
related: Metadata Key Set
related: Reference metadata
related: Code
related: Data Structure Definition
related: Dimension
related: Member Selection
related: Metadata Set
related: Attribute
top concept of: SDMX Glossary 2.1

Title
type: Concept
comment: "Title" may be used as a semantic name describing a statistical object. In SDMX, a title can be referred, for example, to a time series as a "time series title", or to an Observation as an "observation title". This Concept may be used several times in a Data Structure Definition (DSD) by suffixing the ID corresponding to the attachment level, e.g. TITLE_TS (series level), or TITLE_OBS (observation level).
term status: upload
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Attachment level
definition: Textual label used to refer to a statistical object.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TITLE
related: Concept
related: Statistical Data and Metadata eXchange
related: Data Structure Definition
related: Series
related: Attachment level
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Data exchange
type: Concept
comment: Data exchange should take place in such a manner that the information content or meaning assigned to the data is not altered during the transmission.
term status: newTerm
definition: Process of sending and receiving data.
in scheme: SDMX Glossary 2.1
related: Bilateral exchange
related: Data sharing
related: Multilateral exchange
top concept of: SDMX Glossary 2.1
recommended representation: StringDatatype

Level
type: Concept
comment: In a "level based" hierarchy the Level describes a group of Codes which are characterised by homogeneous coding, and where the parent of each Code in the group is at the same higher level of the Hierarchy. In a "value based" hierarchy the Level describes information about the Hierarchical Codes at the specified nesting Level. A Statistical Classification has a structure which is composed of one or several Levels. A Level often is associated with a Concept, which defines it. A linear classification has only one Level.
requires: Code
term status: upload
broader: Hierarchy
definition: Identifiable position to which codes in a scheme of codes are related.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).LEVEL
related: Code
related: Concept
related: Coding Format
related: Hierarchical Code
related: Hierarchy
related: Statistical classification
top concept of: SDMX Glossary 2.1

Reporting Taxonomy
type: Concept
comment: This is used to group the Reporting Categories that link to Dataflows and Metadataflows to support data publication.
requires: Metadataflow
requires: Component
requires: Dataflow
term status: upload
broader: Reporting Category
definition: Scheme which defines the composition structure of a data report where each Component can be described by an independent Dataflow Definition or Metadataflow Definition.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REP_TAXO
related: Metadataflow
related: Category
related: Reporting Category
related: Dataflow
top concept of: SDMX Glossary 2.1

Metadata key value
type: Concept
comment: This is a part of a Constraint.
requires: Component
requires: Metadata Structure Definition
requires: Metadata Set
term status: upload
broader: Component
broader: Metadata Structure Definition
broader: Metadata Set
definition: Value in a Metadata Set of an identifier Component defined in a Metadata Structure Definition.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).META_KEY_VAL
related: Constraint
top concept of: SDMX Glossary 2.1

Frequency of observation
type: Concept
comment: If a data series has a constant time interval between its observations, this interval determines the frequency of the series (e.g. monthly, quarterly, yearly). "Frequency" - also called "periodicity" - may refer to several stages in the production process, e.g. in data collection or in data dissemination. (e.g. a time series could be available at annual frequency but the underlying data are compiled monthly). Therefore, "Frequency" can be broken down into "Frequency - data collection" and "Frequency - data dissemination".
requires: Time period
term status: upload
alternative label: Periodicity
broader: Time period
definition: Time interval at which observations occur over a given time period.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).FREQ
related: Series
related: Frequency of data collection
related: Frequency of dissemination
top concept of: SDMX Glossary 2.1
codelist ID: CL_FREQ
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Frequency of data collection
type: Concept
comment: The frequencies with which the source data are collected and produced could be different: a time series could be collected from the respondents at quarterly frequency but the data production may have a monthly frequency. The frequency of data collection should therefore be described.
term status: upload
definition: Time interval at which the source data are collected.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).FREQ_COLL
related: Frequency of observation
related: Series
related: Frequency of dissemination
top concept of: SDMX Glossary 2.1
codelist ID: CL_FREQ
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Title complement
type: Concept
comment: "Title complement" is an additional name to "Title" describing a statistical object. In SDMX, a title complement can be referred, for example, to a time series as a "time series title complement", or to an Observation as an "observation title complement". This concept may be used several times in a DSD by suffixing the ID corresponding to the attachment level, e.g. TITLE_COMPL_TS (series level), or TITLE_COMPL_OBS (observation level).
term status: newTerm
definition: Detailed textual label used to refer to a statistical object.
in scheme: SDMX Glossary 2.1
related: Concept
related: Statistical Data and Metadata eXchange
related: Title
related: Data Structure Definition
related: Series
related: Attachment level
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Punctuality
type: Concept
comment: Punctuality may be calculated, for instance, with reference to target dates announced in an official release calendar, laid down by regulations or previously agreed among partners.
requires: Time lag
term status: upload
broader: Release policy - release calendar
definition: Time lag between the actual delivery of the data and the target date when it should have been delivered.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PUNCTUALITY
related: Release policy - release calendar
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Cross-domain Codelist
type: Concept
comment: 1) Potential application across all statistical domains. Examples: CL_OBS_STATUS, CL_CONF_STATUS, CL_DECIMALS, CL_UNIT_MULT, CL_AREA. Explanatory note: Key term for this criterion is "potential". These Codelists must not necessarily be implemented in all Data Structure Definitions (DSDs) but they potentially could. For example, Codelist "Unit multiplier" could possibly be used in all implementations dealing with statistical figures but some implementations might not see the need for such a Dimension because the statistical values do not require it, e.g. average number of children per household. Inversely, in this example a Codelist for decimals will be absolutely necessary. 2) Codelists maintained by the SWG on its initiative because 1) they are intended for broad use within the SDMX community and 2) there is a strong need for harmonisation across domains which are not necessarily closely connected with each other. Examples for case 1: CL_AGE, CL_CIVIL_STATUS, CL_FREQ, CL_TIME_FORMAT, CL_SEX, CL_ADJUSTMENT. Explanatory note: By proposing such Codelists it is hoped to promote harmonisation across domains and provide ready-to-use artefacts to implementers. Example for case 2: CL_ACTIVITY. Explanatory note: International activity classifications are typically used in different statistical domains (e.g. economic versus social statistics). Without an established CDCL made available in centralised registries, the risk is that one domain develops a Codelist without taking into account the fact that other domains might use the same classification system. 3) Codelists recommended as CDCL by the SDMX Statistical Working Group (SWG) although they are in principle maintained by third organisations. Examples: CL_AREA (based on the ISO 3166 alpha-2 codes for countries); CL_CURRENCY (based on the ISO 4217 3-character codes for currencies). Explanatory note: In these cases, the value added by the SWG is to propose guidelines on specific methodological issues, e.g. how to code a cou…
requires: Codelist
requires: Statistical Data and Metadata eXchange
term status: upload
alternative label: CDCL
broader: Content-Oriented Guidelines
definition: SDMX Codelist meeting at least one of the criteria below: 1) Potential application across all statistical domains; 2) Codelist maintained by the SDMX Statistical Working Group (SWG) on its initiative; 3) Codelist recommended as CDCL by the SDMX SWG although they are in principle maintained by third organisations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CDCL
related: Codelist
related: Unit multiplier
related: Code
related: Statistical Data and Metadata eXchange
related: Content-Oriented Guidelines
related: Data Structure Definition
related: Decimals
related: Dimension
related: Statistical subject-matter domain
related: Statistical classification
related: Artefact
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept

Data Consumer Scheme
type: Concept
comment: In SDMX a Data Consumer Scheme comprises a non-hierarchic list of Data Consumers. Each maintenance agency can have a single Data Consumer Scheme, and may have none. The identity of the Data Consumer is a combination of the identity of the Data Consumer Scheme (which includes the maintenance agency) in which it resides and the identity of the Data Consumer in that scheme.
requires: Data Consumer
term status: upload
broader: Data Consumer
broader: Statistical Data and Metadata eXchange
broader: Maintenance agency
definition: Maintained collection of Data Consumers.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_CONSUM_SCH
related: Item Scheme
related: Agency Scheme
related: Data Consumer
related: Statistical Data and Metadata eXchange
related: Maintenance agency
related: Data Provider Scheme
top concept of: SDMX Glossary 2.1

Usage status
type: Concept
comment: Allowed values are mandatory or conditional. Note that in an incremental update a set of data or metadata may omit mandatory attributes.
requires: Metadata Set
requires: Attribute
term status: upload
broader: Incremental update
broader: Metadata Set
broader: Attribute
definition: Indication of the dependency of the presence of a data or metadata attribute when reported in a Data or Metadata Set.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).USAGE_STATUS
related: Incremental update
related: Attribute
top concept of: SDMX Glossary 2.1
recommended representation: StringDatatype

Release policy - user access
type: Concept
term status: upload
alternative label: Release policy user access
broader: Release policy
definition: Policy for release of the data to users, scope of dissemination (e.g. to the public, to selected users), how users are informed that the data are being released, and whether the policy determines the dissemination of statistical data to all users.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REL_POL_US_AC
related: Release policy - release calendar
related: Release policy - transparency
related: Release policy - release calendar access
related: Release policy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Unit of measure
type: Concept
comment: The unit of measure is a quantity or increment by which something is counted or described, such as kg, mm, °C, °F, monetary units such as Euro or US dollar, simple number counts or index numbers. The unit of measure in connection with the unit multiplier, provides the level of detail for the value of the variable. For data messages, the concept is usually represented by codes. For metadata messages the concept is usually represented by free text.
requires: Statistical unit
term status: upload
alternative label: Unit measure
alternative label: Unit of measurement
broader: Unit multiplier
broader: Code
broader: Currency
definition: Unit in which the data values are expressed.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).UNIT_MEASURE
related: Unit multiplier
related: Code
related: Concept
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_UNIT_MEASURE
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Statistical variable
type: Concept
comment: The term "variable" is meant here in the mathematical sense, i.e. a quantity which may take any one of specified set of values. It is convenient to apply the same word to denote non-measurable characteristics, e.g. "sex" is a variable in this sense since any human individual may take one of two "values", male or female.
requires: Concept
requires: Category
requires: Measure
requires: Statistical classification
requires: Statistical unit
term status: upload
alternative label: Variable
broader: Sex
broader: Age
broader: Category
broader: Measure
broader: Occupation
definition: Concept used as a characteristic of a unit being observed that may assume more than one of a set of values to which a numerical measure or a category from a classification can be assigned.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).VARIABLE
related: Sex
top concept of: SDMX Glossary 2.1

Member Value
type: Concept
comment: This is a part of a Constraint.
requires: Member Selection
term status: upload
broader: Member Selection
definition: Single value of the set of values for a Member Selection.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MEMBER_VAL
related: Constraint
related: Member Selection
top concept of: SDMX Glossary 2.1

Category
type: Concept
comment: The Category can link to any identifiable object and can help discovery of structural metadata. In a data dissemination or data collection system the Category will probably link to a Dataflow or Metadataflow to support data or metadata discovery or data or metadata collection management. The Category can link to multiple identifiable objects and any identifiable object can link to multiple Categories, possibly in different Category Schemes. The link between a single Category and a single identifiable object is contained in a Categorisation.
requires: Concept
requires: Structural metadata
term status: upload
broader: Metadataflow
broader: Category Scheme
broader: Dataflow
broader: Structural metadata
definition: Structural metadata concept that classifies structural metadata objects.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CATEGORY
related: Metadataflow
related: Category Scheme
related: Categorisation
related: Dataflow
related: Structural metadata
top concept of: SDMX Glossary 2.1

Ownership sector
type: Concept
comment: Refers to the legal organisation and the principal functions, behaviour and objectives of the economic unit with which a job is associated.
requires: Statistical unit
term status: newTerm
definition: Disaggregation of economy by public or private ownership of the economic unit.
in scheme: SDMX Glossary 2.1
related: Job
related: Sector
related: Economic sector
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_ECON_OWNER
recommended representation: CodeListDatatype

Valuation
type: Concept
comment: Standard national accounts valuations include the basic price (what the seller receives) and the purchaser's price (what the purchaser pays). The purchaser's price is the basic price, plus taxes less subsidies on products, plus invoiced transportation and insurance services, plus distribution margin. Other valuation bases may be used in other contexts. International trade in goods considers the free on board (fob) price and cost-insurance-freight price, among others. The Concept refers to valuation rules used for recording flows and stocks, including how consistent the practices used are with internationally accepted standards, guidelines, or good practices.
requires: Statistical unit
term status: upload
definition: Definition of the price per unit, for goods and services flows and asset stocks.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).VALUATION
related: Concept
top concept of: SDMX Glossary 2.1
codelist ID: CL_VALUATION
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Expenditure according to purpose
type: Concept
comment: This concept is typically used in the SNA (System of National Accounts) where transactions are first analysed according to their nature, then, for certain sectors or kind of transactions, from the expenditure side, by purpose, answering the question "for what purpose?" The classifications supporting this concept are the following: Classification of the functions of government (COFOG); Classification of individual consumption by purpose (COICOP), Classification of the purposes of non-profit institutions serving households (COPNI); Classification of outlays of producers by purpose (COPP). The main purpose of these classifications is to provide statistics which experience has shown to be of general interest for a wide variety of analytical uses. For example, COICOP shows items such as household expenditure on food, health and education services all of which are important indicators of national welfare; COFOG shows government expenditure on health, education, defence, etc. and is also used to distinguish between collective services and individual consumption of goods and services provided by government.
requires: Institutional sector
term status: upload
definition: Breakdown of spending by institutional sectors between major expenditure functions.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).EXPENDITURE
related: Concept
related: Statistical indicator
related: Sector
related: Statistical classification
top concept of: SDMX Glossary 2.1
codelist ID: CL_COFOG; CL_COICOP; CL_COPNI; CL_COPP
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Non-sampling error
type: Concept
comment: Non-sampling errors may arise from many different sources such as defects in the sampling frame, faulty demarcation of sample units, defects in the selection of sample units, mistakes in the collection of data due to personal variations, misunderstanding, bias, negligence or dishonesty on the part of the investigator or of the interviewer, mistakes at the stage of the processing of the data, etc. Non-sampling errors may be categorised as: Coverage errors (or frame errors) due to divergences between the target population and the frame population; Measurement errors occurring during data collection; Nonresponse errors caused by no data collected for a population unit or for some survey variables; Processing errors due to errors introduced during data entry, data editing, sometimes coding and imputation; Model assumption errors.
requires: Attribute
term status: upload
broader: Coverage error
broader: Model assumption error
broader: Measurement error
broader: Imputation
broader: Attribute
definition: Error in sample estimates which cannot be attributed to sampling fluctuations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).NONSAMPLING_ERR
related: Accuracy - overall
related: Coverage error
related: Measurement error
related: Sampling error
related: Statistical unit
related: Accuracy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Measure
type: Concept
comment: For this statistical indicator: "Number of accidents per thousand of population", the measure is "Number of accidents". The terms "Measure" and "Statistical indicator" have often been used interchangeably, therefore the existing uses of the terms may differ from the definitions described here.
term status: upload
broader: Data Structure Definition
definition: Data element that represents a simple aggregation and which takes one or more vectors as arguments and returns a scalar.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MEASURE
related: Unit of measure
related: Concept
related: Statistical indicator
related: Data Structure Definition
top concept of: SDMX Glossary 2.1

Data collection method
type: Concept
comment: There are a number of data collection methods used for official statistics, including computer-aided personal or telephone interview (CAPI/CATI), mailed questionnaires, electronic or internet questionnaires, direct observation, administrative data sources, web-scraping and crowdsourcing sources. The data collection may be exclusively for statistical purposes, or primarily for non-statistical purposes.
term status: upload
broader: Quality management - quality assurance
definition: Method applied for gathering data for official statistics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COLL_METHOD
related: Data Source
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Data revision - studies
type: Concept
comment: Description of periodic studies related to data revisions. These studies can contain quantitative measures of the effects of revisions, such as mean revision and revision variance in estimates.
term status: upload
alternative label: Data revision studies
broader: Data revision
definition: Information about data revision studies and analyses.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REV_STUDY
related: Data revision - practice
related: Data revision
related: Measure
related: Data revision - policy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Comparability - over time
type: Concept
comment: Comparability over time refers to the degree of comparability between the results of two or several surveys related to the same domain, carried out by the same statistical agency.
term status: upload
alternative label: Comparability over time
broader: Comparability
definition: Extent to which statistics are comparable or reconcilable over time.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMPAR_TIME
related: Comparability
related: Comparability - geographical
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Quality management
type: Concept
comment: This metadata element refers to the application of a formalised system that documents the structure, responsibilities and procedures put in place for satisfying users, while continuing to improve the data production and dissemination process. It also includes how well the resources meet the requirement.
term status: upload
definition: Systems and frameworks in place within an organisation to manage the quality of statistical products and processes.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).QUALITY_MGMNT
related: Quality management - quality assessment
related: Quality management - quality assurance
related: Quality management - quality documentation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

SDMX Registry
type: Concept
comment: The functionality and behaviour of a repository for structural metadata is specified as part of the SDMX standard. In order for this repository to be compliant with the SDMX specification it must support the ability to accept for submission SDMX structural and Data Source metadata and the ability to accept an SDMX-compliant query for the metadata. An SDMX Registry is provided as a web service and the technical mechanisms used for the submission and query are specified in the SDMX Registry Specification and the SDMX Web Services Guidelines. It is not obligatory for an SDMX-compliant registry to support all of the SDMX structural metadata nor all of the varieties of methods of query and response specified in the SDMX Registry Specification and SDMX Web Services Guidelines. However, in order to be SDMX-compliant an SDMX Registry must comply with the SDMX Registry Specification and the SDMX Web Services Guidelines.
requires: Data Source
requires: Statistical Data and Metadata eXchange
requires: Structural metadata
term status: upload
broader: Data Source
broader: Statistical Data and Metadata eXchange
broader: Structural metadata
definition: Repository for structural metadata and registered Data Sources whose interfaces and behaviour comply with the SDMX technical standards.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_REG
related: Data Source
related: Statistical Data and Metadata eXchange
related: Notification
related: Structural metadata
related: SDMX Registry Interface (in the context of registry)
top concept of: SDMX Glossary 2.1

Break reason
type: Concept
comment: Time series breaks can be explained by changes to classifications, methodology, survey scope, data sources, etc.
requires: Series
requires: Attribute
term status: newTerm
definition: Attribute that describes the reason for a break in a time series.
in scheme: SDMX Glossary 2.1
related: Data Source
related: Series
related: Statistical classification
top concept of: SDMX Glossary 2.1
codelist ID: CL_BREAK_REASON
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Dissemination format
type: Concept
comment: This metadata element refers to the various means of dissemination used for making the data available to the public. It includes a description of the various formats available, including where and how to get the information (for instance paper, electronic publications, online databases).
term status: upload
definition: Media by which statistical data and metadata are disseminated.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DISS_FORMAT
related: Dissemination format - news release
related: Dissemination format - other formats
related: Dissemination format - online database
related: Dissemination format - microdata access
related: Dissemination format - publications
top concept of: SDMX Glossary 2.1
codelist ID: CL_ DISS_FORMAT
concept type: CrossDomainConcept
recommended representation: StringDatatype

Time format
type: Concept
comment: The technical time format and its related Codelist are part of the technical standards for SDMX-EDI and SDMX-XML. In version 2.0 of SDMX there is a recommendation to use the time format attribute to gives additional information on the way time is represented in the message. Following an appraisal of its usefulness this is no longer required. However, it is still possible, if required, to include the time format attribute in SDMX-ML.
requires: Representation
term status: upload
broader: Codelist
broader: SDMX-EDI
broader: Statistical Data and Metadata eXchange
broader: Representation
definition: Technical format for the representation of time.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TIME_FORMAT
related: Codelist
related: SDMX-EDI
related: Statistical Data and Metadata eXchange
related: SDMX-ML
related: Attribute
top concept of: SDMX Glossary 2.1
codelist ID: CL_TIME_FORMAT
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Timeliness - source data
type: Concept
comment: Compared to the parent concept - timeliness - this concept only covers the time period between the end of the reference period and the receipt of the data by the data compiling agency. This time period is determined by factors such as delays reflecting the institutional arrangements for data transmission.
requires: Compiling agency
requires: Reference period
term status: upload
broader: Timeliness
definition: Time between the end of a reference period and the actual receipt of the data by the compiling agency.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TIME_SOURCE
related: Concept
related: Time period
related: Compiling agency
related: Timeliness
related: Reference period
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Time period - collection
type: Concept
comment: This is not a stand-alone concept; it is related to the concept TIME_PERIOD which it further specifies (e.g. TIME_PERIOD "Monthly" and TIME_PER_COLLECT "End of period"). This concept is crucial in case of time period transformations.
requires: Time period
requires: Reference period
term status: upload
broader: Time period
definition: Segment(s) of the time period for which the observations have been collected (such as middle, average or end of period) for the target reference period.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TIME_PER_COLLECT
related: Concept
related: Time period
top concept of: SDMX Glossary 2.1
codelist ID: CL_TIME_PER_COLLECT
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Data revision - policy
type: Concept
comment: This metadata element is used to describe the general guidelines for handling data revisions applied by a data providing agency.
term status: upload
alternative label: Data revision policy
broader: Data revision
definition: Policy aimed at ensuring the transparency of disseminated data, whereby preliminary data are compiled that are later revised.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REV_POLICY
related: Data Provider
related: Data revision - practice
related: Data revision
related: Data revision - studies
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Structural validation
type: Concept
comment: In part the validation can be performed by processes that check the syntax of the data for conformance with the standard, e.g. a process for validating an XML instance (e.g. an SDMX Data Set) against the XML schema that defines the allowable structure and content of the instance. In SDMX the structural metadata contain additional metadata that can be used for validation but which cannot be expressed in an XML schema. Examples of these additional metadata include Constraints and Data Providers. The Constraint is used to specify the codes that are contained in a Codelist and which are valid for the type (sub set) of data that are to be expressed in Data Set in given context. The Data Provider specifies which type of data is expected or allowed to be reported or disseminated by a specific individual or organisation.
requires: Structural metadata
requires: Reference metadata
term status: upload
broader: Structural metadata
definition: Process to determine the validity of data and reference metadata using structural metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STRUCT_VALIDATION
related: Codelist
related: Data Provider
related: Code
related: Statistical Data and Metadata eXchange
related: Structural metadata
related: Reference metadata
related: Data Set
top concept of: SDMX Glossary 2.1

Population coverage
type: Concept
comment: The population coverage describes the types of population as regards their earnings, the types of education, etc., covered by the statistics whenever applicable.
term status: newTerm
definition: Definition of the main types of population covered by the statistics.
in scheme: SDMX Glossary 2.1
related: Geographical coverage
related: Sector coverage
related: Time coverage
related: Coverage
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Metadataflow
type: Concept
comment: A reference metadata set also has a set of structural metadata which describes how it is organised. This metadata identifies what reference metadata concepts are being reported, how these concepts relate to each other (typically as hierarchies), what their presentational structure is, how they may be represented (as free text, as coded values, etc.), and with which formal object types they are associated.
requires: Concept
requires: Reference metadata
term status: upload
alternative label: Metadata flow
broader: Hierarchy
broader: Structural metadata
broader: Reference metadata
definition: Collection of metadata concepts, structure and usage when used to collect or disseminate reference metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).METADATAFLOW
related: Concept
related: Hierarchy
related: Category
related: Dataflow
related: Structural metadata
related: Reference metadata
top concept of: SDMX Glossary 2.1

Statistical population
type: Concept
comment: There are two types of population: target population and survey population. A "target population" is the population outlined in the survey objects about which information is to be sought and a "survey population" is the population from which information is obtained in a survey. The target population is also known as the scope of the survey and the survey population as the coverage of the survey. For administrative Data Sources, the corresponding populations are the "target population", as defined by the relevant legislation and regulations, and the actual "client population".
term status: upload
broader: Data Source
definition: Total membership or population or "universe" of a defined class of people, objects or events.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STAT_POP
related: Data Source
related: Coverage
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Sector coverage
type: Concept
comment: This metadata element describes all applicable sectors associated with the Data Set. An example is "Production units and households" in environmental accounts.
requires: Sector
term status: upload
definition: Description of sectors covered by the statistics.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COVERAGE_SECTOR
related: Geographical coverage
related: Time coverage
related: Sector
related: Coverage
related: Statistical unit
related: Population coverage
related: Data Set
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Contact organisation unit
type: Concept
comment: This contact refers to the contact point for data and metadata.
term status: upload
alternative label: Organisation unit contact
broader: Contact
definition: Addressable subdivision of an organisation.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ORGANISATION_UNIT
related: Contact phone number
related: Contact name
related: Contact person function
related: Contact email address
related: Contact mail address
related: Contact organisation
related: Contact
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Reporting Category
type: Concept
comment: This is used to group Dataflows and Metadataflows to support data publication.
requires: Component
term status: upload
broader: Representation
definition: Component of a Reporting Taxonomy that gives structure to a report and links to data and metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REP_CATEGORY
related: Metadataflow
related: Reporting Taxonomy
related: Representation
related: Dataflow
top concept of: SDMX Glossary 2.1

Occupation
type: Concept
comment: The concept of "occupation" is defined as a set of jobs whose main tasks and duties are characterized by a high degree of similarity. Persons may be classified by occupation through their relationship to a present, past or future job. A "job" is defined as "the set of tasks and duties performed or meant to be performed by one person for a single economic unit" (19th International Conference of Labour Statisticians - ICLS). The latest international standard for classification of occupations is the 2008 International Standard Classification of Occupations (ISCO-08). The agency responsible for this topic is the International Labour Organization (ILO).
requires: Job
term status: upload
broader: Reference period
definition: Kind of work done in a job as defined by the main tasks and duties performed.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).OCCUPATION
related: Concept
related: Job
related: Statistical classification
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_OCCUPATION
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Structure Set
type: Concept
comment: The Structure Set can contain maps between two Item Schemes of the same type: Codelist, Concept Scheme, Organisation Unit Scheme, Data Provider Scheme, Data Consumer Scheme. The Structure Set can also contain a map between two Data Structures i.e. map of the Dimensions and Attributes and corresponding code values where these are also mapped. A typical use of Structure Sets is to provide mappings between an SDMX data structure used in an internal system with an SDMX structure of an external dataset when imported to or exported from the internal system.
requires: Component
term status: upload
broader: Codelist
broader: Concept Scheme
broader: Component
broader: Item Scheme
broader: Code
broader: Statistical Data and Metadata eXchange
broader: Dimension
broader: Data Consumer Scheme
broader: Organisation Unit Scheme
broader: Data Provider Scheme
broader: Attribute
broader: Data Set
definition: Maintainable collection of Structure Maps that link Components together in a source/target relationship where there is a semantic equivalence between the source and the target Components.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STRUCT_SET
related: Codelist
related: Concept Scheme
related: Item Scheme
related: Code
related: Map
related: Statistical Data and Metadata eXchange
related: Dimension
related: Data Consumer Scheme
related: Organisation Unit Scheme
related: Data Provider Scheme
related: Attribute
related: Data Set
top concept of: SDMX Glossary 2.1

Incremental update
type: Concept
comment: Such Data Sets contain only the data that need to be updated. For any one series the data may contain only attributes (i.e. no observations); or just data (i.e. no attributes); or a mixture of observations and attributes. Note that in an incremental update a set of data or metadata may omit mandatory attributes.
requires: Metadata Set
term status: upload
broader: Metadata Set
broader: Data Set
broader: Attribute
definition: Data or metadata message that is used for changing a part of the content of a Data or Metadata Set.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).INCREMENT_UPD
related: Series
related: Data Set
related: Attribute
top concept of: SDMX Glossary 2.1

Confidentiality - status
type: Concept
comment: This concept is related to data and determines the exact status of the value. i.e. if a specific value is confidential or not. This concept is always coded, i.e. it takes its value from the respective Codelist.
requires: Attribute
term status: upload
alternative label: Confidentiality status
broader: Confidentiality
definition: Information about the confidentiality status of the object to which this attribute is attached.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONF_STATUS
related: Codelist
related: Confidentiality - policy
related: Concept
related: Confidentiality - data treatment
related: Confidentiality - redistribution authorisation policy
related: Confidentiality
top concept of: SDMX Glossary 2.1
codelist ID: CL_CONF_STATUS
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Time lag
type: Concept
comment: This metadata element quantifies the interval of time between the release date of results and the date of reference for the data.
requires: Reference period
term status: updated
broader: Timeliness
definition: Interval of time (expressed in days, weeks, etc.) from the last day of the reference period to the day of publication of results.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TIMELAG_FINAL
related: Timeliness
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: ObsTimePeriodDatatype
recommended representation: TimeRangeDatatype

Processing error
type: Concept
comment: Sources of processing errors include all post-collection operations, as well as the printing of questionnaires. Most processing errors occur in data for individual units, although errors can also be introduced in the implementation of systems and estimates. In survey data, for example, processing errors may include transcription errors, coding errors, data entry errors and errors of arithmetic in tabulation.
term status: upload
definition: Error in final survey results arising from the faulty implementation of correctly planned implementation methods.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROCESSING_ERR
related: Coverage error
related: Model assumption error
related: Measurement error
related: Non-sampling error
related: Non-response error
related: Statistical unit
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Member Selection
type: Concept
comment: This is a part of a Constraint.
requires: Component
term status: upload
broader: Constraint
definition: Set of permissible values for one Component of a data or metadata structure.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MEMBER_SEL
related: Member Value
related: Constraint
top concept of: SDMX Glossary 2.1

Hierarchical Codelist
type: Concept
comment: The Codelist in SDMX can be hierarchical but it is capable of being processed as flat list as each Code can have only one parent code. A Hierarchical Codelist (HCL) is able to have multiple hierarchies and can have formal Levels. The Codes used in an HCL are derived from one or more Codelists therefore an HCL can combine Codes from multiple Codelists and define hierarchies from these Codes. For example, adding geographic codes such as continents or regions.
requires: Code
requires: Hierarchy
term status: upload
alternative label: Hierarchical Code list
alternative label: HCL
broader: Codelist
broader: Code
broader: Hierarchy
broader: Statistical Data and Metadata eXchange
definition: Organised collection of Codes that may be part of many parent/child relationships with other Codes in the scheme, as defined by one or more hierarchies of the scheme.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).HIERARCHIC_CODE_LIST
related: Codelist
related: Code
related: Hierarchy
related: Statistical Data and Metadata eXchange
top concept of: SDMX Glossary 2.1

Contact email address
type: Concept
term status: upload
broader: Contact
definition: E-mail address of the contact points for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_EMAIL
related: Contact phone number
related: Contact name
related: Contact person function
related: Contact mail address
related: Contact organisation unit
related: Contact organisation
related: Contact
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Cost and burden
type: Concept
comment: The cost is associated with a statistical product and can be financial, human or time-related. It may consist of staff costs, data collection costs and other costs related to reporting obligations. The burden is often measured by costs for the respondents (businesses, institutions, households, individuals) imposed by a statistical obligation. The overall burden of delivering the information depends on: a) the number of respondents; b) the average time required to provide the information, including time spent after receipt of the questionnaire ("recontact time"); and c) the hourly cost of a respondent's time.
term status: upload
alternative label: Cost burden
definition: Cost associated with the collection and production of a statistical product, as well as the burden imposed on respondents.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COST_BURDEN
related: Cost and burden - efficiency management
related: Cost and burden - resources
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

SDMX Information Model
type: Concept
comment: This model is represented in UML (Unified Modelling Language). Section Two of the SDMX technical standard (SDMX Information Model) describes the parts of the model that pertain to structural metadata. Additional structures that relate to Subscription (request to be notified of changes) and Notification (of the changes) are described in Section Five of the SDMX technical standard (Registry Specification). All implementation artefacts such as SDMX-ML and SDMX-EDI specifications for data and structures are derived from the SDMX Information Model and there is a close correlation between the model and these implementation artefacts. This close correlation results in the ability to build syntax and version independent software that can work at the level of the model but which support the various syntaxes and versions of the SDMX implementation artefacts.
requires: Statistical Data and Metadata eXchange
requires: Attribute
term status: upload
alternative label: SDMX-IM
broader: SDMX-EDI
broader: Notification
broader: Statistical Data and Metadata eXchange
broader: SDMX-ML
broader: Structural metadata
broader: Subscription
broader: Artefact
broader: Attribute
definition: Conceptual model for defining and describing the classes, attributes, and relationships of the SDMX standard.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_IM
related: Component
related: SDMX-JSON
related: SDMX-EDI
related: Notification
related: Statistical Data and Metadata eXchange
related: SDMX Technical Specification
related: Language
related: SDMX-ML
related: Structural metadata
related: Subscription
related: Artefact
top concept of: SDMX Glossary 2.1

Economic sector
type: Concept
comment: There is a general agreement on having a high-level breakdown of the economic activity in three main sectors: Primary (extraction, fishing, farming, etc.); Secondary (manufacturing); Tertiary (sales and services). Some authors add two new categories: Quaternary (information and knowledge-based services); Quinary (human services).
requires: Economic activity
term status: newTerm
definition: High-level grouping of economic activities based on the types of goods and services produced.=
in scheme: SDMX Glossary 2.1
related: Economic activity
related: Ownership sector
related: Category
related: Sector
top concept of: SDMX Glossary 2.1
codelist ID: CL_ACTIVITY
concept type: CrossDomainConcept
recommended representation: CodeListPartialDatatype

Validation and Transformation Language
type: Concept
comment: This logical formalisation of validation and transformation rules can be implemented in several programming languages for execution (SAS, R, Java, SQL, etc.), but will provide a "neutral" expression of the processing taking place.
requires: Language
requires: Statistical unit
term status: upload
alternative label: VTL
definition: Statistics-oriented language and information model used to express logical validation rules and transformations on data, whether described as a dimensional table or as unit-record data.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).VTL
related: Language
top concept of: SDMX Glossary 2.1

Sex
type: Concept
comment: This concept is applied if data need to be categorised by sex. The concept is in general coded, i.e. represented through a Codelist. It applies not only to human beings but also to animals and other living organisms.
term status: upload
broader: Codelist
definition: State of being male or female.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SEX
related: Codelist
related: Concept
top concept of: SDMX Glossary 2.1
codelist ID: CL_SEX
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Confidentiality - policy
type: Concept
comment: This metadata element is used to provide textual descriptions and references to legislation or other rules related to statistical confidentiality. It should provide the assurance that all necessary methods assuring confidentiality have been applied to the data.
requires: Measure
term status: upload
alternative label: Confidentiality policy
broader: Confidentiality
definition: Legislative measures or other formal procedures which prevent unauthorised disclosure of data that identify a person or economic entity either directly or indirectly.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONF_POLICY
related: Confidentiality - data treatment
related: Confidentiality - status
related: Confidentiality - redistribution authorisation policy
related: Confidentiality
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Base weight
type: Concept
requires: Base period
term status: upload
broader: Base period
definition: Weight of a weighting system for an index number computed according to the information relating to the base period instead, for example, of the current period.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).BASE_WEIGHT
related: Base period
top concept of: SDMX Glossary 2.1
codelist ID: CL_BASE_WEIGHT
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype
recommended representation: DecimalDatatype

Push (reporting method)
type: Concept
comment: Different data collecting organisations have varying methods of implementing a push reporting method. Most of these use web technology or email.
requires: Reference metadata
term status: upload
broader: Reference metadata
definition: Data or reference metadata reporting method that requires the provider to make the information available by means of transfer such as email or other electronic method.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PUSH_METHOD
related: Pull (reporting method)
top concept of: SDMX Glossary 2.1

Professionalism
type: Concept
comment: To retain trust in official statistics, the statistical agencies need to decide according to strictly professional considerations, including scientific principles and professional ethics, on the methods and procedures for the collection, processing, storage and presentation of statistical data (United Nations Fundamental Principles of Official Statistics, principle 2). This metadata element describes the elements providing assurances that: statistics are produced on an impartial basis; elements providing assurances that the choices of sources and statistical techniques as well as decisions about dissemination are informed solely by statistical considerations; elements providing assurances that the recruitment and promotion of staff are based on relevant aptitude; elements providing assurances that the statistical entity is entitled to comment on erroneous interpretation and misuse of statistics, guidelines for staff behaviour and procedures used to make these guidelines known to staff; other practices that provide assurances of the independence, integrity, and accountability of the statistical agency.
term status: upload
broader: Comment
definition: Standard, skill and ability suitable for producing statistics of good quality.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROF
related: Professionalism - code of conduct
related: Professionalism - impartiality
related: Professionalism - methodology
related: Professionalism - statistical commentary
related: Comment
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Statistical subject-matter domain
type: Concept
comment: Within SDMX, the list of statistical subject-matter domains (aligned to the Classification of International Statistical Activities maintained by the Conference of European Statisticians of the United Nations Economic Commission for Europe, UNECE) is a standard reference list against which the categorisation schemes of various participants in exchange arrangements can be mapped to facilitate data and metadata exchange. This allows the identification of subject-matter domain groups involved in the development of guidelines and recommendations relevant to one or more statistical domains. Each of these groups could define domain-specific Data Structure Definitions, Concepts, etc.
requires: Concept
term status: upload
alternative label: Domain Subject-matter domain
alternative label: Statistical domain
broader: Content-Oriented Guidelines
definition: Statistical activity that has common characteristics with respect to concepts and methodologies for data collection, manipulation and transformation.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STAT_SUBJECT_MATTER
related: Concept
related: Statistical Data and Metadata eXchange
related: Content-Oriented Guidelines
related: Data Structure Definition
related: Categorisation
related: Statistical classification
top concept of: SDMX Glossary 2.1

Classification system
type: Concept
comment: When relevant, deviations from statistical standards, guidelines, or good practices, should be documented.
requires: Data Set
term status: upload
broader: Data Set
definition: Metadata element used to a) list the classification(s) being used for a given Data Set or set of Data Sets, and b) describe how these conform to internationally agreed standards, guidelines, or good practices.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CLASS_SYSTEM
related: Statistical classification
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Statistical concepts and definitions
type: Concept
comment: This metadata element is used to define and describe the types of variables provided (raw figures, annual growth rates, index, flow or stock data, etc.) referring to internationally accepted statistical standards, guidelines, or good practices on which the concepts and definitions that are used for compiling the statistics are based. Discrepancies should be documented.
requires: Statistical variable
term status: upload
broader: Statistical subject-matter domain
broader: Measure
definition: Definitions and descriptions of the main variables provided.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).STAT_CONC_DEF
related: Statistical variable
related: Concept
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Coverage
type: Concept
comment: This metadata element is used to describe the dimensions delimiting the statistics produced, e.g. geographical, products, economic and other sectors, industry, occupation, transactions, etc., as well as relevant exceptions and exclusions. It can also specify the period of time for which data are provided. The term "Coverage" describes the scope of the data compiled, rather than the characteristics of the survey.
term status: newTerm
definition: Definition of the scope of the data compiled.
in scheme: SDMX Glossary 2.1
related: Geographical coverage
related: Sector coverage
related: Coverage error
related: Time coverage
related: Dimension
related: Sector
related: Occupation
related: Population coverage
top concept of: SDMX Glossary 2.1
codelist ID: CL_COVERAGE
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Reference period
type: Concept
comment: In many cases, the reference period and time period will be identical, but there are also cases where they are different. This can happen if data are not available for the target reference period, but are available for a time period which is judged to be sufficiently close. For example, the reference period may be a calendar year, whereas data may only be available for a fiscal year. In such cases, "reference period" should refer to the target reference period rather than the actual time period of the data. The difference between target and actual reference period can be highlighted in a free text note.
term status: upload
broader: Time period
definition: Timespan or point in time to which the measured observation is intended to refer.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REF_PERIOD
related: Time period
related: Base period
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: ObsTimePeriodDatatype

Artefact
type: Concept
comment: Artefacts provide features which are reusable by derived elements to support general functionality such as identity, versioning etc. Examples of SDMX artefacts are "Identifiable Artefacts " and "Maintainable Artefacts".
requires: Concept
requires: Statistical Data and Metadata eXchange
term status: upload
broader: Maintainable Artefact
broader: Statistical Data and Metadata eXchange
broader: Identifiable Artefact
definition: Abstract concept denoting an element in the SDMX model having specific characteristics which are inherited by other elements.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ARTEFACT
related: Maintainable Artefact
related: Statistical Data and Metadata eXchange
related: Identifiable Artefact
related: Versionable Artefact
related: Annotable Artefact
related: Nameable Artefact
top concept of: SDMX Glossary 2.1

Data Provider
type: Concept
comment: Data Providers are maintained in a Data Provider Scheme. The Data Provider can be linked to the type of data (Dataflow) or reference metadata (Metadataflow) that it reports or disseminates. This link provides the data collection system or data dissemination system.
requires: Reference metadata
term status: upload
alternative label: Data providing agency
broader: Metadataflow
broader: Data Provider Scheme
broader: Dataflow
broader: Reference metadata
definition: Organisation or individual that reports or disseminates data or reference metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_PROVIDER
related: Metadataflow
related: Item Scheme
related: Data Provider Scheme
related: Dataflow
related: Reference metadata
top concept of: SDMX Glossary 2.1
codelist ID: CL_ORGANISATION
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Category Scheme
type: Concept
comment: The Category Scheme comprises a hierarchy of Categories which may include any type of useful classification for the organisation of data and metadata.
requires: Category
term status: upload
broader: Hierarchy
broader: Category
definition: Descriptive information for a subdivision of categories into groups based on characteristics, which the objects have in common.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CATEGORY_SCH
related: Item Scheme
related: Hierarchy
related: Category
related: Statistical classification
top concept of: SDMX Glossary 2.1

Sibling group
type: Concept
comment: Originally from SDMX-EDI a sibling group is uniquely identified by a Data Set identifier combined with the sibling group key.
requires: Dimension
requires: Series
term status: upload
broader: SDMX-EDI
broader: Dimension
broader: Data Set
definition: Set of time series whose Keys differ only in the value taken by the frequency Dimension.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SIBLING_GR
related: SDMX-EDI
related: Series Key
related: Data Set
top concept of: SDMX Glossary 2.1

Statistical Data and Metadata eXchange
type: Concept
comment: SDMX is an ISO standard designed to describe statistical data and metadata, normalise their exchange, and improve their efficient sharing across organisations. The SDMX initiative is sponsored by seven international organisations (Bank of International Settlements (BIS), European Central Bank (ECB), Eurostat, International Monetary Fund (IMF), Organisation for Economic Co-operation and Development (OECD), United Nations Statistical Division (UNSD) and World Bank) to facilitate the exchange of statistical data and metadata using information technologies. This standard provides an integrated approach to facilitating statistical data and metadata exchange, enabling interoperable implementations within and between systems concerned with the exchange, reporting and dissemination of statistical data and their related meta-information. It is not just a format for data exchange: it includes a set of technical standards and content-oriented guidelines, and is supported by an IT architecture and tools to be used for the efficient exchange and sharing of statistical data and metadata. Taken together, those elements may be used to support improved business processes for any statistical organisation.
requires: Content-Oriented Guidelines
term status: upload
alternative label: SDMX
broader: Content-Oriented Guidelines
definition: Technical standard and content-oriented guidelines for the exchange and sharing of statistical information between organisations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX
related: Content-Oriented Guidelines
related: Data exchange
top concept of: SDMX Glossary 2.1

Quality management - quality assurance
type: Concept
comment: This metadata element refers to all the planned and systematic activities implemented that can be demonstrated to provide confidence that the data production processes will fulfil the requirements for the statistical output. This includes the design of programmes for quality management, the description of planning process, scheduling of work, frequency of plan updates, and other organisational arrangements to support and maintain planning function.
requires: Measure
term status: upload
alternative label: Quality assurance
broader: Quality management
definition: Guidelines focusing on quality in general and dealing with quality of statistical programmes, including measures for ensuring the efficient use of resources.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).QUALITY_ASSURE
related: Quality management - quality assessment
related: Quality management
related: Quality management - quality documentation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Identifiable Artefact
type: Concept
comment: In SDMX the identity comprises a mandatory Id and some optional attributes. Identifiable Artefacts inherit the capability of having Annotations.
term status: upload
broader: Annotation
broader: Statistical Data and Metadata eXchange
broader: Attribute
definition: Construct that contains structures capable of providing identity to an object.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).IDENTIFIABLE_ART
related: Annotation
related: Maintainable Artefact
related: Statistical Data and Metadata eXchange
related: Versionable Artefact
related: Annotable Artefact
related: Attribute
related: Nameable Artefact
related: Artefact
top concept of: SDMX Glossary 2.1

Contact mail address
type: Concept
term status: upload
broader: Contact
definition: Postal address of the contact points for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_MAIL
related: Contact phone number
related: Contact name
related: Contact person function
related: Contact email address
related: Contact organisation unit
related: Contact organisation
related: Contact
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Observation status
type: Concept
comment: This item is normally coded and uses codes providing information about the status of a value, with respect to events such as "break", "estimated value", "forecast", "missing value", or "provisional value". In some cases, there is more than one event that may have influenced the value (e.g. a break in methodology may be accompanied with the fact that an observation is an estimate).
term status: upload
broader: Code
definition: Information on the quality of a value or an unusual or missing value.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).OBS_STATUS
related: Code
top concept of: SDMX Glossary 2.1
codelist ID: CL_OBS_STATUS
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Dissemination agency
type: Concept
comment: This metadata element is needed in order to differentiate the compiling organisation from the organisation disseminating the data. The dissemination agency could be different from the reporting agency and the compilation agency.
term status: newTerm
definition: Organisation disseminating the data being reported.
in scheme: SDMX Glossary 2.1
related: Reporting agency
related: Compiling agency
top concept of: SDMX Glossary 2.1
codelist ID: CL_ORGANISATION
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Standard Annotation
type: Concept
comment: A drawback of the Annotation construct is that it conveys no semantics. Annotations are containers for additional information relating to the Artefact to which they are attached. This means that for an Annotation to be interpreted in the same way by exchange partners a reference is needed that defines some standard behaviour and implementation. When implemented in systems and applications standard Annotations are often referred to as "actionable Annotations" or "machine-actionable Annotations".
term status: newTerm
definition: Information that is structured in a predefined way so that exchange partners can understand its content in an unambiguous way, and machines can parse the information and perform a specific action in response.
in scheme: SDMX Glossary 2.1
related: Annotation
related: Artefact
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: ConceptSchemeDatatype

Data Structure Definition for global use
type: Concept
comment: A DSD for global use is meeting one of the two criteria below: 1) It is designed as a standard data structure for global use (i.e. having a very wide geographical coverage or cross-domain nature), with more than one SDMX sponsor organisation represented in the ownership group and one of the members of the ownership group acting as maintenance agency on behalf of the ownership group; 2) DSDs labelled as "global" by the SDMX sponsors considering the recognised expertise in the domain concerned of one of the organisations represented in the ownership group and the potential usefulness of the artefact for the whole SDMX community; in this case the DSD will have to meet strict criteria of versioning, governance, maintenance, adoption and endorsement.
requires: Data Structure Definition
term status: upload
alternative label: DSD for global use
alternative label: Global DSD
broader: Ownership group
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Maintenance agency
broader: Artefact
definition: DSD agreed by a number of international organisations for use within their respective constituencies.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DSD_GLOBAL
related: Ownership group
related: Geographical coverage
related: Statistical Data and Metadata eXchange
related: Data Structure Definition
related: Maintenance agency
related: Local Data Structure Definition
related: Artefact
top concept of: SDMX Glossary 2.1

Documentation on methodology - advance notice
type: Concept
comment: This metadata element informs users in advance about major changes in methodology, source data, and statistical techniques.
term status: upload
alternative label: Documentation on methodology advance notice
broader: Documentation on methodology
definition: Policy on notifying the public of changes in methodology, indicating whether the public is notified before a methodological change affects disseminated data and, if so, how long before.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ADV_NOTICE
related: Documentation on methodology
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Data description
type: Concept
comment: This summary description should provide an immediate understanding of the data to users (also to those who do not have a broader technical knowledge of the Data Set in question). Data can be displayed to users as tables, graphs or maps. According to the United Nations' Fundamental Principles of Official Statistics, the choice of appropriate presentation methods should be made in accordance with professional considerations. Data presentation includes the description of the Data Set disseminated with the main variables covered, the classifications and breakdowns used, the reference area, a summary information on the time period covered and, if applicable, the base period used.
requires: Statistical indicator
requires: Data Set
term status: upload
alternative label: Detailed description of data representation
broader: Time period
broader: Reference area
broader: Base period
broader: Data Set
definition: Metadata element describing the main characteristics of the Data Set in an easily understandable manner, referring to the main data and indicators disseminated.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_PRES
related: Statistical variable
related: Time period
related: Reference area
related: Base period
related: Statistical classification
related: Data Set
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Sector
type: Concept
comment: "Sector" is a specific term used in the United Nations System of National Accounts (SNA) to denote one of the mutually exclusive institutional sectors that group together institutional units on the basis of their principal functions, behaviour and objectives: nonfinancial corporations, financial corporations, general government, non-profit institutions serving households (NPISHs), and households. A sector can be a subgroup of an economic activity - as in "coal mining sector" - or a group of economic activities - as in "service sector" - or a cross-section of a group of economic activities - as in "informal sector".
requires: Statistical classification
term status: newTerm
definition: Classification of statistical entities engaged in similar kinds of activities.
in scheme: SDMX Glossary 2.1
related: Economic activity
related: Economic sector
related: Institutional sector
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_SECTOR
recommended representation: CodeListDatatype

isIncluded
type: Concept
comment: This is used in validity Constraints to specify if the Constraint lists the items that are included in the list of valid contents, or are to be excluded from the list of valid contents.
term status: upload
definition: Construct that indicates whether the contained values of a container object is to be included or excluded from the valid list of values.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).IS_INCLUDED
related: Constraint
top concept of: SDMX Glossary 2.1

Labour force status
type: Concept
comment: Persons of working age may be classified in a short reference period according to their labour force status as being employed, unemployed, or outside the labour force. The three main categories of labour force status are mutually exclusive and exhaustive. The labour force status of a person is established based on the activity principle, one hour-criterion and short reference period. While even during a short period, persons may be engaged in multiple activities, in the labour force status classification priority is given to 1-hour of employment over other activities; and to unemployment over outside the labour force. The latest international standards on this topic are contained in the Resolution concerning statistics of work, employment and labour underutilization adopted by the 19th International Conference of Labour Statisticians (ICLS) in 2013. The agency responsible for this topic is the International Labour Organization.
requires: Age
requires: Reference period
requires: Statistical classification
term status: newTerm
definition: Classification of the working age population based on the person's relation to the labour market in a short reference period.
in scheme: SDMX Glossary 2.1
related: Age
related: Category
related: Reference period
related: Statistical classification
top concept of: SDMX Glossary 2.1
codelist ID: CL_LABOUR_FORCE_STATUS
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Attribute
type: Concept
comment: The specific statistical object in a Data Set can be a Data Set, Observation, Series Key or partial key, and in a Metadata Set can be any object in the SDMX Information Model. Concepts such as units, magnitude, currency of denomination, titles (these are all commonly specified as attributes in a data structure) and methodological comments, quality statements (commonly specified as attributes in a metadata structure ) can be used as attributes in the context of an agreed data exchange. The Attribute Value is the reported value in a Data Set or a Metadata Set such as a specific currency or a specific dissemination policy applicable to the object to which the Attribute Value is attached.
requires: Concept
term status: upload
broader: Data Structure Definition
definition: Statistical concept providing qualitative information about a specific statistical object.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ATTRIBUTE
related: Concept
related: Constraint
related: Title
related: Metadata Structure Definition
related: Series Key
related: SDMX Information Model
related: Attribute Relationship
related: Data Set
related: Currency
related: Data Structure Definition
related: Comment
related: Attachment level
related: Dataflow
related: Metadata Set
related: Statistical unit
top concept of: SDMX Glossary 2.1

Coherence - internal
type: Concept
comment: This metadata element is used to describe the differences in the statistical results calculated for the same statistical domain, based on stable or changing methodology (e.g. between provisional and final statistics or between different reference years showing break in series). Frequently, a group of statistics of a different type (in monetary value, in volume or constant price, price indicators, etc.) measures the same phenomenon using different methodologies. For instance, statistics on employment, depending on whether they result from employers' declarations or household surveys do not lead exactly to the same results. However, there are often differences in the concepts used (e.g. de jure or de facto population), in the registration date, in the cif/fob registration for external trade, etc. It is very important to check that these representations do not diverge too much in order to anticipate users' questions and for preparing corrective actions.
requires: Data Set
term status: upload
alternative label: Internal coherence
broader: Coherence
definition: Extent to which statistics are consistent within a given Data Set.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COHER_INTERNAL
related: Coherence - cross domain
related: Concept
related: Statistical indicator
related: Coherence
related: Statistical subject-matter domain
related: Series
related: Representation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Education level
type: Concept
comment: The International Standard Classification of Education (ISCED), maintained by the Institute for Statistics (UIS) of the United Nations Educational, Scientific and Cultural Organisation (UNESCO), is used to classify programmes and their resulting qualifications into levels and fields of education. It is a widely-used global reference classification for education systems which provides a comprehensive framework for organising education programmes and qualifications by applying uniform and internationally agreed definitions to facilitate comparisons of education systems across countries. ISCED is the international framework for assembling, compiling and analysing cross-nationally comparable data related to students, teachers, educational attainment and education expenditure. ISCED 2011 is the second major revision of this classification (initially developed in the 1970s and revised in 1997). It was adopted by the UNESCO General Conference in November 2011.
term status: upload
alternative label: Level of education
alternative label: Level of educational programme
definition: Ordered set which groups and classifies education programmes according to the knowledge, skills, competencies and qualifications which they are designed to impart.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).EDUCATION_LEV
related: Statistical classification
top concept of: SDMX Glossary 2.1
codelist ID: CL_EDUCATION_LEV
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Bilateral exchange
type: Concept
comment: Apart from bilateral exchange, the SDMX initiative identifies two other basic forms of exchange of statistics and metadata between organisations, i.e. multilateral exchange and data-sharing.
term status: newTerm
definition: Exchange of data and/or metadata between a sending organisation and a receiving organisation where all aspects of the exchange process are agreed between counterparties, including the mechanism for exchange of data and metadata, the formats, the frequency or schedule, and the mode used for communications regarding the exchange.
in scheme: SDMX Glossary 2.1
related: Statistical Data and Metadata eXchange
related: Data sharing
related: Data exchange
related: Multilateral exchange
top concept of: SDMX Glossary 2.1
recommended representation: StringDatatype

Time period
type: Concept
comment: The observation corresponds to a specific point in time (e.g. a single day) or a period (e.g. a month, a fiscal year, or a calendar year). This is used as a time stamp and is of particular importance for time series data. In cases where the actual time period of the data differs from the target reference period, "time period" refers to the actual period.
term status: upload
broader: Reference period
definition: Timespan or point in time to which the observation actually refers.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).TIME_PERIOD
related: Time period - collection
related: Series
related: Reference period
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: ObsTimePeriodDatatype

Dissemination format - other formats
type: Concept
comment: Examples of other dissemination formats are analytical publications edited by policy users. This concept includes, as a sub-element, "Supplementary data", i.e. any customised tabulation that can be provided to meet specific requests (including information on procedures for obtaining access to these data).
term status: upload
alternative label: Other dissemination format
broader: Dissemination format
definition: References to the most important other data dissemination done.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DISS_OTHER
related: Dissemination format - news release
related: Concept
related: Dissemination format
related: Dissemination format - online database
related: Dissemination format - microdata access
related: Dissemination format - publications
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Technical information
type: Concept
comment: This metadata element can be used to describe IT aspects about the data, e.g. the storage system used, or technical systems related to the exchange.
term status: newTerm
definition: Technical details related to the data.
in scheme: SDMX Glossary 2.1
related: Recommended uses and limitations
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Attribute Relationship
type: Concept
comment: A part of the specification of Attribute in a Data Structure Definition denotes to which part of the data the Attribute can relate in a Data Set. This can be the entire Data Set, specific grouping of the Dimensions, or an Observation. This is a version 2.1 construct. In version 2.0 this was known as the "attachment level".
requires: Data Set
requires: Attribute
requires: Artefact
term status: upload
broader: Data Structure Definition
broader: Dimension
broader: Attachment level
broader: Artefact
broader: Data Set
broader: Attribute
definition: Specification of the type of artefact to which a data attribute can be attached in a Data Set.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ATTRIBUTE_REL
related: Data Structure Definition
related: Dimension
related: Attachment level
related: Data Set
related: Attribute
top concept of: SDMX Glossary 2.1

Relevance - user satisfaction
type: Concept
comment: In quality assurance frameworks this element indicates how the views and opinions of the users are collected. If user satisfaction surveys are conducted, the way users' views and opinions are collected should be described and the main results shown (in the form of a user satisfaction index if available); the date of the most recent user satisfaction survey should also be mentioned. Otherwise, any other indication or measure to determine user satisfaction might be used.
term status: upload
alternative label: Relevance user satisfaction
broader: Relevance
definition: Description of how well the disseminated statistics meet the expressed user needs.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).USER_SAT
related: Relevance - user needs
related: Quality management - quality assurance
related: Measure
related: Relevance
related: Relevance - completeness
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Reference metadata
type: Concept
comment: Preferably, reference metadata should include all of the following: a) "conceptual" metadata, describing the concepts used and their practical implementation, allowing users to understand what the statistics are measuring and, thus, their fitness for use; b) "methodological" metadata, describing methods used for the generation of the data (e.g. sampling, collection methods, editing processes); and c) "quality" metadata, describing the different quality dimensions of the resulting statistics (e.g. timeliness, accuracy). Note that (a) does not define the actual structure of a Data Set in terms of concepts used, their representation, and role (Dimensions, Attributes, Measures) in a data structure. These metadata are referred to as Structural Metadata.
term status: upload
broader: Dimension
broader: Timeliness
broader: Measure
broader: Representation
broader: Structural metadata
broader: Attribute
broader: Data Set
definition: Metadata describing the contents and the quality of the statistical data.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REF_METADATA
related: Concept
related: Metadata Structure Definition
related: Measure
related: Structural metadata
related: Cross-domain Concept
related: Data Set
related: Concept Scheme
related: Dimension
related: Timeliness
related: Representation
related: Metadata Set
related: Structural validation
related: Attribute
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept

Data validation
type: Concept
comment: Data validation describes methods and processes for assessing statistical data, and how the results of the assessments are monitored and made available to improve statistical processes. All the controls made in terms of quality of the data to be published or already published are included in the validation process. Validation also takes into account the results of studies and analysis of revisions and how they are used to improve statistical processes. In this process, two dimensions can be distinguished: (i) validation before publication of the figures and (ii) validation after publication.
requires: Data compilation
term status: upload
broader: Dimension
broader: Data compilation
definition: Process of monitoring the results of data compilation and ensuring the quality of the statistical results.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_VALIDATION
related: Dimension
related: Data compilation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Accuracy - overall
type: Concept
comment: This metadata element is used to describe the main sources of random and systematic error in the statistical outputs, and provide a summary assessment of all errors with special focus on the impact on key estimates. The bias assessment can be in quantitative or qualitative terms, or both. It should reflect the producer's best current understanding (sign and order of magnitude) including actions taken to reduce bias. Revision aspects should also be included here if considered relevant.
requires: Component
requires: Measure
requires: Accuracy
requires: Data Set
term status: upload
alternative label: Overall accuracy
broader: Accuracy
definition: Assessment of accuracy, linked to a certain Data Set or domain, which is summarising the various components into one single measure.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ACCURACY_OVERALL
related: Non-sampling error
related: Sampling error
related: Accuracy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

SDMX-JSON
type: Concept
comment: SDMX-JSON is a data exchange format for data discovery and data visualisation on the web. It conforms to JSON (JavaScript Object Notation) standard specification, and it supports the SDMX 2.1 Information Model. SDMX-JSON is compatible with the SDMX RESTful Web Services API, and it supports all features of the SDMX RESTful API for data queries. The SDMX-JSON data exchange format is documented in the SDMX-JSON Data Message specification.
requires: Statistical Data and Metadata eXchange
term status: upload
broader: Statistical Data and Metadata eXchange
definition: JSON format for the dissemination of SDMX-structured data and metadata on the web.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_JSON
related: Statistical Data and Metadata eXchange
related: Data exchange
related: SDMX Information Model
top concept of: SDMX Glossary 2.1

Global Registry
type: Concept
comment: The SDMX Global Registry is the central reference point and authoritative source for SDMX global Data Structure Definitions and related objects. The contents of the Global Registry are subject to the SDMX Global Registry content policy which defines the criteria that the SDMX artefacts must meet before the artefacts can be included in the Global Registry.
requires: Statistical Data and Metadata eXchange
requires: Structural metadata
term status: upload
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Structural metadata
broader: Artefact
definition: Central and discoverable repository for SDMX structural metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).GLOBAL_REGISTRY
related: Statistical Data and Metadata eXchange
related: Data Structure Definition
related: Artefact
top concept of: SDMX Glossary 2.1

Reference area
type: Concept
comment: The concept refers to the country, geographical or political group of countries or regions within a country. The concept is subject to a variety of hierarchies, as countries comprise territorial entities that are states (as understood by international law and practice), regions and other territorial entities that are not states but for which statistical data are produced internationally on a separate and independent basis.
term status: upload
broader: Hierarchy
definition: Country or geographic area to which the measured statistical phenomenon relates.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REF_AREA
related: Counterpart reference area
related: Geographical coverage
related: Concept
related: Hierarchy
top concept of: SDMX Glossary 2.1
codelist ID: CL_AREA
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Data Structure Definition
type: Concept
comment: A DSD defines the structure of an organised collection of data (Data Set) by means of Concepts with specific roles, and their representation. In order to exchange or disseminate statistical information, an institution needs to specify which statistical concepts are necessary for identifying the series (and for use as Dimensions) and which statistical concepts are to be used as attributes and measures. These definitions form the Data Structure Definition. In a data collection scenario the specification of the Data Structure Definition is often a collaborative venture between the collecting institution and its partners. There are three types of construct in the DSD: Dimension, Attribute, and Measure. Each of these combines a Concept with its representation (this can be either a reference to a Codelist or a non-coded data type such as "integer", "string", or one of the "date/time" types. The roles of the three types of construct (Dimension, Attribute, and Measure) are as follows: A Dimension is an identifying Component, sometimes referred to as a "classificatory variable". When a value is given to each of the Dimensions in a Data Set (this is often called a "Key" or a "series") the resulting Key, when combined with a time value, uniquely identifies an observation. For instance, country, indicator, measurement unit, frequency, and Time Dimensions together identify the cells in a cross-country time series with multiple indicators (e.g. gross domestic product, gross domestic debt) measured in different units (e.g. various currencies, percent changes) and at different frequencies (e.g. annual, quarterly). The cells in such a multi-dimensional table contain the Observation Values. The DSD construct that specifies the Concept and expected representation of an observation is called a Measure. The semantics of the measure is derived from the Dimensions or a sub set of them and, if not specified in a Dimension, an Attribute indicating the measurement unit e.g. indicator and mea…
requires: Concept
requires: Dimension
requires: Measure
requires: Representation
requires: Structural metadata
requires: Attribute
requires: Data Set
term status: upload
alternative label: DSD
broader: Data Set
definition: Set of structural metadata associated to a Data Set, which includes information about how Concepts are associated with the Measures, Dimensions, and Attributes of a data cube, along with information about the Representation of data and related descriptive metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DSD
related: Codelist
related: Unit of measure
related: Statistical variable
related: Concept
related: Title
related: Measure
related: Data Set
related: Component
related: Currency
related: Confidentiality - status
related: Statistical indicator
related: Dimension
related: Series
related: Representation
related: Statistical unit
related: Attribute
top concept of: SDMX Glossary 2.1

Comparability - geographical
type: Concept
comment: Geographical comparability refers to the degree of comparability between similar survey results measuring the same phenomenon across geographical areas or regions. The surveys are in general conducted by different statistical agencies, referring to populations in different geographical areas, sometimes based on a harmonised methodology.
term status: upload
alternative label: Geographical comparability
broader: Comparability
definition: Extent to which statistics are comparable between geographical areas.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COMPAR_GEO
related: Comparability
related: Comparability - over time
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Series
type: Concept
comment: Series are an ordered sequence of qualitative or quantitative data samples or observations used to predict or demonstrate trends through time and space. The series can be classified by the criteria used to arranged them: time (historical or chronological), geolocation (spatial or geographical), occurrence (condition or frequency). Time series is a basic building block of many datasets. It groups data that share the same dimension values except for the time dimension, allowing users to see changes in data over time, holding all other dimensions constant. Series is the generic concept, of which time series is the most common example. A series can be disambiguated by any single dimension, as long as the values for other dimensions do not change.
requires: Dimension
term status: newTerm
alternative label: Time series
definition: Set of data observations disambiguated by the values of a single dimension, usually time.
in scheme: SDMX Glossary 2.1
related: Concept
related: Break reason
related: Series Key
related: Dimension
related: Data Set
top concept of: SDMX Glossary 2.1

Sampling error
type: Concept
comment: Sampling errors are distinct from errors due to imperfect selection, bias in response or estimation, errors of observation and recording, etc. For probability sampling, the random variation due to sampling can be calculated. For non-probability sampling, random errors cannot be calculated without reference to some kind of model. The totality of sampling errors in all possible samples of the same size generates the sampling distribution of the statistic which is being used to estimate the parent value.
term status: upload
definition: Part of the difference between a population value and an estimate thereof, derived from a random sample, which is due to the fact that only a subset of the population is enumerated.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SAMPLING_ERR
related: Accuracy - overall
related: Non-sampling error
related: Accuracy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Data extraction date
type: Concept
comment: This information is in the Header of a Data Set, typically for processing by the receiving system in its administration of the Data Set.
requires: Data Source
term status: upload
broader: Data Source
broader: Data Set
definition: Date and time that the data are gathered from a Data Source.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).DATA_EXTRACT_DATE
related: Data Set
top concept of: SDMX Glossary 2.1

Attachment level
type: Concept
comment: For each attribute specified in a data structure, there is a definition of whether this attribute takes a: value for each observation in the Data Set; value for each time series in the Data Set; value for each group in the Data Set; single value for the entire Data Set. Some metadata concepts (e.g. frequency) may not be meaningful at the observation level, but only when applied to a higher level (e.g. to a time series of observations). Time, on the other hand, is meaningful at observation level, because every observation is associated with a specific point or period in time. Data Structure Definitions and Metadata Structure Definitions provide information about the level at which a particular concept descriptor is relevant: at observation level, time series level, group level, dataset level or even Agency level. This is known as the "attachment level" of the concept. This is a version 2.0 construct. In version 2.1 this is known as the "Attribute Relationship".
requires: Attribute
term status: upload
broader: Attribute
definition: Property of an attribute defining the object to which data or metadata are linked.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ATTACHMENT_LEV
related: Concept
related: Metadata Structure Definition
related: Data Structure Definition
related: Series
related: Attribute Relationship
related: Data Set
related: Attribute
top concept of: SDMX Glossary 2.1

Codelist
type: Concept
comment: The SDMX technical standards are sufficiently generic to allow institutions to adopt and implement any specific representation. However, the use of common Codelists will facilitate users to work even more efficiently as it eases the maintenance of, and reduces the need for, mapping systems and interfaces delivering data and metadata to users. Therefore, a choice over Codelists has a great impact on the efficiency of data sharing. From version 2.1 of the standard it is possible to exchange and disseminate a partial Codelist which is extracted from the full Codelist and which supports the dimension values valid for a particular Data Structure Definition (DSD). The content of the partial Codelist is specified on a Constraint and can be specified for any object to which a Constraint may be attached. This makes it possible to use common (and often quite large) Codelists in multiple DSDs and then to limit their content for use in a specific DSD.
requires: Concept
term status: upload
alternative label: Code list
broader: Statistical Data and Metadata eXchange
broader: Dimension
broader: Data Structure Definition
broader: Representation
definition: Predefined set of terms from which some statistical coded Concepts take their values.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CODELIST
related: Item Scheme
related: Coding Format
related: Constraint
related: Statistical Data and Metadata eXchange
related: Dimension
related: Data Structure Definition
related: Representation
top concept of: SDMX Glossary 2.1

Annotation
type: Concept
comment: The Annotation construct in SDMX is available to most of the SDMX structural metadata artefacts. This facility is essentially a flexible extension mechanism allowing metadata to be added to SDMX structural metadata or to a Data Set. Note that whilst the SDMX Annotation has a specific structure (Title, Type, URL, Text) individual organisations are free to use these in any way and any combination they wish. An Annotation can only be processed in a meaningful way (i.e. other than viewing it) by systems that understand the semantic of the Annotation.
term status: upload
broader: Title
broader: Statistical Data and Metadata eXchange
broader: Structural metadata
broader: Artefact
broader: Data Set
definition: Construct that contains user or organisation-specific metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ANNOTATION
related: Standard Annotation
related: Title
related: Statistical Data and Metadata eXchange
related: Annotable Artefact
related: Structural metadata
related: Artefact
related: Data Set
top concept of: SDMX Glossary 2.1

Age
type: Concept
comment: Age can be expressed as a number, e.g. 25 years old, or as a range, e.g. "between 25 and 29 years" or "6 to 11 months".
term status: upload
definition: Length of time that an entity has lived or existed.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).AGE
top concept of: SDMX Glossary 2.1
codelist ID: CL_AGE
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Item Scheme
type: Concept
comment: There are four types of Item Schemes in SDMX: Codelist, Concept Scheme, Category Scheme, Organisation Scheme (and four sub schemes: Agency, Data Provider, Data Consumer, Organisation Unit).
term status: upload
broader: Data Provider
broader: Concept Scheme
broader: Codelist
broader: Category Scheme
broader: Data Consumer
broader: Statistical Data and Metadata eXchange
definition: Descriptive information for an arrangement or division of objects into groups based on characteristics which the objects have in common.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ITEM_SCH
related: Concept Scheme
related: Codelist
related: Data Provider
related: Agency Scheme
related: Category Scheme
related: Data Consumer
related: Statistical Data and Metadata eXchange
related: Data Consumer Scheme
related: Data Provider Scheme
related: Organisation Unit Scheme
related: Statistical unit
top concept of: SDMX Glossary 2.1

Status in employment
type: Concept
comment: Status in employment is a key characteristic of the job held by an employed person. It is established based on the type of authority that the employed person is able to exercise in relation to the work performed and the type of economic risk to which the employed person is exposed.
requires: Job
term status: newTerm
alternative label: Employment status
definition: Type of explicit or implicit contract of employment which an employed person has in their job.
in scheme: SDMX Glossary 2.1
related: Job
top concept of: SDMX Glossary 2.1
codelist ID: CL_EMPLOYMENT_STATUS
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Status of worker
type: Concept
comment: Status of worker is a key characteristic of the job or work activity performed by a person in an economic unit. It is established based on the type of authority that the worker is able to exercise in relation to the work performed and the type of economic risk to which the worker is exposed. The classification of status of worker applies to all forms of work including own-use production work, employment, volunteer work, unpaid trainee work and other forms of work.
requires: Statistical unit
term status: newTerm
alternative label: Worker status
definition: Nature of the relationship between a worker and the economic unit in which or for which the work is performed.
in scheme: SDMX Glossary 2.1
related: Status in employment
related: Job
related: Statistical classification
related: Statistical unit
top concept of: SDMX Glossary 2.1
codelist ID: CL_WORKER_STATUS
concept type: CrossDomainConcept
recommended representation: CodeListDatatype

Coding Format
type: Concept
comment: The specification of the format information for the Codes, such as whether the Codes are alphabetic, numeric or alphanumeric, and the code length.
requires: Codelist
requires: Code
requires: Representation
term status: upload
broader: Code
definition: Specification of the Representation for the Codes in a Codelist.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CODING_FORMAT
related: Codelist
related: Code
related: Level
top concept of: SDMX Glossary 2.1

SDMX Technical Specification
type: Concept
comment: The Information Model at the core of this International Standard has been developed to support statistics as collected and used by governmental and supra-national statistical organisations, and this model is also applicable to other organisational contexts involving statistical data and related metadata. This set of standards comprises a number of specifications covering the Information Model, various syntax implementations of the model, metadata registry for storage, query, and retrieval, and web services for both data and structural metadata.
term status: upload
broader: Structural metadata
definition: Set of standards enabling interoperable implementations within and between systems concerned with the exchange, reporting and dissemination of statistical data and related metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_TECH_SPEC
related: SDMX Information Model
related: Structural metadata
top concept of: SDMX Glossary 2.1

Model assumption error
type: Concept
comment: Error due to domain specific models needed to define the target of estimation.
requires: Component
requires: Seasonal adjustment
requires: Accuracy
term status: upload
broader: Component
broader: Seasonal adjustment
broader: Accuracy
definition: Error that occurs due to the use of methods, such as calibration, generalised regression estimator, calculation based on full scope or constant scope, benchmarking, seasonal adjustment and other models not included in other accuracy components, in order to calculate statistics or indexes.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MODEL_ASSUMP_ERR
related: Coverage error
related: Processing error
related: Non-sampling error
related: Measurement error
related: Non-response error
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Base period
type: Concept
comment: The base period refers to the period when the published index is 100, or to which weights or base data refer to. It can be one single year (e.g. 1995=100) but it may be as short as one day or as long as a specified number of years. "Base period" may include an indication of the value of the series in the base period (usually 1 or 100).
requires: Series
term status: upload
definition: Period of time used as the base of an index number, or to which a constant series refers.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).BASE_PER
related: Base weight
related: Series
related: Reference period
top concept of: SDMX Glossary 2.1
codelist ID: CL_BASE_PER
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: ObsTimePeriodDatatype
recommended representation: CodeListDatatype

Adjustment
type: Concept
comment: Adjustments may be associated with changes in definitions, exchange rates, prices, seasons and other factors. Adjustments are in particular applied to compile consistent time series, but the concept is also used for describing adjustments related to other types of data. Adjustment can be distinguished from editing and imputation, in that before adjustment, the data are already of sufficient quality to be considered usable.
requires: Data Set
term status: upload
broader: Imputation
broader: Data Set
definition: Set of procedures employed to modify statistical data to enable it to conform to national or international standards or to address data quality differences when compiling specific Data Sets.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).ADJUSTMENT
related: Concept
related: Price adjustment
related: Seasonal adjustment
related: Imputation
related: Series
top concept of: SDMX Glossary 2.1
codelist ID: CL_ADJUSTMENT
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Contact organisation
type: Concept
term status: upload
alternative label: Organisation contact
broader: Contact
definition: Organisation of the contact point(s) for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_ORGANISATION
related: Contact phone number
related: Contact name
related: Contact person function
related: Contact email address
related: Contact mail address
related: Contact organisation unit
related: Contact
related: Contact fax number
top concept of: SDMX Glossary 2.1
codelist ID: CL_ORGANISATION
concept type: CrossDomainConcept
recommended representation: StringDatatype
recommended representation: CodeListDatatype

Quality management - quality assessment
type: Concept
comment: The overall assessment of data quality may include the result of a scoring or grading process for quality. Scoring may be quantitative or qualitative.
term status: upload
alternative label: Quality assessment
broader: Quality management
definition: Overall evaluation of data quality, based on standard quality criteria.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).QUALITY_ASSMNT
related: Quality management
related: Quality management - quality assurance
related: Quality management - quality documentation
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Ownership group
type: Concept
comment: The daily maintenance of the artefacts is delegated to one of the members of the ownership group, called the "maintenance agency". Proposals for changes are proposed by the maintenance agency but the decision-making body is the ownership group. There can be several distinct maintenance agencies within a given global SDMX implementation.
requires: Statistical Data and Metadata eXchange
requires: Data Structure Definition
requires: Artefact
term status: upload
broader: Statistical Data and Metadata eXchange
broader: Data Structure Definition
broader: Maintenance agency
broader: Artefact
definition: Set of organisations which collegially endorse the responsibility for the governance of an SDMX Data Structure Definition and its related artefacts.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).OWNER_GRP
related: Fast-track change
related: Statistical Data and Metadata eXchange
related: Maintenance agency
related: Artefact
top concept of: SDMX Glossary 2.1

Professionalism - methodology
type: Concept
term status: upload
alternative label: Professionalism methodology
broader: Professionalism
definition: Elements providing assurances that the choices of sources and statistical techniques as well as decisions about dissemination are informed solely by statistical considerations.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).PROF_METH
related: Professionalism - code of conduct
related: Professionalism - impartiality
related: Professionalism - statistical commentary
related: Professionalism
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Maintainable Artefact
type: Concept
comment: Maintainable Artefacts inherit the capability of having versioning name, identity and Annotations. In addition a Maintainable Artefact can have an indication that the artefact and its contained items (e.g. the contained items of a Codelist are the Codes) are "final" and there are restrictions on what type of change is allowed without changing the version.
requires: Maintenance agency
term status: upload
broader: Annotation
broader: Codelist
broader: Code
broader: Maintenance agency
broader: Artefact
definition: Construct that contains structures capable of providing a Maintenance Agency to an object.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MAINTAINABLE_ART
related: Codelist
related: Annotation
related: Code
related: Identifiable Artefact
related: Annotable Artefact
related: Versionable Artefact
related: Artefact
related: Nameable Artefact
top concept of: SDMX Glossary 2.1

Release policy - release calendar access
type: Concept
comment: Access to the release calendar information. A hyperlink should be provided if available.
requires: Release policy - release calendar
term status: upload
alternative label: Release calendar access
broader: Release policy
definition: Description of how the release calendar can be accessed.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).REL_CAL_ACCESS
related: Release policy - user access
related: Release policy - release calendar
related: Release policy - transparency
related: Release policy
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Coverage error
type: Concept
comment: Coverage errors include over-coverage, under-coverage and misclassification. Incomplete sampling frames often result in coverage errors.
requires: Component
term status: upload
broader: Component
definition: Error caused by a failure to cover adequately all components of the population being studied, which results in differences between the target population and the sampling frame.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).COVERAGE_ERR
related: Model assumption error
related: Processing error
related: Non-sampling error
related: Measurement error
related: Non-response error
related: Coverage
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype

Contact name
type: Concept
term status: upload
broader: Contact
definition: Name of the contact points for the data or metadata.
in scheme: SDMX Glossary 2.1
notation: urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).CONTACT_NAME
related: Contact phone number
related: Contact person function
related: Contact email address
related: Contact mail address
related: Contact organisation unit
related: Contact organisation
related: Contact
related: Contact fax number
top concept of: SDMX Glossary 2.1
concept type: CrossDomainConcept
recommended representation: StringDatatype