Last modified by Helena K. on 2026/06/09 19:45

From version 32.1
edited by Artur K.
on 2025/09/30 13:28
Change comment: There is no comment for this version
To version 33.1
edited by Artur K.
on 2025/11/05 14:26
Change comment: There is no comment for this version

Summary

Details

Page properties
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: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: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:
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 and cross-sectional data, [[structural metadata>>doc:Glossary.Structural metadata.WebHome]], and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] ([[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]])
17 +* standardised XML and JSON schemas for the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] and [[SDMX-JSON>>doc:Glossary.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:Glossary.SDMX Registry.WebHome]]/Repository (SDMXRR) is tasked with providing structure, organisation, and maintenance and query interfaces for most of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[components>>doc:Glossary.Component.WebHome]] required to support the data sharing 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:Glossary.Statistical data and metadata exchange.WebHome]]-RR provides support for the submission and retrieval of all [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc: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.
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: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.
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>>doc:sdmx:Glossary.Concept.WebHome]](%%) 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:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML, JSON (and conventional) [[artefacts>>doc:Glossary.Artefact.WebHome]] will be produced (e.g., Data Structure, Metadata Structure, [[Code List>>doc:Glossary.Code list.WebHome]] and (% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]](%%) definitions – often collectively called [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] – XML schemas generated from [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], XSLT stylesheets for transformation and display of data and metadata, terminology references, etc.). The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model supports interoperability, and it is important to be able to discover and share these [[artefacts>>doc:Glossary.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: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:Glossary.Statistical data and metadata exchange.WebHome]], with an emphasis on maintenance, retrieval and sharing of the [[structural metadata>>doc:Glossary.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:Glossary.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:Glossary.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:Glossary.Statistical data and metadata exchange.WebHome]] community manage the proliferation of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] assets and to support data sharing 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: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.
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:Glossary.SDMX Information Model.WebHome]] ([[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]])
49 +* with UML diagrams that are not a part of the [[SDMX-IM>>doc:Glossary.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:Glossary.Notification.WebHome]] mechanism must support e-mail and HTTP/HTTPS protocols as described. Normative registry interfaces are specified in the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] specification (Section 3 of the [[SDMX>>doc:Glossary.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: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.
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:Glossary.SDMX Registry.WebHome]]/repository is, in broad terms, to allow organisations to publish statistical data and [[reference metadata>>doc: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:
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:Glossary.Structural metadata.WebHome]] that describes the structure and valid content of data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] sources such as databases, [[metadata repositories>>doc:Glossary.Metadata repository.WebHome]], [[data sets>>doc:Glossary.Data set.WebHome]], [[metadata sets>>doc:Glossary.Metadata set.WebHome]]. This [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] enables software applications to understand and to interpret the data and [[reference metadata>>doc: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:Glossary.Reference metadata.WebHome]]. This facilitates data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] dissemination by implementing the data sharing vision of [[SDMX>>doc:Glossary.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:Glossary.Structural metadata.WebHome]] and the exchange context (referred to as “data provisioning”) involves the following steps for [[maintenance agencies>>doc:Glossary.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:Glossary.Data structure definition.WebHome]] or [[DSD>>doc:Glossary.Data structure definition.WebHome]] in this document but also known as “key family”), which defines the [[dimensions>>doc:Glossary.Dimension.WebHome]], [[measures>>doc:Glossary.Measure.WebHome]] and [[attributes>>doc:Glossary.Attribute.WebHome]] of a [[dataset>>doc:Glossary.Data set.WebHome]] and their valid value set;
71 +* if required, defining a subset or view of a [[DSD>>doc:Glossary.Data structure definition.WebHome]] which allows some restriction of content called a “[[dataflow>>doc:Glossary.Dataflow.WebHome]] definition”;
72 +* agreeing and creating a specification of the structure of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] ([[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]]) which defines the metadata [[attributes>>doc:Glossary.Attribute.WebHome]] and their presentational arrangement in a Metadataset or as part of a [[Dataset>>doc:Glossary.Data set.WebHome]], and their valid values and content;
73 +* if required, defining a subset or view of an [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] which allows some restriction of content called a “[[metadataflow>>doc:Glossary.Metadataflow.WebHome]]”;
74 +* defining which subject matter domains (specified as a [[Category Scheme>>doc:Glossary.Category scheme.WebHome]]) are related to the [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:Glossary.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:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] – this is called a [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] or Metadata [[Provision Agreement>>doc:Glossary.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:Glossary.Data structure definition.WebHome]] ([[DSD>>doc:Glossary.Data structure definition.WebHome]]) and [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] ([[MSD>>doc:Glossary.Metadata structure definition.WebHome]])
85 +* Flow: refers to [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]
86 +* [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]: refers to [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] (for data) and Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]
87 +* Provider Scheme: refers to [[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]] and Metadata Provider Scheme
88 +* Provider: refers to [[Data Provider>>doc:Glossary.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:Glossary.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:Glossary.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.Statistical data and metadata exchange.WebHome]] registries.
96 +* making the [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and data available in [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]]/JSON conformant data files or databases (which respond to an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] query with data). The data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] files or databases must be web accessible, and must conform to an agreed [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] ([[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] subset);
97 +* registering the existence of published [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] and data files or databases with one or more [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] registries.
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:Glossary.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:Glossary.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:Glossary.Subscription.WebHome]]-based [[notification>>doc: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:Glossary.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: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:Glossary.Statistical data and metadata exchange.WebHome]]-enabled data or [[reference metadata>>doc:Glossary.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:Glossary.Category scheme.WebHome]] to find [[Dataflows>>doc:Glossary.Dataflow.WebHome]] (and hence [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]]) and [[Metadataflows>>doc:Glossary.Metadataflow.WebHome]] which structure the type of data and/or [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] being sought;
114 +* build a query, in terms of the selected [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], which specifies what data are required and submitting this to a service that can query an [[SDMX registry>>doc:Glossary.SDMX Registry.WebHome]] which will return a list of (URLs of) data and [[reference metadata>>doc: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:Glossary.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: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:Glossary.Structural metadata.WebHome]] repository which supports a provisioning [[metadata repository>>doc:Glossary.Metadata repository.WebHome]] which supports the registry services. These are all supported by the [[SDMX-ML>>doc: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:Glossary.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:Glossary.Structural metadata.WebHome]] service which supports the lifecycle of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]] such as [[Maintenance Agencies>>doc:Glossary.Maintenance agency.WebHome]], [[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreements>>doc:Glossary.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:Glossary.Statistical data and metadata exchange.WebHome]] REST API supports all of the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:Glossary.Artefact.WebHome]]. The only structural [[artefacts>>doc:Glossary.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:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]]
139 139  
140 -As of the initial 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:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 no messages are defined to support these [[artefacts>>doc:Glossary.Artefact.WebHome]]; hence, users may need to use [[SDMX>>doc:Glossary.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:Glossary.Structural metadata.WebHome]] that describes the various types of data-store which model [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-conformant databases or files, and to link to these [[data sources>>doc:Glossary.Data source.WebHome]]. These links can be specified for a data/metadata provider, for a specific data or [[metadata flow>>doc:Glossary.Metadataflow.WebHome]]. In the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] model this is called the Provision or Metadata [[Provision Agreement>>doc:Glossary.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:Glossary.Subscription.WebHome]] Request
156 +* Submit [[Subscription>>doc:Glossary.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:Glossary.Subscription.WebHome]] Request
162 +* Query [[Subscription>>doc:Glossary.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: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:Glossary.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:Glossary.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:Glossary.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: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.
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>>doc:sdmx:Glossary.Level.WebHome]](%%) 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:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc: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:Glossary.Structural metadata.WebHome]] that can be processed by the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR is a MaintainableArtefact, with the exception of [[Item Schemes>>doc:Glossary.Item scheme.WebHome]], where changes at an Item (% style="color:#e74c3c" %)[[level>>doc:Glossary.Level.WebHome]](%%) is also possible (see next section on the [[SDMX Information Model>>doc:Glossary.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:Glossary.Structural metadata.WebHome]]. This mechanism can be the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] REST interface for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] (this is defined in the corresponding GitHub project, dedicated to the [[SDMX>>doc: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:Glossary.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:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:Glossary.Artefact.WebHome]] that may be queried are defined in the [[SDMX>>doc: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]]
192 192  
193 193  === 5.2.4 Data and Reference Metadata Registration Service ===
194 194  
... ... @@ -199,21 +199,21 @@
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
202 +The Data Registration Service allows [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant files and web-accessible databases containing published data and [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] to be registered in the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]]. The registration process MAY validate the content of the [[datasets>>doc:Glossary.Data set.WebHome]] or metadata-sets, and MAY extract a concise [[representation>>doc:Glossary.Representation.WebHome]] of the contents in terms of (% style="color:#e74c3c" %)concept(%%) values (e.g., values of the data [[attribute>>doc:Glossary.Attribute.WebHome]], [[dimension>>doc:Glossary.Dimension.WebHome]], metadata [[attribute>>doc:Glossary.Attribute.WebHome]]), or entire keys, and storing this as a record in the registry to enable discovery of the original [[dataset>>doc:Glossary.Data set.WebHome]] or
203 203  
204 -metadata-set. These are called (% style="color:#e74c3c" %)[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) in the SDMX-IM.
204 +metadata-set. These are called (% style="color:#e74c3c" %)[[Constraints>>doc:Glossary.Constraint.WebHome]](%%) in the SDMX-IM.
205 205  
206 206  The Data Registration Service MAY validate the following, subject to the access control mechanism implemented in the Registry:
207 207  
208 -* that the data/metadata provider is allowed to register the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadataset;
209 -* that the content of the [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] or metadataset meets the validation (% style="color:#e74c3c" %)[[constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%). This is dependent upon such (% style="color:#e74c3c" %)[[constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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]];
210 -* 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;
211 -* that a simple [[data source>>doc:sdmx:Glossary.Data source.WebHome]] exists (i.e., a file accessible at a URL);
212 -* that the correct [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] is used by the registered data;
213 -* 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]];
214 -* that the valid [[representations>>doc:sdmx:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) 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:Glossary.Data set.WebHome]] or metadataset;
209 +* that the content of the [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset meets the validation (% style="color:#e74c3c" %)[[constraints>>doc:Glossary.Constraint.WebHome]](%%). This is dependent upon such (% style="color:#e74c3c" %)[[constraints>>doc:Glossary.Constraint.WebHome]](%%) being defined in the structural repository and which reference the relevant [[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], [[Data Provider>>doc:Glossary.Data provider.WebHome]], Metadata Provider, [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]], [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]];
210 +* that a queryable [[data source>>doc:Glossary.Data source.WebHome]] exists – this would necessitate the registration service querying the service to determine its existence;
211 +* that a simple [[data source>>doc:Glossary.Data source.WebHome]] exists (i.e., a file accessible at a URL);
212 +* that the correct [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] is used by the registered data;
213 +* that the [[components>>doc:Glossary.Component.WebHome]] ([[Dimensions>>doc:Glossary.Dimension.WebHome]], [[Attributes>>doc:Glossary.Attribute.WebHome]], [[Measures>>doc:Glossary.Measure.WebHome]]) are consistent with the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]];
214 +* that the valid [[representations>>doc:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)[[concepts>>doc:Glossary.Concept.WebHome]](%%) to which these [[components>>doc:Glossary.Component.WebHome]] correspond conform to the definition in the [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
215 215  
216 -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:Glossary.Attribute.WebHome]] which takes one of the following values:
217 217  
218 218  (% style="width:893.835px" %)
219 219  |(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour**
... ... @@ -221,16 +221,16 @@
221 221  |(% 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
222 222  |(% style="width:241px" %)Delete|(% style="width:650px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
223 223  
224 -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:Glossary.Attribute.WebHome]] which may be present to determine how an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] compliant [[dataset>>doc:Glossary.Data set.WebHome]] or metadataset indexing application must index the [[datasets>>doc:Glossary.Data set.WebHome]] or metadatasets upon registration. The indexing application behaviour is as follows:
225 225  
226 226  (% style="width:896.835px" %)
227 227  |**Boolean Attribute**|(% style="width:712px" %)**Behaviour if Value is “true”**
228 228  |indexTimeSeries|(% style="width:712px" %)A compliant indexing application must index all the time series keys
229 229  |indexDataSet|(% style="width:712px" %)(((
230 -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]].
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.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:Glossary.Dimension.WebHome]] of the [[Dataset>>doc:Glossary.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:Glossary.Dimension.WebHome]] values (the Key) is actually present in the [[Dataset>>doc:Glossary.Data set.WebHome]]
232 232  )))
233 -|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:Glossary.Time period.WebHome]] range(s) for which data are present in the [[Dataset>>doc:Glossary.Data set.WebHome]].
234 234  
235 235  === 5.2.5 Data Discovery ===
236 236  
... ... @@ -241,57 +241,57 @@
241 241  
242 242  === 5.2.6 Subscription and Notification ===
243 243  
244 -The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] Service implements the following Registry Interfaces:
244 +The [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]] Service implements the following Registry Interfaces:
245 245  
246 246  * SubmitSubscriptionRequest
247 247  * SubmitSubscriptionResponse
248 248  * NotifyRegistryEvent
249 249  
250 -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 paradigm relies upon the consumers of data and metadata being able to pull information from [[data providers>>doc:Glossary.Data provider.WebHome]]’ dissemination systems. For this to work efficiently, a [[data consumer>>doc: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:Glossary.Data set.WebHome]] has been updated and re-registered). Additionally, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] systems may also want to know if a new [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]], or [[Code List>>doc:Glossary.Code list.WebHome]] has been added. The [[Subscription>>doc:Glossary.Subscription.WebHome]] and [[Notification>>doc:Glossary.Notification.WebHome]] Service comprises two parts: [[subscription>>doc:Glossary.Subscription.WebHome]] management, and [[notification>>doc:Glossary.Notification.WebHome]].
251 251  
252 -[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request which contains:
252 +[[Subscription>>doc:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:Glossary.Subscription.WebHome]] request which contains:
253 253  
254 -* a query or (% style="color:#e74c3c" %)[[constraint>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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).
255 -* 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 +* a query or (% style="color:#e74c3c" %)[[constraint>>doc:Glossary.Constraint.WebHome]](%%) 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:Glossary.Dataflow.WebHome]], or for a domain [[category>>doc:Glossary.Category.WebHome]], or changes to a Data Structure Definition).
255 +* a list of URIs or endpoints to which an XML [[notification>>doc:Glossary.Notification.WebHome]] message can be sent. Supported endpoint types will be email (mailto and HTTP POST (a normal http:~/~/ address);
256 256  * request for a list of submitted subscriptions;
257 -* deletion of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]];
257 +* deletion of a [[subscription>>doc:Glossary.Subscription.WebHome]];
258 258  
259 -[[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:Glossary.Notification.WebHome]] requires that the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository and the provisioning [[metadata repository>>doc:Glossary.Metadata repository.WebHome]] monitor any event which is of interest to a user (the object of a [[subscription>>doc:Glossary.Subscription.WebHome]] request query), and to issue an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[notification>>doc:Glossary.Notification.WebHome]] document to the endpoints specified in the relevant [[subscriptions>>doc:Glossary.Subscription.WebHome]].
260 260  
261 261  === 5.2.7 Registry Behaviour ===
262 262  
263 -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
263 +The following table defines the behaviour of the [[SDMX Registry>>doc:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages. It should be noted, though, that as of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0, an extended versioning scheme newly including semantic versioning is foreseen for all [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]]. Moreover, while the old versioning scheme is allowed, given there is no more
264 264  
265 -a "final" flag, there is no way guaranteeing the consistency across (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%) of a Maintainable, unless semantic versioning is used.
265 +a "final" flag, there is no way guaranteeing the consistency across (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) of a Maintainable, unless semantic versioning is used.
266 266  
267 -Given the above, the behaviour described in the following table concerns either draft [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] using semantic versioning or any [[Artefacts>>doc:sdmx:Glossary.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.Artefact.WebHome]] that follows semantic versioning, unless a newer (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%) is introduced according to the semantic versioning rules. Furthermore, even when draft [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] are submitted, the registry has to verify semantic versioning is respected against the previous non-draft (% style="color:#e74c3c" %)[[versions>>doc:sdmx:Glossary.Version.WebHome]](%%). It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] applies to externally shared [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]. This means that any system may internally perform any change within a (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%) 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.
267 +Given the above, the behaviour described in the following table concerns either draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] using semantic versioning or any [[Artefacts>>doc:Glossary.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:Glossary.Artefact.WebHome]] that follows semantic versioning, unless a newer (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) is introduced according to the semantic versioning rules. Furthermore, even when draft [[Artefacts>>doc:Glossary.Artefact.WebHome]] are submitted, the registry has to verify semantic versioning is respected against the previous non-draft (% style="color:#e74c3c" %)[[versions>>doc:Glossary.Version.WebHome]](%%). It is worth noting that the rules for semantic versioning and replacing or maintaining semantically versioned [[Artefacts>>doc:Glossary.Artefact.WebHome]] applies to externally shared [[Artefacts>>doc:Glossary.Artefact.WebHome]]. This means that any system may internally perform any change within a (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) of an [[Artefact>>doc:Glossary.Artefact.WebHome]], until the latter is shared outside of that system or becomes public. Then (as also explained in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”) the [[Artefacts>>doc:Glossary.Artefact.WebHome]] must adhere to the Semantic Versioning rules.
268 268  
269 269  (% style="width:982.835px" %)
270 270  |(% style="width:217px" %)**Interface**|(% style="width:763px" %)**Behaviour**
271 271  |(% style="width:217px" %)All|(% style="width:763px" %)(((
272 -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: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.
273 273  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.
274 -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: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:
275 275  
276 -a) Be a draft (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%).
276 +a) Be a draft (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%).
277 277  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.
278 278  
279 -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:Glossary.Statistical data and metadata exchange.WebHome]] documentation MUST be obeyed.
280 280  )))
281 281  |(% style="width:217px" %)Structure submission|(% style="width:763px" %)(((
282 -Structures are submitted at the level of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the level of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
282 +Structures are submitted at the level of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the level of the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]].
283 283  )))
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.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: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:Glossary.Statistical data and metadata exchange.WebHome]] data query.
285 285  
286 286  = 6 Identification of SDMX Objects =
287 287  
288 288  == 6.1 Identification, Versioning, and Maintenance ==
289 289  
290 -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:Glossary.SDMX Information Model.WebHome]] inherit from one of:
291 291  
292 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.
293 293  * //**NameableArtefact**// – this has all of the features of //IdentifiableArtefact// plus the ability to have a multi-lingual name and description.
294 -* //**VersionableArtefact**// – this has all of the above features plus a (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%) 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>>doc:Glossary.Version.WebHome]](%%) number, according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”, and a validity period.
295 295  * //**MaintainableArtefact**// – this has all of the above features, plus registry and structure URIs, and an association to the maintenance organisation of the object.
296 296  
297 297  === 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
... ... @@ -300,7 +300,7 @@
300 300  
301 301  **Figure 5: Class diagram of fundamental artefacts in the SDMX-IM**
302 302  
303 -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:Glossary.Attribute.WebHome]] to be stored in a registry for objects that are one of:
304 304  
305 305  * //Annotable//
306 306  * //Identifiable//
... ... @@ -309,7 +309,7 @@
309 309  * //Maintainable//
310 310  
311 311  (% style="width:1038.83px" %)
312 -|(% 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:Glossary.Attribute.WebHome]]**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
313 313  |(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
314 314  |(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
315 315  |(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
... ... @@ -334,11 +334,11 @@
334 334  
335 335  //Identifiable// plus
336 336  )))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
337 -|(% colspan="2" %)(% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]]|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%) number according to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules.
337 +|(% colspan="2" %)(% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]]|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) number according to [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules.
338 338  |(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
339 339  |(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
340 340  |(% colspan="2" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
341 -|(% 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: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:Glossary.SDMX-ML.WebHome]] file.
342 342  |(% 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.
343 343  |(% colspan="2" %) |(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.
344 344  |(% 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.
... ... @@ -349,24 +349,24 @@
349 349  
350 350  === 6.2.1 Agencies and Metadata Providers ===
351 351  
352 -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:Glossary.Maintenance agency.WebHome]] in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is maintained in an [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
353 353  
354 354  [[image:SDMX 3.1 Section 5_en_67b3555e.jpg||height="313" width="554"]]
355 355  
356 356  **Figure 6: Agency Scheme Model**
357 357  
358 -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 level of this structure is maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top 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 version (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:Glossary.Statistical data and metadata exchange.WebHome]] is extremely important. The Agency Id system used in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is an nlevel structure. The top level of this structure is maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] has a fixed id and version (version ‘1.0’) and is never declared explicitly in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism.
359 359  
360 -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:Glossary.Statistical data and metadata exchange.WebHome]] adopts the following rules:
361 361  
362 -* Agencies are maintained in an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme).
363 -* 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]].
364 -* The “top-level” agency is [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-level” [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
365 -* Agencies registered in the top-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.
366 -* The AgencyScheme has a fixed (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%), 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:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme).
363 +* The agency of the [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] must also be declared in a (different) [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
364 +* The “top-level” agency is [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-level” [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
365 +* Agencies registered in the top-level scheme can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]]. Agencies in these second-tier schemes can themselves maintain a single [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] and so on.
366 +* The AgencyScheme has a fixed (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%), i.e., ‘1.0’, hence it is an exception from the Semantic Versioning that other [[Artefacts>>doc:Glossary.Artefact.WebHome]] follow.
367 367  * There can be only one AgencyScheme maintained by any one Agency. It has a fixed id of AGENCIES.
368 -* 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]].
369 -* The format of the agency identifier is agencyID.agencyID etc. The top-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:Glossary.Hierarchy.WebHome]] of Organisation is not inherited by [[Maintenance Agency>>doc:Glossary.Maintenance agency.WebHome]] – thus each [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]] is a flat list of [[Maintenance Agencies>>doc:Glossary.Maintenance agency.WebHome]].
369 +* The format of the agency identifier is agencyID.agencyID etc. The top-level agency in this identification mechanism is the agency registered in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[agency scheme>>doc:Glossary.Agency scheme.WebHome]]. In other words, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is not a part of the hierarchical ID structure for agencies. However, [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] is, itself, a [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]] and is contained in the top-(% style="color:#e74c3c" %)level(%%) [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
370 370  
371 371  This supports a hierarchical structure of agencyID.
372 372  
... ... @@ -376,14 +376,14 @@
376 376  
377 377  **Figure 7: Example of Hierarchic Structure of Agencies**
378 378  
379 -The following organizations maintain an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
379 +The following organizations maintain an [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]].
380 380  
381 -* [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] – contains Agencies AA, BB
381 +* [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] – contains Agencies AA, BB
382 382  * AA – contains Agencies CC, DD
383 383  * BB – contains Agencies CC, DD
384 384  * DD – Contains Agency EE
385 385  
386 -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:Glossary.Hierarchy.WebHome]] excluding [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]].
387 387  
388 388  e.g., the id of EE as an agencyID is AA.DD.EE
389 389  
... ... @@ -393,27 +393,27 @@
393 393  
394 394  **Figure 8: Example Showing Use of Agency Identifiers**
395 395  
396 -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:Glossary.Maintenance agency.WebHome]] has an identical [[Code list>>doc:Glossary.Code list.WebHome]] with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure.
397 397  
398 -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:Glossary.Maintainable artefact.WebHome]], i.e., the Metadatasets; the latter are the containers of [[reference metadata>>doc:Glossary.Reference metadata.WebHome]] combined with a target that those metadata refer to.
399 399  
400 400  === 6.2.2 Universal Resource Name (URN) ===
401 401  
402 402  ==== 6.2.2.1 Introduction ====
403 403  
404 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) etc.).
404 +To provide interoperability between [[SDMX Registry>>doc: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:Glossary.SDMX Information Model.WebHome]] objects. Most of these unique identifiers are composite (containing [[maintenance agency>>doc: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:Glossary.Component.WebHome]] in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR APIs. In other words, the URN for any [[Identifiable Artefact>>doc:Glossary.Identifiable artefact.WebHome]] is constructed from its [[component>>doc:Glossary.Component.WebHome]] identifiers (agency, id, (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) etc.).
405 405  
406 406  ==== 6.2.2.2 URN Structure //__Case Rules for URN__// ====
407 407  
408 408  For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
409 409  
410 -SDMXprefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-version).*containerobject-id.object-id
410 +SDMXprefix.[[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-version).*containerobject-id.object-id
411 411  
412 412  ~* this can repeat and may not be present (see explanation below)
413 413  
414 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) information that is allowed is for the maintainable object.
414 +Note that in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] there are no concrete [[Versionable Artefacts>>doc:Glossary.Versionable artefact.WebHome]] that are not a [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]]. For this reason, the only (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) information that is allowed is for the maintainable object.
415 415  
416 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) 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:Glossary.Maintenance agency.WebHome]] identifier is separated from the [[maintainable artefact>>doc:Glossary.Maintainable artefact.WebHome]] identifier by a colon ‘:’. All other identifiers in the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] URN syntax are separated by a period ‘.’. The (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) information is encapsulated in parentheses ‘()’ and adheres to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, as explained in [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning.
417 417  
418 418  ==== 6.2.2.3 Explanation of the generic structure ====
419 419  
... ... @@ -429,13 +429,13 @@
429 429  
430 430  **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.
431 431  
432 -**maintainable-object-[[version>>doc:sdmx:Glossary.Version.WebHome]]** is the (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%), 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-[[version>>doc:Glossary.Version.WebHome]]** is the (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%), according to the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] versioning rules, of the maintainable object and is enclosed in parentheses ‘()’, which are always present.
433 433  
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.Code.WebHome]] is in a maintained object ([[Codelist>>doc:sdmx:Glossary.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>>doc:sdmx:Glossary.Level.WebHome]](%%) 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/ 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:Glossary.Code.WebHome]] is in a maintained object ([[Codelist>>doc:Glossary.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>>doc:Glossary.Level.WebHome]](%%) in its [[hierarchy>>doc: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/ TimeDimension, or a Measure.
435 435  
436 -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>>doc:sdmx:Glossary.Concept.WebHome]](%%) can have a parent (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) these are maintained in a flat structure and therefore do not have a containerobject-id.
436 +Note that although a [[Code>>doc:Glossary.Code.WebHome]] can have a parent [[Code>>doc:Glossary.Code.WebHome]] and a (% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]](%%) can have a parent (% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]](%%) these are maintained in a flat structure and therefore do not have a containerobject-id.
437 437  
438 -For example, the sequence is agency:DSDid((% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%)).DimensionId and not agency:DSDid((% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%)).DimensionDescriptorId.DimensionId.
438 +For example, the sequence is agency:DSDid((% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%)).DimensionId and not agency:DSDid((% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%)).DimensionDescriptorId.DimensionId.
439 439  
440 440  object-id is the identifier of the actual object unless the actual object is a //Maintainable// object. If present it is always the last id and is not followed by any other character.
441 441  
... ... @@ -455,48 +455,48 @@
455 455  
456 456  __Actual object is contained in a maintained object with no intermediate containing__ __object but__ __the object type itself is hierarchical__
457 457  
458 -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: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:Glossary.Category.WebHome]] in a CategoryScheme. The [[Category>>doc:Glossary.Category.WebHome]] is hierarchical, and all intermediate [[Categories>>doc:Glossary.Category.WebHome]] are shown as a contained object. The example below shows the generic structure for CategoryScheme/ [[Category>>doc:Glossary.Category.WebHome]]/ [[Category>>doc:Glossary.Category.WebHome]].
459 459  
460 460  SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
461 461  
462 462  Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
463 463  
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.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:Glossary.Metadata structure definition.WebHome]]/ MetadataAttributeDescriptor/ MetadataAttribute/ MetadataAttribute
465 465  
466 466  SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id
467 467  
468 468  //__**Concrete Examples of the URN Structure**__//
469 469  
470 -The [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] CRED_EXT_DEBT of legacy (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%) 2.1 maintained by the toplevel Agency TFFS would have the URN:
470 +The [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] CRED_EXT_DEBT of legacy (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) 2.1 maintained by the toplevel Agency TFFS would have the URN:
471 471  
472 472  urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(2.1)
473 473  
474 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) 1.0.0 would be:
474 +The URN for a [[code>>doc:Glossary.Code.WebHome]] for Argentina maintained by ISO in the [[code list>>doc:Glossary.Code list.WebHome]] CL_3166A2 of semantic (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) 1.0.0 would be:
475 475  
476 -urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.codelist.[[Code>>doc:sdmx:Glossary.Code.WebHome]]=ISO:CL_3166A2(1.0.0).AR
476 +urn:[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.codelist.[[Code>>doc:Glossary.Code.WebHome]]=ISO:CL_3166A2(1.0.0).AR
477 477  
478 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) 1.0.0draft would be:
478 +The URN for a [[category>>doc:Glossary.Category.WebHome]] (id of 1) which has parent [[category>>doc:Glossary.Category.WebHome]] (id of 2) maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] in the [[category scheme>>doc:Glossary.Category scheme.WebHome]] SUBJECT_MATTER_DOMAINS of the semantic extended (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) 1.0.0draft would be:
479 479  
480 -urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.categoryscheme.[[Category>>doc:sdmx:Glossary.Category.WebHome]]=[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2
480 +urn:[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.categoryscheme.[[Category>>doc:Glossary.Category.WebHome]]=[[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]:SUBJECT_MATT ER_DOMAINS(1.0.0-draft).1.2
481 481  
482 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) 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:Glossary.Attribute.WebHome]] maintained by [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] in the [[MSD>>doc:Glossary.Metadata structure definition.WebHome]] CONTACT_METADATA of semantic (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) 1.0.0 where the [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] of the Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]] is CONTACT_DETAILS/CONTACT_NAME would be:
483 483  
484 -urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.metadatastructure.MetadataAttribute=[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME
484 +urn:[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.metadatastructure.MetadataAttribute=[[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]: CONTACT_METADATA(1.0.0).CONTACT_DETAILS.CONTACT_NAME
485 485  
486 -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>>doc:sdmx:Glossary.Version.WebHome]](%%) 1.0.0 would be:
486 +The TFFS defines ABC as a sub-Agency of TFFS then the URN of a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] maintained by ABC and identified as EXTERNAL_DEBT of semantic (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%) 1.0.0 would be:
487 487  
488 -urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.datastructure.[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]=TFFS.ABC:EXTERNAL_ DEBT(1.0.0)
488 +urn:[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]]:org.[[sdmx>>doc:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.datastructure.[[Dataflow>>doc:Glossary.Dataflow.WebHome]]=TFFS.ABC:EXTERNAL_ DEBT(1.0.0)
489 489  
490 -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:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST support this globally unique identification scheme. The [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to create the URN from the individual identification [[attributes>>doc:Glossary.Attribute.WebHome]] submitted and to transform the URN to these identification [[attributes>>doc:Glossary.Attribute.WebHome]]. The identification [[attributes>>doc:Glossary.Attribute.WebHome]] are:
491 491  
492 -* **Identifiable and [[Nameable Artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]]**: id (in some cases this id may be hierarchic)
493 -* **Maintainable [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]**: id, (% style="color:#e74c3c" %)[[version>>doc:sdmx:Glossary.Version.WebHome]](%%), agencyId
492 +* **Identifiable and [[Nameable Artefacts>>doc:Glossary.Nameable artefact.WebHome]]**: id (in some cases this id may be hierarchic)
493 +* **Maintainable [[Artefacts>>doc:Glossary.Artefact.WebHome]]**: id, (% style="color:#e74c3c" %)[[version>>doc:Glossary.Version.WebHome]](%%), agencyId
494 494  
495 -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:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST be able to resolve the unique identifier of an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[artefact>>doc:Glossary.Artefact.WebHome]] and to produce an [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] rendering of that [[artefact>>doc:Glossary.Artefact.WebHome]] if it is located in the Registry.
496 496  
497 497  === 6.2.3 Table of SDMX-IM Packages and Classes ===
498 498  
499 -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:Glossary.SDMX Information Model.WebHome]] together with the concrete classes that are in these packages and whose objects have a URN.
500 500  
501 501  (% style="width:750.835px" %)
502 502  |(% style="width:222px" %)**Package**|(% style="width:526px" %)**URN class name (model class name where this is different)**
... ... @@ -513,9 +513,9 @@
513 513  |(% style="width:222px" %) |(% style="width:526px" %)
514 514  |(% style="width:222px" %)datastructure|(% style="width:526px" %)AttributeDescriptor
515 515  |(% style="width:222px" %) |(% style="width:526px" %)DataAttribute
516 -|(% style="width:222px" %) |(% style="width:526px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]
516 +|(% style="width:222px" %) |(% style="width:526px" %)[[Dataflow>>doc:Glossary.Dataflow.WebHome]]
517 517  |(% style="width:222px" %) |(% style="width:526px" %)DataStructure (DataStructureDefinition)
518 -|(% style="width:222px" %) |(% style="width:526px" %)[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
518 +|(% style="width:222px" %) |(% style="width:526px" %)[[Dimension>>doc:Glossary.Dimension.WebHome]]
519 519  |(% style="width:222px" %) |(% style="width:526px" %)DimensionDescriptor
520 520  |(% style="width:222px" %) |(% style="width:526px" %)GroupDimensionDescriptor
521 521  |(% style="width:222px" %) |(% style="width:526px" %)Measure
... ... @@ -533,7 +533,7 @@
533 533  (((
534 534  (% style="width:751.835px" %)
535 535  |(% style="width:221px" %)**Package**|(% style="width:528px" %)**URN class name (model class name where this is different)**
536 -|(% style="width:221px" %) |(% style="width:528px" %)[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]
536 +|(% style="width:221px" %) |(% style="width:528px" %)[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]
537 537  |(% style="width:221px" %) |(% style="width:528px" %)MetadataSet
538 538  |(% style="width:221px" %) |(% style="width:528px" %)
539 539  |(% style="width:221px" %)process|(% style="width:528px" %)Process
... ... @@ -544,7 +544,7 @@
544 544  |(% style="width:221px" %) |(% style="width:528px" %)MetadataConstraint
545 545  |(% style="width:221px" %) |(% style="width:528px" %)MetadataProvisionAgreement
546 546  |(% style="width:221px" %) |(% style="width:528px" %)ProvisionAgreement
547 -|(% style="width:221px" %) |(% style="width:528px" %)[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]]
547 +|(% style="width:221px" %) |(% style="width:528px" %)[[Subscription>>doc:Glossary.Subscription.WebHome]]
548 548  |(% style="width:221px" %) |(% style="width:528px" %)
549 549  |(% style="width:221px" %)structuremapping|(% style="width:528px" %)CategorySchemeMap
550 550  |(% style="width:221px" %) |(% style="width:528px" %)ConceptSchemeMap
... ... @@ -553,21 +553,21 @@
553 553  |(% style="width:221px" %) |(% style="width:528px" %)RepresentationMap
554 554  |(% style="width:221px" %) |(% style="width:528px" %)StructureMap
555 555  |(% style="width:221px" %) |(% style="width:528px" %)
556 -|(% style="width:221px" %)codelist|(% style="width:528px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]]
556 +|(% style="width:221px" %)codelist|(% style="width:528px" %)[[Code>>doc:Glossary.Code.WebHome]]
557 557  |(% style="width:221px" %) |(% style="width:528px" %)Codelist
558 558  |(% style="width:221px" %) |(% style="width:528px" %)HierarchicalCode
559 -|(% style="width:221px" %) |(% style="width:528px" %)[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]
559 +|(% style="width:221px" %) |(% style="width:528px" %)[[Hierarchy>>doc:Glossary.Hierarchy.WebHome]]
560 560  |(% style="width:221px" %) |(% style="width:528px" %)HierarchyAssociation
561 -|(% style="width:221px" %) |(% style="width:528px" %)(% style="color:#e74c3c" %)[[Level>>doc:sdmx:Glossary.Level.WebHome]]
561 +|(% style="width:221px" %) |(% style="width:528px" %)(% style="color:#e74c3c" %)[[Level>>doc:Glossary.Level.WebHome]]
562 562  |(% style="width:221px" %) |(% style="width:528px" %)ValueList
563 563  |(% style="width:221px" %) |(% style="width:528px" %)
564 564  |(% style="width:221px" %)categoryscheme|(% style="width:528px" %)Categorisation
565 -|(% style="width:221px" %) |(% style="width:528px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]
565 +|(% style="width:221px" %) |(% style="width:528px" %)[[Category>>doc:Glossary.Category.WebHome]]
566 566  |(% style="width:221px" %) |(% style="width:528px" %)CategoryScheme
567 567  |(% style="width:221px" %) |(% style="width:528px" %)ReportingCategory
568 568  |(% style="width:221px" %) |(% style="width:528px" %)ReportingTaxonomy
569 569  |(% style="width:221px" %) |(% style="width:528px" %)
570 -|(% style="width:221px" %)conceptscheme|(% style="width:528px" %)(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]]
570 +|(% style="width:221px" %)conceptscheme|(% style="width:528px" %)(% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]]
571 571  |(% style="width:221px" %) |(% style="width:528px" %)ConceptScheme
572 572  |(% style="width:221px" %) |(% style="width:528px" %)
573 573  |(% style="width:221px" %)transformation|(% style="width:528px" %)CustomType
... ... @@ -591,7 +591,7 @@
591 591  
592 592  === 6.2.4 URN Identification components of SDMX objects ===
593 593  
594 -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:Glossary.Component.WebHome]] for all [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] object types that have identification. Note the actual [[attributes>>doc: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:Glossary.Attribute.WebHome]] of the Agency class that is associated to the ConceptScheme.
595 595  
596 596  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:
597 597  
... ... @@ -602,7 +602,7 @@
602 602  |(% 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
603 603  |(% style="width:289px" %)//AgencyScheme//|(% style="width:600px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:383px" %)ECB:**AGENCIES**(**1.0**)
604 604  |(% style="width:289px" %)//Categorisation//|(% style="width:600px" %)categorisationAgencyId:categoris(% style="color:#000000" %)ationId(version)|(% style="width:383px" %)IMF:cat001(1.0.0)
605 -|(% 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 …
605 +|(% style="width:289px" %)[[Category>>doc: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 …
606 606  |(% style="width:289px" %)//CategoryScheme//|(% style="width:600px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:383px" %)IMF:SDDS(1.0.0)
607 607  
608 608  |(% style="width:285px" %)**Classname**|(% style="width:569px" %)**Ending URN pattern**|(% style="width:794px" %)**Example**
... ... @@ -609,10 +609,10 @@
609 609  |(% style="width:285px" %)//CategorySchemeMap//|(% style="width:569px" %)(((
610 610  (% style="color:#000000" %)catSchemeMapAgencyId:catSchemeMapId(version)
611 611  )))|(% style="width:794px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
612 -|(% 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
613 -|(% style="width:285px" %)//[[Codelist>>doc:sdmx:Glossary.Code list.WebHome]]//|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codeListId(version)|(% style="width:794px" %)SDMX:CL_FREQ(1.0.0)
612 +|(% style="width:285px" %)[[Code>>doc:Glossary.Code.WebHome]]|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codelistId(version).codeId|(% style="width:794px" %)SDMX:CL_FREQ(1.0.0).Q
613 +|(% style="width:285px" %)//[[Codelist>>doc:Glossary.Code list.WebHome]]//|(% style="width:569px" %)(% style="color:#000000" %)codeListAgencyId:codeListId(version)|(% style="width:794px" %)SDMX:CL_FREQ(1.0.0)
614 614  |(% 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
615 -|(% style="width:285px" %)(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]]|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:794px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
615 +|(% style="width:285px" %)(% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]]|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:794px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
616 616  |(% style="width:285px" %)//ConceptScheme//|(% style="width:569px" %)(% style="color:#000000" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:794px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
617 617  |(% style="width:285px" %)//ConceptSchemeMap//|(% style="width:569px" %)(((
618 618  (% style="color:#000000" %)conceptSchemeMapAgencyId:conceptSchemeMap Id(version)
... ... @@ -627,7 +627,7 @@
627 627  |(% style="width:279px" %)//DataConsumerScheme//|(% style="width:563px" %)(((
628 628  dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**)
629 629  )))|(% style="width:776px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
630 -|(% 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)
630 +|(% style="width:279px" %)//[[Dataflow>>doc:Glossary.Dataflow.WebHome]]//|(% style="width:563px" %)(% style="color:#000000" %)dataflowAgencyId:dataflowId(version)|(% style="width:776px" %)TFFS:CRED_EXT_DEBT(1.0.0)
631 631  |(% style="width:279px" %)DataProvider|(% style="width:563px" %)(((
632 632  (% style="color:#000000" %)dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId
633 633  )))|(% style="width:776px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
... ... @@ -635,7 +635,7 @@
635 635  (% style="color:#000000" %)dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**)
636 636  )))|(% style="width:776px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
637 637  |(% style="width:279px" %)//DataStructure//|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0)
638 -|(% 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
638 +|(% style="width:279px" %)[[Dimension>>doc:Glossary.Dimension.WebHome]]|(% style="width:563px" %)(% style="color:#000000" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:776px" %)TFFS:EXT_DEBT(1.0.0).FREQ
639 639  |(% style="width:279px" %)(((
640 640  DimensionDescriptor
641 641  
... ... @@ -645,7 +645,7 @@
645 645  )))|(% style="width:563px" %)(((
646 646  dataStructureDefinitionAgencyId:dataStructureDef initionId((% style="color:#000000" %)version)(%%).componentListId
647 647  
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.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:Glossary.Data structure definition.WebHome]])
649 649  )))|(% style="width:776px" %)(((
650 650  TFFS:EXT_DEBT(1.0.0).DimensionDescriptor
651 651  
... ... @@ -657,9 +657,9 @@
657 657  |(% 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
658 658  
659 659  |(% style="width:281px" %)**Classname**|(% style="width:562px" %)**Ending URN pattern**|(% style="width:772px" %)**Example**
660 -|(% 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)
660 +|(% style="width:281px" %)//[[Hierarchy>>doc:Glossary.Hierarchy.WebHome]]//|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0)
661 661  |(% style="width:281px" %)//HierarchyAssociation//|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:772px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
662 -|(% style="width:281px" %)(% style="color:#e74c3c" %)[[Level>>doc:sdmx:Glossary.Level.WebHome]]|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0).LVL1
662 +|(% style="width:281px" %)(% style="color:#e74c3c" %)[[Level>>doc:Glossary.Level.WebHome]]|(% style="width:562px" %)(% style="color:#000000" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:772px" %)UNESCO:H-C-GOV(1.0.0).LVL1
663 663  |(% 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
664 664  |(% style="width:281px" %)MetadataAttribute|(% style="width:562px" %)(((
665 665  (% style="color:#000000" %)msdAgencyId:msdId(version).metadataAttributeId.
... ... @@ -668,7 +668,7 @@
668 668  )))|(% style="width:772px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
669 669  |(% 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
670 670  |(% style="width:281px" %)//MetadataConstraint//|(% style="width:562px" %)(% style="color:#000000" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:772px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
671 -|(% 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)
671 +|(% style="width:281px" %)//[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]//|(% style="width:562px" %)(% style="color:#000000" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:772px" %)IMF:SDDS_MDF(1.0.0)
672 672  |(% 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
673 673  |(% style="width:281px" %)//MetadataProviderScheme//|(% style="width:562px" %)(% style="color:#000000" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:772px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
674 674  |(% style="width:281px" %)//MetadataProvisionAgreement//|(% style="width:562px" %)(% style="color:#000000" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:772px" %)IMF:SDDS_MDF_AB(1.0.0)
... ... @@ -701,10 +701,10 @@
701 701  |(% style="width:282px" %)Ruleset|(% style="width:566px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:768px" %)ECB:RULESET_23(1.0.0).SET111
702 702  |(% style="width:282px" %)//RulesetScheme//|(% style="width:566px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:768px" %)ECB:RULESET_23(1.0.0)
703 703  |(% style="width:282px" %)//StructureMap//|(% style="width:566px" %)structureMapAgencyId:structureMap(version)|(% style="width:768px" %)SDMX:BOP_STRUCTURES(1.0.0)
704 -|(% style="width:282px" %)[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]]|(% style="width:566px" %)(((
705 -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.
704 +|(% style="width:282px" %)[[Subscription>>doc:Glossary.Subscription.WebHome]]|(% style="width:566px" %)(((
705 +The [[Subscription>>doc:Glossary.Subscription.WebHome]] is not itself an [[Identifiable Artefact>>doc:Glossary.Identifiable artefact.WebHome]] and therefore it does not follow the rules for URN structure.
706 706  The name of the URN is registryURN There is no pre-determined format.
707 -)))|(% 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.
707 +)))|(% style="width:768px" %)This cannot be generated by a common mechanism as [[subscriptions>>doc: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: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:Glossary.Subscription.WebHome]], and for the application creating the [[subscription>>doc:Glossary.Subscription.WebHome]] to store the registry URN that is returned from the registry in the [[subscription>>doc:Glossary.Subscription.WebHome]] response message.
708 708  |(% 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
709 709  |(% 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
710 710  |(% style="width:282px" %)//TransformationScheme//|(% style="width:566px" %)(% style="color:#000000" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:768px" %)ECB: TRANSFORMATION_SCHEME(1.0.0)
... ... @@ -729,88 +729,88 @@
729 729  
730 730  === 7.1.1 Introduction ===
731 731  
732 -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>>doc:sdmx:Glossary.Concept.WebHome]](%%) 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:Glossary.SDMX Registry.WebHome]] must have the ability to support agencies in their role of defining and disseminating [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:Glossary.Artefact.WebHome]]. These [[artefacts>>doc:Glossary.Artefact.WebHome]] include [[data structure definitions>>doc:Glossary.Data structure definition.WebHome]], [[code lists>>doc:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)[[concepts>>doc:Glossary.Concept.WebHome]](%%) etc. and are fully defined in the [[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]]. An authenticated agency may submit valid [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] definitions which must be stored in the registry. Note that the term “[[structural metadata>>doc:Glossary.Structural metadata.WebHome]]” refers as a general term to all structural [[components>>doc:Glossary.Component.WebHome]] ([[Data Structure Definitions>>doc:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definitions>>doc:Glossary.Metadata structure definition.WebHome]], [[Code Lists>>doc:Glossary.Code list.WebHome]], [[Concept Schemes>>doc:Glossary.Concept scheme.WebHome]], etc.)
733 733  
734 -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: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:Glossary.SDMX-ML.WebHome]] messages for [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] and the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] RESTful API for structure queries. The message may contain all [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] items for the whole registry, [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] items for one [[maintenance agency>>doc:Glossary.Maintenance agency.WebHome]], or individual [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] items.
735 735  
736 -[[Structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items
736 +[[Structural metadata>>doc:Glossary.Structural metadata.WebHome]] items
737 737  
738 -* 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:Glossary.Maintenance agency.WebHome]] which created them;
739 739  * may only be deleted by the agency which created them;
740 740  * may not be deleted if they are referenced from other constructs in the Registry.
741 741  
742 -The 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>>doc:sdmx:Glossary.Level.WebHome]](%%) 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 level of granularity for the maintenance of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] [[Structural Metadata>>doc:Glossary.Structural metadata.WebHome]] objects in the registry is the [[Maintainable Artefact>>doc:Glossary.Maintainable artefact.WebHome]]. Especially for [[Item Schemes>>doc:Glossary.Item scheme.WebHome]], though, partial maintenance may be performed, i.e., at the (% style="color:#e74c3c" %)[[level>>doc:Glossary.Level.WebHome]](%%) of the Item, by submitting an [[Item Scheme>>doc:Glossary.Item scheme.WebHome]] with the 'isPartial' flag set and a reduced set of Items.
743 743  
744 -The following table lists the [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
744 +The following table lists the [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]].
745 745  
746 746  (% style="width:825.835px" %)
747 747  |(% colspan="2" style="width:455px" %)**Maintainable Artefacts**|(% style="width:367px" %)**Content**
748 748  |(% style="width:160px" %)**Abstract Class**|(% style="width:295px" %)**Concrete Class**|(% style="width:367px" %)
749 -|(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]]|(% style="width:295px" %)Codelist|(% style="width:367px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]]
750 -|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]|(% style="width:367px" %)(% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]]
751 -|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]|(% style="width:367px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]
752 -|(% style="width:160px" %) |(% style="width:295px" %)[[Organisation Unit Scheme>>doc:sdmx:Glossary.Organisation unit scheme.WebHome]]|(% style="width:367px" %)Organisation Unit
753 -|(% style="width:160px" %) |(% style="width:295px" %)[[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]]|(% style="width:367px" %)Agency
754 -|(% 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:Glossary.Item scheme.WebHome]]|(% style="width:295px" %)Codelist|(% style="width:367px" %)[[Code>>doc:Glossary.Code.WebHome]]
750 +|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]]|(% style="width:367px" %)(% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]]
751 +|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:Glossary.Category scheme.WebHome]]|(% style="width:367px" %)[[Category>>doc:Glossary.Category.WebHome]]
752 +|(% style="width:160px" %) |(% style="width:295px" %)[[Organisation Unit Scheme>>doc:Glossary.Organisation unit scheme.WebHome]]|(% style="width:367px" %)Organisation Unit
753 +|(% style="width:160px" %) |(% style="width:295px" %)[[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]]|(% style="width:367px" %)Agency
754 +|(% style="width:160px" %) |(% style="width:295px" %)[[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]]|(% style="width:367px" %)[[Data Provider>>doc:Glossary.Data provider.WebHome]]
755 755  |(% style="width:160px" %) |(% style="width:295px" %)Metadata Provider Scheme|(% style="width:367px" %)Metadata Provider
756 -|(% 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]]
757 -|(% 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:Glossary.Data consumer scheme.WebHome]]|(% style="width:367px" %)[[Data Consumer>>doc:Glossary.Data consumer.WebHome]]
757 +|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy|(% style="width:367px" %)Reporting [[Category>>doc:Glossary.Category.WebHome]]
758 758  |(% style="width:160px" %) |(% style="width:295px" %)Transformation Scheme|(% style="width:367px" %)Transformation
759 759  |(% style="width:160px" %) |(% style="width:295px" %)Custom Type Scheme|(% style="width:367px" %)Custom Type
760 760  |(% style="width:160px" %) |(% style="width:295px" %)Name Personalisation Scheme|(% style="width:367px" %)Name Personalisation
761 -|(% 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>>doc:sdmx:Glossary.Code list.WebHome]] Mapping [[Vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] (% style="color:#e74c3c" %)[[Concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) Mapping
761 +|(% style="width:160px" %) |(% style="width:295px" %)[[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] Mapping Scheme|(% style="width:367px" %)[[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] [[Codelist>>doc:Glossary.Code list.WebHome]] Mapping [[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] (% style="color:#e74c3c" %)[[Concept>>doc:Glossary.Concept.WebHome]](%%) Mapping
762 762  |(% style="width:160px" %) |(% style="width:295px" %)Ruleset Scheme|(% style="width:367px" %)Ruleset
763 763  |(% style="width:160px" %) |(% style="width:295px" %)User Defined Operator Scheme|(% style="width:367px" %)User Defined Operator
764 764  |(% style="width:160px" %)Enumerated List|(% style="width:295px" %)ValueList|(% style="width:367px" %)Value Item
765 -|(% style="width:160px" %)Structure|(% style="width:295px" %)[[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]|(% style="width:367px" %)(((
766 -[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor
767 -Group [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor
768 -[[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
769 -Time [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]
770 -[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor
771 -Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
765 +|(% style="width:160px" %)Structure|(% style="width:295px" %)[[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]|(% style="width:367px" %)(((
766 +[[Dimension>>doc:Glossary.Dimension.WebHome]] Descriptor
767 +Group [[Dimension>>doc:Glossary.Dimension.WebHome]] Descriptor
768 +[[Dimension>>doc:Glossary.Dimension.WebHome]]
769 +Time [[Dimension>>doc:Glossary.Dimension.WebHome]]
770 +[[Attribute>>doc:Glossary.Attribute.WebHome]] Descriptor
771 +Data [[Attribute>>doc:Glossary.Attribute.WebHome]]
772 772  Measure Descriptor
773 773  Measure
774 774  )))
775 -|(% 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]]
776 -|(% style="width:160px" %)Structure Usage|(% style="width:295px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]|(% style="width:367px" %)
777 -|(% 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:Glossary.Metadata structure definition.WebHome]]|(% style="width:367px" %)Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]] Descriptor Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]]
776 +|(% style="width:160px" %)Structure Usage|(% style="width:295px" %)[[Dataflow>>doc:Glossary.Dataflow.WebHome]]|(% style="width:367px" %)
777 +|(% style="width:160px" %) |(% style="width:295px" %)[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]]|(% style="width:367px" %)
778 778  |(% style="width:160px" %)None|(% style="width:295px" %)Process|(% style="width:367px" %)Process Step
779 779  |(% style="width:160px" %)None|(% style="width:295px" %)Structure Map|(% style="width:367px" %)(((
780 -[[Component>>doc:sdmx:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]](%%)
781 -Epoch (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]](%%)
782 -Date Pattern (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]]
780 +[[Component>>doc:Glossary.Component.WebHome]] (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]](%%)
781 +Epoch (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]](%%)
782 +Date Pattern (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]]
783 783  )))
784 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Map|(% style="width:367px" %)[[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping
785 -|(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] Map|(% style="width:295px" %)Organisation Scheme Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]]
786 -|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]]
787 -|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]]
788 -|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:sdmx:Glossary.Map.WebHome]]
789 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]|(% style="width:367px" %)
790 -|(% style="width:160px" %)None|(% style="width:295px" %)Metadata [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]|(% style="width:367px" %)
791 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]|(% style="width:367px" %)Hierarchical [[Code>>doc:sdmx:Glossary.Code.WebHome]]
792 -|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] Association|(% style="width:367px" %)
784 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Representation>>doc:Glossary.Representation.WebHome]] Map|(% style="width:367px" %)[[Representation>>doc:Glossary.Representation.WebHome]] Mapping
785 +|(% style="width:160px" %)[[Item Scheme>>doc:Glossary.Item scheme.WebHome]] Map|(% style="width:295px" %)Organisation Scheme Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]]
786 +|(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]] Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]]
787 +|(% style="width:160px" %) |(% style="width:295px" %)[[Category Scheme>>doc:Glossary.Category scheme.WebHome]] Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]]
788 +|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy Map|(% style="width:367px" %)Item (% style="color:#e74c3c" %)[[Map>>doc:Glossary.Map.WebHome]]
789 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]|(% style="width:367px" %)
790 +|(% style="width:160px" %)None|(% style="width:295px" %)Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]]|(% style="width:367px" %)
791 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:Glossary.Hierarchy.WebHome]]|(% style="width:367px" %)Hierarchical [[Code>>doc:Glossary.Code.WebHome]]
792 +|(% style="width:160px" %)None|(% style="width:295px" %)[[Hierarchy>>doc:Glossary.Hierarchy.WebHome]] Association|(% style="width:367px" %)
793 793  |(% style="width:160px" %)None|(% style="width:295px" %)Categorisation|(% style="width:367px" %)
794 -|(% style="width:160px" %)(% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]]|(% style="width:295px" %)Data (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]]|(% style="width:367px" %)DataKeySet
794 +|(% style="width:160px" %)(% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]]|(% style="width:295px" %)Data (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]]|(% style="width:367px" %)DataKeySet
795 795  |(% style="width:160px" %) |(% style="width:295px" %) |(% style="width:367px" %)CubeRegion
796 -|(% style="width:160px" %)(% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]]|(% style="width:295px" %)Metadata (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]]|(% style="width:367px" %)MetadataTargetRegion
796 +|(% style="width:160px" %)(% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]]|(% style="width:295px" %)Metadata (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]]|(% style="width:367px" %)MetadataTargetRegion
797 797  
798 798  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
799 799  
800 800  === 7.1.2 Item Scheme, Structure ===
801 801  
802 -The [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] included in the structural definitions are:
802 +The [[artefacts>>doc:Glossary.Artefact.WebHome]] included in the structural definitions are:
803 803  
804 -* 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:Glossary.Item scheme.WebHome]] (Codelist, [[Concept Scheme>>doc:Glossary.Concept scheme.WebHome]], [[Category Scheme>>doc:Glossary.Category scheme.WebHome]], Organisation Scheme, [[Agency Scheme>>doc:Glossary.Agency scheme.WebHome]], [[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]], Metadata Provider Scheme, [[Data Consumer Scheme>>doc:Glossary.Data consumer scheme.WebHome]], [[Organisation Unit Scheme>>doc:Glossary.Organisation unit scheme.WebHome]], Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, [[Vtl>>doc:Glossary.Validation and transformation language.WebHome]] Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
805 805  * All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}}
806 -* All types of Structure ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]])
807 -* 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:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]])
807 +* All types of Structure Usage ([[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]])
808 808  
809 809  === 7.1.3 Structure Usage ===
810 810  
811 811  ==== 7.1.3.1 Structure Usage: Basic Concepts ====
812 812  
813 -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:Glossary.Dataflow.WebHome]] and [[Metadataflow>>doc: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:Glossary.Category.WebHome]] in one or more [[Category Scheme>>doc: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:Glossary.Category scheme.WebHome]].
814 814  
815 815  ==== 7.1.3.2 Structure Usage Schematic ====
816 816  
... ... @@ -824,63 +824,63 @@
824 824  
825 825  **Figure 10: SDMX-IM of links from Structure Usage to Category**
826 826  
827 -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:Glossary.Dataflow.WebHome]] and the [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], the following links must be maintained in the registry:
828 828  
829 -* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] to Data Structure Definition
830 -* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] to Metadata Structure Definition
829 +* [[Dataflow>>doc:Glossary.Dataflow.WebHome]] to Data Structure Definition
830 +* [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] to Metadata Structure Definition
831 831  
832 832  The following links may be created by means of a Categorisation
833 833  
834 -* Categorisation to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and [[Category>>doc:sdmx:Glossary.Category.WebHome]]
835 -* Categorisation to [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] and [[Category>>doc:sdmx:Glossary.Category.WebHome]]
834 +* Categorisation to [[Dataflow>>doc:Glossary.Dataflow.WebHome]] and [[Category>>doc:Glossary.Category.WebHome]]
835 +* Categorisation to [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] and [[Category>>doc:Glossary.Category.WebHome]]
836 836  
837 837  == 7.2 Data and Metadata Provisioning ==
838 838  
839 839  === 7.2.1 Provisioning Agreement: Basic concepts ===
840 840  
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.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 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: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 level agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and [[timeliness>>doc:Glossary.Timeliness.WebHome]] metadata can be supported by this framework which makes it practical to implement information supply chain monitoring.
842 842  
843 843  Note that the term “data provisioning” here includes both the provisioning of data and metadata.
844 844  
845 -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: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.
846 846  
847 847  === 7.2.2 Provisioning Agreement Model – pull use case ===
848 848  
849 -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:Glossary.Reference metadata.WebHome]] and wishes to make it available to an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] enabled community is called a [[Data Provider>>doc:Glossary.Data provider.WebHome]]. In terms of the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]], the [[Data Provider>>doc:Glossary.Data provider.WebHome]] is maintained in a [[Data Provider Scheme>>doc:Glossary.Data provider scheme.WebHome]].
850 850  
851 851  [[image:SDMX 3.1 Section 5_en_5a16c7fe.jpg||height="455" width="551"]]
852 852  
853 853  **Figure 11: SDMX-IM of the Data Provider**
854 854  
855 -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:Glossary.Data provider.WebHome]] does not inherit the [[hierarchy>>doc:Glossary.Hierarchy.WebHome]] association. The diagram below shows a logical schematic of the data model classes required to maintain [[provision agreements>>doc:Glossary.Provision agreement.WebHome]].
856 856  
857 857  [[image:SDMX 3.1 Section 5_en_b08fd1a2.jpg||height="299" width="533"]]
858 858  
859 859  **Figure 12: Schematic of the Provision Agreement**
860 860  
861 -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:Glossary.Representation.WebHome]] of the data required in order to maintain [[Provision Agreements>>doc:Glossary.Provision agreement.WebHome]].
862 862  
863 863  [[image:SDMX 3.1 Section 5_en_c63d10ab.jpg||height="246" width="579"]]
864 864  
865 865  **Figure 13: Logical class diagram of the information contained in the Provision Agreement**
866 866  
867 -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:Glossary.Provision agreement.WebHome]] is [[structural metadata>>doc:Glossary.Structural metadata.WebHome]]. Each [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] must reference a [[Data Provider>>doc:Glossary.Data provider.WebHome]] or Metadata Provider and a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] Definition. The Data/Metadata Provider and the [[Dataflow>>doc:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:Glossary.Metadataflow.WebHome]] must exist already in order to set up a Metadata Provision or [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]].
868 868  
869 869  == 7.3 Data and Metadata Constraints ==
870 870  
871 871  === 7.3.1 Data and Metadata Constraints: Basic Concepts ===
872 872  
873 -(% style="color:#e74c3c" %)[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) are, effectively, lists of the valid or actual content of data and metadata. (% style="color:#e74c3c" %)[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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>>doc:Glossary.Constraint.WebHome]](%%) are, effectively, lists of the valid or actual content of data and metadata. (% style="color:#e74c3c" %)[[Constraints>>doc:Glossary.Constraint.WebHome]](%%) can be used to specify a subset of the theoretical content of [[data set>>doc:Glossary.Data set.WebHome]] or [[metadata set>>doc:Glossary.Metadata set.WebHome]] which can be derived from the specification of the [[DSD>>doc:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:Glossary.Metadata structure definition.WebHome]]. A (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]](%%) can comprise a list of keys or a list of content (usually [[code>>doc:Glossary.Code.WebHome]] values) of a specific [[component>>doc:Glossary.Component.WebHome]] such as a [[dimension>>doc:Glossary.Dimension.WebHome]] or [[attribute>>doc:Glossary.Attribute.WebHome]].
874 874  
875 -(% style="color:#e74c3c" %)[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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>>doc:Glossary.Constraint.WebHome]](%%) comprise the specification of subsets of key or [[attribute>>doc:Glossary.Attribute.WebHome]] values that are to be provided for a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], or directly attached to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc: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: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:Glossary.Code list.WebHome]] for each of the [[Dimensions>>doc:Glossary.Dimension.WebHome]]) is often more than is intended to be supplied according to a specific [[Dataflow>>doc:Glossary.Dataflow.WebHome]].
876 876  
877 -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 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>>doc:sdmx:Glossary.Constraint.WebHome]](%%). The (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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: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:Glossary.Data provider.WebHome]] could constrain the [[data source>>doc:Glossary.Data source.WebHome]] (at the level of the [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]] or the [[Data Provider>>doc: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>>doc:Glossary.Constraint.WebHome]](%%). The (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]](%%) is also used to define a [[code list>>doc:Glossary.Code list.WebHome]] subset which is used to populate a partial [[code list>>doc:Glossary.Code list.WebHome]], and in generating a schema for data reporters to validate their [[datasets>>doc:Glossary.Data set.WebHome]] against.
878 878  
879 -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:Glossary.Data structure definition.WebHome]] which restrict values in some [[code lists>>doc:Glossary.Code list.WebHome]], especially where many such subsets restrict the same [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]. Such a view is called a [[Dataflow>>doc:Glossary.Dataflow.WebHome]], and there can be one or more defined for any [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
880 880  
881 -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:Glossary.Data provider.WebHome]], it must conform to a [[Dataflow>>doc:Glossary.Dataflow.WebHome]] (and hence to a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]]). The [[Dataflow>>doc:Glossary.Dataflow.WebHome]] is thus a means of enabling content based processing.
882 882  
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.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:Glossary.Dimension.WebHome]] [[codes>>doc:Glossary.Code.WebHome]] that actually exist in a [[data source>>doc:Glossary.Data source.WebHome]] (these can be used to build relevant selection tables).
884 884  
885 885  === 7.3.2 Data and Metadata Constraints: Schematic ===
886 886  
... ... @@ -896,23 +896,23 @@
896 896  
897 897  Logical class diagram showing inheritance between and reference to constrainable artefacts.
898 898  
899 -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:Glossary.Data provider.WebHome]], Metadata Provider, [[Dataflow>>doc:Glossary.Dataflow.WebHome]], [[Metadataflow>>doc:Glossary.Metadataflow.WebHome]], [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Metadata [[Provision Agreement>>doc:Glossary.Provision agreement.WebHome]], Data Structure.
900 900  
901 -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>>doc:sdmx:Glossary.Constraint.WebHome]](%%) specified. Note that the actual (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]](%%) as submitted is associated to the reference classes defines in the (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]](%%) Attachment. these are used to refer to the classes to which the (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]](%%) applies.
901 +Definition, [[Metadata Structure Definition>>doc:Glossary.Metadata structure definition.WebHome]] are all concrete sub-classes of Constrainable [[Artefact>>doc:Glossary.Artefact.WebHome]] and can therefore have Data (% style="color:#e74c3c" %)[[Constraints>>doc:Glossary.Constraint.WebHome]](%%) specified. Note that the actual (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]](%%) as submitted is associated to the reference classes defines in the (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]](%%) Attachment. these are used to refer to the classes to which the (% style="color:#e74c3c" %)[[Constraint>>doc:Glossary.Constraint.WebHome]](%%) applies.
902 902  
903 -The content of the (% style="color:#e74c3c" %)[[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]](%%) 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>>doc:Glossary.Constraint.WebHome]](%%) can be found in the [[SDMX Information Model>>doc:Glossary.SDMX Information Model.WebHome]] document.
904 904  
905 905  == 7.4 Data Registration ==
906 906  
907 907  === 7.4.1 Basic Concepts ===
908 908  
909 -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:Glossary.Data provider.WebHome]] has published a new [[dataset>>doc:Glossary.Data set.WebHome]] conforming to an existing [[Dataflow>>doc:Glossary.Dataflow.WebHome]] (and hence [[Data Structure Definition>>doc: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:Glossary.Statistical data and metadata exchange.WebHome]] RESTful query with an [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] data stream.
910 910  
911 -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: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:Glossary.Data consumer.WebHome]]. To do this, the [[Data Provider>>doc:Glossary.Data provider.WebHome]] registers the new [[dataset>>doc:Glossary.Data set.WebHome]] with one or more [[SDMX>>doc: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:Glossary.Data provider.WebHome]] and “knows” what [[data flows>>doc:Glossary.Dataflow.WebHome]] the [[data provider>>doc:Glossary.Data provider.WebHome]] has agreed to make available.
912 912  
913 913  The same mechanism can be used to report or make available a metadata set.
914 914  
915 -[[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:Glossary.Statistical data and metadata exchange.WebHome]]-RR supports [[dataset>>doc:Glossary.Data set.WebHome]] registration via the Registration Request, which can be created by the [[Data Provider>>doc:Glossary.Data provider.WebHome]] (giving the [[Data Provider>>doc: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.
916 916  
917 917  === 7.4.2 The Registration Request ===
918 918  
... ... @@ -924,7 +924,7 @@
924 924  
925 925  ==== 7.4.2.2 Registration Request Model ====
926 926  
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.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:Glossary.Data set.WebHome]] to be registered. The Registration can optionally have information, which has been extracted from the Registration:
928 928  
929 929  * validFrom
930 930  * validTo
... ... @@ -932,7 +932,7 @@
932 932  
933 933  The last updated date is useful during the discovery process to make sure the client knows which data is freshest.
934 934  
935 -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:Glossary.Attribute.WebHome]] which takes one of the following values:
936 936  
937 937  (((
938 938  (% style="width:918.835px" %)
... ... @@ -946,15 +946,15 @@
946 946  
947 947  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
948 948  
949 -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:Glossary.Data source.WebHome]], which can understand an API query (i.e., a RESTful query – RESTDatasource) and respond appropriately. Each [[data source>>doc: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.
950 950  
951 -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:Glossary.SDMX-ML.WebHome]] file that is available at a URL.
952 952  
953 -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: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.
954 954  
955 -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:Glossary.Attribute.WebHome]] that state how a SimpleDatasource is to be indexed when registered. The Registry registration process must act as follows:
956 956  
957 -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:Glossary.Data set.WebHome]] is extracted and made available via the availability REST API as documented here:
958 958  
959 959  https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md
960 960  
... ... @@ -961,24 +961,24 @@
961 961  (((
962 962  (% style="width:918.835px" %)
963 963  |**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
964 -|indexTimeSeries|(% style="width:745px" %)Extract all the [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] and create a KeySet(s) Constraint.
965 -|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:Glossary.Series key.WebHome]] and create a KeySet(s) Constraint.
965 +|indexDataSet|(% style="width:745px" %)Extract all the [[codes>>doc:Glossary.Code.WebHome]] and other content of the Key value of the [[Series Key>>doc:Glossary.Series key.WebHome]] in a [[Data Set>>doc:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:Glossary.Member selection.WebHome]] of [[Dimension>>doc:Glossary.Dimension.WebHome]] [[Components>>doc:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)Constraints(%%) model in the [[SDMX-IM>>doc:Glossary.SDMX Information Model.WebHome]], and the associated Selection Value.
966 966  |indexReportingPeriod|(% style="width:745px" %)(((
967 -This applies only to a registered __[[dataset>>doc:sdmx:Glossary.Data set.WebHome]]__.
968 -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:Glossary.Data set.WebHome]]__.
968 +Extract the Reporting Begin and Reporting End from the Header of the Message containing the [[data set>>doc:Glossary.Data set.WebHome]], and create a [[Reference Period>>doc:Glossary.Reference period.WebHome]] constraint.
969 969  )))
970 970  |indexAttributes|(% style="width:745px" %)(((
971 971  **Data Set**
972 -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>>doc:sdmx:Glossary.Constraint.WebHome]](%%) model in the SDMXIM, and the associated Selection Value
972 +Extract the content of the [[Attribute>>doc:Glossary.Attribute.WebHome]] Values in a [[Data Set>>doc:Glossary.Data set.WebHome]] and create one or more Cube Regions containing [[Member Selections>>doc:Glossary.Member selection.WebHome]] of Data [[Attribute>>doc:Glossary.Attribute.WebHome]] [[Components>>doc:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)[[Constraints>>doc:Glossary.Constraint.WebHome]](%%) model in the SDMXIM, and the associated Selection Value
973 973  
974 974  **Metadata Set**
975 -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>>doc:sdmx:Glossary.Constraint.WebHome]](%%) model in the
975 +Indicate the presence of a Reported [[Attribute>>doc:Glossary.Attribute.WebHome]] by creating one or more Cube Regions containing [[Member Selections>>doc:Glossary.Member selection.WebHome]] of Metadata [[Attribute>>doc:Glossary.Attribute.WebHome]] [[Components>>doc:Glossary.Component.WebHome]] of the (% style="color:#e74c3c" %)[[Constraints>>doc:Glossary.Constraint.WebHome]](%%) model in the
976 976  )))
977 977  |**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
978 -| |(% 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:Glossary.SDMX Information Model.WebHome]]. Note that the content is not stored in the Selection Value.
979 979  )))
980 980  
981 -(% style="color:#e74c3c" %)[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
981 +(% style="color:#e74c3c" %)[[Constraints>>doc:Glossary.Constraint.WebHome]](%%) that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
982 982  
983 983  The Registration must reference the ProvisionAgreement to which it relates.
984 984  
... ... @@ -986,9 +986,9 @@
986 986  
987 987  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”.
988 988  
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.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:Glossary.Data set.WebHome]] or query service.
990 990  
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.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:Glossary.Data set.WebHome]], that the response will contain some successful and some failed statuses. The logical model for the RegistrationResponse is shown below:
992 992  
993 993  [[image:SDMX 3.1 Section 5_en_cdba03b5.jpg||height="371" width="579"]]
994 994  
... ... @@ -996,11 +996,11 @@
996 996  
997 997  == 7.5 Subscription and Notification Service ==
998 998  
999 -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:Glossary.SDMX Registry.WebHome]]/Repository will change regularly: new [[code lists>>doc:Glossary.Code list.WebHome]] and key families will be published and new [[datasets>>doc: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.
1000 1000  
1001 -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: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:Glossary.Notification.WebHome]] of qualifying events will be delivered. The [[subscription>>doc:Glossary.Subscription.WebHome]] will be identified in the registry by a URN, which is returned to the user when the [[subscription>>doc:Glossary.Subscription.WebHome]] is created. If the user wants to delete the [[subscription>>doc:Glossary.Subscription.WebHome]] at a later point, the [[subscription>>doc:Glossary.Subscription.WebHome]] URN is used as identification. [[Subscriptions>>doc:Glossary.Subscription.WebHome]] have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired [[subscriptions>>doc:Glossary.Subscription.WebHome]], and will notify the subscriber on expiry.
1002 1002  
1003 -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:Glossary.Artefact.WebHome]] is modified, any [[subscriptions>>doc: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:Glossary.Subscription.WebHome]]. This is called a “[[notification>>doc:Glossary.Notification.WebHome]]”.
1004 1004  
1005 1005  === 7.5.1 Subscription Logical Class Diagram ===
1006 1006  
... ... @@ -1010,18 +1010,18 @@
1010 1010  
1011 1011  === 7.5.2 Subscription Information ===
1012 1012  
1013 -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:Glossary.Subscription.WebHome]] always contains:
1014 1014  
1015 -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.
1016 -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.
1017 -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:Glossary.Notification.WebHome]] must be sent if the [[subscription>>doc:Glossary.Subscription.WebHome]] is activated. The URIs can be either mailto~: or http: protocol. In the former case an email [[notification>>doc:Glossary.Notification.WebHome]] is sent; in the latter an HTTP POST [[notification>>doc:Glossary.Notification.WebHome]] is sent.
1016 +1. A user-defined identifier, which is returned in the response to the [[subscription>>doc:Glossary.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:Glossary.Subscription.WebHome]] becomes active and expires. The subscriber may be sent a [[notification>>doc:Glossary.Notification.WebHome]] on expiration of the [[subscription>>doc:Glossary.Subscription.WebHome]].
1018 1018  1. A selector which specifies which type of events are of interest. The set of event types is:
1019 1019  
1020 1020  (% style="width:1061.83px" %)
1021 1021  |**Event Type**|(% style="width:660px" %)**Comment**
1022 -|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.
1023 -|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.
1024 -|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.
1022 +|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to [[Maintainable Artefacts>>doc:Glossary.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository.
1023 +|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published [[dataset>>doc:Glossary.Data set.WebHome]] is registered. This can be either a SDMXML data file or an [[SDMX>>doc:Glossary.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:Glossary.Reference metadata.WebHome]] file or an [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] conformant database.
1025 1025  |ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType
1026 1026  
1027 1027  === 7.5.3 Wildcard Facility ===
... ... @@ -1074,20 +1074,20 @@
1074 1074  
1075 1075  === 7.5.4 Structural Repository Events ===
1076 1076  
1077 -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:Glossary.Maintainable artefact.WebHome]] ([[data structure definition>>doc:Glossary.Data structure definition.WebHome]], [[concept scheme>>doc:Glossary.Concept scheme.WebHome]], codelist, [[metadata structure definition>>doc:Glossary.Metadata structure definition.WebHome]], [[category scheme>>doc:Glossary.Category scheme.WebHome]], etc.) is added to, deleted from, or modified in the [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] repository, a [[structural metadata>>doc:Glossary.Structural metadata.WebHome]] event is triggered. [[Subscriptions>>doc:Glossary.Subscription.WebHome]] may be set up to monitor all such events, or focus on specific [[artefacts>>doc:Glossary.Artefact.WebHome]] such as a [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]].
1078 1078  
1079 1079  === 7.5.5 Registration Events ===
1080 1080  
1081 -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:Glossary.Data set.WebHome]] or metadata-set is registered a registration event is created. A [[subscription>>doc:Glossary.Subscription.WebHome]] may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below:
1082 1082  
1083 1083  (((
1084 1084  (% style="width:1082.83px" %)
1085 1085  |(% style="width:230px" %)**Selector**|(% style="width:850px" %)**Comment**
1086 -|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] registered by the specified dataprovider will activate the notification.
1087 -|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] for the agreement will activate the notification.
1088 -|(% 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.
1089 -|(% 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
1090 -|(% 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.
1086 +|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] registered by the specified dataprovider will activate the notification.
1087 +|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] for the agreement will activate the notification.
1088 +|(% style="width:230px" %)[[Dataflow>>doc:Glossary.Dataflow.WebHome]]|(% style="width:850px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] for the specified [[dataflow>>doc:Glossary.Dataflow.WebHome]] will activate the notification.
1089 +|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] for those [[dataflows>>doc:Glossary.Dataflow.WebHome]] that are based on the specified [[Data Structure Definition>>doc:Glossary.Data structure definition.WebHome]] will activate the notification
1090 +|(% style="width:230px" %)Category|(% style="width:850px" %)Any [[datasets>>doc:Glossary.Data set.WebHome]] registered for those [[dataflows>>doc:Glossary.Dataflow.WebHome]], [[provision agreements>>doc:Glossary.Provision agreement.WebHome]] that are categorised by the category.
1091 1091  )))
1092 1092  
1093 1093  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
... ... @@ -1100,24 +1100,24 @@
1100 1100  
1101 1101  **Figure 20: Logical Class Diagram of the Notification**
1102 1102  
1103 -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:Glossary.Notification.WebHome]] is an XML document that is sent to a user via email or http POST whenever a [[subscription>>doc:Glossary.Subscription.WebHome]] is activated. It is an asynchronous one-way message.
1104 1104  
1105 -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:Glossary.Component.WebHome]] that caused the event to be triggered, the following common information is in the message:
1106 1106  
1107 1107  * Date and time that the event occurred
1108 -* The URN of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that caused the event
1109 -* 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:Glossary.Artefact.WebHome]] that caused the event
1109 +* The URN of the [[Subscription>>doc:Glossary.Subscription.WebHome]] that produced the [[notification>>doc:Glossary.Notification.WebHome]]
1110 1110  * Event Action: Add, Replace, or Delete.
1111 1111  
1112 -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:Glossary.Notification.WebHome]] as detailed below.
1113 1113  
1114 1114  === 7.6.2 Structural Event Component ===
1115 1115  
1116 -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:Glossary.Notification.WebHome]] will contain the MaintainableArtefact that triggered the event in a form similar to the [[SDMX-ML>>doc:Glossary.SDMX-ML.WebHome]] structural message (using elements from that namespace).
1117 1117  
1118 1118  === 7.6.3 Registration Event Component ===
1119 1119  
1120 -The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will contain the Registration.
1120 +The [[notification>>doc:Glossary.Notification.WebHome]] will contain the Registration.
1121 1121  
1122 1122  ----
1123 1123  
© Semantic R&D Group, 2026