<?xml version='1.0' encoding='UTF-8'?><message:Structure xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:message="http://www.sdmx.org/resources/sdmxml/schemas/v3_0/message" xmlns:str="http://www.sdmx.org/resources/sdmxml/schemas/v3_0/structure" xmlns:com="http://www.sdmx.org/resources/sdmxml/schemas/v3_0/common"><message:Header><message:ID>IREF331158</message:ID><message:Test>false</message:Test><message:Prepared>2026-05-13T00:45:16Z</message:Prepared><message:Sender id="Unknown"/><message:Receiver id="not_supplied"/></message:Header><message:Structures><str:ConceptSchemes><str:ConceptScheme urn="urn:sdmx:org.sdmx.infomodel.conceptscheme.ConceptScheme=SDMX:CROSS_DOMAIN_CONCEPTS(2.0)" isExternalReference="false" isPartial="true" agencyID="SDMX" id="CROSS_DOMAIN_CONCEPTS" version="2.0"><com:Name xml:lang="en">SDMX Cross Domain Concept Scheme</com:Name><com:Description xml:lang="en">The Cross Domain Concept Scheme (starting from v2.0) is created from the set of concepts in the SDMX Glossary, which 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.In short, the overall message of the glossary is the following: if a term is used, then its precise meaning should correspond to the SDMX Glossary definition, and any reference to a particular phenomenon described in the SDMX Glossary should use the appropriate term.Version 1.0 of the SDMX Glossary, which replaces the Metadata Common Vocabulary (MCV) published in 2009, was finalised in February 2016. The Cross Domain Concept Scheme v1.0 was created from the MCV concepts.For any question, comment or correction, feel free to contact the SDMX Statistical Working Group (SWG) at the following address: swg@sdmx.org.</com:Description><str:Concept urn="urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SDMX:CROSS_DOMAIN_CONCEPTS(2.0).SDMX_EDI" id="SDMX_EDI"><com:Annotations><com:Annotation><com:AnnotationType>CONTEXT</com:AnnotationType><com:AnnotationText xml:lang="en">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.</com:AnnotationText></com:Annotation><com:Annotation><com:AnnotationType>RELATED_TERMS</com:AnnotationType><com:AnnotationText xml:lang="en">SDMX information model, SDMX-IM</com:AnnotationText></com:Annotation><com:Annotation><com:AnnotationType>SOURCE</com:AnnotationType><com:AnnotationText xml:lang="en">SDMX (2016) (https://sdmx.org/)</com:AnnotationText></com:Annotation></com:Annotations><com:Name xml:lang="en">SDMX-EDI</com:Name><com:Description xml:lang="en">UN/EDIFACT format for exchange of SDMX-structured data and metadata for time series.</com:Description></str:Concept></str:ConceptScheme></str:ConceptSchemes></message:Structures></message:Structure>