Wiki source code of SDMX STANDARDS: SECTION 5

Version 29.5 by Helena on 2025/05/16 14:15

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