Map

Last modified by Artur on 2025/08/04 16:07


Upload
https://purl.semanticip.org/linked-data/sdmx/concept/MAP TTL
Map

Correspondence between two or more objects.

In SDMX there are a variety of such correspondences. Item Scheme Map. Codes, concepts, categories, and organisations (data providers, data consumers, organisation units) are mapped in Code List Map, Concept Scheme Map, Category Scheme Map, Organisation Scheme Map. Each map is a correspondence between the items in one scheme or list and the items in a second scheme or list, where the schemes or list must be of the same type (e.g. code lists to code list). Each scheme or list map contains a map for each item in the scheme or list - Code Map, Concept Map, Category Map, Organisation Map, Structure Map. Data and metadata structures can be mapped at level of the components comprising the structure (Component Map). The map can be specified at the level of the Dataflow or Data Structure, or the Metadataflow or Metadata Structure. The map takes into the constraints that are attached to the structural artefact that is mapped. Each component in a component map can be associated with an appropriate item scheme map that specifies the correspondence between the item schemes in the source and target components.

Statistical data and metadata exchange, Item scheme, Code, Category, Data provider, Data consumer, Code list, Concept scheme, Category scheme, Component, Dataflow, Metadataflow, Artefact

urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).MAP

Used in the following terms: -
Backlinks: 1 Introduction, 11 ItemSchemeMap, 13 Structure Mapping, 5 Data Bases and SDMX, 9 Structure Map

Еще (9)9 Structure Set and Mappings, Change History, Part I. Message Namespace, Part II.Common Namespace, Part III. Structure Namespace, Revision History, SDMX 3.0 Standards. Section 1. Framework for SDMX technical standards, SDMX 3.1 Standards. Section 1. Framework, SDMX 3.1 Standards. Section 5. Registry Specification: Logical Interfaces