Wiki source code of SDMX 2.1 Standards. Section 5. Registry Specification: Logical Interfaces

Last modified by Helena on 2025/09/10 11:19

version	line-number	content
1.1	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
	4
	5	Revision History
	6
3.4	7	(% style="width:833.294px" %)
	8	\|(% style="width:122px" %)Revision\|(% style="width:126px" %)Date\|(% style="width:581px" %)Contents
	9	\|(% style="width:122px" %) \|(% style="width:126px" %)April 2011\|(% style="width:581px" %)Initial release
	10	\|(% style="width:122px" %)1.0\|(% style="width:126px" %)July 2011\|(% style="width:581px" %)Rectification of problems of the specifications dated April 2011
	11	\|(% style="width:122px" %)2.0\|(% style="width:126px" %)July 2020\|(% style="width:581px" %)Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
1.1	12
	13	Corrigendum
	14
	15	The following problems with the specification dated April 2011 have been rectified as described below.
	16
16.1	17	~1. Problem
1.1	18
16.1	19	Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] as it was identified in version 2.0, and not as it is identified in version 2.1.
1.1	20
	21	Rectification
	22
16.1	23	[[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] is a [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] at version 2.1 and so the relationship is shown directly to the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] class and not indirectly to the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] via a ProvisionAgreementRef class.
1.1	24
	25	~1. Problem
	26
14.2	27	Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Registration class without the indexAttributes [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
1.1	28
	29	Rectification
	30
14.2	31	The [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] indexAttribute [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is added to the Registration class and a description is of its purpose is given in the table at line 916.
1.1	32
	33	2. Problem
	34
	35	Lines 437 and 648 of the April 2011 document mention that the fixed id for an AgencyScheme is AGENCY_SCHEME whereas it should be AGENCIES. Rectification
	36
	37	The reference to AGENCY_SCHEME is changed to AGENCIES.
	38
14.2	39	Adoption of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] in 2020
1.1	40
14.2	41	The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] specifications dated July 2011 envisaged the adoption of a language aimed at defining algorithms for the derivation of the data and presented a basic framework requiring however further elaboration for its actual use.
1.1	42
16.1	43	Following the adoption of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] ([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]]) version 2.0 and its application to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] 2.1, this section of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] specifications has been integrated by introducing the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] package, [[maintainable artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]], [[nameable artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]] to the sections 5.2.3, 6.2.2, 6.2.3, 6.2.4 and 7.1.1.
1.1	44
	45	= 1 Introduction =
	46
15.1	47	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:
1.1	48
15.1	49	* the availability of an abstract information model capable of supporting timeseries and cross-sectional data, [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]], and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-IM)
	50	* standardised XML schemas derived from the model ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-ML)
1.1	51	* the use of web-services technology (XML, XSD, WSDL, WADL)
	52
15.1	53	Such an architecture needs to be well organised, and the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]]/Repository ([[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR) 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 datasharing vision.
1.1	54
15.1	55	However, it is important to emphasis 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.
1.1	56
15.1	57	Standard formats for the exchange of aggregated statistical data and metadata as prescribed in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] v2.1 are envisaged to bring benefits to the statistical community because data reporting and dissemination processes can be made more efficient.
1.1	58
15.1	59	As organisations migrate to [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] enabled systems, many XML (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 [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] definitions (often collectively called [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]), XML schemas generated from data and [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], XSLT style-sheets 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.
1.1	60
	61	This is the role of the registry.
	62
15.1	63	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.
1.1	64
15.1	65	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:
1.1	66
15.1	67	* [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository
1.1	68	* data and metadata registration
	69	* query
	70
15.1	71	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.
1.1	72
	73	= 2 Scope and Normative Status =
	74
15.1	75	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.
1.1	76
	77	In this document, functions and behaviours of the Registry Interfaces are described in four ways:
	78
	79	* in text
	80	* with tables
15.1	81	* 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]])
	82	* 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 diagram are clearly marked as “Logical Class Diagram ...”)
1.1	83
	84	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.
	85
15.1	86	Note that sections 5 and 6 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 (Part 03 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standard). All other sections of this document are informative.
1.1	87
15.1	88	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.
1.1	89
	90	= 3 Scope of the SDMX Registry/Repository =
	91
	92	== 3.1 Objective ==
	93
15.1	94	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:
1.1	95
15.1	96	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.
	97	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]].
1.1	98
	99	== 3.2 Structural Metadata ==
	100
15.1	101	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]]:
1.1	102
15.1	103	* 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
	104	* 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”
	105	* 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 [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] and presentational arrangement of a Metadataset and their valid values and content
	106	* if required, defining a subset or view of a [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which allows some restriction of content called a “[[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] definition”
	107	* 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]] Definitions to enable browsing
	108	* defining one or more lists of [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] (which includes metadata providers)
	109	* defining which [[Data Providers>>doc:sdmx:Glossary.Data provider.WebHome]] have agreed to publish a given [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] and/or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition - this is called a [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	110
	111	[[image:1747824122996-812.jpeg]]
	112
	113	Figure 1: Schematic of the Basic Structural Artifacts in the SDMX-IM
	114
	115	== 3.3 Registration ==
	116
15.1	117	Publishing the data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] involves the following steps for a [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]:
1.1	118
15.1	119	* making the [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and data available in [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] conformant data files or databases (which respond to an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] query with [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data). The data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] files or databases must be webaccessible, and must conform to an agreed [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] subset)
	120	* registering the existence of published [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] and data files or databases with one or more [[SDMX registries>>doc:sdmx:Glossary.SDMX Registry.WebHome]]
1.1	121
	122	[[image:1747824123003-199.jpeg]]
	123
	124	Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM
	125
	126	== 3.4 Notification ==
	127
15.1	128	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:
1.1	129
15.1	130	* 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
1.1	131
	132	== 3.5 Discovery ==
	133
15.1	134	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:
1.1	135
15.1	136	* optionally browsing a subject matter domain [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] to find [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definitions (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
	137	* 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
	138	* processing the query result set and retrieving data and/or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] from the supplied URLs
1.1	139
	140	[[image:1747824123006-476.jpeg]]
	141
	142	Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM
	143
	144	= 4 SDMX Registry/Repository Architecture =
	145
	146	== 4.1 Architectural Schematic ==
	147
15.1	148	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.
1.1	149
	150	[[image:1747824123008-995.jpeg]]
	151
	152	Figure 4: Schematic of the Registry Content and Services
	153
	154	== 4.2 Structural Metadata Repository ==
	155
15.1	156	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.
1.1	157
15.1	158	Note that the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Submit Structure Request message 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 supported by the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Submit Structure Request are::
1.1	159
	160	* Registration of data and metadata sources
	161	* Subscription and Notification
	162
15.1	163	Separate registry-based messages are defined to support these [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]].
1.1	164
	165	== 4.3 Provisioning Metadata Repository ==
	166
15.1	167	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 provider>>doc:sdmx:Glossary.Data provider.WebHome]], 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 Agreement.
1.1	168
	169	This layer is supported by the Data and Metadata Registration Service.
	170
	171	= 5 Registry Interfaces and Services =
	172
	173	== 5.1 Registry Interfaces ==
	174
	175	The Registry Interfaces are:
	176
	177	* Notify Registry Event
15.1	178	* Submit [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Request
	179	* Submit [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Response
1.1	180	* Submit Registration Request
	181	* Submit Registration Response
	182	* Query Registration Request
	183	* Query Registration Response
15.1	184	* Query [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Request
	185	* Query [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] Response
1.1	186	* Submit Structure Request
	187	* Submit Structure Response
	188
	189	The registry interfaces are invoked in one of two ways:
	190
15.1	191	1. The interface is the name of the root node of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] document
	192	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.
1.1	193
15.1	194	In addition to these interfaces the registry must support a mechanism for querying for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This is detailed in 5.2.2.
1.1	195
15.1	196	All these interactions with the Registry – with the exception of Notify Registry Event – 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.
1.1	197
15.1	198	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 request-response pattern, because it is inherently asynchronous.
1.1	199
	200	== 5.2 Registry Services ==
	201
	202	=== 5.2.1 Introduction ===
	203
	204	The services described in this section do not imply that each is implemented as a discrete web service.
	205
	206	=== 5.2.2 Structure Submission and Query Service ===
	207
15.1	208	This service must implement the following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Interfaces:
1.1	209
	210	* SubmitStructureRequest
	211	* SubmitStructureResponse
	212
15.1	213	These interfaces allow structural definitions to be created, modified, and removed in a controlled fashion. It also allows the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] to be queried and retrieved either in part or as a whole. 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 (see next section on the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Information Model).
1.1	214
	215	=== 5.2.3 Structure Query Service ===
	216
15.1	217	The registry must support a mechanism for querying for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. This mechanism can be one or both of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message and 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 Part 7 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] standards). The registry response to both of these query mechanisms is the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Structure message which has as its root node
1.1	218
	219	* Structure
	220
15.1	221	The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] structural [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] that may be queried are:
1.1	222
15.1	223	* [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] and metadataflows
	224	* [[data structure definitions>>doc:sdmx:Glossary.Data structure definition.WebHome]] and [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
1.1	225	* codelists
15.1	226	* [[concept>>doc:sdmx:Glossary.Concept.WebHome]] schemes
1.1	227	* reporting taxonomies
15.1	228	* [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]]
1.1	229	* structure sets
	230	* processes
	231	* hierarchical code lists
15.1	232	* [[constraints>>doc:sdmx:Glossary.Constraint.WebHome]]
1.1	233	* category schemes
15.1	234	* categorisations and categorised objects (examples are categorised [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] and metadatflows, [[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]] registered [[data sources>>doc:sdmx:Glossary.Data source.WebHome]] and metadata sources)
	235	* organisation schemes ([[agency scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]], [[data provider scheme>>doc:sdmx:Glossary.Data provider scheme.WebHome]], [[data consumer scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]], organisation unit scheme)
1.1	236
15.1	237	Due to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] implementation the other structural [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that may be queried are:
1.1	238
	239	* transformation schemes
	240	* custom type schemes
	241	* name personalisation schemes
15.1	242	* [[vtl>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes
1.1	243	* ruleset schemes
	244	* user defined operator schemes
	245
15.1	246	The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] query messages that are a part of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message are:
1.1	247
	248	* StructuresQuery
	249	* DataflowQuery
	250	* MetadataflowQuery
	251	* DataStructureQuery
	252	* MetadataStructureQuery
	253	* CategorySchemeQuery
	254	* ConceptScheneQuery
	255	* CodelistQuery
	256	* HierarchicalCodelistQuery
	257	* OrganisationSchemeQuery
	258	* ReportingTaxonomyQuery
	259	* StructureSetQuery
	260	* ProcessQuery
	261	* CategorisationQuery
	262	* ProvisionAgreementQuery
	263	* ConstraintQuery
	264
15.1	265	Due to the [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] implementation the other query messages that became a part of the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query message are:
1.1	266
	267	* TransformationSchemeQuery
	268	* CustomTypeSchemeQuery
	269	* VtlMappingSchemeQuery
	270	* NamePersonalisationSchemeQuery
	271	* RulesetSchemeQuery
	272	* UserDefinedOperatorSchemeQuery
	273
	274	=== 5.2.4 Data and Reference Metadata Registration Service ===
	275
15.1	276	This service must implement the following [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Interfaces:
1.1	277
	278	* SubmitRegistrationRequest
	279	* SubmitRegistrationResponse
	280	* QueryRegistrationRequest
	281	* QueryRegistrationResponse
	282
15.1	283	The Data and Metadata Registration Service allows [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant XML 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 data-sets or metadata-sets, and MAY extract a concise [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the contents in terms of [[concept>>doc:sdmx:Glossary.Concept.WebHome]] 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 data-set or metadata-set. These are called [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-IM.
1.1	284
	285	The Data and Metadata Registration Service MAY validate the following, subject to the access control mechanism implemented in the Registry:
	286
15.1	287	* that the [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] is allowed to register the data-set or metadata-set
	288	* that the content of the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] meets the validation [[constraints>>doc:sdmx:Glossary.Constraint.WebHome]]. This is dependent upon such [[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]], [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], Provision Agreement
	289	* 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
	290	* that a simple [[data source>>doc:sdmx:Glossary.Data source.WebHome]] exists (i.e. a file accessible at a URL)
	291	* that the correct [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] is used by the registered data 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]], Identifier [[Components>>doc:sdmx:Glossary.Component.WebHome]] etc.) are consistent with the [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
	292	* that the valid [[representations>>doc:sdmx:Glossary.Representation.WebHome]] of the [[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]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
1.1	293
15.1	294	The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values:
1.1	295
17.1	296	\|(% style="width:219px" %)Action Attribute Value\|(% style="width:1652px" %)Behaviour
3.6	297	\|(% style="width:219px" %)Append\|(% style="width:1652px" %)Add this registration to the registry
	298	\|(% style="width:219px" %)Replace\|(% style="width:1652px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
	299	\|(% style="width:219px" %)Delete\|(% style="width:1652px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
	300
15.1	301	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 [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]] indexing application must index the [[Datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]] upon registration. The indexing application behaviour is as follows:
3.6	302
17.1	303	\|(% style="width:228px" %)Boolean Attribute\|(% style="width:1644px" %)Behaviour if Value is “true”
15.1	304	\|(% style="width:228px" %)indexTimeSeries\|(% style="width:1644px" %)A compliant indexing application must index all the time [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] (for a [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] registration) or metadata target values (for a [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]] registration)
	305	\|(% style="width:228px" %)indexDataSet\|(% style="width:1644px" %)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]] (for a [[Dataset>>doc:sdmx:Glossary.Data set.WebHome]] registration) or the range of actual (present) values for each Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes an enumerated value.
	306	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]]
	307	\|(% style="width:228px" %)indexReportingPeriod\|(% style="width:1644px" %)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]] or [[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]
1.1	308
	309	=== 5.2.5 Data and Reference Metadata Discovery ===
	310
	311	The Data and Metadata Discovery Service implements the following Registry Interfaces:
	312
1.3	313	* QueryRegistrationRequest
	314	* QueryRegistrationResponse
1.1	315
	316	=== 5.2.6 Subscription and Notification ===
	317
15.1	318	The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] and [[Notification>>doc:sdmx:Glossary.Notification.WebHome]] Service implements the following Registry Interfaces:
1.1	319
	320	* SubmitSubscriptionRequest
	321	* SubmitSubscriptionResponse
	322	* NotifyRegistryEvent
	323
15.1	324	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]], [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] or [[Metadata Structure Definition>>doc:sdmx:Glossary.Metadata structure definition.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]].
1.1	325
15.1	326	[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] management involves a user submitting a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request which contains:
1.1	327
15.1	328	* a query or [[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>>doc:sdmx:Glossary.Data structure definition.WebHome]]).
	329	* a list of URIs or end-points to which an XML [[notification>>doc:sdmx:Glossary.Notification.WebHome]] message can be sent. Supported end-point types will be email (mailto : ) and HTTP POST (a normal http:~/~/ address)
1.1	330	* request for a list of submitted subscriptions
15.1	331	* deletion of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]
1.1	332
15.1	333	[[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-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document to the end-points specified in the relevant subscriptions.
1.1	334
	335	=== 5.2.7 Registry Behaviour ===
	336
15.1	337	The following table defines the behaviour of the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] for the various Registry Interface messages.
1.1	338
3.3	339	\|(% style="width:227px" %)Interface\|(% style="width:1644px" %)Behaviour
	340	\|(% style="width:227px" %)All\|(% style="width:1644px" %)(((
15.1	341	1) If the action is set to “replace” then the entire contents of the existing maintainable object in the Registry MUST be replaced by the object submitted, unless the final [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is set to “true” in which case the only changes that are allowed are to the following constructs:
1.1	342
15.1	343	* Name – this applies to the Maintainable object and its contained elements, such a [[Code>>doc:sdmx:Glossary.Code.WebHome]] in a [[Code list>>doc:sdmx:Glossary.Code list.WebHome]].
	344	* Description - this applies to the Maintainable object and its contained elements, such a [[Code>>doc:sdmx:Glossary.Code.WebHome]] in a [[Code list>>doc:sdmx:Glossary.Code list.WebHome]].
	345	* Annotation - this applies to the Maintainable object and its contained elements, such a [[Code>>doc:sdmx:Glossary.Code.WebHome]] in a [[Code list>>doc:sdmx:Glossary.Code list.WebHome]].
1.1	346	* validTo
	347	* validFrom
	348	* structureURL
	349	* serviceURL
	350	* uri
	351	* isExternalReference
	352
1.4	353	2) 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.
	354	3) If the action is set to “delete” then the Registry MUST verify that the object can deleted. In order to qualify for deletion the object must:
1.1	355
15.1	356	а) Not have the final [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] set to “true”
1.4	357	b) Not be referenced from any other object in the Registry.
1.1	358
15.1	359	4) The [[version>>doc:sdmx:Glossary.Version.WebHome]] rules in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Schema documentation MUST be obeyed.
	360	5) The specific rules for the elements and [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] documented in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Schema MUST be obeyed.
1.1	361	)))
15.1	362	\|(% style="width:227px" %)SubmitStructureRequest\|(% style="width:1644px" %)Structures are submitted at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] and the behaviour in “All” above is therefore at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
3.3	363	\|(% style="width:227px" %)SubmitProvisioningRequest\|(% style="width:1644px" %)No additional behaviour.
	364	\|(% style="width:227px" %)Submit Registration Request\|(% style="width:1644px" %)(((
15.1	365	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.
	366	For a queryable datasource the Registry MAY validate that the source exists and can accept an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data query.
1.1	367	)))
	368
	369	= 6 Identification of SDMX Objects =
	370
	371	== 6.1 Identification, Versioning, and Maintenance ==
	372
15.1	373	All major classes of the [[SDMX Information model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] inherit from one of:
1.1	374
	375	* 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.
	376	* NamableArtefact - this has all of the features of IdentifiableArtefact plus the ability to have a multi-lingual name and description,
15.1	377	* VersionableArtefact – this has all of the above features plus a [[version>>doc:sdmx:Glossary.Version.WebHome]] number and a validity period.
	378	* MaintainableArtefact – this has all of the above features, and indication as to whether the object is “final” and cannot be changed or deleted, registry and structure URIs, plus an association to the [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] of the object.
1.1	379
	380	=== 6.1.1 Identification, Naming, Versioning, and Maintenance Model ===
	381
1.6	382	[[image:1747824504225-229.png]]
	383
1.1	384	Figure 5: Class diagram of fundamental artefacts in the SDMX-IM
	385
15.1	386	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:
1.1	387
	388	* Annotable
	389	* Identifiable
	390	* Nameable
	391	* Versionable
	392	* Maintainable
	393
1.6	394	(% style="width:935.294px" %)
17.1	395	\|Object Type\|(% style="width:244px" %)Data Attributes\|(% style="width:99px" %)Status\|Data type\|(% style="width:389px" %)Notes
1.6	396	\|Annotable\|(% style="width:244px" %)AnnotationTitle\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)
	397	\| \|(% style="width:244px" %)AnnotationType\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)
	398	\| \|(% style="width:244px" %)AnnotationURN\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)
	399	\| \|(% style="width:244px" %)(((
15.1	400	AnnotationText in the form of [[International String>>doc:sdmx:Glossary.International string.WebHome]]
1.6	401	)))\|(% style="width:99px" %)C\| \|(% style="width:389px" %)This can have languagespecific variants.
	402	\|Identifiable\|(% style="width:244px" %)all content as for Annotable plus\|(% style="width:99px" %) \| \|(% style="width:389px" %)
	403	\| \|(% style="width:244px" %)id\|(% style="width:99px" %)M\|string\|(% style="width:389px" %)
	404	\| \|(% style="width:244px" %)uri\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)
	405	\| \|(% style="width:244px" %)urn\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)Although the urn is computable and therefore may not be submitted or stored physically, the Registry must return the urn for each object, and must be able to service a query on an object referenced solely by its urn.
	406	\|Nameable\|(% style="width:244px" %)all content as for Identifiable plus\|(% style="width:99px" %) \| \|(% style="width:389px" %)
15.1	407	\| \|(% style="width:244px" %)Name in the form of [[International String>>doc:sdmx:Glossary.International string.WebHome]]\|(% style="width:99px" %)M\|string\|(% style="width:389px" %)This can have languagespecific variants.
1.6	408	\| \|(% style="width:244px" %)(((
15.1	409	Description in the form of [[International String>>doc:sdmx:Glossary.International string.WebHome]]
1.6	410	)))\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)This can have languagespecific variants.
	411	\|Versionable\|(% style="width:244px" %)All content as for Identifiable plus\|(% style="width:99px" %) \| \|(% style="width:389px" %)
15.1	412	\| \|(% style="width:244px" %)[[version>>doc:sdmx:Glossary.Version.WebHome]]\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)This is the [[version>>doc:sdmx:Glossary.Version.WebHome]] number. If not present the default is 1.0
1.6	413	\| \|(% style="width:244px" %)validFrom\|(% style="width:99px" %)C\|Date/time\|(% style="width:389px" %)
	414	\| \|(% style="width:244px" %)validTo\|(% style="width:99px" %)C\|Date/time\|(% style="width:389px" %)
	415	\|Maintainable\|(% style="width:244px" %)All content as for Versionable plus\|(% style="width:99px" %) \| \|(% style="width:389px" %)
15.1	416	\| \|(% style="width:244px" %)final\|(% style="width:99px" %) \|boolean\|(% style="width:389px" %)Value of “true” indicates that this is a final specification and it cannot be changed except as a new [[version>>doc:sdmx:Glossary.Version.WebHome]]. Note that providing a “final’ object is not referenced from another object then it may be deleted.
	417	\| \|(% style="width:244px" %)isExternalReference\|(% style="width:99px" %)C\|boolean\|(% style="width:389px" %)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 structureURI, each of which must return a valid [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file.
1.6	418	\| \|(% style="width:244px" %)serviceURL\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)The url of the service that can be queried for this resource
	419	\| \|(% style="width:244px" %)structureURL\|(% style="width:99px" %)C\|string\|(% style="width:389px" %)The url of the resource.
15.1	420	\| \|(% style="width:244px" %)(Maintenance) agencyId\|(% style="width:99px" %)M\|string\|(% style="width:389px" %)The object must be linked to a [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]].
1.1	421
17.1	422	Table 1: Common Attributes of Object Types
1.1	423
	424	== 6.2 Unique identification of SDMX objects ==
	425
	426	=== 6.2.1 Agencies ===
	427
15.1	428	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.
1.1	429
9.2	430	[[image:1747994320263-112.png]]
	431
16.1	432	Figure 6: Agency Scheme Model
1.1	433
15.1	434	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 n-[[level>>doc:sdmx:Glossary.Level.WebHome]] structure. The top [[level>>doc:sdmx:Glossary.Level.WebHome]] of this structure is maintained by [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. Any Agency in this top [[level>>doc:sdmx:Glossary.Level.WebHome]] 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>>doc:sdmx:Glossary.Version.WebHome]] and is never declared explicitly in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] object identification mechanism.
1.1	435
15.1	436	In order to achieve this [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] adopts the following rules:
1.1	437
15.1	438	1. Agencies are maintained in an [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]] (which is a sub class of Organisation Scheme)
	439	1. 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]].
	440	1. The “top-[[level>>doc:sdmx:Glossary.Level.WebHome]]” agency is [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and maintains the “top-[[level>>doc:sdmx:Glossary.Level.WebHome]]” [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
	441	1. Agencies registered in the top-[[level>>doc:sdmx:Glossary.Level.WebHome]] 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.
	442	1. The AgencyScheme cannot be versioned and so take a default [[version>>doc:sdmx:Glossary.Version.WebHome]] number of 1.0 and cannot be made “final”.
1.1	443	1. There can be only one AgencyScheme maintained by any one Agency. It has a fixed Id of AGENCIES.
15.1	444	1. The /hierarchy 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.
	445	1. The format of the agency identifier is agencyID.agencyID etc. The toplevel 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-[[level>>doc:sdmx:Glossary.Level.WebHome]] [[Agency Scheme>>doc:sdmx:Glossary.Agency scheme.WebHome]].
1.1	446
	447	This supports a hierarchical structure of agencyID.
	448
	449	An example is shown below.
	450
	451	[[image:1747824123012-527.jpeg]]
	452
9.3	453	Figure 7: Example of Hierarchic Structure of Agencies
1.1	454
	455	The following organizations maintain an Agency Scheme.
	456
	457	* SDMX – contains Agencies AA, BB
	458	* AA – contains Agencies CC, DD
	459	* BB – contains Agencies CC, DD
	460	* DD – Contains Agency EE
	461
15.1	462	Each agency is identified by its full [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]] excluding SDMX.
1.1	463
	464	e.g. the id of EE as an agencyID is AA.DD.EE
	465
	466	An example of this is shown in the XML snippet below.
	467
7.1	468	[[image:1747832400104-286.png]]
1.1	469
2.1	470	Figure 8: Example Showing Use of Agency Identifiers
1.1	471
15.1	472	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.
1.1	473
	474	=== 6.2.2 Universal Resource Name (URN) ===
	475
	476	==== 6.2.2.1 Introduction ====
	477
15.1	478	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, [[version>>doc:sdmx:Glossary.Version.WebHome]] etc.).
1.1	479
	480	==== 6.2.2.2 URN Structure ====
	481
9.1	482	(% class="wikigeneratedid" id="HCaseRulesforURN" %)
	483	//Case Rules for URN//
1.1	484
	485	For the URN, all parts of the string are case sensitive. The Id of any object must be UPPER CASE. Therefore, CRED_ext_Debt is invalid and it should be CRED_EXT_DEBT.
	486
	487	The generic structure of the URN is as follows:
	488
3.3	489	>SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobject-id(maintainedobject-version).*containerobject-id.object-id
1.1	490
	491	~* this can repeat and may not be present (see explanation below)
	492
16.1	493	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 version information that is allowed is for the maintainable object.
1.1	494
15.1	495	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(.).
1.1	496
	497	==== 6.2.2.3 Explanation of the generic structure ====
	498
	499	In the explanation below the actual object that is the target of the URN is called the //actual object//.
	500
3.2	501	SDMXPrefix: urn:sdmx:org.
1.1	502
	503	SDMX-IM package name: sdmx.infomodel.package=
	504
	505	[[image:1747824123016-678.png]]
	506
	507	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.
	508
15.1	509	(maintainable-object-version) is the [[version>>doc:sdmx:Glossary.Version.WebHome]] of the maintainable object and is enclosed in round brackets (). It will always be present.
1.1	510
15.1	511	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 ([[Code List>>doc:sdmx:Glossary.Code list.WebHome]]) and has no intermediary container object, whereas a Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has an intermediary container object (Report Structure) and may have an intermediary container object which is its parent Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]. For this reason the container object id may repeat, with each repetition identifying the object at the next-lower [[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 [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor, [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor, and [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Descriptor 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 [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Descriptor, [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] Descriptor, and [[Measure>>doc:sdmx:Glossary.Measure.WebHome]] Descriptor is not included when the actual object is a Data [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] or a [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]/[[Measure>>doc:sdmx:Glossary.Measure.WebHome]] [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]/ Time [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]], or a [[Measure>>doc:sdmx:Glossary.Measure.WebHome]].
1.1	512
15.1	513	Note that although a [[Code>>doc:sdmx:Glossary.Code.WebHome]] can have a parent [[Code>>doc:sdmx:Glossary.Code.WebHome]] and a [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] can have a parent [[Concept>>doc:sdmx:Glossary.Concept.WebHome]] these are maintained in a flat structure and therefore do not have a container-object-id.
1.1	514
15.1	515	For example the sequence is agency:DSDid([[version>>doc:sdmx:Glossary.Version.WebHome]]).DimensionId and not agency:DSDid([[version>>doc:sdmx:Glossary.Version.WebHome]]).DimensionDescriptorId.DimensionId.
1.1	516
	517	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.
	518
2.2	519	===== __//Generic Examples of the URN Structure//__ =====
1.1	520
2.2	521	__Actual object is a maintainable__
1.1	522
2.5	523	> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version)
1.1	524
2.2	525	__Actual object is contained in a maintained object with no intermediate containing object__
1.1	526
2.5	527	> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).object-id
1.1	528
2.2	529	__Actual object is contained in a maintained object with an intermediate containing object__
1.1	530
2.5	531	> SDMXPrefix.SDMX-IM package name.classname=agency
1.1	532
	533	id:maintained-object-id(version).contained-object-id.object-id
	534
2.2	535	__Actual object is contained in a maintained object with no intermediate containing object but the object type itself is hierarchical__
1.1	536
15.1	537	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 [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]. 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 [[Category Scheme>>doc:sdmx:Glossary.Category scheme.WebHome]]/[[Category>>doc:sdmx:Glossary.Category.WebHome]]/[[Category>>doc:sdmx:Glossary.Category.WebHome]]
1.1	538
2.5	539	> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id.object-id
1.1	540
2.3	541	__Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical__
1.1	542
15.1	543	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 Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] where the contained objects are Report Structure (first contained object id) and Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] (subsequent contained object Ids). The example below shows the generic structure for [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]/Report Structure/Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]/Metadata [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]
1.1	544
2.5	545	> SDMXPrefix.SDMX-IM package name.classname=agency id:maintained-object-id(version).contained-object-id. contained-object-id contained-object-id.object-id
1.1	546
2.4	547	===== __//Concrete Examples of the URN Structure//__ =====
1.1	548
15.1	549	The [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] CRED_EXT_DEBT version 1.0 maintained by the top level Agency TFFS would have the URN:
1.1	550
2.5	551	> urn:sdmx:org.sdmx.infomodel.datastructure.DataStucture=TFFS:CRED_EXT_ DEBT(1.0)
1.1	552
15.1	553	The URN for a [[code>>doc:sdmx:Glossary.Code.WebHome]] for Argentina maintained by ISO in the code list CL_3166A2 version 1.0 would be:
1.1	554
2.5	555	> urn:sdmx:org.sdmx.infomodel.codelist.Code=ISO:CL_3166A2(1.0).AR
1.1	556
15.1	557	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 version 1.0 would be:
1.1	558
2.5	559	> urn:sdmx:org.sdmx.infomodel.categoryscheme.Category=SDMX:SUBJE CT_MATTER_DOMAINS(1.0).1.2
1.1	560
15.1	561	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 [[version>>doc:sdmx:Glossary.Version.WebHome]] 1.0 in the Report Structure CONTACT_REPORT where the hierarchy of the Metadata Attribute is
1.1	562
	563	CONTACT_DETAILS/CONTACT_NAME would be:
	564
2.5	565	> urn:sdmx:org.sdmx.infomodel.metadatastructure.MetadataAttribut e=SDMX:CONTACT_METADATA(1.0).CONTACT_REPORT.CONTACT_DETAILS.CO NTACT_NAME
1.1	566
15.1	567	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 version 1.0 would be:
1.1	568
2.5	569	> urn:sdmx:org.sdmx.infomodel.datastructure.Dataflow=TFFS.ABC:EX
1.1	570
	571	TERNAL_DEBT(1.0)
	572
15.1	573	The [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR MUST support this globally unique identification scheme. The SDMXRR 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:
1.1	574
15.1	575	* Identifiable and [[Nameable Artefacts>>doc:sdmx:Glossary.Nameable artefact.WebHome]]: id (in some cases this id may be hierarchic)
	576	* Maintainable [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]]: id, [[version>>doc:sdmx:Glossary.Version.WebHome]], agencyId,
1.1	577
15.1	578	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.
1.1	579
	580	=== 6.2.3 Table of SDMX-IM Packages and Classes ===
	581
15.1	582	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.
1.1	583
9.4	584	(% style="width:644.294px" %)
	585	\|(% style="width:127px" %)Package\|(% style="width:494px" %)(((
2.6	586	URN Classname (model classname where this is different)
1.1	587	)))
9.4	588	\|(% style="width:127px" %)base\|(% style="width:494px" %)Agency
	589	\|(% style="width:127px" %) \|(% style="width:494px" %)OrganisationUnitScheme
	590	\|(% style="width:127px" %) \|(% style="width:494px" %)AgencyScheme
	591	\|(% style="width:127px" %) \|(% style="width:494px" %)DataProviderScheme
	592	\|(% style="width:127px" %) \|(% style="width:494px" %)DataConsumerScheme
	593	\|(% style="width:127px" %) \|(% style="width:494px" %)OrganisationUnit
	594	\|(% style="width:127px" %) \|(% style="width:494px" %)DataProvider
	595	\|(% style="width:127px" %) \|(% style="width:494px" %)DataConsumer
	596	\|(% style="width:127px" %)datastructure\|(% style="width:494px" %)DataStructure (DataStructureDefinition)
	597	\|(% style="width:127px" %) \|(% style="width:494px" %)AttributeDescriptor
	598	\|(% style="width:127px" %) \|(% style="width:494px" %)DataAttribute
	599	\|(% style="width:127px" %) \|(% style="width:494px" %)GroupDimensionDescriptor
	600	\|(% style="width:127px" %) \|(% style="width:494px" %)DimensionDescriptor
	601	\|(% style="width:127px" %) \|(% style="width:494px" %)Dimension
	602	\|(% style="width:127px" %) \|(% style="width:494px" %)MeasureDimension
	603	\|(% style="width:127px" %) \|(% style="width:494px" %)TimeDimension
	604	\|(% style="width:127px" %) \|(% style="width:494px" %)MeasureDescriptor
	605	\|(% style="width:127px" %) \|(% style="width:494px" %)PrimaryMeasure
	606	\|(% style="width:127px" %) \|(% style="width:494px" %)Dataflow (DataflowDefinition)
	607	\|(% style="width:127px" %)metadatastructure\|(% style="width:494px" %)MetadataTarget
	608	\|(% style="width:127px" %) \|(% style="width:494px" %)DimensionDescriptorValueTarget
	609	\|(% style="width:127px" %) \|(% style="width:494px" %)IdentifiableObjectTarget
	610	\|(% style="width:127px" %) \|(% style="width:494px" %)ReportPeriodTarget
	611	\|(% style="width:127px" %) \|(% style="width:494px" %)DataSetTarget
	612	\|(% style="width:127px" %) \|(% style="width:494px" %)ReportStructure
	613	\|(% style="width:127px" %) \|(% style="width:494px" %)MetadataAttribute
	614	\|(% style="width:127px" %) \|(% style="width:494px" %)(((
1.1	615	MetadataStructure
	616
	617	(MetadataStructureDefinition)
	618	)))
9.4	619	\|(% style="width:127px" %) \|(% style="width:494px" %)Metadataflow (MetadataflowDefinition)
	620	\|(% style="width:127px" %)process\|(% style="width:494px" %)Process
	621	\|(% style="width:127px" %) \|(% style="width:494px" %)ProcessStep
	622	\|(% style="width:127px" %) \|(% style="width:494px" %)Transition
	623	\|(% style="width:127px" %)registry\|(% style="width:494px" %)ProvisionAgreement
	624	\|(% style="width:127px" %) \|(% style="width:494px" %)AttachmentConstraint
	625	\|(% style="width:127px" %) \|(% style="width:494px" %)ContentConstraint
	626	\|(% style="width:127px" %) \|(% style="width:494px" %)Subscription
	627	\|(% style="width:127px" %)mapping\|(% style="width:494px" %)StructureMap
	628	\|(% style="width:127px" %) \|(% style="width:494px" %)StructureSet
	629	\|(% style="width:127px" %) \|(% style="width:494px" %)ComponentMap
	630	\|(% style="width:127px" %) \|(% style="width:494px" %)ConceptSchemeMap
	631	\|(% style="width:127px" %) \|(% style="width:494px" %)OrganisationSchemeMap
	632	\|(% style="width:127px" %) \|(% style="width:494px" %)CodelistMap
	633	\|(% style="width:127px" %) \|(% style="width:494px" %)CategorySchemeMap
	634	\|(% style="width:127px" %) \|(% style="width:494px" %)ReportingTaxonomyMap
	635	\|(% style="width:127px" %) \|(% style="width:494px" %)ConceptMap
	636	\|(% style="width:127px" %) \|(% style="width:494px" %)OrganisationMap
	637	\|(% style="width:127px" %) \|(% style="width:494px" %)CodeMap
	638	\|(% style="width:127px" %) \|(% style="width:494px" %)HybridCodelistMap
	639	\|(% style="width:127px" %) \|(% style="width:494px" %)CategoryMap
	640	\|(% style="width:127px" %) \|(% style="width:494px" %)HybridCodeMap
	641	\|(% style="width:127px" %) \|(% style="width:494px" %)ReportingCategoryMap
	642	\|(% style="width:127px" %)codelist\|(% style="width:494px" %)Codelist
	643	\|(% style="width:127px" %) \|(% style="width:494px" %)HierarchicalCodelist
	644	\|(% style="width:127px" %) \|(% style="width:494px" %)Hierarchy
	645	\|(% style="width:127px" %) \|(% style="width:494px" %)Hierarchy
	646	\|(% style="width:127px" %) \|(% style="width:494px" %)Code
	647	\|(% style="width:127px" %) \|(% style="width:494px" %)HierarchicalCode
	648	\|(% style="width:127px" %) \|(% style="width:494px" %)Level
	649	\|(% style="width:127px" %)categoryscheme\|(% style="width:494px" %)CategoryScheme
	650	\|(% style="width:127px" %) \|(% style="width:494px" %)Category
	651	\|(% style="width:127px" %) \|(% style="width:494px" %)Categorisation
	652	\|(% style="width:127px" %) \|(% style="width:494px" %)ReportingTaxonomy
	653	\|(% style="width:127px" %) \|(% style="width:494px" %)ReportingCategory
	654	\|(% style="width:127px" %)conceptscheme\|(% style="width:494px" %)ConceptScheme
	655	\|(% style="width:127px" %) \|(% style="width:494px" %)Concept
	656	\|(% style="width:127px" %)transformation\|(% style="width:494px" %)TransformationScheme
	657	\|(% style="width:127px" %) \|(% style="width:494px" %)Transformation
	658	\|(% style="width:127px" %) \|(% style="width:494px" %)CustomTypeScheme
	659	\|(% style="width:127px" %) \|(% style="width:494px" %)CustomType
	660	\|(% style="width:127px" %) \|(% style="width:494px" %)NamePersonalisationScheme
	661	\|(% style="width:127px" %) \|(% style="width:494px" %)NamePersonalisation
	662	\|(% style="width:127px" %) \|(% style="width:494px" %)VtlCodelistMapping
	663	\|(% style="width:127px" %) \|(% style="width:494px" %)VtlConceptMapping
	664	\|(% style="width:127px" %) \|(% style="width:494px" %)VtlDataflowMapping
	665	\|(% style="width:127px" %) \|(% style="width:494px" %)VtlConceptSchemeMapping
	666	\|(% style="width:127px" %) \|(% style="width:494px" %)RulesetScheme
	667	\|(% style="width:127px" %) \|(% style="width:494px" %)Ruleset
	668	\|(% style="width:127px" %) \|(% style="width:494px" %)UserDefinedOperatorScheme
	669	\|(% style="width:127px" %) \|(% style="width:494px" %)UserDefinedOperator
1.1	670
15.1	671	Table 2: [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] Packages and Contained Classes
1.1	672
	673	=== 6.2.4 URN Identification components of SDMX objects ===
	674
15.1	675	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.
1.1	676
	677	~* indicates that the object is maintainable.
	678
	679	Note that for brevity the URN examples omit the prefix. All URNs have the prefix
	680
2.7	681	> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
1.1	682
9.4	683	(% style="width:1277.29px" %)
	684	\|(% style="width:269px" %)SDMX Class\|(% style="width:453px" %)Key attribute(s)\|(% style="width:550px" %)Example of URN
15.1	685	\|(% style="width:269px" %)Agency\|(% style="width:453px" %)The URN for an Agency is shown later in this table. The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical.\|(% style="width:550px" %)(((
1.1	686	IMF
2.9	687	Sub agency in the IMF AGENCIES
1.1	688	IMF.SubAgency1
	689	)))
9.4	690	\|(% style="width:269px" %)*ConceptScheme\|(% style="width:453px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)\|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
	691	\|(% style="width:269px" %)Concept\|(% style="width:453px" %)conceptSchemeAgencyId:
	692	conceptSchemeId(version).conceptId\|(% style="width:550px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
	693	\|(% style="width:269px" %)*Codelist\|(% style="width:453px" %)codeListAgencyId:codeListId(version)\|(% style="width:550px" %)SDMX:CL_FREQ(1.0)
	694	\|(% style="width:269px" %)Code\|(% style="width:453px" %)codeListAgencyId:codelistId(version).codeId\|(% style="width:550px" %)SDMX:CL_FREQ(1.0).Q
	695	\|(% style="width:269px" %)(((
2.8	696	*Hierarchical Codelist
9.4	697	)))\|(% style="width:453px" %)hierachicalCodelistAgencyId:
	698	hierarchicalCodelistId(version)\|(% style="width:550px" %)(((
2.8	699	UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
1.1	700	)))
9.4	701	\|(% style="width:269px" %)Hierarchy\|(% style="width:453px" %)(((
1.1	702	hierachicalcodeListAgencyId:
	703	hierarchicalcodelistId(version).Hierarchy
9.4	704	)))\|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0).
2.9	705	H-C-GOV
9.4	706	\|(% style="width:269px" %)Level\|(% style="width:453px" %)(((
1.1	707	hierachicalcodeListAgencyId:
	708	hierarchicalcodelistId(version).Hierarchy.Level
9.4	709	)))\|(% style="width:550px" %)(((
1.1	710	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
	711	)))
9.4	712	\|(% style="width:269px" %)HierarchicalCode\|(% style="width:453px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode\|(% style="width:550px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
	713	\|(% style="width:269px" %)*DataStructure\|(% style="width:453px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0)
	714	\|(% style="width:269px" %)(((
1.1	715	Dimension
	716	Descriptor
	717	Measure
	718	Descriptor
	719	Attribute
	720	Descriptor
9.4	721	)))\|(% style="width:453px" %)(((
1.1	722	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
	723	componentListId
	724	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
9.4	725	)))\|(% style="width:550px" %)(((
1.1	726	TFFS:EXT_DEBT(1.0).DimensionDescriptor
	727
	728	TFFS:EXT_DEBT(1.0).MeasureDescriptor
	729
	730	TFFS:EXT_DEBT(1.0).AttributeDescriptor
	731	)))
9.4	732	\|(% style="width:269px" %)(((
1.1	733	GroupDimension
	734	Descriptor
9.4	735	)))\|(% style="width:453px" %)(((
1.1	736	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
	737	groupDimensionDescriptorId
9.4	738	)))\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).SIBLING
	739	\|(% style="width:269px" %)Dimension\|(% style="width:453px" %)(((
1.1	740	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	741	dimensionId
9.4	742	)))\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).FREQ
	743	\|(% style="width:269px" %)TimeDimension\|(% style="width:453px" %)(((
1.1	744	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	745	timeDimensionId
9.4	746	)))\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
	747	\|(% style="width:269px" %)Measure Dimension\|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	748	measureDimensionId\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
	749	\|(% style="width:269px" %)DataAttrribute\|(% style="width:453px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
	750	\|(% style="width:269px" %)PrimaryMeasure\|(% style="width:453px" %)(((
1.1	751	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	752	primaryMeasureId
9.4	753	)))\|(% style="width:550px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
	754	\|(% style="width:269px" %)(((
2.9	755	*Category Scheme
9.4	756	)))\|(% style="width:453px" %)categorySchemeAgencyId:
	757	categorySchemeId(version)\|(% style="width:550px" %)IMF:SDDS(1.0)
	758	\|(% style="width:269px" %)Category\|(% style="width:453px" %)categorySchemeAgencyId:
2.9	759	categorySchemeId(version).
9.4	760	categoryId.categoryId categoryId.categoryId etc.\|(% style="width:550px" %)(((
1.1	761	IMF:SDDS(1.0):
	762	level_1_category.level_2_category …
	763	)))
9.4	764	\|(% style="width:269px" %)(((
2.9	765	*Reporting Taxonomy
9.4	766	)))\|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)\|(% style="width:550px" %) IMF:REP_1(1.0)
	767	\|(% style="width:269px" %)ReportingCategory\|(% style="width:453px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId\|(% style="width:550px" %)(((
1.1	768	IMF:REP_1(1.0):
	769	level_1_repcategory.level_2_repcategory …
	770	)))
9.4	771	\|(% style="width:269px" %)*Categorisation\|(% style="width:453px" %)categorisationAgencyId: categorisationId(version)\|(% style="width:550px" %)IMF:cat001(1.0)
	772	\|(% style="width:269px" %)(((
2.9	773	*Organisation Unit Scheme
9.4	774	)))\|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)\|(% style="width:550px" %)ECB:ORGANISATIONS(1.0)
	775	\|(% style="width:269px" %)Organisation Unit\|(% style="width:453px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId\|(% style="width:550px" %)ECB:ORGANISATIONS(1.0).1F
	776	\|(% style="width:269px" %)*AgencyScheme\|(% style="width:453px" %)agencySchemeAgencyId: agencySchemeId(version)\|(% style="width:550px" %)ECB:AGENCIES(1.0)
1.1	777
9.4	778	(% style="width:1274.29px" %)
	779	\|(% style="width:262px" %)Agency\|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId\|(% style="width:535px" %)ECB:AGENCY(1.0).AA
2.10	780	\|(% style="width:262px" %)(((
	781	*DataProvider Scheme
9.4	782	)))\|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)\|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0)
	783	\|(% style="width:262px" %)DataProvider\|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId\|(% style="width:535px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
2.10	784	\|(% style="width:262px" %)(((
	785	*DataConsumer Scheme
9.4	786	)))\|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)\|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0)
	787	\|(% style="width:262px" %)Data Consumer\|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId\|(% style="width:535px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
2.10	788	\|(% style="width:262px" %)(((
	789	*Metadata Structure
9.4	790	)))\|(% style="width:369px" %)MSDAgencyId:MSDId(version)\|(% style="width:535px" %)IMF:SDDS_MSD(1.0)
2.10	791	\|(% style="width:262px" %)MetadataTarget\|(% style="width:369px" %)(((
1.1	792	MSDAgencyId:
	793	MSDId(version).metadataTargetId
9.4	794	)))\|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY
2.10	795	\|(% style="width:262px" %)(((
1.1	796	Dimension
	797	DescriptorValues
	798	Target
2.10	799	)))\|(% style="width:369px" %)(((
1.1	800	MSDAgencyId: MSDId(version).
	801	metadataTargetId.keyDescriptorValueTargetId
9.4	802	)))\|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
2.10	803	\|(% style="width:262px" %)Identifiable Object Target\|(% style="width:369px" %)(((
	804	MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId
9.4	805	)))\|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
2.10	806	\|(% style="width:262px" %)DataSetTarget\|(% style="width:369px" %)(((
1.1	807	MSDAgencyId:
2.10	808	MSDId(version).metadataTargetId.dataSetTargetId
9.4	809	)))\|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
2.10	810	\|(% style="width:262px" %)PeportPeriod Target\|(% style="width:369px" %)(((
	811	MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId
9.4	812	)))\|(% style="width:535px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
1.1	813
9.4	814	(% style="width:1277.29px" %)
	815	\|(% style="width:270px" %)(((
1.1	816	ReportStructure
9.4	817	)))\|(% style="width:454px" %)(((
2.10	818	MSDAgencyId: MSDId(version).reportStructureId
9.4	819	)))\|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
	820	\|(% style="width:270px" %)(((
3.6	821	Metadata Attribute
9.4	822	)))\|(% style="width:454px" %)(((
2.10	823	MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
9.4	824	)))\|(% style="width:549px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
	825	\|(% style="width:270px" %)*Dataflow\|(% style="width:454px" %)dataflowAgencyId: dataflowId(version)\|(% style="width:549px" %)TFFS:CRED_EXT_DEBT(1.0)
	826	\|(% style="width:270px" %)*Provision Agreement\|(% style="width:454px" %)(((
1.1	827	provisionAgreementAgencyId:provisionAgreem entId(version)
9.4	828	)))\|(% style="width:549px" %)(((
1.1	829	TFFS:CRED_EXT_DEBT_AB(1.0)
	830	)))
9.4	831	\|(% style="width:270px" %)(((
3.6	832	*Content Constraint
9.4	833	)))\|(% style="width:454px" %)constraintAgencyId:ContentConstraintId(versio n)\|(% style="width:549px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
	834	\|(% style="width:270px" %)(((
3.6	835	*Attachment Constraint
9.4	836	)))\|(% style="width:454px" %)(((
1.1	837	constraintAgencyId:
	838
	839	attachmentConstraintId(version)
9.4	840	)))\|(% style="width:549px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
	841	\|(% style="width:270px" %)*Metadataflow\|(% style="width:454px" %)metadataflowAgencyId: metadataflowId(version)\|(% style="width:549px" %)IMF:SDDS_FLOW(1.0)
	842	\|(% style="width:270px" %)*StructureSet\|(% style="width:454px" %)structureSetAgencyId: structureSetId(version)\|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0)
	843	\|(% style="width:270px" %)StructureMap\|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). structureMapId\|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
	844	\|(% style="width:270px" %)Component Map\|(% style="width:454px" %)(((
1.1	845	structureSetAgencyId: structureSetId(version).
	846
	847	structureMapId. componentMapId
9.4	848	)))\|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
	849	\|(% style="width:270px" %)CodelistMap\|(% style="width:454px" %)structureSetAgencyId: structureSetId(version). codelistMapId\|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
	850	\|(% style="width:270px" %)CodeMap\|(% style="width:454px" %)structureSetAgencyId: structureSetId(version).
1.1	851	codeListMapId.
9.4	852	codeMapId\|(% style="width:549px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
1.1	853
9.4	854	(% style="width:1279.29px" %)
	855	\|(% style="width:271px" %)(((
	856	CategorySchemeMap
	857	)))\|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
	858	\|(% style="width:271px" %)CategoryMap\|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_MAP
	859	\|(% style="width:271px" %)Organisation SchemeMap\|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
	860	\|(% style="width:271px" %)Organisation Map\|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). organisationSchemeMapId. organisationMapId\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP.IMF_1C0
	861	\|(% style="width:271px" %)(((
1.1	862	Concept
	863
	864	SchemeMap
9.4	865	)))\|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). conceptSchemeMapId\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD
	866	\|(% style="width:271px" %)ConceptMap\|(% style="width:453px" %)(((
1.1	867	structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
	868	conceptMapId
9.4	869	)))\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
	870	\|(% style="width:271px" %)(((
3.6	871	ReportingTaxonomyMap
9.4	872	)))\|(% style="width:453px" %)structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP
	873	\|(% style="width:271px" %)(((
3.7	874	ReportingCategoryMap
9.4	875	)))\|(% style="width:453px" %)(((
1.1	876	structureSetAgencyId: structureSetId(version).
	877	reportngCategoryId
9.4	878	)))\|(% style="width:551px" %)SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
1.1	879
9.4	880	(% style="width:1282.29px" %)
	881	\|(% style="width:272px" %)(((
3.6	882	HybridCodelistMap
9.4	883	)))\|(% style="width:450px" %)structureSetAgencyId: structureSetId(version).
	884	hybridCodelistMapId.\|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
	885	\|(% style="width:272px" %)HybridCodeMap\|(% style="width:450px" %)structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId\|(% style="width:557px" %)SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
	886	\|(% style="width:272px" %)*Process\|(% style="width:450px" %)processAgencyId: processId{version]\|(% style="width:557px" %)BIS:PROCESS1(1.0)
	887	\|(% style="width:272px" %)ProcessStep\|(% style="width:450px" %)(((
1.1	888	processAgencyId: processId(version).
	889	processStepId
9.4	890	)))\|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1
	891	\|(% style="width:272px" %)Transition\|(% style="width:450px" %)(((
1.1	892	processAgencyId: processId(version).
	893	processStepId transitionId
9.4	894	)))\|(% style="width:557px" %)BIS:PROCESS1(1.0).STEP1.TRANSITION1
15.1	895	\|(% style="width:272px" %)Subscription\|(% style="width:450px" %)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, The name of the URN is registryURN There is no pre-determined format.\|(% style="width:557px" %)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 registryURN that is returned from the registry in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response message.
9.4	896	\|(% style="width:272px" %)(((
3.6	897	*Transformation Scheme
9.4	898	)))\|(% style="width:450px" %)transformationSchemeAgencyId transformationSchemeId(version)\|(% style="width:557px" %)ECB: TRANSFORMATION_SCHEME(1.0)
	899	\|(% style="width:272px" %)Transformation\|(% style="width:450px" %)(((
1.1	900	transformationSchemeAgencyId transformationSchemeId(version)
	901	transformationId
9.4	902	)))\|(% style="width:557px" %)ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
	903	\|(% style="width:272px" %)CustomType Scheme\|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version)\|(% style="width:557px" %)ECB:CUSTOM_TYPE_SCHEME(1.0)
1.1	904
9.4	905	(% style="width:1281.29px" %)
	906	\|(% style="width:275px" %)CustomType\|(% style="width:450px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId\|(% style="width:552px" %)ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
	907	\|(% style="width:275px" %)(((
1.1	908	Name
	909	Personalisation
	910	Scheme
9.4	911	)))\|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)\|(% style="width:552px" %)ECB:PSN_SCHEME(1.0)
	912	\|(% style="width:275px" %)(((
1.1	913	Name
	914	Personalisation
9.4	915	)))\|(% style="width:450px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
	916	namePersonalisationId\|(% style="width:552px" %)ECB:PSN_SCHEME(1.0).PSN1234
	917	\|(% style="width:275px" %)VtlMapping Scheme\|(% style="width:450px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)\|(% style="width:552px" %)ECB:CLIST_MP(2.0)
	918	\|(% style="width:275px" %)VtlCodelist Mapping\|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId\|(% style="width:552px" %)ECB:CLIST_MP(2.0).ABZ
	919	\|(% style="width:275px" %)VtlConcept Mapping\|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId\|(% style="width:552px" %)ECB:CLIST_MP(1.0).XYA
	920	\|(% style="width:275px" %)VtlDataflow Mapping\|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId\|(% style="width:552px" %)ECB:CLIST_MP(1.0).MOQ
	921	\|(% style="width:275px" %)(((
1.1	922	VtlConcept
	923
	924	SchemeMapping
9.4	925	)))\|(% style="width:450px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptSchemeId\|(% style="width:552px" %)ECB:CLIST_MP(1.0).Z11
	926	\|(% style="width:275px" %)RulesetScheme\|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version)\|(% style="width:552px" %)ECB:RULESET_23(1.0)
	927	\|(% style="width:275px" %)Ruleset\|(% style="width:450px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId\|(% style="width:552px" %)ECB:RULESET_23(1.0).SET111
	928	\|(% style="width:275px" %)(((
3.7	929	UserDefinedOperatorScheme
9.4	930	)))\|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)\|(% style="width:552px" %)ECB:OS_CALC(1.2)
	931	\|(% style="width:275px" %)UserDefined Operator\|(% style="width:450px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId\|(% style="width:552px" %)ECB:OS_CALC(1.2).OS267
1.1	932
3.7	933	Table 3: Table of identification components for SDMX Identifiable Artefacts
1.1	934
	935	= 7 Implementation Notes =
	936
	937	== 7.1 Structural Definition Metadata ==
	938
	939	=== 7.1.1 Introduction ===
	940
15.1	941	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]], [[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.)
1.1	942
15.1	943	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]] registry messages for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Query message for structure queries. The use of SOAP is also recommended, as described in the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Web Services Guidelines. 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.
1.1	944
15.1	945	[[Structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] items
1.1	946
15.1	947	* may only be modified by the [[maintenance agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]] which created them
1.1	948	* may only be deleted by the agency which created them
	949	* may not be deleted if they are referenced from other constructs in the Registry
	950
15.1	951	The [[level>>doc:sdmx:Glossary.Level.WebHome]] 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]]. In other words, any function such as add, modify, delete is at the [[level>>doc:sdmx:Glossary.Level.WebHome]] of the [[Maintainable Artefact>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]. For instance, if a [[Code>>doc:sdmx:Glossary.Code.WebHome]] is added to a [[Code List>>doc:sdmx:Glossary.Code list.WebHome]], or the Name of a [[Code>>doc:sdmx:Glossary.Code.WebHome]] is changed, the Registry must replace the existing [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] with the submitted [[Code List>>doc:sdmx:Glossary.Code list.WebHome]] of the same [[Maintenance Agency>>doc:sdmx:Glossary.Maintenance agency.WebHome]], [[Code List>>doc:sdmx:Glossary.Code list.WebHome]], Id and Version.
1.1	952
15.1	953	The following table lists the [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
1.1	954
2.10	955	(% style="width:640.294px" %)
	956	\|(% colspan="2" rowspan="1" style="width:186px" %)Maintainable Artefacts\|(% style="width:206px" %)Content
	957	\|(% style="width:171px" %)Abstract Class\|(% style="width:232px" %)Concrete Class\|(% style="width:206px" %)
	958	\|(% style="width:171px" %)Item Scheme\|(% style="width:232px" %)Codelist\|(% style="width:206px" %)Code
	959	\|(% style="width:171px" %) \|(% style="width:232px" %)Concept Scheme\|(% style="width:206px" %)Concept
	960	\|(% style="width:171px" %) \|(% style="width:232px" %)Category Scheme\|(% style="width:206px" %)Category
	961	\|(% style="width:171px" %) \|(% style="width:232px" %)Organisation Unit Scheme\|(% style="width:206px" %)Organisation Unit
	962	\|(% style="width:171px" %) \|(% style="width:232px" %)Agency Scheme\|(% style="width:206px" %)Agency
	963	\|(% style="width:171px" %) \|(% style="width:232px" %)Data Provider Scheme\|(% style="width:206px" %)Data Provider
	964	\|(% style="width:171px" %) \|(% style="width:232px" %)Data Consumer Scheme\|(% style="width:206px" %)Data Consumer
	965	\|(% style="width:171px" %) \|(% style="width:232px" %)Reporting Taxonomy\|(% style="width:206px" %)Reporting Category
	966	\|(% style="width:171px" %) \|(% style="width:232px" %)Transformation Scheme\|(% style="width:206px" %)Transformation
	967	\|(% style="width:171px" %) \|(% style="width:232px" %)Custom Type Scheme\|(% style="width:206px" %)Custom Type
	968	\|(% style="width:171px" %) \|(% style="width:232px" %)Name Personalisation Scheme\|(% style="width:206px" %)Name Personalisation
	969	\|(% style="width:171px" %) \|(% style="width:232px" %)Vtl Mapping Scheme\|(% style="width:206px" %)Vtl Codelist Mapping
	970	\|(% style="width:171px" %) \|(% style="width:232px" %) \|(% style="width:206px" %)Vtl Dataflow Mapping
	971	\|(% style="width:171px" %) \|(% style="width:232px" %) \|(% style="width:206px" %)Vtl Concept Scheme Mapping
	972	\|(% style="width:171px" %) \|(% style="width:232px" %)Ruleset Scheme\|(% style="width:206px" %)Ruleset
	973	\|(% style="width:171px" %) \|(% style="width:232px" %)User Defined Operator Scheme\|(% style="width:206px" %)User Defined Operator
	974	\|(% style="width:171px" %) \|(% style="width:232px" %) \|(% style="width:206px" %)User Defined Operator
	975	\|(% style="width:171px" %)Structure\|(% style="width:232px" %)Data Structure Definition\|(% style="width:206px" %)(((
1.1	976	Dimension Descriptor
	977	Group Dimension
	978	Descriptor
	979	Dimension
	980	Measure Dimension
	981	Time Dimension
	982	Attribute Descriptor
	983	Data Attribute
	984	Measure Descriptor
	985	Primary Measure
	986	)))
2.10	987	\|(% style="width:171px" %) \|(% style="width:232px" %)Metadata Structure Definition\|(% style="width:206px" %)(((
	988	Metadata Target, Dimension Descriptor
1.1	989	Values Target Identifiable
	990	Object Target
	991	Report Period Target
	992	Data SetTarget
	993	Report Structure
	994	Metadata Attribute
	995	)))
2.11	996	\|(% style="width:171px" %)Structure Usage\|(% style="width:232px" %)Dataflow Definition\|(% style="width:206px" %)
	997	\|(% style="width:171px" %) \|(% style="width:232px" %)Metadataflow Definition\|(% style="width:206px" %)
	998	\|(% style="width:171px" %)None\|(% style="width:232px" %)Process\|(% style="width:206px" %)Process Step
	999	\|(% style="width:171px" %)None\|(% style="width:232px" %)Structure Set\|(% style="width:206px" %)(((
1.1	1000	Component Map
	1001	Concept Scheme Map
	1002	Codelist Map
	1003	Category Scheme Map
	1004	Reporting Taxonomy Map
	1005	Organisation Scheme Map
	1006	Concept Map
	1007	Code Map
	1008	Category Map
	1009	Organisation Map
	1010	Reporting Category Map
	1011	Hybrid Codelist Map
	1012	Hybrid Code Map
	1013	)))
2.11	1014	\|(% style="width:171px" %)None\|(% style="width:232px" %)Provision Agreement\|(% style="width:206px" %)
	1015	\|(% style="width:171px" %)None\|(% style="width:232px" %)Hierarchical Codelist\|(% style="width:206px" %)(((
1.1	1016	Hierarchy
	1017	Hierarchical Code
	1018	)))
	1019
15.1	1020	Table 4: Table of Maintainable Artefacts for Structural Definition Metadata
1.1	1021
	1022	=== 7.1.2 Item Scheme, Structure ===
	1023
15.1	1024	The [[artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] included in the structural definitions are:
1.1	1025
15.1	1026	* All types of [[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]] ([[Codelist>>doc:sdmx:Glossary.Code list.WebHome]], [[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]], [[Data Consumer Scheme>>doc:sdmx:Glossary.Data consumer scheme.WebHome]], Organisation Unit Scheme)
	1027	* All types of Structure ([[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]], Metadata Structure Definition)
	1028	* All types of Structure Usage ([[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition, [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition)
1.1	1029
	1030	=== 7.1.3 Structure Usage ===
	1031
	1032	==== 7.1.3.1 Structure Usage: Basic Concepts ====
	1033
15.1	1034	The Structure Usage defines, in its concrete classes of [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition and
1.1	1035
15.1	1036	[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition, 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]].
1.1	1037
	1038	==== 7.1.3.2 Structure Usage Schematic ====
	1039
	1040	[[image:1747824123018-658.jpeg]]
	1041
	1042	Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions
	1043
	1044	==== 7.1.3.3 Structure Usage Model ====
	1045
2.12	1046	[[image:1747829078194-749.png]]
	1047
1.1	1048	Figure 10: SDMX-IM of links from Structure Usage to Category
	1049
15.1	1050	In addition to the maintenance of the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition and the [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition the following links must be maintained in the registry:
1.1	1051
15.1	1052	* [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition to Data Structure Definition
	1053	* [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition to Metadata Structure Definition
1.1	1054
	1055	The following links may be created by means of a Categorisation
	1056
15.1	1057	* Categorisation to [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition and Category
	1058	* Categorisation to [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition and Category
1.1	1059
	1060	== 7.2 Data and Metadata Provisioning ==
	1061
	1062	=== 7.2.1 Provisioning Agreement: Basic concepts ===
	1063
15.1	1064	Data provisioning defines a framework in which the provision of different types of statistical data and metadata by various [[data providers>>doc:sdmx:Glossary.Data provider.WebHome]] 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>>doc:sdmx:Glossary.Level.WebHome]] 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.
1.1	1065
15.1	1066	Note that in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] the class “[[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]]” encompasses both data and metadata and the term “data provisioning” here includes both the provisioning of data and metadata.
1.1	1067
15.1	1068	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.
1.1	1069
	1070	=== 7.2.2 Provisioning Agreement Model – pull use case ===
	1071
15.1	1072	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]].
1.1	1073
2.13	1074	[[image:1747829109466-595.png]]
1.1	1075
	1076	Figure 11: SDMX-IM of the Data Provider
	1077
15.1	1078	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]]
1.1	1079
	1080	[[image:1747824123019-181.jpeg]]
	1081
	1082	Figure 12: Schematic of the Provision Agreement
	1083
15.1	1084	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]].
1.1	1085
2.13	1086	[[image:1747829139951-378.png]]
1.1	1087
2.13	1088	(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
	1089	Figure 13: Logical class diagram of the information contained in the Provision Agreement
1.1	1090
15.1	1091	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]] and a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition. The [[Data Provider>>doc:sdmx:Glossary.Data provider.WebHome]] and the [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]]/[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition must exist already in order to set up a [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]].
1.1	1092
	1093	== 7.3 Data and Metadata Constraints ==
	1094
	1095	=== 7.3.1 Data and Metadata Constraints: Basic Concepts ===
	1096
15.1	1097	[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] are, effectively, lists of the valid or actual content of data and metadata. [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] can be used to specify a sub set 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 [[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]].
1.1	1098
15.1	1099	[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] comprise the specification of subsets of key or target values or [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] values that are contained in a Datasource, or is to be provided for a [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]] Definition, 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 actually present in any specific Datasource, or more than is intended to be supplied according to a specific [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition.
1.1	1100
15.1	1101	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 Datasource (at the [[level>>doc:sdmx:Glossary.Level.WebHome]] 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 [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]]. The Content [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] is also used to define a [[code list>>doc:sdmx:Glossary.Code list.WebHome]] sub set which is used to populate a Partial [[Code List>>doc:sdmx:Glossary.Code list.WebHome]].
1.1	1102
15.1	1103	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]] Definition, and there can be one or more defined for any [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]].
1.1	1104
15.1	1105	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]] Definition (and hence to a [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). The [[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] Definition is thus a means of enabling content based processing.
1.1	1106
15.1	1107	In addition, [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] 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 datasource (these can be used to build relevant selection tables), and the Key Set can be used to specify the keys that exist in a datasource (these can be used to guide the user to select only those [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] [[code>>doc:sdmx:Glossary.Code.WebHome]] values that will return data based on the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] values already selected).
1.1	1108
	1109	=== 7.3.2 Data and Metadata Constraints: Schematic ===
	1110
	1111	[[image:1747824123021-978.jpeg]]
	1112
	1113	Figure 14: Schematic of the Constraint and the Artefacts that can be Constrained
	1114
	1115	=== 7.3.3 Data and Metadata Constraints: Model ===
	1116
2.13	1117	[[image:1747829204737-370.png]]
1.1	1118
2.13	1119	Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts
1.1	1120
15.1	1121	The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] specified. Note that the actual [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] applies.
1.1	1122
15.1	1123	The content of the [[Constraint>>doc:sdmx:Glossary.Constraint.WebHome]] can be found in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] document.
1.1	1124
	1125	== 7.4 Data and Metadata Registration ==
	1126
	1127	=== 7.4.1 Basic Concepts ===
	1128
15.1	1129	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]] Definition (and hence [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]). This is implemented as either a web-accessible [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file, or in a database which has a web-services interface capable of responding to an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Query or RESTful query with an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] data stream.
1.1	1130
15.1	1131	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.
1.1	1132
15.1	1133	The same mechanism can be used to report or make available a [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]].
1.1	1134
15.1	1135	[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]-RR supports [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata set>>doc:sdmx:Glossary.Metadata 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.
1.1	1136
	1137	=== 7.4.2 The Registration Request ===
	1138
	1139	==== 7.4.2.1 Registration Request Schematic ====
	1140
	1141	[[image:1747824123025-411.jpeg]]
	1142
3.3	1143	Figure 16: Schematic of the Objects Concerned with Registration
1.1	1144
	1145	==== 7.4.2.2 Registration Request Model ====
	1146
15.1	1147	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]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] to be registered. The Registration can optionally have information which has been extracted from the Registration:
1.1	1148
	1149	* validFrom
	1150	* validTo
	1151	* lastUpdated
	1152
	1153	The last updated date is useful during the discovery process to make sure the client knows which data is freshest.
	1154
15.1	1155	The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values:
1.1	1156
9.5	1157	(% style="width:798.294px" %)
	1158	\|(% style="width:212px" %)Action Attribute Value\|(% style="width:582px" %)Behaviour
	1159	\|(% style="width:212px" %)Append\|(% style="width:582px" %)Add this Registration to the registry
	1160	\|(% style="width:212px" %)Replace\|(% style="width:582px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
	1161	\|(% style="width:212px" %)Delete\|(% style="width:582px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1.1	1162
2.15	1163	[[image:1747829290890-122.png]]
	1164
1.1	1165	Figure 17: Logical Class Diagram of Registration of Data and Metadata
	1166
15.1	1167	The Query Datasource is an abstract class that represents a [[data source>>doc:sdmx:Glossary.Data source.WebHome]] which can understand an [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] query (SOAPDatasource) or RESTful query
1.1	1168
	1169	(RESTDatasource) and respond appropriately. Each of these different Datasources inherit the dataURL from Datasource, and the QueryDatasource has an additional URL to locate a WSDL or WADL document to describe how to access it. All other supported protocols are assumed to use the Simple Datasource URL.
	1170
15.1	1171	A Simple Datasource is used to reference a physical [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] file that is available at a URL.
1.1	1172
15.1	1173	The Registration Request 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.
1.1	1174
15.1	1175	The Registration includes [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] that state how a Simple Datasource is to be indexed when registered. The Registry registration process must act as follows.
1.1	1176
15.1	1177	Information in the data or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] is extracted and placed in one or more Content [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] (see the [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the [[SDMX Information Model>>doc:sdmx:Glossary.SDMX Information Model.WebHome]] – Section 2 of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Standards). The information to be extracted is indicated by the Boolean values set on the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] as shown in the table below.
1.1	1178
10.1	1179	(% style="width:860.294px" %)
	1180	\|(% style="width:185px" %)Indexing Required\|(% style="width:672px" %)Registration Process Activity
15.1	1181	\|(% style="width:185px" %)indexTimeSeries\|(% style="width:672px" %)Extract all the [[series keys>>doc:sdmx:Glossary.Series key.WebHome]] and create a KeySet(s) Constraint.
10.1	1182	\|(% style="width:185px" %)indexDataSet\|(% style="width:672px" %)(((
15.1	1183	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 [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]], and the associated Selection Value.
1.1	1184	)))
10.1	1185	\|(% style="width:185px" %)indexReportingPeriod\|(% style="width:672px" %)(((
15.1	1186	This applies only to a registered [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
	1187	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.
1.1	1188	)))
10.1	1189	\|(% style="width:185px" %)indexAttributes\|(% style="width:672px" %)(((
15.1	1190	[[Data Set>>doc:sdmx:Glossary.Data set.WebHome]]
	1191	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 [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the SDMXIM, and the associated Selection Value
	1192	[[Metadata Set>>doc:sdmx:Glossary.Metadata set.WebHome]]
	1193	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 [[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] model in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]. Note that the content is not stored in the Selection Value.
1.1	1194	)))
	1195
15.1	1196	[[Constraints>>doc:sdmx:Glossary.Constraint.WebHome]] that specify the contents of a Query Datasource are submitted to the Registry in a Submit Structure Request.
1.1	1197
15.1	1198	The Registration must reference the [[Provision Agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] to which it relates.
1.1	1199
	1200	=== 7.4.3 Registration Response ===
	1201
2.16	1202	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 Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
1.1	1203
15.1	1204	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]], metadataset, or query service.
1.1	1205
15.1	1206	The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text 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 Registration Response is shown below:
1.1	1207
2.16	1208	[[image:1747829477882-750.png]]
1.1	1209
	1210	Figure 18: Logical class diagram showing the registration response
	1211
	1212	== 7.5 Subscription and Notification Service ==
	1213
15.1	1214	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, 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.
1.1	1215
15.1	1216	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.
1.1	1217
15.1	1218	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]]”.
1.1	1219
3.2	1220	=== 7.5.1Subscription Logical Class Diagram ===
1.1	1221
2.17	1222	[[image:1747829554603-150.png]]
1.1	1223
	1224	Figure 19: Logical Class Diagram of the Subscription
	1225
	1226	=== 7.5.2 Subscription Information ===
	1227
15.1	1228	Regardless of the type of registry/repository events being observed, a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] always contains:
1.1	1229
15.1	1230	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.
	1231	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.
	1232	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]].
2.17	1233	1. A selector which specifies which type of events are of interest. The set of event types is:
1.1	1234
10.1	1235	(% style="width:1031.29px" %)
	1236	\|(% style="width:319px" %)Event Type\|(% style="width:678px" %)Comment
15.1	1237	\|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS\|(% style="width:678px" %)Life-cycle changes to [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository.
	1238	\|(% style="width:319px" %)DATA_REGISTRATION_EVENTS\|(% style="width:678px" %)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.
	1239	\|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS\|(% style="width:678px" %)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.
10.1	1240	\|(% style="width:319px" %)ALL_EVENTS\|(% style="width:678px" %)All events of the specified EventType
1.1	1241
	1242	=== 7.5.3 Wildcard Facility ===
	1243
15.1	1244	[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] [[notification>>doc:sdmx:Glossary.Notification.WebHome]] supports wildcarded identifier [[components>>doc:sdmx:Glossary.Component.WebHome]] URNs, which are identiiers which have some or all of their [[component>>doc:sdmx:Glossary.Component.WebHome]] parts replaced by the wildcard character `%`. Identifier [[components>>doc:sdmx:Glossary.Component.WebHome]] comprise:
	1245
2.17	1246	* agencyID
	1247	* id
	1248	* version
1.1	1249
15.1	1250	Examples of wildcarded identifier [[components>>doc:sdmx:Glossary.Component.WebHome]] for an identified object type of [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] are shown below.
1.1	1251
2.18	1252	//AgencyID = %
1.1	1253	Id = %
2.18	1254	Version = %//
1.1	1255
15.1	1256	This subscribes to all [[Codelists>>doc:sdmx:Glossary.Code list.WebHome]] of all [[versions>>doc:sdmx:Glossary.Version.WebHome]] for all agencies.
1.1	1257
2.18	1258	//AgencyID = AGENCY1
1.1	1259	Id = CODELIST1
2.18	1260	Version = %//
1.1	1261
15.1	1262	This subscribes to all [[versions>>doc:sdmx:Glossary.Version.WebHome]] of [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] CODELIST1 maintained by the agency
1.1	1263
2.18	1264	//AGENCY1
1.1	1265	AgencyID = AGENCY1
	1266	Id = %
2.18	1267	Version = %//
1.1	1268
15.1	1269	This subscribes to all [[versions>>doc:sdmx:Glossary.Version.WebHome]] of all [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] objects maintained by the agency
1.1	1270
2.18	1271	//AGENCY1
1.1	1272	AgencyID = %
	1273	Id = CODELIST1
2.18	1274	Version = %//
1.1	1275
15.1	1276	This subscribes to all [[versions>>doc:sdmx:Glossary.Version.WebHome]] of [[Codelist>>doc:sdmx:Glossary.Code list.WebHome]] CODELIST1 maintained by the agency
1.1	1277
2.18	1278	//AGENCY1//
1.1	1279
15.1	1280	Note that if the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is to the latest [[version>>doc:sdmx:Glossary.Version.WebHome]] then this can be achieved by the * character
1.1	1281
2.18	1282	//i.e. Version = *//
1.1	1283
15.1	1284	Note that a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] using the URN mechanism cannot use wildcard characters.
1.1	1285
	1286	=== 7.5.4 Structural Repository Events ===
	1287
15.1	1288	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>>doc:sdmx:Glossary.Code list.WebHome]], [[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]].
1.1	1289
	1290	=== 7.5.5 Registration Events ===
	1291
15.1	1292	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:
1.1	1293
9.5	1294	(% style="width:974.294px" %)
	1295	\|(% style="width:295px" %)Selector\|(% style="width:677px" %)Comment
15.1	1296	\|(% style="width:295px" %)DataProvider\|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered by the specified [[data provider>>doc:sdmx:Glossary.Data provider.WebHome]] will activate the notification.
	1297	\|(% style="width:295px" %)ProvisionAgreement\|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for the [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] will activate the notification.
	1298	\|(% style="width:295px" %)[[Dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (&[[Metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]])\|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for the specified [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] (or [[metadataflow>>doc:sdmx:Glossary.Metadataflow.WebHome]]) will activate the notification.
	1299	\|(% style="width:295px" %)DataStructureDefinition & MetadataStructureDefinition\|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for those [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]] (or [[metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]]) that are based on the specified [[Data Structure Definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] will activate the notification.
	1300	\|(% style="width:295px" %)[[Category>>doc:sdmx:Glossary.Category.WebHome]]\|(% style="width:677px" %)Any [[datasets>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] registered for those [[dataflows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[metadataflows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[provision agreements>>doc:sdmx:Glossary.Provision agreement.WebHome]] that are categorised by the [[category>>doc:sdmx:Glossary.Category.WebHome]].
1.1	1301
	1302	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
	1303
	1304	== 7.6 Notification ==
	1305
	1306	=== 7.6.1 Logical Class Diagram ===
	1307
3.1	1308	[[image:1747829675568-610.png]]
1.1	1309
3.1	1310	(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
	1311	Figure 20: Logical Class Diagram of the Notification
1.1	1312
15.1	1313	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.
1.1	1314
15.1	1315	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:
1.1	1316
	1317	* Date and time that the event occurred
15.1	1318	* The URN of the [[artefact>>doc:sdmx:Glossary.Artefact.WebHome]] that caused the event
	1319	* The URN of the [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that produced the [[notification>>doc:sdmx:Glossary.Notification.WebHome]]
1.1	1320	* Event Action: Add, Replace, or Delete.
	1321
15.1	1322	Additionally, supplementary information may be contained in the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] as detailed below.
1.1	1323
	1324	=== 7.6.2 Structural Event Component ===
	1325
15.1	1326	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).
1.1	1327
	1328	=== 7.6.3 Registration Event Component ===
	1329
15.1	1330	The [[notification>>doc:sdmx:Glossary.Notification.WebHome]] will contain the Registration.