Last modified by Helena K. on 2026/06/09 19:45
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,0 +1,1 @@ 1 +SDMX 3.1 Standards. Section 5. Registry Specification: Logical Interfaces - Parent
-
... ... @@ -1,0 +1,1 @@ 1 +Methodology.WebHome - Content
-
... ... @@ -11,69 +11,69 @@ 11 11 12 12 = 1 Introduction = 13 13 14 -The business vision for [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] envisages the promotion of a “data sharing” model to facilitate low-cost, high-quality [[statistical data and metadata exchange>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Data sharing reduces the reporting burden of organisations by allowing them to publish data once and let their counterparties “pull” data and related metadata as required. The scenario is based on: 14 +The business vision for [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] envisages the promotion of a “[[data sharing>>doc:sdmx:Glossary 2\.1.Data sharing.WebHome]]” model to facilitate low-cost, high-quality [[statistical data and metadata exchange>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]. [[Data sharing>>doc:sdmx:Glossary 2\.1.Data sharing.WebHome]] reduces the reporting burden of organisations by allowing them to publish data once and let their counterparties “pull” data and related metadata as required. The scenario is based on: 15 15 16 -* the availability of an abstract information model capable of supporting time series and cross-sectional data, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]) 17 -* standardised XML and JSON schemas for the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary.SDMX-JSON.WebHome]] formats derived from the model (XSD, JSON) 16 +* the availability of an abstract information model capable of supporting [[time series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] and cross-sectional data, [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]], and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]) 17 +* standardised XML and JSON schemas for the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:sdmx:Glossary 2\.1.SDMX-JSON.WebHome]] formats derived from the model (XSD, JSON) 18 18 * the use of web-services technology (XML, JSON, Open API) 19 19 20 -Such an architecture needs to be well organised, and the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/Repository (SDMXRR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[components>>doc:sdmx:Glossary.Component.WebHome]] required to support the data sharing vision. 20 +Such an architecture needs to be well organised, and the [[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]/Repository (SDMXRR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] required to support the [[data sharing>>doc:sdmx:Glossary 2\.1.Data sharing.WebHome]] vision. 21 21 22 -However, it is important to emphasise that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR provides support for the submission and retrieval of all [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and provisioning metadata. Therefore, the Registry not only supports the data-sharing scenario, but this metadata is also vital in order to provide support for data and metadata reporting/collection, and dissemination scenarios. 22 +However, it is important to emphasise that the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR provides support for the submission and retrieval of all [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] and provisioning metadata. Therefore, the Registry not only supports the data-sharing scenario, but this metadata is also vital in order to provide support for data and metadata reporting/collection, and dissemination scenarios. 23 23 24 -Standard formats for the exchange of aggregated statistical data and metadata as prescribed in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] v3.1 are envisaged to bring benefits to the statistical community because data reporting and dissemination processes can be made more efficient. 24 +Standard formats for the exchange of aggregated statistical data and metadata as prescribed in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] v3.1 are envisaged to bring benefits to the statistical community because data reporting and dissemination processes can be made more efficient. 25 25 26 -As organisations migrate to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML, JSON (and conventional) [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] will be produced (e.g., Data Structure, Metadata Structure, [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] and (% style="color:#e74c3c"%)Concept(%%)definitions – often collectively called [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] – XML schemas generated from [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] between parties in a controlled and organized way.26 +As organisations migrate to [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] enabled systems, many XML, JSON (and conventional) [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] will be produced (e.g., Data Structure, Metadata Structure, [[Code List>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and [[Concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] definitions – often collectively called [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] – XML schemas generated from [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] between parties in a controlled and organized way. 27 27 28 28 This is the role of the registry. 29 29 30 -With the fundamental [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards in place, a set of architectural standards are needed to address some of the processes involved in [[statistical data and metadata exchange>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], with an emphasis on maintenance, retrieval and sharing of the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. In addition, the architectural standards support the registration and discovery of data and referential metadata. 30 +With the fundamental [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] standards in place, a set of architectural standards are needed to address some of the processes involved in [[statistical data and metadata exchange>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]], with an emphasis on maintenance, retrieval and sharing of the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. In addition, the architectural standards support the registration and discovery of data and referential metadata. 31 31 32 -These architectural standards address the ‘how’, rather than the ‘what’, and are aimed at enabling existing [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards to achieve their mission. The architectural standards address registry services, which initially comprise: 32 +These architectural standards address the ‘how’, rather than the ‘what’, and are aimed at enabling existing [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] standards to achieve their mission. The architectural standards address registry services, which initially comprise: 33 33 34 -* [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository 34 +* [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] repository 35 35 * data and metadata registration 36 36 * query 37 37 38 -The registry services outlined in this specification are designed to help the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] community manage the proliferation of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] assets and to support data sharing for reporting and dissemination. 38 +The registry services outlined in this specification are designed to help the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] community manage the proliferation of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] assets and to support [[data sharing>>doc:sdmx:Glossary 2\.1.Data sharing.WebHome]] for reporting and dissemination. 39 39 40 40 = 2 Scope and Normative Status = 41 41 42 -The scope of this document is to specify the logical interfaces for the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry. 42 +The scope of this document is to specify the logical interfaces for the [[SDMX registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]] in terms of the functions required and the data that may be present in the function call, and the behaviour expected of the registry. 43 43 44 44 In this document, functions and behaviours of the Registry Interfaces are described in four ways: 45 45 46 46 * in text 47 47 * with tables 48 -* with UML diagrams excerpted from the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]) 49 -* with UML diagrams that are not a part of the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] but are included here for clarity and to aid implementations (these diagrams are clearly marked as “Logical Class Diagram ...”) 48 +* with UML diagrams excerpted from the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]) 49 +* with UML diagrams that are not a part of the [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] but are included here for clarity and to aid implementations (these diagrams are clearly marked as “Logical Class Diagram ...”) 50 50 51 51 Whilst the introductory section contains some information on the role of the registry, it is assumed that the reader is familiar with the uses of a registry in providing shared metadata across a community of counterparties. 52 52 53 -Note that chapters 5 and 6 below contain normative rules regarding the Registry Interface and the identification of registry objects. Further, the minimum standard for access to the registry is via a REST interface (HTTP or HTTPS), as described in the appropriate sections. The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] mechanism must support e-mail and HTTP/HTTPS protocols as described. Normative registry interfaces are specified in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] specification (Section 3 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standard). All other sections of this document are informative. 53 +Note that chapters 5 and 6 below contain normative rules regarding the Registry Interface and the identification of registry objects. Further, the minimum standard for access to the registry is via a REST interface (HTTP or HTTPS), as described in the appropriate sections. The [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] mechanism must support e-mail and HTTP/HTTPS protocols as described. Normative registry interfaces are specified in the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] specification (Section 3 of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standard). All other sections of this document are informative. 54 54 55 -Note that although the term “authorised user” is used in this document, the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards do not define an access control mechanism. Such a mechanism, if required, must be chosen and implemented by the registry software provider. 55 +Note that although the term “authorised user” is used in this document, the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] standards do not define an access control mechanism. Such a mechanism, if required, must be chosen and implemented by the registry software provider. 56 56 57 57 = 3 Scope of the SDMX Registry/Repository = 58 58 59 59 == 3.1 Objective == 60 60 61 -The objective of the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/repository is, in broad terms, to allow organisations to publish statistical data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] in known formats such that interested third parties can discover these data and interpret them accurately and correctly. The mechanism for doing this is twofold: 61 +The objective of the [[SDMX registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]/repository is, in broad terms, to allow organisations to publish statistical data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] in known formats such that interested third parties can discover these data and interpret them accurately and correctly. The mechanism for doing this is twofold: 62 62 63 -1. To maintain and publish [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that describes the structure and valid content of data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sources such as databases, [[metadata repositories>>doc:sdmx:Glossary.Metadata repository.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. This [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] enables software applications to understand and to interpret the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] in these sources. 64 -1. To enable applications, organisations, and individuals to share and to discover data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. This facilitates data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] dissemination by implementing the data sharing vision of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. 63 +1. To maintain and publish [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] that describes the structure and valid content of data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] sources such as databases, [[metadata repositories>>doc:sdmx:Glossary 2\.1.Metadata repository.WebHome]], [[data sets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]], [[metadata sets>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]]. This [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] enables software applications to understand and to interpret the data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] in these sources. 64 +1. To enable applications, organisations, and individuals to share and to discover data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]]. This facilitates data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] dissemination by implementing the [[data sharing>>doc:sdmx:Glossary 2\.1.Data sharing.WebHome]] vision of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]. 65 65 66 66 == 3.2 Structural Metadata == 67 67 68 -Setting up [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and the exchange context (referred to as “data provisioning”) involves the following steps for [[maintenance agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]]: 68 +Setting up [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] and the exchange context (referred to as “data provisioning”) involves the following steps for [[maintenance agencies>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]]: 69 69 70 -* agreeing and creating a specification of the structure of the data (called a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] in this document but also known as “key family”), which defines the [[dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], [[measures>>doc:sdmx:Glossary.Measure.WebHome]] and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] of a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] and their valid value set; 71 -* if required, defining a subset or view of a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] which allows some restriction of content called a “[[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] definition”; 72 -* agreeing and creating a specification of the structure of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] ([[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]) which defines the metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] and their presentational arrangement in a Metadataset or as part of a [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]], and their valid values and content; 73 -* if required, defining a subset or view of an [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which allows some restriction of content called a “[[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]”; 74 -* defining which subject matter domains (specified as a [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]) are related to the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] to enable browsing; 70 +* agreeing and creating a specification of the structure of the data (called a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] in this document but also known as “key family”), which defines the [[dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], [[measures>>doc:sdmx:Glossary 2\.1.Measure.WebHome]] and [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] of a [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and their valid value set; 71 +* if required, defining a subset or view of a [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] which allows some restriction of content called a “[[dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] definition”; 72 +* agreeing and creating a specification of the structure of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] ([[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]) which defines the metadata [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] and their presentational arrangement in a Metadataset or as part of a [[Dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]], and their valid values and content; 73 +* if required, defining a subset or view of an [[MSD>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] which allows some restriction of content called a “[[metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]”; 74 +* defining which subject matter domains (specified as a [[Category Scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]]) are related to the [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] to enable browsing; 75 75 * defining one or more lists of Data and Metadata Providers; 76 -* defining which Data/Metadata Providers have agreed to publish a given [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] – this is called a [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] or Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]], respectively. 76 +* defining which Data/Metadata Providers have agreed to publish a given [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] – this is called a [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] or Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], respectively. 77 77 78 78 [[image:SDMX 3.1 Section 5_en_c485399b.jpg||height="539" width="443"]] 79 79 ... ... @@ -81,20 +81,20 @@ 81 81 82 82 Note that in Figure 1 (but also most of the relevant subsequent figures) terms that include both data and metadata have been used. For example: 83 83 84 -* Structure Definition: refers to [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]]) and [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] ([[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]) 85 -* Flow: refers to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] 86 -* [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]: refers to [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] (for data) and Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] 87 -* Provider Scheme: refers to [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]] and Metadata Provider Scheme 88 -* Provider: refers to [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] and Metadata Provider 84 +* Structure Definition: refers to [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] ([[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]) and [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] ([[MSD>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]) 85 +* Flow: refers to [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] 86 +* [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]: refers to [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] (for data) and Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] 87 +* Provider Scheme: refers to [[Data Provider Scheme>>doc:sdmx:Glossary 2\.1.Data provider scheme.WebHome]] and Metadata Provider Scheme 88 +* Provider: refers to [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] and Metadata Provider 89 89 90 -In that context, the term “Metadata” refers to [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 90 +In that context, the term “Metadata” refers to [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]]. 91 91 92 92 == 3.3 Registration == 93 93 94 -Publishing the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] involves the following steps for a Data/Metadata Provider: 94 +Publishing the data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] involves the following steps for a Data/Metadata Provider: 95 95 96 -* making the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and data available in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]]/JSON conformant data files or databases (which respond to an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] query with data). The data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] files or databases must be web accessible, and must conform to an agreed [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] subset); 97 -* registering the existence of published [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and data files or databases with one or more [[SDMX>>doc:sdmx:Glossary.S tatisticaldata and metadata exchange.WebHome]]registries.96 +* making the [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] and data available in [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]]/JSON conformant data files or databases (which respond to an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] query with data). The data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] files or databases must be web accessible, and must conform to an agreed [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] ([[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] subset); 97 +* registering the existence of published [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] and data files or databases with one or more [[SDMX registries>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]. 98 98 99 99 [[image:SDMX 3.1 Section 5_en_6e468656.jpg||height="407" width="553"]] 100 100 ... ... @@ -102,17 +102,17 @@ 102 102 103 103 == 3.4 Notification == 104 104 105 -Notifying interested parties of newly published or re-published data, [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] involves: 105 +Notifying interested parties of newly published or re-published data, [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] involves: 106 106 107 -* registry support of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]-based [[notification>>doc:sdmx:Glossary.Notification.WebHome]] service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request. 107 +* registry support of a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]-based [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] request. 108 108 109 109 == 3.5 Discovery == 110 110 111 -Discovering published data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-enabled data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] resource: 111 +Discovering published data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] involves interaction with the registry to fulfil the following logical steps that would be carried out by a user interacting with a service that itself interacts with the registry and an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-enabled data or [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] resource: 112 112 113 -* optionally browsing a subject matter domain [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] to find [[Dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] (and hence [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]]) and [[Metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]] which structure the type of data and/or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] being sought; 114 -* build a query, in terms of the selected [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], which specifies what data are required and submitting this to a service that can query an [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] which will return a list of (URLs of) data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] files and databases which satisfy the query; 115 -* processing the query result set and retrieving data and/or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] from the supplied URLs. 113 +* optionally browsing a subject matter domain [[category scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] to find [[Dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] (and hence [[Data Structure Definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]) and [[Metadataflows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] which structure the type of data and/or [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] being sought; 114 +* build a query, in terms of the selected [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]], which specifies what data are required and submitting this to a service that can query an [[SDMX registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]] which will return a list of (URLs of) data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] files and databases which satisfy the query; 115 +* processing the query result set and retrieving data and/or [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] from the supplied URLs. 116 116 117 117 [[image:SDMX 3.1 Section 5_en_6c6c7b74.jpg||height="328" width="554"]] 118 118 ... ... @@ -122,7 +122,7 @@ 122 122 123 123 == 4.1 Architectural Schematic == 124 124 125 -The architecture of the [[SDMX registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/repository is derived from the objectives stated above. It is a layered architecture that is founded by a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository which supports a provisioning [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] which supports the registry services. These are all supported by the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] required to drive these applications. 125 +The architecture of the [[SDMX registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]/repository is derived from the objectives stated above. It is a layered architecture that is founded by a [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] repository which supports a provisioning [[metadata repository>>doc:sdmx:Glossary 2\.1.Metadata repository.WebHome]] which supports the registry services. These are all supported by the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] schemas. Applications can be built on top of these services which support the reporting, storage, retrieval, and dissemination aspects of the statistical lifecycle as well as the maintenance of the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] required to drive these applications. 126 126 127 127 [[image:SDMX 3.1 Section 5_en_81e92e22.jpg||height="325" width="553"]] 128 128 ... ... @@ -130,18 +130,18 @@ 130 130 131 131 == 4.2 Structural Metadata Repository == 132 132 133 -The basic layer is that of a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] service which supports the lifecycle of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] such as [[Maintenance Agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]], [[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[Provision Agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]], Processes etc. This layer is supported by the Structure Submission and Query Service. 133 +The basic layer is that of a [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] service which supports the lifecycle of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] such as [[Maintenance Agencies>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]], [[Data Structure Definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]], [[Provision Agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], Processes etc. This layer is supported by the Structure Submission and Query Service. 134 134 135 -Note that the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] REST API supports all of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. The only structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that are not yet supported are: 135 +Note that the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] REST API supports all of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]. The only structural [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that are not yet supported are: 136 136 137 137 * Registration of data and metadata sources 138 -* [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] 138 +* [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] 139 139 140 -As of the initial (% style="color:#e74c3c" %)version(%%)of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 no messages are defined to support these [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]; hence, users may need to use [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1 Registry Interface messages, instead.140 +As of the initial version of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 3.0 no messages are defined to support these [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]; hence, users may need to use [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 2.1 Registry Interface messages, instead. 141 141 142 142 == 4.3 Provisioning Metadata Repository == 143 143 144 -The function of this repository is to support the definition of the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that describes the various types of data-store which model [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-conformant databases or files, and to link to these [[data sources>>doc:sdmx:Glossary.Data source.WebHome]]. These links can be specified for a data/metadata provider, for a specific data or [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]]. In the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] model this is called the Provision or Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]. 144 +The function of this repository is to support the definition of the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] that describes the various types of data-store which model [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-conformant databases or files, and to link to these [[data sources>>doc:sdmx:Glossary 2\.1.Data source.WebHome]]. These links can be specified for a data/metadata provider, for a specific data or [[metadata flow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]. In the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] model this is called the Provision or Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]. 145 145 146 146 This layer is supported by the Data and Metadata Registration Service. 147 147 ... ... @@ -152,25 +152,25 @@ 152 152 The Registry Interfaces are: 153 153 154 154 * Notify Registry Event 155 -* Submit [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Request 156 -* Submit [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Response 155 +* Submit [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] Request 156 +* Submit [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] Response 157 157 * Submit Registration Request 158 158 * Submit Registration Response 159 159 * Query Registration Request 160 160 * Query Registration Response 161 -* Query [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Request 162 -* Query [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Response 161 +* Query [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] Request 162 +* Query [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] Response 163 163 164 164 The registry interfaces are invoked in one of two ways: 165 165 166 -1. The interface is the name of the root node of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] document 167 -1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] document. 166 +1. The interface is the name of the root node of the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] document 167 +1. The interface is invoked as a child element of the RegistryInterface message where the RegistryInterface is the root node of the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] document. 168 168 169 -In addition to these interfaces the registry must support a mechanism for submitting and querying for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This is detailed in sections 5.2.2 and 5.2.3. 169 +In addition to these interfaces the registry must support a mechanism for submitting and querying for [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. This is detailed in sections 5.2.2 and 5.2.3. 170 170 171 -All these interactions with the Registry – with the exception of NotifyRegistryEvent – are designed in pairs. The first document, the one which invokes the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR interface, is a “Request” document. The message returned by the interface is a “Response” document. 171 +All these interactions with the Registry – with the exception of NotifyRegistryEvent – are designed in pairs. The first document, the one which invokes the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR interface, is a “Request” document. The message returned by the interface is a “Response” document. 172 172 173 -It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the requestresponse pattern, because it is inherently asynchronous. 173 +It should be noted that all interactions are assumed to be synchronous, with the exception of Notify Registry Event. This document is sent by the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR to all subscribers whenever an even occurs to which any users have subscribed. Thus, it does not conform to the requestresponse pattern, because it is inherently asynchronous. 174 174 175 175 == 5.2 Registry Services == 176 176 ... ... @@ -180,15 +180,15 @@ 180 180 181 181 === 5.2.2 Structure Submission Service === 182 182 183 -The registry must support a mechanism for submitting [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact, with the exception of [[Item Schemes>>doc:sdmx:Glossary.Item scheme.WebHome]], where changes at an Item (% style="color:#e74c3c" %)level(%%) is also possible (see next section on the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]). 183 +The registry must support a mechanism for submitting [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact, with the exception of [[Item Schemes>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]], where changes at an Item (% style="color:#e74c3c" %)level(%%) is also possible (see next section on the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]). 184 184 185 185 === 5.2.3 Structure Query Service === 186 186 187 -The registry must support a mechanism for querying for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). The registry response to this query mechanism is the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Structure message, which has as its root node: 187 +The registry must support a mechanism for querying for [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). The registry response to this query mechanism is the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Structure message, which has as its root node: 188 188 189 189 * Structure 190 190 191 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that may be queried are defined in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structure web service specification which is compatible with this release of the standard __[[https:~~/~~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md>>https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]] __[[https:~~/~~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md>>https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]] 191 +The [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that may be queried are defined in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] structure web service specification which is compatible with this release of the standard __[[https:~~/~~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md>>https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]] __[[https:~~/~~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md>>https://github.com/sdmx-twg/sdmx-rest/blob/master/doc/structures.md]] 192 192 193 193 === 5.2.4 Data and Reference Metadata Registration Service === 194 194 ... ... @@ -199,36 +199,38 @@ 199 199 * QueryRegistrationRequest 200 200 * QueryRegistrationResponse 201 201 202 -The Data Registration Service allows [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant files and web-accessible databases containing published data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]. The registration process MAY validate the content of the [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or metadata-sets, and MAY extract a concise [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the contents in terms of (% style="color:#e74c3c" %)concept(%%) values (e.g., values of the data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]], [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]], metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadata-set. These are called (% style="color:#e74c3c" %)Constraints(%%) in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]].202 +The Data Registration Service allows [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] conformant files and web-accessible databases containing published data and [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]. The registration process MAY validate the content of the [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or metadata-sets, and MAY extract a concise [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of the contents in terms of (% style="color:#e74c3c" %)concept(%%) values (e.g., values of the data [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]], [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], metadata [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or 203 203 204 +metadata-set. These are called (% style="color:#e74c3c" %)Constraints(%%) in the [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. 205 + 204 204 The Data Registration Service MAY validate the following, subject to the access control mechanism implemented in the Registry: 205 205 206 -* that the data/metadata provider is allowed to register the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadataset; 207 -* that the content of the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadataset meets the validation (% style="color:#e74c3c" %)constraints(%%). This is dependent upon such (% style="color:#e74c3c" %)constraints(%%) being defined in the structural repository and which reference the relevant [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]], Metadata Provider, [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]; 208 -* that a queryable [[data source>>doc:sdmx:Glossary.Data source.WebHome]] exists – this would necessitate the registration service querying the service to determine its existence; 209 -* that a simple [[data source>>doc:sdmx:Glossary.Data source.WebHome]] exists (i.e., a file accessible at a URL); 210 -* that the correct [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] is used by the registered data; 211 -* that the [[components>>doc:sdmx:Glossary.Component.WebHome]] ([[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]], [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]], [[Measures>>doc:sdmx:Glossary.Measure.WebHome]]) are consistent with the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]; 212 -* that the valid [[representations>>doc:sdmx:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)concepts(%%) to which these [[components>>doc:sdmx:Glossary.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. 208 +* that the data/metadata provider is allowed to register the [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or metadataset; 209 +* that the content of the [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or metadataset meets the validation (% style="color:#e74c3c" %)constraints(%%). This is dependent upon such (% style="color:#e74c3c" %)constraints(%%) being defined in the structural repository and which reference the relevant [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]], Metadata Provider, [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]], [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]; 210 +* that a queryable [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]] exists – this would necessitate the registration service querying the service to determine its existence; 211 +* that a simple [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]] exists (i.e., a file accessible at a URL); 212 +* that the correct [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] is used by the registered data; 213 +* that the [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] ([[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]], [[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]], [[Measures>>doc:sdmx:Glossary 2\.1.Measure.WebHome]]) are consistent with the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]; 214 +* that the valid [[representations>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of the (% style="color:#e74c3c" %)concepts(%%) to which these [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]. 213 213 214 -The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values: 216 +The Registration has an action [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] which takes one of the following values: 215 215 216 216 (% style="width:893.835px" %) 217 -|(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour** 219 +|(% style="width:241px" %)**Action [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] Value**|(% style="width:650px" %)**Behaviour** 218 218 |(% style="width:241px" %)Append|(% style="width:650px" %)Add this registration to the registry 219 219 |(% style="width:241px" %)Replace|(% style="width:650px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request 220 220 |(% style="width:241px" %)Delete|(% style="width:650px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 221 221 222 -The Registration has three Boolean [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] which may be present to determine how an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadataset indexing application must index the [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or metadatasets upon registration. The indexing application behaviour is as follows: 224 +The Registration has three Boolean [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] which may be present to determine how an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] compliant [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or metadataset indexing application must index the [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or metadatasets upon registration. The indexing application behaviour is as follows: 223 223 224 224 (% style="width:896.835px" %) 225 -|**Boolean Attribute**|(% style="width:712px" %)**Behaviour if Value is “true”** 226 -|indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the time series keys 227 +|**Boolean [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]**|(% style="width:712px" %)**Behaviour if Value is “true”** 228 +|indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the [[time series>>doc:sdmx:Glossary 2\.1.Series.WebHome]] keys 227 227 |indexDataSet|(% style="width:712px" %)((( 228 -A compliant indexing application must index the range of actual (present) values for each [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] of the [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]]. 229 -Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] values (the Key) is actually present in the [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] 230 +A compliant indexing application must index the range of actual (present) values for each [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] of the [[Dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]. 231 +Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] values (the Key) is actually present in the [[Dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] 230 230 ))) 231 -|indexReportingPeriod|(% style="width:712px" %)A compliant indexing application must index the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] range(s) for which data are present in the [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]]. 233 +|indexReportingPeriod|(% style="width:712px" %)A compliant indexing application must index the [[time period>>doc:sdmx:Glossary 2\.1.Time period.WebHome]] range(s) for which data are present in the [[Dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]. 232 232 233 233 === 5.2.5 Data Discovery === 234 234 ... ... @@ -239,55 +239,57 @@ 239 239 240 240 === 5.2.6 Subscription and Notification === 241 241 242 -The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] Service implements the following Registry Interfaces: 244 +The [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] Service implements the following Registry Interfaces: 243 243 244 244 * SubmitSubscriptionRequest 245 245 * SubmitSubscriptionResponse 246 246 * NotifyRegistryEvent 247 247 248 -The data sharing paradigm relies upon the consumers of data and metadata being able to pull information from [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]]’ dissemination systems. For this to work efficiently, a [[data consumer>>doc:sdmx:Glossary.Data consumer.WebHome]] needs to know when to pull data, i.e., when something has changed in the registry (e.g., a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] has been updated and re-registered). Additionally, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] systems may also want to know if a new [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], or [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] has been added. The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] Service comprises two parts: [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] management, and [[notification>>doc:sdmx:Glossary.Notification.WebHome]]. 250 +The [[data sharing>>doc:sdmx:Glossary 2\.1.Data sharing.WebHome]] paradigm relies upon the consumers of data and metadata being able to pull information from [[data providers>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]’ dissemination systems. For this to work efficiently, a [[data consumer>>doc:sdmx:Glossary 2\.1.Data consumer.WebHome]] needs to know when to pull data, i.e., when something has changed in the registry (e.g., a [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] has been updated and re-registered). Additionally, [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] systems may also want to know if a new [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], or [[Code List>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] has been added. The [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] Service comprises two parts: [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] management, and [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]. 249 249 250 -[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request which contains: 252 +[[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] request which contains: 251 251 252 -* a query or (% style="color:#e74c3c" %)constraint(%%) expression in terms of a filter which defines the events for which the user is interested (e.g., new data for a specific [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], or for a domain [[category>>doc:sdmx:Glossary.Category.WebHome]], or changes to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). 253 -* a list of URIs or endpoints to which an XML [[notification>>doc:sdmx:Glossary.Notification.WebHome]] message can be sent. Supported endpoint types will be email (mailto and HTTP POST (a normal http:~/~/ address); 254 -* request for a list of submitted [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]]; 255 -* deletion of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]; 254 +* a query or (% style="color:#e74c3c" %)constraint(%%) expression in terms of a filter which defines the events for which the user is interested (e.g., new data for a specific [[dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], or for a domain [[category>>doc:sdmx:Glossary 2\.1.Category.WebHome]], or changes to a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]). 255 +* a list of URIs or endpoints to which an XML [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] message can be sent. Supported endpoint types will be email (mailto and HTTP POST (a normal http:~/~/ address); 256 +* request for a list of submitted [[subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]; 257 +* deletion of a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]; 256 256 257 -[[Notification>>doc:sdmx:Glossary.Notification.WebHome]] requires that the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository and the provisioning [[metadata repository>>doc:sdmx:Glossary.Metadata repository.WebHome]] monitor any event which is of interest to a user (the object of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request query), and to issue an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document to the endpoints specified in the relevant [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]]. 259 +[[Notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] requires that the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] repository and the provisioning [[metadata repository>>doc:sdmx:Glossary 2\.1.Metadata repository.WebHome]] monitor any event which is of interest to a user (the object of a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] request query), and to issue an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] document to the endpoints specified in the relevant [[subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]. 258 258 259 259 === 5.2.7 Registry Behaviour === 260 260 261 -The following table defines the behaviour of the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages. It should be noted, though, that as of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. Moreover, while the old versioning scheme is allowed, given there is no more a "final" flag, there is no way guaranteeing the consistency across (% style="color:#e74c3c" %)version(%%) of a Maintainable, unless semantic versioning is used.263 +The following table defines the behaviour of the [[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]] for the various Registry Interface messages. It should be noted, though, that as of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all [[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]. Moreover, while the old versioning scheme is allowed, given there is no more 262 262 263 - Given theabove,the behaviour described in thefollowing tableconcerns either draft [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] usingsemantic versioning or any [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] using the old versioning scheme. Nevertheless,inthecase of semantic versioning theregistrymust respect the versioning rules when performingthe actions below. For example, it is not possible to replace a non-draft [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]]that follows semantic versioning,unlessanewer(% style="color:#e74c3c" %)version(%%) is introduced according to thesemanticversioning rules. Furthermore, evenwhen draft [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]are submitted, the registry has to verify semanticversioning isrespectedagainst the previous non-draft(% style="color:#e74c3c" %)versions(%%).It is worth noting that the rulesforsemanticversioningand replacing or maintaining semantically versioned [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] appliesto externally shared [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]].Thismeans that any systemmay internally perform any change within a (% style="color:#e74c3c"%)version(%%) of an [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]], until the latter is shared outside of that system or becomes public. Then(as also explained in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]Standards Section 6 “Technical Notes”)the [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] must adhere to the Semantic Versioning rules.265 +a "final" flag, there is no way guaranteeing the consistency across (% style="color:#e74c3c" %)version(%%) of a Maintainable, unless semantic versioning is used. 264 264 267 +Given the above, the behaviour described in the following table concerns either draft [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] using semantic versioning or any [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] using the old versioning scheme. Nevertheless, in the case of semantic versioning the registry must respect the versioning rules when performing the actions below. For example, it is not possible to replace a non-draft [[Artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that follows semantic versioning, unless a newer (% style="color:#e74c3c" %)version(%%) is introduced according to the semantic versioning rules. Furthermore, even when draft [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] are submitted, the registry has to verify semantic versioning is respected against the previous non-draft (% style="color:#e74c3c" %)versions(%%). It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] applies to externally shared [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]. This means that any system may internally perform any change within a (% style="color:#e74c3c" %)version(%%) of an [[Artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]], until the latter is shared outside of that system or becomes public. Then (as also explained in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”) the [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] must adhere to the Semantic Versioning rules. 268 + 265 265 (% style="width:982.835px" %) 266 266 |(% style="width:217px" %)**Interface**|(% style="width:763px" %)**Behaviour** 267 267 |(% style="width:217px" %)All|(% style="width:763px" %)((( 268 -1. If the action is set to “replace” (or a [[maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted. 272 +1. If the action is set to “replace” (or a [[maintainable Artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] is PUT or POSTed) then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted. 269 269 1. Cross referenced structures MUST exist in either the submitted document (in Structures or Structure Location) or in the registry to which the request is submitted. 270 -1. If the action is set to “delete” (or a [[maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must: 274 +1. If the action is set to “delete” (or a [[maintainable Artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] is DELETEd) then the Registry MUST verify that the object can be deleted. In order to qualify for deletion, the object must: 271 271 272 272 a) Be a draft (% style="color:#e74c3c" %)version(%%). 273 273 b) Not be explicitly{{footnote}}With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4draft does not break integrity of the aforementioned DSD.{{/footnote}} referenced from any other object in the Registry. 274 274 275 -4) The semantic versioning rules in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] documentation MUST be obeyed. 279 +4) The semantic versioning rules in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] documentation MUST be obeyed. 276 276 ))) 277 277 |(% style="width:217px" %)Structure submission|(% style="width:763px" %)((( 278 -Structures are submitted at the (% style="color:#e74c3c" %)level(%%) of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the (% style="color:#e74c3c" %)level(%%) of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. 282 +Structures are submitted at the (% style="color:#e74c3c" %)level(%%) of the [[Maintainable Artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the (% style="color:#e74c3c" %)level(%%) of the [[Maintainable Artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]. 279 279 ))) 280 -|(% style="width:217px" %)SubmitRegistrationRequest|(% style="width:763px" %)If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] data query. 284 +|(% style="width:217px" %)SubmitRegistrationRequest|(% style="width:763px" %)If the datasource is a file (simple datasource) then the file MAY be retrieved and indexed according to the Boolean [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] set in the Registration. For a queryable datasource the Registry MAY validate that the source exists and can accept an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] data query. 281 281 282 282 = 6 Identification of SDMX Objects = 283 283 284 284 == 6.1 Identification, Versioning, and Maintenance == 285 285 286 -All major classes of the [[SDMX Information model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] inherit from one of: 290 +All major classes of the [[SDMX Information model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] inherit from one of: 287 287 288 -* //**IdentifiableArtefact**// – this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual annotations. 292 +* //**IdentifiableArtefact**// – this gives an object the ability to be uniquely identified (see following section on identification), to have a user-defined URI, and to have multi-lingual [[annotations>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]]. 289 289 * //**NameableArtefact**// – this has all of the features of //IdentifiableArtefact// plus the ability to have a multi-lingual name and description. 290 -* //**VersionableArtefact**// – this has all of the above features plus a (% style="color:#e74c3c" %)version(%%) number, according to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period. 294 +* //**VersionableArtefact**// – this has all of the above features plus a (% style="color:#e74c3c" %)version(%%) number, according to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period. 291 291 * //**MaintainableArtefact**// – this has all of the above features, plus registry and structure URIs, and an association to the maintenance organisation of the object. 292 292 293 293 === 6.1.1 Identification, Naming, Versioning, and Maintenance Model === ... ... @@ -294,9 +294,9 @@ 294 294 295 295 [[image:SDMX 3.1 Section 5_en_4a9b2cfc.jpg||height="688" width="587"]] 296 296 297 -**Figure 5: Class diagram of fundamental artefacts in the SDMX-IM** 301 +**Figure 5: Class diagram of fundamental [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] in the [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]** 298 298 299 -The table below shows the identification and related data [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] to be stored in a registry for objects that are one of: 303 +The table below shows the identification and related data [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] to be stored in a registry for objects that are one of: 300 300 301 301 * //Annotable// 302 302 * //Identifiable// ... ... @@ -305,7 +305,7 @@ 305 305 * //Maintainable// 306 306 307 307 (% style="width:1038.83px" %) 308 -|(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]]**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes** 312 +|(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data [[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes** 309 309 |(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) 310 310 |(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) 311 311 |(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %) ... ... @@ -321,48 +321,48 @@ 321 321 )))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) 322 322 |(% colspan="2" %)((( 323 323 Name in the form of InternationalString 324 -)))|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants. 328 +)))|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This can have [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] specific variants. 325 325 |(% colspan="2" %)((( 326 326 Description in the form of InternationalString 327 -)))|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants. 331 +)))|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)This can have [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] specific variants. 328 328 |(% colspan="2" rowspan="4" %)//Versionable//|(% colspan="2" %)((( 329 329 All content as for 330 330 331 331 //Identifiable// plus 332 332 )))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) 333 -|(% colspan="2" %)(% style="color:#e74c3c" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the (% style="color:#e74c3c" %)version(%%) number according to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules. 337 +|(% colspan="2" %)(% style="color:#e74c3c" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the (% style="color:#e74c3c" %)version(%%) number according to [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules. 334 334 |(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %) 335 335 |(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %) 336 336 |(% colspan="2" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) 337 -|(% colspan="2" %) |(% colspan="2" %)[[isExternalReference>>doc:sdmx:Glossary.isExternalReference.WebHome]]|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file. 341 +|(% colspan="2" %) |(% colspan="2" %)[[isExternalReference>>doc:sdmx:Glossary 2\.1.isExternalReference.WebHome]]|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] file. 338 338 |(% colspan="2" %) |(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource. 339 339 |(% colspan="2" %) |(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource. 340 340 |(% colspan="2" %) |(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider. 341 341 342 -**Table 1: Common Attributes of Object Types** 346 +**Table 1: Common [[Attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] of Object Types** 343 343 344 344 == 6.2 Unique identification of SDMX objects == 345 345 346 346 === 6.2.1 Agencies and Metadata Providers === 347 347 348 -The [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is maintained in an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] which itself is a sub class of Organisation Scheme – this is shown in the class diagram below. 352 +The [[Maintenance Agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] is maintained in an [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] which itself is a sub class of Organisation Scheme – this is shown in the class diagram below. 349 349 350 350 [[image:SDMX 3.1 Section 5_en_67b3555e.jpg||height="313" width="554"]] 351 351 352 -**Figure 6: Agency Scheme Model** 356 +**Figure 6: [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] Model** 353 353 354 -The Agency in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is an nlevel structure. The top (% style="color:#e74c3c" %)level(%%) of this structure is maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top (% style="color:#e74c3c" %)level(%%) can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] has a fixed id and (% style="color:#e74c3c" %)version(%%) ((% style="color:#e74c3c" %)version(%%) ‘1.0’) and is never declared explicitly in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism. 358 +The Agency in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] is an nlevel structure. The top (% style="color:#e74c3c" %)level(%%) of this structure is maintained by [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]. Any Agency in this top (% style="color:#e74c3c" %)level(%%) can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] has a fixed id and (% style="color:#e74c3c" %)version(%%) ((% style="color:#e74c3c" %)version(%%) ‘1.0’) and is never declared explicitly in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] object identification mechanism. 355 355 356 -In order to achieve this [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] adopts the following rules: 360 +In order to achieve this [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] adopts the following rules: 357 357 358 -* Agencies are maintained in an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme). 359 -* The agency of the [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] must also be declared in a (different) [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. 360 -* The “top-(% style="color:#e74c3c" %)level(%%)” agency is [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-(% style="color:#e74c3c" %)level(%%)” [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. 361 -* Agencies registered in the top-(% style="color:#e74c3c" %)level(%%) scheme can themselves maintain a single [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] and so on. 362 -* The AgencyScheme has a fixed (% style="color:#e74c3c" %)version(%%), i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] follow. 362 +* Agencies are maintained in an [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme). 363 +* The agency of the [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] must also be declared in a (different) [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]. 364 +* The “top-(% style="color:#e74c3c" %)level(%%)” agency is [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] and maintains the “top-(% style="color:#e74c3c" %)level(%%)” [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]. 365 +* Agencies registered in the top-(% style="color:#e74c3c" %)level(%%) scheme can themselves maintain a single [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] and so on. 366 +* The AgencyScheme has a fixed (% style="color:#e74c3c" %)version(%%), i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] follow. 363 363 * There can be only one AgencyScheme maintained by any one Agency. It has a fixed id of AGENCIES. 364 -* The /[[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of Organisation is not inherited by [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] – thus each [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] is a flat list of [[Maintenance Agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]]. 365 -* The format of the agency identifier is agencyID.agencyID etc. The top-(% style="color:#e74c3c" %)level(%%) agency in this identification mechanism is the agency registered in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. In other words, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However, [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] and is contained in the top-(% style="color:#e74c3c" %)level(%%) [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. 368 +* The /[[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] of Organisation is not inherited by [[Maintenance Agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] – thus each [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]] is a flat list of [[Maintenance Agencies>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]]. 369 +* The format of the agency identifier is agencyID.agencyID etc. The top-(% style="color:#e74c3c" %)level(%%) agency in this identification mechanism is the agency registered in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]. In other words, [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However, [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] and is contained in the top-(% style="color:#e74c3c" %)level(%%) [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]. 366 366 367 367 This supports a hierarchical structure of agencyID. 368 368 ... ... @@ -372,14 +372,14 @@ 372 372 373 373 **Figure 7: Example of Hierarchic Structure of Agencies** 374 374 375 -The following organizations maintain an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]. 379 +The following organizations maintain an [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]. 376 376 377 -* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] – contains Agencies AA, BB 381 +* [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] – contains Agencies AA, BB 378 378 * AA – contains Agencies CC, DD 379 379 * BB – contains Agencies CC, DD 380 380 * DD – Contains Agency EE 381 381 382 -Each agency is identified by its full [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] excluding [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. 386 +Each agency is identified by its full [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] excluding [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]. 383 383 384 384 e.g., the id of EE as an agencyID is AA.DD.EE 385 385 ... ... @@ -389,47 +389,47 @@ 389 389 390 390 **Figure 8: Example Showing Use of Agency Identifiers** 391 391 392 -Each of these [[maintenance agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]] has an identical [[Code list>>doc:sdmx:Glossary.Code list.WebHome]] with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure. 396 +Each of these [[maintenance agencies>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] has an identical [[Code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure. 393 393 394 -Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]], i.e., the Metadatasets; the latter are the containers of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] combined with a target that those metadata refer to. 398 +Following the same principles, the Metadata Provider is the maintenance organisation for a special subset of [[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]], i.e., the Metadatasets; the latter are the containers of [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] combined with a target that those metadata refer to. 395 395 396 396 === 6.2.2 Universal Resource Name (URN) === 397 397 398 398 ==== 6.2.2.1 Introduction ==== 399 399 400 -To provide interoperability between [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/Repositories in a distributed network environment, it is important to have a scheme for uniquely identifying (and thus accessing) all first-class (Identifiable) [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] objects. Most of these unique identifiers are composite (containing [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]], or parent object identifiers), and there is a need to be able to construct a unique reference as a single string. This is achieved by having a globally unique identifier called a universal resource name (URN) which is generated from the actual identification [[components>>doc:sdmx:Glossary.Component.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR APIs. In other words, the URN for any [[Identifiable Artefact>>doc:sdmx:Glossary.Identifiable artefact.WebHome]] is constructed from its [[component>>doc:sdmx:Glossary.Component.WebHome]] identifiers (agency, id, (% style="color:#e74c3c" %)version(%%) etc.). 404 +To provide interoperability between [[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]/Repositories in a distributed network environment, it is important to have a scheme for uniquely identifying (and thus accessing) all first-class (Identifiable) [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] objects. Most of these unique identifiers are composite (containing [[maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]], or parent object identifiers), and there is a need to be able to construct a unique reference as a single string. This is achieved by having a globally unique identifier called a universal resource name (URN) which is generated from the actual identification [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR APIs. In other words, the URN for any [[Identifiable Artefact>>doc:sdmx:Glossary 2\.1.Identifiable artefact.WebHome]] is constructed from its [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] identifiers (agency, id, (% style="color:#e74c3c" %)version(%%) etc.). 401 401 402 402 ==== 6.2.2.2 URN Structure //__Case Rules for URN__// ==== 403 403 404 404 For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows: 405 405 406 -SDMXprefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-(% style="color:#e74c3c" %)version(%%)).*containerobject-id.object-id 410 +SDMXprefix.[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-(% style="color:#e74c3c" %)version(%%)).*containerobject-id.object-id 407 407 408 408 ~* this can repeat and may not be present (see explanation below) 409 409 410 -Note that in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:sdmx:Glossary.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. For this reason, the only (% style="color:#e74c3c" %)version(%%) information that is allowed is for the maintainable object. 414 +Note that in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:sdmx:Glossary 2\.1.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]. For this reason, the only (% style="color:#e74c3c" %)version(%%) information that is allowed is for the maintainable object. 411 411 412 -The [[Maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period ‘.’. The (% style="color:#e74c3c" %)version(%%) information is encapsulated in parentheses ‘()’ and adheres to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning. 416 +The [[Maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period ‘.’. The (% style="color:#e74c3c" %)version(%%) information is encapsulated in parentheses ‘()’ and adheres to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning. 413 413 414 414 ==== 6.2.2.3 Explanation of the generic structure ==== 415 415 416 416 In the explanation below the actual object that is the target of the URN is called the **actual object**. 417 417 418 -**SDMXPrefix**: urn:sdmx:org 422 +**SDMXPrefix**: urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:org 419 419 420 -**SDMX-IM-package-name**: sdmx.infomodel.package= 424 +**[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name**: [[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.package= 421 421 422 422 The packages are: 423 423 424 -base codelist conceptscheme datastructure categoryscheme registry metadatastructure process structuremapping transformation 428 +base [[codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] conceptscheme datastructure categoryscheme registry metadatastructure process structuremapping transformation 425 425 426 426 **maintainable-object-id** is the identifier of the maintainable object. This will always be present as all identifiable objects are either a maintainable object or contained in a maintainable object. 427 427 428 -**maintainable-object-version** is the (% style="color:#e74c3c" %)version(%%), according to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present. 432 +**maintainable-object-(% style="color:#e74c3c" %)version(%%)** is the (% style="color:#e74c3c" %)version(%%), according to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present. 429 429 430 -**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a [[Code>>doc:sdmx:Glossary.Code.WebHome]] is in a maintained object (Codelist) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower (% style="color:#e74c3c" %)level(%%) in its [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]/ TimeDimension, or a Measure. 434 +**container-object-id** is the identifier of an intermediary object that contains the actual object which the URN is identifying. It is not mandatory as many actual objects do not have an intermediary container object. For instance, a [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] is in a maintained object ([[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]) and has no intermediary container object, whereas a MetadataAttribute has an intermediary container object (MetadataAttributeDescriptor) and may have an intermediary container object, which is its parent MetadataAttribute. For this reason, the container object id may repeat, with each repetition identifying the object at the next-lower (% style="color:#e74c3c" %)level(%%) in its [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]. Note that if there is only a single containing object in the model then it is NOT included in the URN structure. This applies to AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor where there can be only one such object and this object has a fixed id. Therefore, whilst each of these has a URN, the id of the AttributeDescriptor, DimensionDescriptor, and MeasureDescriptor is not included when the actual object is a DataAttribute or a [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]/ TimeDimension, or a [[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]]. 431 431 432 -Note that although a [[Code>>doc:sdmx:Glossary.Code.WebHome]] can have a parent [[Code>>doc:sdmx:Glossary.Code.WebHome]] and a (% style="color:#e74c3c" %)Concept(%%) can have a parent (% style="color:#e74c3c" %)Concept(%%) these are maintained in a flat structure and therefore do not have a containerobject-id. 436 +Note that although a [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] can have a parent [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and a (% style="color:#e74c3c" %)Concept(%%) can have a parent (% style="color:#e74c3c" %)Concept(%%) these are maintained in a flat structure and therefore do not have a containerobject-id. 433 433 434 434 For example, the sequence is agency:DSDid((% style="color:#e74c3c" %)version(%%)).DimensionId and not agency:DSDid((% style="color:#e74c3c" %)version(%%)).DimensionDescriptorId.DimensionId. 435 435 ... ... @@ -439,60 +439,60 @@ 439 439 440 440 __Actual object is a maintainable__ 441 441 442 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version) 446 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)) 443 443 444 444 __Actual object is contained in a maintained object with no intermediate containing object__ 445 445 446 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).object-id 450 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).object-id 447 447 448 448 __Actual object is contained in a maintained object with an intermediate containing object__ 449 449 450 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id 454 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).contained-object-id.object-id 451 451 452 452 __Actual object is contained in a maintained object with no intermediate containing__ __object but__ __the object type itself is hierarchical__ 453 453 454 -In this case the object id may not be unique in itself but only within the context of the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a [[Category>>doc:sdmx:Glossary.Category.WebHome]] in a CategoryScheme. The [[Category>>doc:sdmx:Glossary.Category.WebHome]] is hierarchical, and all intermediate [[Categories>>doc:sdmx:Glossary.Category.WebHome]] are shown as a contained object. The example below shows the generic structure for CategoryScheme/ [[Category>>doc:sdmx:Glossary.Category.WebHome]]/ [[Category>>doc:sdmx:Glossary.Category.WebHome]]. 458 +In this case the object id may not be unique in itself but only within the context of the [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] in a CategoryScheme. The [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] is hierarchical, and all intermediate [[Categories>>doc:sdmx:Glossary 2\.1.Category.WebHome]] are shown as a contained object. The example below shows the generic structure for CategoryScheme/ [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]/ [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]. 455 455 456 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id 460 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).contained-object-id.object-id 457 457 458 458 Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical 459 459 460 -In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a MetadataAttribute where the contained objects are MetadataAttributeDescriptor (first contained object id) and MetadataAttribute (subsequent contained object ids). The example below shows the generic structure for [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]/ MetadataAttributeDescriptor/ MetadataAttribute/ MetadataAttribute 464 +In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a MetadataAttribute where the contained objects are MetadataAttributeDescriptor (first contained object id) and MetadataAttribute (subsequent contained object ids). The example below shows the generic structure for [[MSD>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]/ MetadataAttributeDescriptor/ MetadataAttribute/ MetadataAttribute 461 461 462 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id 466 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).contained-object-id.contained-object-id contained-objectid.object-id 463 463 464 464 //__**Concrete Examples of the URN Structure**__// 465 465 466 -The [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] CRED_EXT_DEBT of legacy (% style="color:#e74c3c" %)version(%%) 2.1 maintained by the toplevel Agency TFFS would have the URN: 470 +The [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] CRED_EXT_DEBT of legacy (% style="color:#e74c3c" %)version(%%) 2.1 maintained by the toplevel Agency TFFS would have the URN: 467 467 468 -urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1) 472 +urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1) 469 469 470 -The URN for a [[code>>doc:sdmx:Glossary.Code.WebHome]] for Argentina maintained by ISO in the [[code list>>doc:sdmx:Glossary.Code list.WebHome]] CL_3166A2 of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 would be: 474 +The URN for a [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] for Argentina maintained by ISO in the [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] CL_3166A2 of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 would be: 471 471 472 -urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0.0).AR 476 +urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.[[codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]].[[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]]=ISO:CL_3166A2(1.0.0).AR 473 473 474 -The URN for a [[category>>doc:sdmx:Glossary.Category.WebHome]] (id of 1) which has parent [[category>>doc:sdmx:Glossary.Category.WebHome]] (id of 2) maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] in the [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] SUBJECT_MATTER_DOMAINS of the semantic extended (% style="color:#e74c3c" %)version(%%) 1.0.0draft would be: 478 +The URN for a [[category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] (id of 1) which has parent [[category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] (id of 2) maintained by [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] in the [[category scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] SUBJECT_MATTER_DOMAINS of the semantic extended (% style="color:#e74c3c" %)version(%%) 1.0.0draft would be: 475 475 476 -urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2 480 +urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.categoryscheme.[[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]=[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2 477 477 478 -The URN for a Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] in the [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] CONTACT_METADATA of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 where the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] of the Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is CONTACT_DETAILS/CONTACT_NAME would be: 482 +The URN for a Metadata [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] maintained by [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] in the [[MSD>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] CONTACT_METADATA of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 where the [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] of the Metadata [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] is CONTACT_DETAILS/CONTACT_NAME would be: 479 479 480 -urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribute=SDMX: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME 484 +urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.metadatastructure.MetadataAttribute=[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME 481 481 482 -The TFFS defines ABC as a sub-Agency of TFFS then the URN of a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] maintained by ABC and identified as EXTERNAL_DEBT of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 would be: 486 +The TFFS defines ABC as a sub-Agency of TFFS then the URN of a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] maintained by ABC and identified as EXTERNAL_DEBT of semantic (% style="color:#e74c3c" %)version(%%) 1.0.0 would be: 483 483 484 -urn:sdmx:org.sdmx.infomodel.datastructure.[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]=TFFS.ABC:EXTERNAL_ DEBT(1.0.0) 488 +urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.datastructure.[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]=TFFS.ABC:EXTERNAL_ DEBT(1.0.0) 485 485 486 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST support this globally unique identification scheme. The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to create the URN from the individual identification [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] submitted and to transform the URN to these identification [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. The identification [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are: 490 +The [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR MUST support this globally unique identification scheme. The [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR MUST be able to create the URN from the individual identification [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] submitted and to transform the URN to these identification [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]. The identification [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] are: 487 487 488 -* **Identifiable and [[Nameable Artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]]**: id (in some cases this id may be hierarchic) 489 -* **[[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]**: id, (% style="color:#e74c3c" %)version(%%), agencyId 492 +* **Identifiable and [[Nameable Artefacts>>doc:sdmx:Glossary 2\.1.Nameable artefact.WebHome]]**: id (in some cases this id may be hierarchic) 493 +* **[[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]**: id, (% style="color:#e74c3c" %)version(%%), agencyId 490 490 491 -The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to resolve the unique identifier of an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] and to produce an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] rendering of that [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] if it is located in the Registry. 495 +The [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR MUST be able to resolve the unique identifier of an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] and to produce an [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] rendering of that [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] if it is located in the Registry. 492 492 493 493 === 6.2.3 Table of SDMX-IM Packages and Classes === 494 494 495 -The table below lists all of the packages in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] together with the concrete classes that are in these packages and whose objects have a URN. 499 +The table below lists all of the packages in the [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] together with the concrete classes that are in these packages and whose objects have a URN. 496 496 497 497 (% style="width:750.835px" %) 498 498 |(% style="width:222px" %)**Package**|(% style="width:526px" %)**URN class name (model class name where this is different)** ... ... @@ -509,12 +509,12 @@ 509 509 |(% style="width:222px" %) |(% style="width:526px" %) 510 510 |(% style="width:222px" %)datastructure|(% style="width:526px" %)AttributeDescriptor 511 511 |(% style="width:222px" %) |(% style="width:526px" %)DataAttribute 512 -|(% style="width:222px" %) |(% style="width:526px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] 516 +|(% style="width:222px" %) |(% style="width:526px" %)[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] 513 513 |(% style="width:222px" %) |(% style="width:526px" %)DataStructure (DataStructureDefinition) 514 -|(% style="width:222px" %) |(% style="width:526px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] 518 +|(% style="width:222px" %) |(% style="width:526px" %)[[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] 515 515 |(% style="width:222px" %) |(% style="width:526px" %)DimensionDescriptor 516 516 |(% style="width:222px" %) |(% style="width:526px" %)GroupDimensionDescriptor 517 -|(% style="width:222px" %) |(% style="width:526px" %)Measure 521 +|(% style="width:222px" %) |(% style="width:526px" %)[[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]] 518 518 |(% style="width:222px" %) |(% style="width:526px" %)MeasureDescriptor 519 519 |(% style="width:222px" %) |(% style="width:526px" %)TimeDimension 520 520 |(% style="width:222px" %) |(% style="width:526px" %) ... ... @@ -529,7 +529,7 @@ 529 529 ((( 530 530 (% style="width:751.835px" %) 531 531 |(% style="width:221px" %)**Package**|(% style="width:528px" %)**URN class name (model class name where this is different)** 532 -|(% style="width:221px" %) |(% style="width:528px" %)[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] 536 +|(% style="width:221px" %) |(% style="width:528px" %)[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] 533 533 |(% style="width:221px" %) |(% style="width:528px" %)MetadataSet 534 534 |(% style="width:221px" %) |(% style="width:528px" %) 535 535 |(% style="width:221px" %)process|(% style="width:528px" %)Process ... ... @@ -540,7 +540,7 @@ 540 540 |(% style="width:221px" %) |(% style="width:528px" %)MetadataConstraint 541 541 |(% style="width:221px" %) |(% style="width:528px" %)MetadataProvisionAgreement 542 542 |(% style="width:221px" %) |(% style="width:528px" %)ProvisionAgreement 543 -|(% style="width:221px" %) |(% style="width:528px" %)[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] 547 +|(% style="width:221px" %) |(% style="width:528px" %)[[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] 544 544 |(% style="width:221px" %) |(% style="width:528px" %) 545 545 |(% style="width:221px" %)structuremapping|(% style="width:528px" %)CategorySchemeMap 546 546 |(% style="width:221px" %) |(% style="width:528px" %)ConceptSchemeMap ... ... @@ -549,16 +549,16 @@ 549 549 |(% style="width:221px" %) |(% style="width:528px" %)RepresentationMap 550 550 |(% style="width:221px" %) |(% style="width:528px" %)StructureMap 551 551 |(% style="width:221px" %) |(% style="width:528px" %) 552 -|(% style="width:221px" %)codelist|(% style="width:528px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]] 553 -|(% style="width:221px" %) |(% style="width:528px" %)Codelist 556 +|(% style="width:221px" %)[[codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]|(% style="width:528px" %)[[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] 557 +|(% style="width:221px" %) |(% style="width:528px" %)[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] 554 554 |(% style="width:221px" %) |(% style="width:528px" %)HierarchicalCode 555 -|(% style="width:221px" %) |(% style="width:528px" %)[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] 559 +|(% style="width:221px" %) |(% style="width:528px" %)[[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] 556 556 |(% style="width:221px" %) |(% style="width:528px" %)HierarchyAssociation 557 557 |(% style="width:221px" %) |(% style="width:528px" %)(% style="color:#e74c3c" %)Level 558 558 |(% style="width:221px" %) |(% style="width:528px" %)ValueList 559 559 |(% style="width:221px" %) |(% style="width:528px" %) 560 -|(% style="width:221px" %)categoryscheme|(% style="width:528px" %)Categorisation 561 -|(% style="width:221px" %) |(% style="width:528px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]] 564 +|(% style="width:221px" %)categoryscheme|(% style="width:528px" %)[[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] 565 +|(% style="width:221px" %) |(% style="width:528px" %)[[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] 562 562 |(% style="width:221px" %) |(% style="width:528px" %)CategoryScheme 563 563 |(% style="width:221px" %) |(% style="width:528px" %)ReportingCategory 564 564 |(% style="width:221px" %) |(% style="width:528px" %)ReportingTaxonomy ... ... @@ -583,55 +583,55 @@ 583 583 |(% style="width:221px" %) |(% style="width:528px" %) 584 584 ))) 585 585 586 -**Table 2: SDMX-IM Packages and Contained Classes** 590 +**Table 2: [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] Packages and Contained Classes** 587 587 588 588 === 6.2.4 URN Identification components of SDMX objects === 589 589 590 -The table below describes the identification [[components>>doc:sdmx:Glossary.Component.WebHome]] for all [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object types that have identification. Note the actual [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are all ‘id’ but have been prefixed by their class name or multiple class names to show navigation, e.g., ‘conceptSchemeAgencyId’ is really the ‘Id’ [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] of the Agency class that is associated to the ConceptScheme. 594 +The table below describes the identification [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] for all [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] object types that have identification. Note the actual [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] are all ‘id’ but have been prefixed by their class name or multiple class names to show navigation, e.g., ‘conceptSchemeAgencyId’ is really the ‘Id’ [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] of the Agency class that is associated to the ConceptScheme. 591 591 592 592 Note that for brevity the URN examples omit the prefix (classnames in italics indicate maintainable objects, keywords in bold indicate fixed value) All URNs have the prefix: 593 593 594 -urn:sdmx.org.sdmx.infomodel.{package}.{classname}= 598 +urn:[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].org.[[sdmx>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].infomodel.{package}.{classname}= 595 595 596 596 (% style="width:1272.83px" %) 597 597 |(% style="width:289px" %)**Classname**|(% style="width:600px" %)**Ending URN pattern**|(% style="width:383px" %)**Example** 598 598 |(% style="width:289px" %)Agency{{footnote}}The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.{{/footnote}}|(% style="width:600px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:383px" %)ECB:**AGENCIES**(**1.0**).AA 599 599 |(% style="width:289px" %)//AgencyScheme//|(% style="width:600px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:383px" %)ECB:**AGENCIES**(**1.0**) 600 -|(% style="width:289px" %)//Categorisation//|(% style="width:600px" %)categorisationAgencyId:categoris(% style="color:#000000" %)ationId(version)|(% style="width:383px" %)IMF:cat001(1.0.0) 601 -|(% style="width:289px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]|(% style="width:600px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:383px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category … 604 +|(% style="width:289px" %)//[[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]]//|(% style="width:600px" %)categorisationAgencyId:categoris(% style="color:#000000" %)ationId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:383px" %)IMF:cat001(1.0.0) 605 +|(% style="width:289px" %)[[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]|(% style="width:600px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:383px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category … 602 602 |(% style="width:289px" %)//CategoryScheme//|(% style="width:600px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:383px" %)IMF:SDDS(1.0.0) 603 603 604 604 |(% style="width:285px" %)**Classname**|(% style="width:569px" %)**Ending URN pattern**|(% style="width:794px" %)**Example** 605 605 |(% style="width:285px" %)//CategorySchemeMap//|(% style="width:569px" %)((( 606 -(% style="color:#000000" %)catSchemeMapAgencyId:catSchemeMapId(version) 607 -)))|(% style="width:794px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0) 608 -|(% style="width:285px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]]|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codelistId(version).codeId|(% style="width:794px" %)SDMX:CL_FREQ(1.0.0).Q 609 -|(% style="width:285px" %)//Codelist//|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codeListId(version)|(% style="width:794px" %)SDMX:CL_FREQ(1.0.0) 610 -|(% style="width:285px" %)ComponentMap|(% style="width:569px" %)(% style="color:#000000" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:794px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY 611 -|(% style="width:285px" %)(% style="color:#e74c3c" %)Concept|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:794px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ 612 -|(% style="width:285px" %)//ConceptScheme//|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:794px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0) 610 +(% style="color:#000000" %)catSchemeMapAgencyId:catSchemeMapId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) 611 +)))|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:EUROSTAT_SUBJECT_DOMAIN(1.0.0) 612 +|(% style="width:285px" %)[[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]]|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codelistId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).codeId|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:CL_FREQ(1.0.0).Q 613 +|(% style="width:285px" %)//[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]//|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codeListId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:CL_FREQ(1.0.0) 614 +|(% style="width:285px" %)ComponentMap|(% style="width:569px" %)(% style="color:#000000" %)structureMapAgencyId:structureMap((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).com ponentMapId|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY 615 +|(% style="width:285px" %)(% style="color:#e74c3c" %)Concept|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ 616 +|(% style="width:285px" %)//ConceptScheme//|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:CROSS_DOMAIN_CONCEPTS(1.0.0) 613 613 |(% style="width:285px" %)//ConceptSchemeMap//|(% style="width:569px" %)((( 614 -(% style="color:#000000" %)conceptSchemeMapAgencyId:conceptSchemeMap Id(version) 615 -)))|(% style="width:794px" %)SDMX:CONCEPT_MAP(1.0.0) 616 -|(% style="width:285px" %)CustomType|(% style="width:569px" %)(% style="color:#000000" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:794px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1 617 -|(% style="width:285px" %)//CustomTypeScheme//|(% style="width:569px" %)(% style="color:#000000" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:794px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0) 618 -|(% style="width:285px" %)DataAttrribute|(% style="width:569px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:794px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS 619 -|(% style="width:285px" %)//DataConstraint//|(% style="width:569px" %)(% style="color:#000000" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:794px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0) 618 +(% style="color:#000000" %)conceptSchemeMapAgencyId:conceptSchemeMap Id((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) 619 +)))|(% style="width:794px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:CONCEPT_MAP(1.0.0) 620 +|(% style="width:285px" %)CustomType|(% style="width:569px" %)(% style="color:#000000" %)customTypeSchemeAgencyId customTypeSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) customTypeId|(% style="width:794px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1 621 +|(% style="width:285px" %)//CustomTypeScheme//|(% style="width:569px" %)(% style="color:#000000" %)customTypeSchemeAgencyId customTypeSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:794px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0) 622 +|(% style="width:285px" %)DataAttrribute|(% style="width:569px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).dataAttributeId|(% style="width:794px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS 623 +|(% style="width:285px" %)//DataConstraint//|(% style="width:569px" %)(% style="color:#000000" %)dataConstraintAgencyId:dataConstraintId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:794px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0) 620 620 621 621 |(% style="width:279px" %)**Classname**|(% style="width:563px" %)**Ending URN pattern**|(% style="width:776px" %)**Example** 622 -|(% style="width:279px" %)DataConsumer|(% style="width:563px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:776px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1 626 +|(% style="width:279px" %)DataConsumer|(% style="width:563px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:776px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:**DATA_CONSUMERS**(**1.0**).CONSUMER_1 623 623 |(% style="width:279px" %)//DataConsumerScheme//|(% style="width:563px" %)((( 624 624 dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**) 625 -)))|(% style="width:776px" %)SDMX:**DATA_CONSUMERS**(**1.0**) 626 -|(% style="width:279px" %)//[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]//|(% style="width:563px" %)(% style="color:#000000" %)dataflowAgencyId:dataflowId(version)|(% style="width:776px" %)TFFS:CRED_EXT_DEBT(1.0.0) 629 +)))|(% style="width:776px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:**DATA_CONSUMERS**(**1.0**) 630 +|(% style="width:279px" %)//[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]//|(% style="width:563px" %)(% style="color:#000000" %)dataflowAgencyId:dataflowId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:776px" %)TFFS:CRED_EXT_DEBT(1.0.0) 627 627 |(% style="width:279px" %)DataProvider|(% style="width:563px" %)((( 628 628 (% style="color:#000000" %)dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId 629 -)))|(% style="width:776px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1 633 +)))|(% style="width:776px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:**DATA_PROVIDERS**(**1.0**).PROVIDER_1 630 630 |(% style="width:279px" %)//DataProviderScheme//|(% style="width:563px" %)((( 631 631 (% style="color:#000000" %)dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**) 632 -)))|(% style="width:776px" %)SDMX:**DATA_PROVIDERS**(**1.0**) 633 -|(% style="width:279px" %)//DataStructure//|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0) 634 -|(% style="width:279px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0).FREQ 636 +)))|(% style="width:776px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:**DATA_PROVIDERS**(**1.0**) 637 +|(% style="width:279px" %)//DataStructure//|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0) 638 +|(% style="width:279px" %)[[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).dimensionId|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0).FREQ 635 635 |(% style="width:279px" %)((( 636 636 DimensionDescriptor 637 637 ... ... @@ -639,9 +639,9 @@ 639 639 640 640 AttributeDescriptor 641 641 )))|(% style="width:563px" %)((( 642 -dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: #000000" %)version)(%%).componentListId646 +dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))(%%).componentListId 643 643 644 -where the componentListId is the name of the class (there is only one occurrence of each in the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]) 648 +where the componentListId is the name of the class (there is only one occurrence of each in the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]) 645 645 )))|(% style="width:776px" %)((( 646 646 TFFS:EXT_DEBT(1.0.0).DimensionDescriptor 647 647 ... ... @@ -649,75 +649,75 @@ 649 649 650 650 TFFS:EXT_DEBT(1.0.0).AttributeDescriptor 651 651 ))) 652 -|(% style="width:279px" %)GroupDimensionDescriptor|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0).SIBLING 653 -|(% style="width:279px" %)HierarchicalCode|(% style="width:563px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:776px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1 656 +|(% style="width:279px" %)GroupDimensionDescriptor|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).groupDimensionDescriptorId|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0).SIBLING 657 +|(% style="width:279px" %)HierarchicalCode|(% style="width:563px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).hierarchica lCode.hierarchicalCode|(% style="width:776px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1 654 654 655 655 |(% style="width:281px" %)**Classname**|(% style="width:562px" %)**Ending URN pattern**|(% style="width:772px" %)**Example** 656 -|(% style="width:281px" %)//[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]//|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0) 657 -|(% style="width:281px" %)//HierarchyAssociation//|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:772px" %)UNESCO:CL_EXP_SOURCE(1.0.0) 658 -|(% style="width:281px" %)(% style="color:#e74c3c" %)Level|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0).LVL1 659 -|(% style="width:281px" %)Measure|(% style="width:562px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:772px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE 660 +|(% style="width:281px" %)//[[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]//|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0) 661 +|(% style="width:281px" %)//HierarchyAssociation//|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)UNESCO:CL_EXP_SOURCE(1.0.0) 662 +|(% style="width:281px" %)(% style="color:#e74c3c" %)Level|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).(% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)level|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0).LVL1 663 +|(% style="width:281px" %)[[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]]|(% style="width:562px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).measureId|(% style="width:772px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE 660 660 |(% style="width:281px" %)MetadataAttribute|(% style="width:562px" %)((( 661 -(% style="color:#000000" %)msdAgencyId:msdId(version).metadataAttributeId. 665 +(% style="color:#000000" %)msdAgencyId:msdId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).metadataAttributeId. 662 662 663 663 (% style="color:#000000" %)metadataAttributeId 664 664 )))|(% style="width:772px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD 665 -|(% style="width:281px" %)MetadataAttributeDescriptor|(% style="width:562px" %)(% style="color:#000000" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:772px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor 666 -|(% style="width:281px" %)//MetadataConstraint//|(% style="width:562px" %)(% style="color:#000000" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:772px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0) 667 -|(% style="width:281px" %)//[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]//|(% style="width:562px" %)(% style="color:#000000" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:772px" %)IMF:SDDS_MDF(1.0.0) 668 -|(% style="width:281px" %)MetadataProvider|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:772px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1 669 -|(% style="width:281px" %)//MetadataProviderScheme//|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:772px" %)SDMX:**METADATA_PROVIDERS**(**1.0**) 670 -|(% style="width:281px" %)//MetadataProvisionAgreement//|(% style="width:562px" %)(% style="color:#000000" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:772px" %)IMF:SDDS_MDF_AB(1.0.0) 671 -|(% style="width:281px" %)//MetadataSet//|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderId:metadataSetId(version)|(% style="width:772px" %)MD_PROVIDER:METADATASET(1.0.0) 672 -|(% style="width:281px" %)//MetadataStructure//|(% style="width:562px" %)(% style="color:#000000" %)msdAgencyId:msdId(version)|(% style="width:772px" %)IMF:SDDS_MSD(1.0.0) 669 +|(% style="width:281px" %)MetadataAttributeDescriptor|(% style="width:562px" %)(% style="color:#000000" %)msdAgencyId:msdId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).metadataAttributeDe scriptorId|(% style="width:772px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor 670 +|(% style="width:281px" %)//MetadataConstraint//|(% style="width:562px" %)(% style="color:#000000" %)metadataConstraintAgencyId:metadataConstraintI d((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0) 671 +|(% style="width:281px" %)//[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]//|(% style="width:562px" %)(% style="color:#000000" %)metadataflowAgencyId:metadataflowId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)IMF:SDDS_MDF(1.0.0) 672 +|(% style="width:281px" %)MetadataProvider|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:772px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1 673 +|(% style="width:281px" %)//MetadataProviderScheme//|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:772px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:**METADATA_PROVIDERS**(**1.0**) 674 +|(% style="width:281px" %)//MetadataProvisionAgreement//|(% style="width:562px" %)(% style="color:#000000" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)IMF:SDDS_MDF_AB(1.0.0) 675 +|(% style="width:281px" %)//MetadataSet//|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderId:metadataSetId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)MD_PROVIDER:METADATASET(1.0.0) 676 +|(% style="width:281px" %)//MetadataStructure//|(% style="width:562px" %)(% style="color:#000000" %)msdAgencyId:msdId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:772px" %)IMF:SDDS_MSD(1.0.0) 673 673 674 674 |(% style="width:283px" %)**Classname**|(% style="width:564px" %)**Ending URN pattern**|(% style="width:771px" %)**Example** 675 -|(% style="width:283px" %)NamePersonalisation|(% style="width:564px" %)(% style="color:#000000" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:771px" %)ECB:PSN_SCHEME(1.0.0).PSN1234 676 -|(% style="width:283px" %)//NamePersonalisationScheme//|(% style="width:564px" %)(% style="color:#000000" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:771px" %)ECB:PSN_SCHEME(1.0.0) 677 -|(% style="width:283px" %)//OrganisationSchemeMap//|(% style="width:564px" %)(% style="color:#000000" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:771px" %)SDMX:AGENCIES_PROVIDERS(1.0.0) 678 -|(% style="width:283px" %)OrganisationUnit|(% style="width:564px" %)(% style="color:#000000" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version).organisationUnitId|(% style="width:771px" %)ECB:ORGANISATIONS(1.0.0).1F 679 -|(% style="width:283px" %)//OrganisationUnitScheme//|(% style="width:564px" %)(% style="color:#000000" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:771px" %)ECB:ORGANISATIONS(1.0.0) 680 -|(% style="width:283px" %)//Process//|(% style="width:564px" %)(% style="color:#000000" %)processAgencyId:processId{version)|(% style="width:771px" %)BIS:PROCESS1(1.0.0) 679 +|(% style="width:283px" %)NamePersonalisation|(% style="width:564px" %)(% style="color:#000000" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) namePersonalisationId|(% style="width:771px" %)ECB:PSN_SCHEME(1.0.0).PSN1234 680 +|(% style="width:283px" %)//NamePersonalisationScheme//|(% style="width:564px" %)(% style="color:#000000" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:771px" %)ECB:PSN_SCHEME(1.0.0) 681 +|(% style="width:283px" %)//OrganisationSchemeMap//|(% style="width:564px" %)(% style="color:#000000" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:771px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:AGENCIES_PROVIDERS(1.0.0) 682 +|(% style="width:283px" %)OrganisationUnit|(% style="width:564px" %)(% style="color:#000000" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).organisationUnitId|(% style="width:771px" %)ECB:ORGANISATIONS(1.0.0).1F 683 +|(% style="width:283px" %)//OrganisationUnitScheme//|(% style="width:564px" %)(% style="color:#000000" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:771px" %)ECB:ORGANISATIONS(1.0.0) 684 +|(% style="width:283px" %)//Process//|(% style="width:564px" %)(% style="color:#000000" %)processAgencyId:processId{(% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:771px" %)BIS:PROCESS1(1.0.0) 681 681 |(% style="width:283px" %)ProcessStep|(% style="width:564px" %)((( 682 -(% style="color:#000000" %)processAgencyId:processId(version).processStepId. 686 +(% style="color:#000000" %)processAgencyId:processId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).processStepId. 683 683 684 684 (% style="color:#000000" %)processStepId 685 685 )))|(% style="width:771px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1 686 -|(% style="width:283px" %)//ProvisionAgreement//|(% style="width:564px" %)(% style="color:#000000" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:771px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0) 690 +|(% style="width:283px" %)//ProvisionAgreement//|(% style="width:564px" %)(% style="color:#000000" %)provisionAgreementAgencyId:provisionAgreement Id((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:771px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0) 687 687 |(% style="width:283px" %)ReportingCategory|(% style="width:564px" %)((( 688 688 (% style="color:#000000" %)reportingTaxonomyAgencyId: 689 689 690 -(% style="color:#000000" %)reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId 694 +(% style="color:#000000" %)reportingTaxonomyId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).reportingCategoryI d.reportingCategoryId 691 691 )))|(% style="width:771px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT 692 -|(% style="width:283px" %)//ReportingTaxonomy//|(% style="width:564px" %)(% style="color:#000000" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:771px" %)IMF:REP_1(1.0.0) 693 -|(% style="width:283px" %)//ReportingTaxonomyMap//|(% style="width:564px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:771px" %)SDMX:RT_MAP(1.0.0) 696 +|(% style="width:283px" %)//ReportingTaxonomy//|(% style="width:564px" %)(% style="color:#000000" %)reportingTaxonomyAgencyId:reportingTaxonomyI d((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:771px" %)IMF:REP_1(1.0.0) 697 +|(% style="width:283px" %)//ReportingTaxonomyMap//|(% style="width:564px" %)repTaxonomyAgencyId:repTaxonomyId((% style="color:#e74c3c" %)version(%%))|(% style="width:771px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:RT_MAP(1.0.0) 694 694 695 695 |(% style="width:282px" %)**Classname**|(% style="width:566px" %)**Ending URN pattern**|(% style="width:768px" %)**Example** 696 -|(% style="width:282px" %)//RepresentationMap//|(% style="width:566px" %)repMapAgencyId:repMapId(version)|(% style="width:768px" %)SDMX:REF_AREA_MAPPING(1.0.0) 697 -|(% style="width:282px" %)Ruleset|(% style="width:566px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:768px" %)ECB:RULESET_23(1.0.0).SET111 698 -|(% style="width:282px" %)//RulesetScheme//|(% style="width:566px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:768px" %)ECB:RULESET_23(1.0.0) 699 -|(% style="width:282px" %)//StructureMap//|(% style="width:566px" %)structureMapAgencyId:structureMap(version)|(% style="width:768px" %)SDMX:BOP_STRUCTURES(1.0.0) 700 -|(% style="width:282px" %)[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]]|(% style="width:566px" %)((( 701 -The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is not itself an [[Identifiable Artefact>>doc:sdmx:Glossary.Identifiable artefact.WebHome]] and therefore it does not follow the rules for URN structure. 700 +|(% style="width:282px" %)//RepresentationMap//|(% style="width:566px" %)repMapAgencyId:repMapId((% style="color:#e74c3c" %)version(%%))|(% style="width:768px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:REF_AREA_MAPPING(1.0.0) 701 +|(% style="width:282px" %)Ruleset|(% style="width:566px" %)rulesetSchemeAgencyId rulesetSchemeId((% style="color:#e74c3c" %)version(%%)) rulesetId|(% style="width:768px" %)ECB:RULESET_23(1.0.0).SET111 702 +|(% style="width:282px" %)//RulesetScheme//|(% style="width:566px" %)rulesetSchemeAgencyId rulesetSchemeId((% style="color:#e74c3c" %)version(%%))|(% style="width:768px" %)ECB:RULESET_23(1.0.0) 703 +|(% style="width:282px" %)//StructureMap//|(% style="width:566px" %)structureMapAgencyId:structureMap((% style="color:#e74c3c" %)version(%%))|(% style="width:768px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:BOP_STRUCTURES(1.0.0) 704 +|(% style="width:282px" %)[[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]|(% style="width:566px" %)((( 705 +The [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] is not itself an [[Identifiable Artefact>>doc:sdmx:Glossary 2\.1.Identifiable artefact.WebHome]] and therefore it does not follow the rules for URN structure. 702 702 The name of the URN is registryURN There is no pre-determined format. 703 -)))|(% style="width:768px" %)This cannot be generated by a common mechanism as [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]], although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and for the application creating the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] to store the registry URN that is returned from the registry in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response message. 704 -|(% style="width:282px" %)TimeDimension|(% style="width:566px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:768px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD 705 -|(% style="width:282px" %)Transformation|(% style="width:566px" %)(% style="color:#000000" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:768px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1 706 -|(% style="width:282px" %)//TransformationScheme//|(% style="width:566px" %)(% style="color:#000000" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:768px" %)ECB: TRANSFORMATION_SCHEME(1.0.0) 707 +)))|(% style="width:768px" %)This cannot be generated by a common mechanism as [[subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]], although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a [[maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]], and for the application creating the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] to store the registry URN that is returned from the registry in the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] response message. 708 +|(% style="width:282px" %)TimeDimension|(% style="width:566px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).timeDimensionId|(% style="width:768px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD 709 +|(% style="width:282px" %)Transformation|(% style="width:566px" %)(% style="color:#000000" %)transformationSchemeAgencyId transformationSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) transformationId|(% style="width:768px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1 710 +|(% style="width:282px" %)//TransformationScheme//|(% style="width:566px" %)(% style="color:#000000" %)transformationSchemeAgencyId transformationSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:768px" %)ECB: TRANSFORMATION_SCHEME(1.0.0) 707 707 |(% style="width:282px" %)**Classname**|(% style="width:566px" %)**Ending URN pattern**|(% style="width:768px" %)**Example** 708 708 |(% style="width:282px" %)Transition|(% style="width:566px" %)((( 709 -(% style="color:#000000" %)processAgencyId:processId(version).processStepId. 713 +(% style="color:#000000" %)processAgencyId:processId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)).processStepId. 710 710 transitionId 711 711 )))|(% style="width:768px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1 712 -|(% style="width:282px" %)UserDefinedOperator|(% style="width:566px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:768px" %)ECB:OS_CALC(1.2.0).OS267 713 -|(% style="width:282px" %)//UserDefinedOperatorScheme//|(% style="width:566px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:768px" %)ECB:OS_CALC(1.2.0) 714 -|(% style="width:282px" %)//ValueList//|(% style="width:566px" %)(% style="color:#000000" %)valuelistAgencyId:valuelistId(version)|(% style="width:768px" %)SDMX:VLIST(1.0.0) 715 -|(% style="width:282px" %)VtlCodelistMapping|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:768px" %)ECB:CLIST_MP(2.0.0).ABZ 716 -|(% style="width:282px" %)VtlConceptMapping|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:768px" %)ECB:CLIST_MP(1.0.0).XYA 717 -|(% style="width:282px" %)VtlDataflowMapping|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:768px" %)ECB:CLIST_MP(1.0.0).MOQ 718 -|(% style="width:282px" %)//VtlMappingScheme//|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:768px" %)ECB:CLIST_MP(2.0.0) 716 +|(% style="width:282px" %)UserDefinedOperator|(% style="width:566px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) usserDefinedOperatorId|(% style="width:768px" %)ECB:OS_CALC(1.2.0).OS267 717 +|(% style="width:282px" %)//UserDefinedOperatorScheme//|(% style="width:566px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:768px" %)ECB:OS_CALC(1.2.0) 718 +|(% style="width:282px" %)//ValueList//|(% style="width:566px" %)(% style="color:#000000" %)valuelistAgencyId:valuelistId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:768px" %)[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]:VLIST(1.0.0) 719 +|(% style="width:282px" %)VtlCodelistMapping|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) vtlCodelistMappingId|(% style="width:768px" %)ECB:CLIST_MP(2.0.0).ABZ 720 +|(% style="width:282px" %)VtlConceptMapping|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) vtlConceptMappingId|(% style="width:768px" %)ECB:CLIST_MP(1.0.0).XYA 721 +|(% style="width:282px" %)VtlDataflowMapping|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %)) vtlDataflowMappingId|(% style="width:768px" %)ECB:CLIST_MP(1.0.0).MOQ 722 +|(% style="width:282px" %)//VtlMappingScheme//|(% style="width:566px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId VtlMappingSchemeId((% style="color: rgb(0, 0, 0); color: rgb(231, 76, 60)" %)version(% style="color:#000000" %))|(% style="width:768px" %)ECB:CLIST_MP(2.0.0) 719 719 720 -**Table 3: Table of identification components for SDMX Identifiable Artefacts** 724 +**Table 3: Table of identification [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] for [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[Identifiable Artefacts>>doc:sdmx:Glossary 2\.1.Identifiable artefact.WebHome]]** 721 721 722 722 = 7 Implementation Notes = 723 723 ... ... @@ -725,190 +725,190 @@ 725 725 726 726 === 7.1.1 Introduction === 727 727 728 -The [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] must have the ability to support agencies in their role of defining and disseminating [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. These [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] include [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) etc. and are fully defined in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. An authenticated agency may submit valid [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] definitions which must be stored in the registry. Note that the term “[[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]” refers as a general term to all structural [[components>>doc:sdmx:Glossary.Component.WebHome]] ([[Data Structure Definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[Code Lists>>doc:sdmx:Glossary.Code list.WebHome]], [[Concept Schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], etc.) 732 +The [[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]] must have the ability to support agencies in their role of defining and disseminating [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]. These [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] include [[data structure definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) etc. and are fully defined in the [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. An authenticated agency may submit valid [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] definitions which must be stored in the registry. Note that the term “[[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]” refers as a general term to all structural [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] ([[Data Structure Definitions>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]], [[Code Lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], [[Concept Schemes>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]], etc.) 729 729 730 -At a minimum, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] definitions may be submitted to and queried from the registry via an HTTP/HTTPS POST in the form of one of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] messages for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] RESTful API for structure queries. The message may contain all [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items for the whole registry, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items for one [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]], or individual [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items. 734 +At a minimum, [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] definitions may be submitted to and queried from the registry via an HTTP/HTTPS POST in the form of one of the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] messages for [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] and the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] RESTful API for structure queries. The message may contain all [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] items for the whole registry, [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] items for one [[maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]], or individual [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] items. 731 731 732 -[[Structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items 736 +[[Structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] items 733 733 734 -* may only be modified by the [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] which created them; 738 +* may only be modified by the [[maintenance agency>>doc:sdmx:Glossary 2\.1.Maintenance agency.WebHome]] which created them; 735 735 * may only be deleted by the agency which created them; 736 736 * may not be deleted if they are referenced from other constructs in the Registry. 737 737 738 -The (% style="color:#e74c3c" %)level(%%) of granularity for the maintenance of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Structural Metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] objects in the registry is the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. Especially for [[Item Schemes>>doc:sdmx:Glossary.Item scheme.WebHome]], though, partial maintenance may be performed, i.e., at the (% style="color:#e74c3c" %)level(%%) of the Item, by submitting an [[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] with the 'isPartial' flag set and a reduced set of Items. 742 +The (% style="color:#e74c3c" %)level(%%) of granularity for the maintenance of [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] [[Structural Metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] objects in the registry is the [[Maintainable Artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]. Especially for [[Item Schemes>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]], though, partial maintenance may be performed, i.e., at the (% style="color:#e74c3c" %)level(%%) of the Item, by submitting an [[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] with the 'isPartial' flag set and a reduced set of Items. 739 739 740 -The following table lists the [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. 744 +The following table lists the [[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]. 741 741 742 742 (% style="width:825.835px" %) 743 -|(% colspan="2" style="width:455px" %)**Maintainable Artefacts**|(% style="width:367px" %)**Content** 747 +|(% colspan="2" style="width:455px" %)**[[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]]**|(% style="width:367px" %)**Content** 744 744 |(% style="width:160px" %)**Abstract Class**|(% style="width:295px" %)**Concrete Class**|(% style="width:367px" %) 745 -|(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]]|(% style="width:295px" %)Codelist|(% style="width:367px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]] 746 -|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]|(% style="width:367px" %)(% style="color:#e74c3c" %)Concept 747 -|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]|(% style="width:367px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]] 748 -|(% style="width:160px" %) |(% style="width:295px" %)[[Organisation Unit Scheme>>doc:sdmx:Glossary.Organisation unit scheme.WebHome]]|(% style="width:367px" %)Organisation Unit 749 -|(% style="width:160px" %) |(% style="width:295px" %)[[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]|(% style="width:367px" %)Agency 750 -|(% style="width:160px" %) |(% style="width:295px" %)[[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]]|(% style="width:367px" %)[[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] 749 +|(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]]|(% style="width:295px" %)[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]|(% style="width:367px" %)[[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] 750 +|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]]|(% style="width:367px" %)(% style="color:#e74c3c" %)Concept 751 +|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]]|(% style="width:367px" %)[[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] 752 +|(% style="width:160px" %) |(% style="width:295px" %)[[Organisation Unit Scheme>>doc:sdmx:Glossary 2\.1.Organisation unit scheme.WebHome]]|(% style="width:367px" %)Organisation [[Unit>>doc:sdmx:Glossary 2\.1.Statistical unit.WebHome]] 753 +|(% style="width:160px" %) |(% style="width:295px" %)[[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]]|(% style="width:367px" %)Agency 754 +|(% style="width:160px" %) |(% style="width:295px" %)[[Data Provider Scheme>>doc:sdmx:Glossary 2\.1.Data provider scheme.WebHome]]|(% style="width:367px" %)[[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] 751 751 |(% style="width:160px" %) |(% style="width:295px" %)Metadata Provider Scheme|(% style="width:367px" %)Metadata Provider 752 -|(% style="width:160px" %) |(% style="width:295px" %)[[Data Consumer Scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]]|(% style="width:367px" %)[[Data Consumer>>doc:sdmx:Glossary.Data consumer.WebHome]] 753 -|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy|(% style="width:367px" %)Reporting [[Category>>doc:sdmx:Glossary.Category.WebHome]]756 +|(% style="width:160px" %) |(% style="width:295px" %)[[Data Consumer Scheme>>doc:sdmx:Glossary 2\.1.Data consumer scheme.WebHome]]|(% style="width:367px" %)[[Data Consumer>>doc:sdmx:Glossary 2\.1.Data consumer.WebHome]] 757 +|(% style="width:160px" %) |(% style="width:295px" %)[[Reporting Taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]]|(% style="width:367px" %)[[Reporting Category>>doc:sdmx:Glossary 2\.1.Reporting category.WebHome]] 754 754 |(% style="width:160px" %) |(% style="width:295px" %)Transformation Scheme|(% style="width:367px" %)Transformation 755 755 |(% style="width:160px" %) |(% style="width:295px" %)Custom Type Scheme|(% style="width:367px" %)Custom Type 756 756 |(% style="width:160px" %) |(% style="width:295px" %)Name Personalisation Scheme|(% style="width:367px" %)Name Personalisation 757 -|(% style="width:160px" %) |(% style="width:295px" %)[[Vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Mapping Scheme|(% style="width:367px" %)[[Vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Codelist Mapping [[Vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (% style="color:#e74c3c" %)Concept(%%) Mapping 761 +|(% style="width:160px" %) |(% style="width:295px" %)[[Vtl>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] Mapping Scheme|(% style="width:367px" %)[[Vtl>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] Mapping [[Vtl>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] (% style="color:#e74c3c" %)Concept(%%) Mapping 758 758 |(% style="width:160px" %) |(% style="width:295px" %)Ruleset Scheme|(% style="width:367px" %)Ruleset 759 759 |(% style="width:160px" %) |(% style="width:295px" %)User Defined Operator Scheme|(% style="width:367px" %)User Defined Operator 760 760 |(% style="width:160px" %)Enumerated List|(% style="width:295px" %)ValueList|(% style="width:367px" %)Value Item 761 -|(% style="width:160px" %)Structure|(% style="width:295px" %)[[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]|(% style="width:367px" %)((( 762 -[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor 763 -Group [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor 764 -[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] 765 -Time [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] 766 -[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor 767 -Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] 768 -Measure Descriptor 769 -Measure 765 +|(% style="width:160px" %)Structure|(% style="width:295px" %)[[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]|(% style="width:367px" %)((( 766 +[[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] Descriptor 767 +Group [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] Descriptor 768 +[[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] 769 +Time [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] 770 +[[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] Descriptor 771 +Data [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] 772 +[[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]] Descriptor 773 +[[Measure>>doc:sdmx:Glossary 2\.1.Measure.WebHome]] 770 770 ))) 771 -|(% style="width:160px" %) |(% style="width:295px" %)[[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]|(% style="width:367px" %)Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] 772 -|(% style="width:160px" %)Structure Usage|(% style="width:295px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]|(% style="width:367px" %) 773 -|(% style="width:160px" %) |(% style="width:295px" %)[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]|(% style="width:367px" %) 775 +|(% style="width:160px" %) |(% style="width:295px" %)[[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]|(% style="width:367px" %)Metadata [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] Descriptor Metadata [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] 776 +|(% style="width:160px" %)Structure Usage|(% style="width:295px" %)[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]|(% style="width:367px" %) 777 +|(% style="width:160px" %) |(% style="width:295px" %)[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]|(% style="width:367px" %) 774 774 |(% style="width:160px" %)None|(% style="width:295px" %)Process|(% style="width:367px" %)Process Step 775 775 |(% style="width:160px" %)None|(% style="width:295px" %)Structure (% style="color:#e74c3c" %)Map|(% style="width:367px" %)((( 776 -[[Component>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)Map(%%) 780 +[[Component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] (% style="color:#e74c3c" %)Map(%%) 777 777 Epoch (% style="color:#e74c3c" %)Map(%%) 778 778 Date Pattern (% style="color:#e74c3c" %)Map 779 779 ))) 780 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping 781 -|(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:295px" %)Organisation Scheme (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 782 -|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 783 -|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 784 -|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 785 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]|(% style="width:367px" %) 786 -|(% style="width:160px" %)None|(% style="width:295px" %)Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]|(% style="width:367px" %) 787 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]|(% style="width:367px" %)Hierarchical [[Code>>doc:sdmx:Glossary.Code.WebHome]]788 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association|(% style="width:367px" %) 789 -|(% style="width:160px" %)None|(% style="width:295px" %)Categorisation|(% style="width:367px" %) 784 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)[[Representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] Mapping 785 +|(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:295px" %)Organisation Scheme (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 786 +|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 787 +|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 788 +|(% style="width:160px" %) |(% style="width:295px" %)[[Reporting Taxonomy>>doc:sdmx:Glossary 2\.1.Reporting taxonomy.WebHome]] (% style="color:#e74c3c" %)Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)Map 789 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]|(% style="width:367px" %) 790 +|(% style="width:160px" %)None|(% style="width:295px" %)Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]|(% style="width:367px" %) 791 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]|(% style="width:367px" %)[[Hierarchical Code>>doc:sdmx:Glossary 2\.1.Hierarchical code.WebHome]] 792 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] Association|(% style="width:367px" %) 793 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]]|(% style="width:367px" %) 790 790 |(% style="width:160px" %)(% style="color:#e74c3c" %)Constraint|(% style="width:295px" %)Data (% style="color:#e74c3c" %)Constraint|(% style="width:367px" %)DataKeySet 791 791 |(% style="width:160px" %) |(% style="width:295px" %) |(% style="width:367px" %)CubeRegion 792 792 |(% style="width:160px" %)(% style="color:#e74c3c" %)Constraint|(% style="width:295px" %)Metadata (% style="color:#e74c3c" %)Constraint|(% style="width:367px" %)MetadataTargetRegion 793 793 794 -**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata** 798 +**Table 4: Table of [[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] for Structural Definition Metadata** 795 795 796 796 === 7.1.2 Item Scheme, Structure === 797 797 798 -The [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] included in the structural definitions are: 802 +The [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] included in the structural definitions are: 799 799 800 -* All types of [[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] (Codelist, [[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]], Organisation Scheme, [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]], [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]], Metadata Provider Scheme, [[Data Consumer Scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]], [[Organisation Unit Scheme>>doc:sdmx:Glossary.Organisation unit scheme.WebHome]], Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, [[Vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme) 804 +* All types of [[Item Scheme>>doc:sdmx:Glossary 2\.1.Item scheme.WebHome]] ([[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], [[Concept Scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]], [[Category Scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]], Organisation Scheme, [[Agency Scheme>>doc:sdmx:Glossary 2\.1.Agency scheme.WebHome]], [[Data Provider Scheme>>doc:sdmx:Glossary 2\.1.Data provider scheme.WebHome]], Metadata Provider Scheme, [[Data Consumer Scheme>>doc:sdmx:Glossary 2\.1.Data consumer scheme.WebHome]], [[Organisation Unit Scheme>>doc:sdmx:Glossary 2\.1.Organisation unit scheme.WebHome]], Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, [[Vtl>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme) 801 801 * All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}} 802 -* All types of Structure ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]) 803 -* All types of Structure Usage ([[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]) 806 +* All types of Structure ([[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]) 807 +* All types of Structure Usage ([[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]]) 804 804 805 805 === 7.1.3 Structure Usage === 806 806 807 807 ==== 7.1.3.1 Structure Usage: Basic Concepts ==== 808 808 809 -The Structure Usage defines, in its concrete classes of [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], which flows of data and metadata use which specific Structure, and importantly for the support of data and metadata discovery, the Structure Usage can be linked to one or more [[Category>>doc:sdmx:Glossary.Category.WebHome]] in one or more [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] using the Categorisation mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the [[Category Schemes>>doc:sdmx:Glossary.Category scheme.WebHome]]. 813 +The Structure Usage defines, in its concrete classes of [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], which flows of data and metadata use which specific Structure, and importantly for the support of data and metadata discovery, the Structure Usage can be linked to one or more [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] in one or more [[Category Scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]] using the [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the [[Category Schemes>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]]. 810 810 811 811 ==== 7.1.3.2 Structure Usage Schematic ==== 812 812 813 813 [[image:SDMX 3.1 Section 5_en_9b750e13.jpg||height="246" width="438"]] 814 814 815 -**Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions** 819 +**Figure 9: Schematic of Linking the Data and [[Metadata Flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] to [[Categories>>doc:sdmx:Glossary 2\.1.Category.WebHome]] and Structure Definitions** 816 816 817 817 ==== 7.1.3.3 Structure Usage Model ==== 818 818 819 819 [[image:SDMX 3.1 Section 5_en_1c94cbe.jpg||height="548" width="578"]] 820 820 821 -**Figure 10: SDMX-IM of links from Structure Usage to Category** 825 +**Figure 10: [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] of links from Structure Usage to [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]** 822 822 823 -In addition to the maintenance of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and the [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], the following links must be maintained in the registry: 827 +In addition to the maintenance of the [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and the [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], the following links must be maintained in the registry: 824 824 825 -* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] to Data Structure Definition 826 -* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] to Metadata Structure Definition 829 +* [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] to [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] 830 +* [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] to [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] 827 827 828 -The following links may be created by means of a Categorisation 832 +The following links may be created by means of a [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] 829 829 830 -* Categorisation to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[Category>>doc:sdmx:Glossary.Category.WebHome]] 831 -* Categorisation to [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] and [[Category>>doc:sdmx:Glossary.Category.WebHome]] 834 +* [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] to [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] and [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] 835 +* [[Categorisation>>doc:sdmx:Glossary 2\.1.Categorisation.WebHome]] to [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] and [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] 832 832 833 833 == 7.2 Data and Metadata Provisioning == 834 834 835 835 === 7.2.1 Provisioning Agreement: Basic concepts === 836 836 837 -Data/Metadata provisioning defines a framework in which the provision of different types of statistical data and metadata by various data/metadata providers can be specified and controlled. This framework is the basis on which the existence of data can be made known to the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-enabled community and hence the basis on which data can subsequently be discovered. Such a framework can be used to regulate the data content to facilitate the building of intelligent applications. It can also be used to facilitate the processing implied by service (% style="color:#e74c3c" %)level(%%) agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and [[timeliness>>doc:sdmx:Glossary.Timeliness.WebHome]] metadata can be supported by this framework which makes it practical to implement information supply chain monitoring. 841 +Data/Metadata provisioning defines a framework in which the provision of different types of statistical data and metadata by various data/metadata providers can be specified and controlled. This framework is the basis on which the existence of data can be made known to the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-enabled community and hence the basis on which data can subsequently be discovered. Such a framework can be used to regulate the data content to facilitate the building of intelligent applications. It can also be used to facilitate the processing implied by service (% style="color:#e74c3c" %)level(%%) agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and [[timeliness>>doc:sdmx:Glossary 2\.1.Timeliness.WebHome]] metadata can be supported by this framework which makes it practical to implement information supply chain monitoring. 838 838 839 839 Note that the term “data provisioning” here includes both the provisioning of data and metadata. 840 840 841 -Although the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] directly supports the data-sharing “pull” model, it is also useful in “push” exchanges (bilateral and gateway scenarios), or in a dissemination environment. It should be noted, too, that in any exchange scenario, the registry functions as a repository of structural metadata. 845 +Although the [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] directly supports the data-sharing “pull” model, it is also useful in “push” exchanges (bilateral and gateway scenarios), or in a dissemination environment. It should be noted, too, that in any exchange scenario, the registry functions as a repository of [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. 842 842 843 843 === 7.2.2 Provisioning Agreement Model – pull use case === 844 844 845 -An organisation which publishes statistical data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and wishes to make it available to an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] enabled community is called a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]. In terms of the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]], the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] is maintained in a [[Data Provider Scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]]. 849 +An organisation which publishes statistical data or [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] and wishes to make it available to an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] enabled community is called a [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]. In terms of the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]], the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] is maintained in a [[Data Provider Scheme>>doc:sdmx:Glossary 2\.1.Data provider scheme.WebHome]]. 846 846 847 847 [[image:SDMX 3.1 Section 5_en_5a16c7fe.jpg||height="455" width="551"]] 848 848 849 -**Figure 11: SDMX-IM of the Data Provider** 853 +**Figure 11: [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] of the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]** 850 850 851 -Note that the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] does not inherit the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] association. The diagram below shows a logical schematic of the data model classes required to maintain [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]]. 855 +Note that the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] does not inherit the [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] association. The diagram below shows a logical schematic of the data model classes required to maintain [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]. 852 852 853 853 [[image:SDMX 3.1 Section 5_en_b08fd1a2.jpg||height="299" width="533"]] 854 854 855 -**Figure 12: Schematic of the Provision Agreement** 859 +**Figure 12: Schematic of the [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]** 856 856 857 -The diagram below is a logical [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the data required in order to maintain [[Provision Agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]]. 861 +The diagram below is a logical [[representation>>doc:sdmx:Glossary 2\.1.Representation.WebHome]] of the data required in order to maintain [[Provision Agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]. 858 858 859 859 [[image:SDMX 3.1 Section 5_en_c63d10ab.jpg||height="246" width="579"]] 860 860 861 -**Figure 13: Logical class diagram of the information contained in the Provision Agreement** 865 +**Figure 13: Logical class diagram of the information contained in the [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]** 862 862 863 -A [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] is [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. Each [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] must reference a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] or Metadata Provider and a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition. The Data/Metadata Provider and the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] must exist already in order to set up a Metadata Provision or [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]. 867 +A [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] is [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]]. Each [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] must reference a [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] or Metadata Provider and a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] Definition. The Data/Metadata Provider and the [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] must exist already in order to set up a Metadata Provision or [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]]. 864 864 865 865 == 7.3 Data and Metadata Constraints == 866 866 867 867 === 7.3.1 Data and Metadata Constraints: Basic Concepts === 868 868 869 -(% style="color:#e74c3c" %)Constraints(%%) are, effectively, lists of the valid or actual content of data and metadata. (% style="color:#e74c3c" %)Constraints(%%) can be used to specify a subset of the theoretical content of [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] which can be derived from the specification of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]. A (% style="color:#e74c3c" %)Constraint(%%) can comprise a list of keys or a list of content (usually [[code>>doc:sdmx:Glossary.Code.WebHome]] values) of a specific [[component>>doc:sdmx:Glossary.Component.WebHome]] such as a [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] or [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. 873 +(% style="color:#e74c3c" %)Constraints(%%) are, effectively, lists of the valid or actual content of data and metadata. (% style="color:#e74c3c" %)Constraints(%%) can be used to specify a subset of the theoretical content of [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]] which can be derived from the specification of the [[DSD>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[MSD>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]. A (% style="color:#e74c3c" %)Constraint(%%) can comprise a list of keys or a list of content (usually [[code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] values) of a specific [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] such as a [[dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] or [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]. 870 870 871 -(% style="color:#e74c3c" %)Constraints(%%) comprise the specification of subsets of key or [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] values that are to be provided for a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], or directly attached to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]. This is important metadata because, for example, the full range of possibilities which is implied by the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] (e.g., the complete set of valid keys is the Cartesian product of all the values in the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] for each of the [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]]) is often more than is intended to be supplied according to a specific [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]. 875 +(% style="color:#e74c3c" %)Constraints(%%) comprise the specification of subsets of key or [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] values that are to be provided for a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], or directly attached to a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]]. This is important metadata because, for example, the full range of possibilities which is implied by the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] (e.g., the complete set of valid keys is the Cartesian product of all the values in the [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] for each of the [[Dimensions>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]]) is often more than is intended to be supplied according to a specific [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]. 872 872 873 -Often a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] will not be able to provide data for all key combinations, either because the combination itself is not meaningful, or simply because the provider does not have the data for that combination. In this case the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] could constrain the [[data source>>doc:sdmx:Glossary.Data source.WebHome]] (at the (% style="color:#e74c3c" %)level(%%) of the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] or the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]) by supplying metadata that defines the key combinations or cube regions that are available. This is done by means of a (% style="color:#e74c3c" %)Constraint(%%). The (% style="color:#e74c3c" %)Constraint(%%) is also used to define a [[code list>>doc:sdmx:Glossary.Code list.WebHome]] subset which is used to populate a partial [[code list>>doc:sdmx:Glossary.Code list.WebHome]], and in generating a schema for data reporters to validate their [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] against. 877 +Often a [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] will not be able to provide data for all key combinations, either because the combination itself is not meaningful, or simply because the provider does not have the data for that combination. In this case the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] could constrain the [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]] (at the (% style="color:#e74c3c" %)level(%%) of the [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] or the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]]) by supplying metadata that defines the key combinations or cube regions that are available. This is done by means of a (% style="color:#e74c3c" %)Constraint(%%). The (% style="color:#e74c3c" %)Constraint(%%) is also used to define a [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] subset which is used to populate a partial [[code list>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], and in generating a schema for data reporters to validate their [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] against. 874 874 875 -Furthermore, it is often useful to define subsets or views of the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] which restrict values in some [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], especially where many such subsets restrict the same [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. Such a view is called a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], and there can be one or more defined for any [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. 879 +Furthermore, it is often useful to define subsets or views of the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] which restrict values in some [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], especially where many such subsets restrict the same [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]. Such a view is called a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], and there can be one or more defined for any [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]. 876 876 877 -Whenever data is published or made available by a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]], it must conform to a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (and hence to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). The [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] is thus a means of enabling content based processing. 881 +Whenever data is published or made available by a [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]], it must conform to a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] (and hence to a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]). The [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] is thus a means of enabling content based processing. 878 878 879 -In addition, DataAvailabilityConstraints can be extremely useful in a data visualisation system, such as dissemination of statistics on a website. In such a system a Cube Region can be used to specify the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] [[codes>>doc:sdmx:Glossary.Code.WebHome]] that actually exist in a [[data source>>doc:sdmx:Glossary.Data source.WebHome]] (these can be used to build relevant selection tables). 883 +In addition, DataAvailabilityConstraints can be extremely useful in a data visualisation system, such as dissemination of statistics on a website. In such a system a Cube Region can be used to specify the [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] that actually exist in a [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]] (these can be used to build relevant selection tables). 880 880 881 881 === 7.3.2 Data and Metadata Constraints: Schematic === 882 882 883 883 [[image:SDMX 3.1 Section 5_en_28d0cadc.jpg||height="326" width="580"]] 884 884 885 -**Figure 14: Schematic of the Constraint and the Artefacts that can be constrained** 889 +**Figure 14: Schematic of the (% style="color:#e74c3c" %)Constraint(%%) and the [[Artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that can be constrained** 886 886 887 887 === 7.3.3 Data and Metadata Constraints: Model === 888 888 889 889 [[image:SDMX 3.1 Section 5_en_a3184f6a.jpg||height="298" width="579"]] 890 890 891 -**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artefacts** 895 +**Figure 15: Logical class diagram showing inheritance between and reference to constrainable [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]** 892 892 893 -Logical class diagram showing inheritance between and reference to constrainable artefacts. 897 +Logical class diagram showing inheritance between and reference to constrainable [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]]. 894 894 895 -The class diagram above shows that [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]], Metadata Provider, [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]], Data Structure. 899 +The class diagram above shows that [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]], Metadata Provider, [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]], Data Structure. 896 896 897 -Definition, [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] are all concrete sub-classes of Constrainable [[Artefact>>doc:sdmx:Glossary.Artefact.WebHome]] and can therefore have Data (% style="color:#e74c3c" %)Constraints(%%) specified. Note that the actual (% style="color:#e74c3c" %)Constraint(%%) as submitted is associated to the reference classes defines in the (% style="color:#e74c3c" %)Constraint(%%) Attachment. these are used to refer to the classes to which the (% style="color:#e74c3c" %)Constraint(%%) applies. 901 +Definition, [[Metadata Structure Definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] are all concrete sub-classes of Constrainable [[Artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] and can therefore have Data (% style="color:#e74c3c" %)Constraints(%%) specified. Note that the actual (% style="color:#e74c3c" %)Constraint(%%) as submitted is associated to the reference classes defines in the (% style="color:#e74c3c" %)Constraint(%%) Attachment. these are used to refer to the classes to which the (% style="color:#e74c3c" %)Constraint(%%) applies. 898 898 899 -The content of the (% style="color:#e74c3c" %)Constraint(%%) can be found in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] document. 903 +The content of the (% style="color:#e74c3c" %)Constraint(%%) can be found in the [[SDMX Information Model>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]] document. 900 900 901 901 == 7.4 Data Registration == 902 902 903 903 === 7.4.1 Basic Concepts === 904 904 905 -A [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] has published a new [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] conforming to an existing [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (and hence [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). This is implemented as either a web-accessible SDMXML file, or in a database which has a web-services interface capable of responding to an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] RESTful query with an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data stream. 909 +A [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] has published a new [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] conforming to an existing [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] (and hence [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]). This is implemented as either a web-accessible SDMXML file, or in a database which has a web-services interface capable of responding to an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] RESTful query with an [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] data stream. 906 906 907 -The [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] wishes to make this new data available to one or more data collectors in a “pull” scenario, or to make the data available to [[data consumers>>doc:sdmx:Glossary.Data consumer.WebHome]]. To do this, the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] registers the new [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] with one or more [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant registries that have been configured with structural and provisioning metadata. In other words, the registry “knows” the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] and “knows” what [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]] the [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] has agreed to make available. 911 +The [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] wishes to make this new data available to one or more data collectors in a “pull” scenario, or to make the data available to [[data consumers>>doc:sdmx:Glossary 2\.1.Data consumer.WebHome]]. To do this, the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] registers the new [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] with one or more [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] conformant registries that have been configured with structural and provisioning metadata. In other words, the registry “knows” the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] and “knows” what [[data flows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] the [[data provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] has agreed to make available. 908 908 909 -The same mechanism can be used to report or make available a metadata set. 913 +The same mechanism can be used to report or make available a [[metadata set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]]. 910 910 911 -[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR supports [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] registration via the Registration Request, which can be created by the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] (giving the [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] maximum control). The registry responds to the registration request with a registration response which indicates if the registration was successful. In the event of an error, the error messages are returned as a registry exception within the response. 915 +[[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]]-RR supports [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] registration via the Registration Request, which can be created by the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] (giving the [[Data Provider>>doc:sdmx:Glossary 2\.1.Data provider.WebHome]] maximum control). The registry responds to the registration request with a registration response which indicates if the registration was successful. In the event of an error, the error messages are returned as a registry exception within the response. 912 912 913 913 === 7.4.2 The Registration Request === 914 914 ... ... @@ -920,7 +920,7 @@ 920 920 921 921 ==== 7.4.2.2 Registration Request Model ==== 922 922 923 -The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] to be registered. The Registration can optionally have information, which has been extracted from the Registration: 927 +The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] to be registered. The Registration can optionally have information, which has been extracted from the Registration: 924 924 925 925 * validFrom 926 926 * validTo ... ... @@ -928,11 +928,11 @@ 928 928 929 929 The last updated date is useful during the discovery process to make sure the client knows which data is freshest. 930 930 931 -The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values: 935 +The Registration has an action [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] which takes one of the following values: 932 932 933 933 ((( 934 934 (% style="width:918.835px" %) 935 -|(% style="width:224px" %)**Action Attribute Value**|(% style="width:692px" %)**Behaviour** 939 +|(% style="width:224px" %)**Action [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] Value**|(% style="width:692px" %)**Behaviour** 936 936 |(% style="width:224px" %)Append|(% style="width:692px" %)Add this Registration to the registry 937 937 |(% style="width:224px" %)Replace|(% style="width:692px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest 938 938 |(% style="width:224px" %)Delete|(% style="width:692px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest ... ... @@ -942,15 +942,15 @@ 942 942 943 943 **Figure 17: Logical Class Diagram of Registration of Data and Metadata** 944 944 945 -The //QueryDatasource// is an abstract class that represents a [[data source>>doc:sdmx:Glossary.Data source.WebHome]], which can understand an API query (i.e., a RESTful query – RESTDatasource) and respond appropriately. Each [[data source>>doc:sdmx:Glossary.Data source.WebHome]] inherits the dataURL from //Datasource//, and the //QueryDatasource// has an additional URL to locate the specification of the service (specURL) to describe how to access it. All other supported protocols are assumed to use the SimpleDatasource URL. 949 +The //QueryDatasource// is an abstract class that represents a [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]], which can understand an API query (i.e., a RESTful query – RESTDatasource) and respond appropriately. Each [[data source>>doc:sdmx:Glossary 2\.1.Data source.WebHome]] inherits the dataURL from //Datasource//, and the //QueryDatasource// has an additional URL to locate the specification of the service (specURL) to describe how to access it. All other supported protocols are assumed to use the SimpleDatasource URL. 946 946 947 -A SimpleDatasource is used to reference a physical [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file that is available at a URL. 951 +A SimpleDatasource is used to reference a physical [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] file that is available at a URL. 948 948 949 -The RegistrationRequest has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which defines whether this is a new (append) or updated (replace) Registration, or that the Registration is to be deleted (delete). The id is only provided for the replace and delete actions, as the Registry will allocate the unique id of the (new) Registration. 953 +The RegistrationRequest has an action [[attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] which defines whether this is a new (append) or updated (replace) Registration, or that the Registration is to be deleted (delete). The id is only provided for the replace and delete actions, as the Registry will allocate the unique id of the (new) Registration. 950 950 951 -The Registration includes [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] that state how a SimpleDatasource is to be indexed when registered. The Registry registration process must act as follows: 955 +The Registration includes [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] that state how a SimpleDatasource is to be indexed when registered. The Registry registration process must act as follows: 952 952 953 -Information in the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] is extracted and made available via the availability REST API as documented here: 957 +Information in the [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] is extracted and made available via the availability REST API as documented here: 954 954 955 955 https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md 956 956 ... ... @@ -957,21 +957,21 @@ 957 957 ((( 958 958 (% style="width:918.835px" %) 959 959 |**Indexing Required**|(% style="width:745px" %)**Registration Process Activity** 960 -|indexTimeSeries|(% style="width:745px" %)Extract all the [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] and create a KeySet(s) Constraint. 961 -|indexDataSet|(% style="width:745px" %)Extract all the [[codes>>doc:sdmx:Glossary.Code.WebHome]] and other content of the Key value of the [[Series Key>>doc:sdmx:Glossary.Series key.WebHome]] in a [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] of [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]], and the associated Selection Value. 964 +|indexTimeSeries|(% style="width:745px" %)Extract all the [[series keys>>doc:sdmx:Glossary 2\.1.Series key.WebHome]] and create a KeySet(s) (% style="color:#e74c3c" %)Constraint(%%). 965 +|indexDataSet|(% style="width:745px" %)Extract all the [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and other content of the Key value of the [[Series Key>>doc:sdmx:Glossary 2\.1.Series key.WebHome]] in a [[Data Set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary 2\.1.Member selection.WebHome]] of [[Dimension>>doc:sdmx:Glossary 2\.1.Dimension.WebHome]] [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the [[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]], and the associated Selection Value. 962 962 |indexReportingPeriod|(% style="width:745px" %)((( 963 -This applies only to a registered __[[dataset>>doc:sdmx:Glossary.Data set.WebHome]]__. 964 -Extract the Reporting Begin and Reporting End from the Header of the Message containing the [[data set>>doc:sdmx:Glossary.Data set.WebHome]], and create a [[Reference Period>>doc:sdmx:Glossary.Reference period.WebHome]] constraint. 967 +This applies only to a registered __[[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]__. 968 +Extract the Reporting Begin and Reporting End from the Header of the Message containing the [[data set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]], and create a [[Reference Period>>doc:sdmx:Glossary 2\.1.Reference period.WebHome]] (% style="color:#e74c3c" %)constraint(%%). 965 965 ))) 966 966 |indexAttributes|(% style="width:745px" %)((( 967 -**Data Set** 968 -Extract the content of the [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Values in a [[Data Set>>doc:sdmx:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] of Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the SDMXIM, and the associated Selection Value 971 +**[[Data Set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]]** 972 +Extract the content of the [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] Values in a [[Data Set>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary 2\.1.Member selection.WebHome]] of Data [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the SDMXIM, and the associated Selection Value 969 969 970 -**Metadata Set** 971 -Indicate the presence of a Reported [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] by creating one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary.Member selection.WebHome]] of Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] [[Components>>doc:sdmx:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the 974 +**[[Metadata Set>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]]** 975 +Indicate the presence of a Reported [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] by creating one or more Cube Regions containing [[Member Selections>>doc:sdmx:Glossary 2\.1.Member selection.WebHome]] of Metadata [[Attribute>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]] [[Components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the 972 972 ))) 973 973 |**Indexing Required**|(% style="width:745px" %)**Registration Process Activity** 974 -| |(% style="width:745px" %)[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. Note that the content is not stored in the Selection Value. 978 +| |(% style="width:745px" %)[[SDMX-IM>>doc:sdmx:Glossary 2\.1.SDMX Information Model.WebHome]]. Note that the content is not stored in the Selection Value. 975 975 ))) 976 976 977 977 (% style="color:#e74c3c" %)Constraints(%%) that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API). ... ... @@ -982,9 +982,9 @@ 982 982 983 983 After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The SubmitRegistration class has a status field, which is either set to “Success”, “Warning” or “Failure”. 984 984 985 -If the registration has succeeded, a Registration will be returned – this holds the Registry-allocated Id of the newly registered //Datasource// plus a //Datasource// holding the URL to access the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or query service. 989 +If the registration has succeeded, a Registration will be returned – this holds the Registry-allocated Id of the newly registered //Datasource// plus a //Datasource// holding the URL to access the [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or query service. 986 986 987 -The RegistrationResponse returns set of registration status (one for each registration submitted) in terms of a StatusMessage (this is common to all Registry responses) that indicates success or failure. In the event of registration failure, a set of MessageText are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of [[datasets>>doc:sdmx:Glossary.Data set.WebHome]], that the response will contain some successful and some failed statuses. The logical model for the RegistrationResponse is shown below: 991 +The RegistrationResponse returns set of registration status (one for each registration submitted) in terms of a StatusMessage (this is common to all Registry responses) that indicates success or failure. In the event of registration failure, a set of MessageText are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]], that the response will contain some successful and some failed statuses. The logical model for the RegistrationResponse is shown below: 988 988 989 989 [[image:SDMX 3.1 Section 5_en_cdba03b5.jpg||height="371" width="579"]] 990 990 ... ... @@ -992,98 +992,98 @@ 992 992 993 993 == 7.5 Subscription and Notification Service == 994 994 995 -The contents of the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/Repository will change regularly: new [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] and key families will be published and new [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen. 999 +The contents of the [[SDMX Registry>>doc:sdmx:Glossary 2\.1.SDMX Registry.WebHome]]/Repository will change regularly: new [[code lists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and key families will be published and new [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen. 996 996 997 -A user can submit a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a [[notification>>doc:sdmx:Glossary.Notification.WebHome]] of qualifying events will be delivered. The [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] will be identified in the registry by a URN, which is returned to the user when the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is created. If the user wants to delete the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] at a later point, the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] URN is used as identification. [[Subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]], and will notify the subscriber on expiry. 1001 +A user can submit a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] of qualifying events will be delivered. The [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] will be identified in the registry by a URN, which is returned to the user when the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] is created. If the user wants to delete the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] at a later point, the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] URN is used as identification. [[Subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired [[subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]], and will notify the subscriber on expiry. 998 998 999 -When a registry/repository [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] is modified, any [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]. This is called a “[[notification>>doc:sdmx:Glossary.Notification.WebHome]]”. 1003 +When a registry/repository [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] is modified, any [[subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]. This is called a “[[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]”. 1000 1000 1001 1001 === 7.5.1 Subscription Logical Class Diagram === 1002 1002 1003 1003 [[image:SDMX 3.1 Section 5_en_1433df5d.jpg||height="680" width="587"]] 1004 1004 1005 -**Figure 19: Logical Class Diagram of the Subscription** 1009 +**Figure 19: Logical Class Diagram of the [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]** 1006 1006 1007 1007 === 7.5.2 Subscription Information === 1008 1008 1009 -Regardless of the type of registry/repository events being observed, a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] always contains: 1013 +Regardless of the type of registry/repository events being observed, a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] always contains: 1010 1010 1011 -1. A set of URIs describing the end-points to which [[notifications>>doc:sdmx:Glossary.Notification.WebHome]] must be sent if the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is activated. The URIs can be either mailto~: or http: protocol. In the former case an email [[notification>>doc:sdmx:Glossary.Notification.WebHome]] is sent; in the latter an HTTP POST [[notification>>doc:sdmx:Glossary.Notification.WebHome]] is sent. 1012 -1. A user-defined identifier, which is returned in the response to the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request. This helps with asynchronous processing and is NOT stored in the Registry. 1013 -1. A validity period which defines both when the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] becomes active and expires. The subscriber may be sent a [[notification>>doc:sdmx:Glossary.Notification.WebHome]] on expiration of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]. 1015 +1. A set of URIs describing the end-points to which [[notifications>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] must be sent if the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] is activated. The URIs can be either mailto~: or http: protocol. In the former case an email [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] is sent; in the latter an HTTP POST [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] is sent. 1016 +1. A user-defined identifier, which is returned in the response to the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] request. This helps with asynchronous processing and is NOT stored in the Registry. 1017 +1. A validity period which defines both when the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] becomes active and expires. The subscriber may be sent a [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] on expiration of the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]]. 1014 1014 1. A selector which specifies which type of events are of interest. The set of event types is: 1015 1015 1016 1016 (% style="width:1061.83px" %) 1017 -|**Event Type**|(% style="width:660px" %)**Comment** 1018 -|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository. 1019 -|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] is registered. This can be either a SDMXML data file or an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant database. 1020 -|METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] file or an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant database. 1021 +|**Event Type**|(% style="width:660px" %)**[[Comment>>doc:sdmx:Glossary 2\.1.Comment.WebHome]]** 1022 +|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to [[Maintainable Artefacts>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] repository. 1023 +|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] is registered. This can be either a SDMXML data file or an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] conformant database. 1024 +|METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML [[reference metadata>>doc:sdmx:Glossary 2\.1.Reference metadata.WebHome]] file or an [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] conformant database. 1021 1021 |ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType 1022 1022 1023 1023 === 7.5.3 Wildcard Facility === 1024 1024 1025 -Subscription notification supports wildcarded identifier components URNs, which are identifiers which have some or all of their component parts replaced by the wildcard character `*`. Identifier components comprise: 1029 +[[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] supports wildcarded identifier [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] URNs, which are identifiers which have some or all of their [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] parts replaced by the wildcard character `*`. Identifier [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] comprise: 1026 1026 1027 1027 * agencyID 1028 1028 * id 1029 -* version 1033 +* (% style="color:#e74c3c" %)version 1030 1030 1031 -Examples of wildcarded identifier components for an identified object type of Codelist are shown below: 1035 +Examples of wildcarded identifier [[components>>doc:sdmx:Glossary 2\.1.Component.WebHome]] for an identified object type of [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] are shown below: 1032 1032 1033 1033 >(% style="font-size:18px" %) AgencyID = * 1034 1034 >(% style="font-size:18px" %) Id = * 1035 1035 >(% style="font-size:18px" %) Version = * 1036 1036 1037 -This subscribes to all Codelists of all versions for all agencies. 1041 +This subscribes to all [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] of all (% style="color:#e74c3c" %)versions(%%) for all agencies. 1038 1038 1039 1039 > (% style="font-size:18px" %)AgencyID = AGENCY1 1040 1040 >(% style="font-size:18px" %) Id = CODELIST1 1041 1041 >(% style="font-size:18px" %) Version = * 1042 1042 1043 -This subscribes to all versions of Codelist CODELIST1 maintained by the agency AGENCY1. 1047 +This subscribes to all (% style="color:#e74c3c" %)versions(%%) of [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] CODELIST1 maintained by the agency AGENCY1. 1044 1044 1045 1045 > (% style="font-size:18px" %)AgencyID = AGENCY1 1046 1046 >(% style="font-size:18px" %) Id = * 1047 1047 >(% style="font-size:18px" %) Version = * 1048 1048 1049 -This subscribes to all versions of all Codelist objects maintained by the agency AGENCY1. 1053 +This subscribes to all (% style="color:#e74c3c" %)versions(%%) of all [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] objects maintained by the agency AGENCY1. 1050 1050 1051 1051 > (% style="font-size:18px" %)AgencyID = * 1052 1052 >(% style="font-size:18px" %) Id = CODELIST1 1053 1053 >(% style="font-size:18px" %) Version = * 1054 1054 1055 -This subscribes to all versions of Codelist CODELIST1 maintained by any agency. 1059 +This subscribes to all (% style="color:#e74c3c" %)versions(%%) of [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] CODELIST1 maintained by any agency. 1056 1056 1057 -Note that if the subscription is to the latest stable version then this can be achieved by the + character, i.e.: 1061 +Note that if the [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] is to the latest stable (% style="color:#e74c3c" %)version(%%) then this can be achieved by the + character, i.e.: 1058 1058 1059 1059 >(% style="font-size:18px" %) Version = + 1060 1060 1061 -A subscription to the latest version (whether stable, draft or non-versioned) can be achieved by the ~~ character, i.e.: 1065 +A [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] to the latest (% style="color:#e74c3c" %)version(%%) (whether stable, draft or non-versioned) can be achieved by the ~~ character, i.e.: 1062 1062 1063 1063 > (% style="font-size:18px" %)Version = ~~ 1064 1064 1065 -A subscription to the latest stable version within major version 2 starting with version 2.3.1 can be achieved by adding the + character after the minor version number, i.e.: 1069 +A [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] to the latest stable (% style="color:#e74c3c" %)version(%%) within major (% style="color:#e74c3c" %)version(%%) 2 starting with (% style="color:#e74c3c" %)version(%%) 2.3.1 can be achieved by adding the + character after the minor (% style="color:#e74c3c" %)version(%%) number, i.e.: 1066 1066 1067 1067 >(% style="font-size:18px" %) Version = 2.3+.1 1068 1068 1069 -The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”. 1073 +The complete [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] versioning syntax can be found in the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”. 1070 1070 1071 1071 === 7.5.4 Structural Repository Events === 1072 1072 1073 -Whenever a [[maintainable artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] ([[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]], codelist, [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]], etc.) is added to, deleted from, or modified in the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository, a [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] event is triggered. [[Subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] may be set up to monitor all such events, or focus on specific [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] such as a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. 1077 +Whenever a [[maintainable artefact>>doc:sdmx:Glossary 2\.1.Maintainable artefact.WebHome]] ([[data structure definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]], [[concept scheme>>doc:sdmx:Glossary 2\.1.Concept scheme.WebHome]], [[codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]], [[metadata structure definition>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]], [[category scheme>>doc:sdmx:Glossary 2\.1.Category scheme.WebHome]], etc.) is added to, deleted from, or modified in the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] repository, a [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] event is triggered. [[Subscriptions>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] may be set up to monitor all such events, or focus on specific [[artefacts>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] such as a [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]]. 1074 1074 1075 1075 === 7.5.5 Registration Events === 1076 1076 1077 -Whenever a [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadata-set is registered a registration event is created. A [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below: 1081 +Whenever a [[dataset>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] or metadata-set is registered a registration event is created. A [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below: 1078 1078 1079 1079 ((( 1080 1080 (% style="width:1082.83px" %) 1081 -|(% style="width:230px" %)**Selector**|(% style="width:850px" %)**Comment** 1082 -|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] registered by the specified dataprovider will activate the notification. 1083 -|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] for the agreement will activate the notification. 1084 -|(% style="width:230px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] for the specified [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] will activate the notification. 1085 -|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] for those [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] that are based on the specified [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] will activate the notification 1086 -|(% style="width:230px" %)Category|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] registered for those [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] that are categorised by the category. 1085 +|(% style="width:230px" %)**Selector**|(% style="width:850px" %)**[[Comment>>doc:sdmx:Glossary 2\.1.Comment.WebHome]]** 1086 +|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] registered by the specified dataprovider will activate the [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]. 1087 +|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] for the agreement will activate the [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]. 1088 +|(% style="width:230px" %)[[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] for the specified [[dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] will activate the [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]. 1089 +|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] for those [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] that are based on the specified [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] will activate the [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] 1090 +|(% style="width:230px" %)[[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary 2\.1.Data set.WebHome]] registered for those [[dataflows>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], [[provision agreements>>doc:sdmx:Glossary 2\.1.Provision agreement.WebHome]] that are categorised by the [[category>>doc:sdmx:Glossary 2\.1.Category.WebHome]]. 1087 1087 ))) 1088 1088 1089 1089 The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration. ... ... @@ -1094,26 +1094,26 @@ 1094 1094 1095 1095 [[image:SDMX 3.1 Section 5_en_8bc1b889.jpg||height="379" width="579"]] 1096 1096 1097 -**Figure 20: Logical Class Diagram of the Notification** 1101 +**Figure 20: Logical Class Diagram of the [[Notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]]** 1098 1098 1099 -A [[notification>>doc:sdmx:Glossary.Notification.WebHome]] is an XML document that is sent to a user via email or http POST whenever a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is activated. It is an asynchronous one-way message. 1103 +A [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] is an XML document that is sent to a user via email or http POST whenever a [[subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] is activated. It is an asynchronous one-way message. 1100 1100 1101 -Regardless of the registry [[component>>doc:sdmx:Glossary.Component.WebHome]] that caused the event to be triggered, the following common information is in the message: 1105 +Regardless of the registry [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] that caused the event to be triggered, the following common information is in the message: 1102 1102 1103 1103 * Date and time that the event occurred 1104 -* The URN of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that caused the event 1105 -* The URN of the [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that produced the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] 1108 +* The URN of the [[artefact>>doc:sdmx:Glossary 2\.1.Artefact.WebHome]] that caused the event 1109 +* The URN of the [[Subscription>>doc:sdmx:Glossary 2\.1.Subscription.WebHome]] that produced the [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] 1106 1106 * Event Action: Add, Replace, or Delete. 1107 1107 1108 -Additionally, supplementary information may be contained in the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] as detailed below. 1112 +Additionally, supplementary information may be contained in the [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] as detailed below. 1109 1109 1110 1110 === 7.6.2 Structural Event Component === 1111 1111 1112 -The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will contain the MaintainableArtefact that triggered the event in a form similar to the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] structural message (using elements from that namespace). 1116 +The [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] will contain the MaintainableArtefact that triggered the event in a form similar to the [[SDMX-ML>>doc:sdmx:Glossary 2\.1.SDMX-ML.WebHome]] structural message (using elements from that namespace). 1113 1113 1114 1114 === 7.6.3 Registration Event Component === 1115 1115 1116 -The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will contain the Registration. 1120 +The [[notification>>doc:sdmx:Glossary 2\.1.Notification.WebHome]] will contain the Registration. 1117 1117 1118 1118 ---- 1119 1119
- SUZ.Methodology.Code.MethodologyClass[0]
-
- SKMS.Methodology.Code.MethodologyClass[0]
-