Changes for page SDMX 3.0 Standards. Section 5. Registry Specification: Logical Functionality

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 4 removed)
  • 1747307906944-697.png
  • SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1edb9829.jpg
  • SDMX 3-0-0 SECTION 5 FINAL-1.0_en_8a88db1c.jpg
  • SDMX 3-0-0 SECTION 5 FINAL-1.0_en_99c4cc7e.jpg

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-SDMX STANDARDS: SECTION 5
	1	+1 Introduction

Content

...	...	@@ -1,17 +1,14 @@
1		-{{box title="**Contents**"}}
2		-{{toc/}}
3		-{{/box}}
	1	+**Revision History**
4	4
5		-= Revision History =
	3	+:
6	6
7	7	(((
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
	6	+|**Revision**|**Date**|**Contents**
	7	+|DRAFT 1.0|May 2021|Draft release updated for SDMX 3.0 for public consultation
	8	+|1.0|October 2021|Public release for SDMX 3.0
12	12	)))
13	13
14		-= 1 Introduction =
	11	+= {{id name="_Toc93831"/}}1 Introduction =
15	15
16	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	17
...	...	@@ -33,10 +33,12 @@
33	33
34	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	35
36		-* structural metadata repository
37		-* data and metadata registration
38		-* query
	33	+• structural metadata repository
39	39
	35	+• data and metadata registration
	36	+
	37	+• query
	38	+
40	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	41
42	42	= {{id name="_Toc93832"/}}2 Scope and Normative Status =
...	...	@@ -79,8 +79,7 @@
79	79
80	80	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_28806f51.jpg||height="539" width="443"]]
81	81
82		-(% class="wikigeneratedid" id="HFigure1:SchematicoftheBasicStructuralArtefactsintheSDMX-IM" %)
83		-**Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM**
	81	+====== Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM ======
84	84
85	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	86
...	...	@@ -107,7 +107,7 @@
107	107
108	108	Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
109	109
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.
	108	+• 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.
111	111
112	112	== {{id name="_Toc93838"/}}3.5 Discovery ==
113	113
...	...	@@ -166,8 +166,9 @@
166	166
167	167	The registry interfaces are invoked in one of two ways:
168	168
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.
	167	+*
	168	+*1. The interface is the name of the root node of the SDMX-ML document
	169	+*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.
171	171
172	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	173
...	...	@@ -243,22 +243,23 @@
243	243	* that the components (Dimensions, Attributes, Measures, Metadata Attributes, etc.) are consistent with the Data Structure Definition or Metadata Structure Definition;
244	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	245
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
	245	+|**Action Attribute Value**|**Behaviour**
	246	+|Append|Add this registration to the registry
	247	+|Replace|Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
	248	+|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
251	251
252	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	253
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.
	252	+|**Boolean Attribute**|**Behaviour if Value is “true”**
	253	+|indexTimeSeries|A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadataset registration)
	254	+|indexDataSet|(((
	255	+A compliant indexing application must index the range of actual
	256	+
	257	+(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.
	258	+
259	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	260	)))
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.
	261	+|indexReportingPeriod|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.
262	262
263	263	=== {{id name="_Toc93850"/}}5.2.5 Data and Reference Metadata Discovery ===
264	264
...	...	@@ -292,9 +292,8 @@
292	292
293	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	294
295		-(% style="width:757.294px" %)
296		-|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
297		-|(% style="width:188px" %)All|(% style="width:542px" %)(((
	295	+|**Interface**|**Behaviour**
	296	+|All|(((
298	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	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	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,14 +301,14 @@
301	301
302	302	a) Be a draft version.
303	303	)))
304		-|(% style="width:188px" %)**Interface**|(% style="width:542px" %)**Behaviour**
305		-|(% style="width:188px" %) |(% style="width:542px" %)(((
306		-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.
	303	+|**Interface**|**Behaviour**
	304	+||(((
	305	+b) Not be explicitly^^[[^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]]^^ referenced from any other object in the Registry.
307	307
308	308	4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
309	309	)))
310		-|(% 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.
311		-|(% 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.
	309	+|Structure submission|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.
	310	+|SubmitRegistrationRequest|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.
312	312
313	313	= {{id name="_Toc93853"/}}6 Identification of SDMX Objects =
314	314
...	...	@@ -335,31 +335,30 @@
335	335	* //Versionable//
336	336	* //Maintainable//
337	337
338		-:
	337	+:
339	339
340	340	(((
341		-(% style="width:1052.29px" %)
342		-|**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
343		-|(% rowspan="4" %)//Annotable//|(% style="width:241px" %)AnnotationTitle|(% style="width:156px" %)C|string|(% style="width:457px" %)
344		-|(% style="width:241px" %)AnnotationType|(% style="width:156px" %)C|string|(% style="width:457px" %)
345		-|(% style="width:241px" %)AnnotationURN|(% style="width:156px" %)C|string|(% style="width:457px" %)
346		-|(% style="width:241px" %)AnnotationText in the form of InternationalString|(% style="width:156px" %)C| |(% style="width:457px" %)This can have languagespecific variants
347		-|(% rowspan="4" %)//Identifiable//|(% style="width:241px" %)All content as for //Annotable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
348		-|(% style="width:241px" %)id|(% style="width:156px" %)M|string|(% style="width:457px" %)
349		-|(% style="width:241px" %)uri|(% style="width:156px" %)C|string|(% style="width:457px" %)
350		-|(% 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.
351		-|(% rowspan="3" %)//Nameable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
352		-|(% style="width:241px" %)Name in the form of InternationalString|(% style="width:156px" %)M|string|(% style="width:457px" %)This can have language specific variants.
353		-|(% style="width:241px" %)Description in the form of InternationalString|(% style="width:156px" %)C|string|(% style="width:457px" %)This can have language specific variants.
354		-|(% rowspan="4" %)//Versionable//|(% style="width:241px" %)All content as for //Identifiable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
355		-|(% style="width:241px" %)version|(% style="width:156px" %)M|string|(% style="width:457px" %)This is the version number according to SDMX versioning rules.
356		-|(% style="width:241px" %)validFrom|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
357		-|(% style="width:241px" %)validTo|(% style="width:156px" %)C|Date/time|(% style="width:457px" %)
358		-|//Maintainable//|(% style="width:241px" %)All content as for //Versionable// plus|(% style="width:156px" %) | |(% style="width:457px" %)
359		-| |(% 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.
360		-| |(% style="width:241px" %)serviceURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the service that can be queried for this resource.
361		-| |(% style="width:241px" %)structureURL|(% style="width:156px" %)C|string|(% style="width:457px" %)The url of the resource.
362		-| |(% 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.
	340	+|**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
	341	+|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
	342	+|AnnotationType|C|string|
	343	+|AnnotationURN|C|string|
	344	+|AnnotationText in the form of InternationalString|C||This can have languagespecific variants
	345	+|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus|||
	346	+|id|M|string|
	347	+|uri|C|string|
	348	+|urn|C|string|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.
	349	+|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus|||
	350	+|Name in the form of InternationalString|M|string|This can have language specific variants.
	351	+|Description in the form of InternationalString|C|string|This can have language specific variants.
	352	+|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus|||
	353	+|version|M|string|This is the version number according to SDMX versioning rules.
	354	+|validFrom|C|Date/time|
	355	+|validTo|C|Date/time|
	356	+|//Maintainable//|All content as for //Versionable// plus|||
	357	+||isExternalReference|C|boolean|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.
	358	+|\\|serviceURL|C|string|The url of the service that can be queried for this resource.
	359	+||structureURL|C|string|The url of the resource.
	360	+||(Maintenance) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
363	363	)))
364	364
365	365	**Table 1: Common Attributes of Object Types**
...	...	@@ -408,8 +408,32 @@
408	408
409	409	An example of this is shown in the XML snippet below:
410	410
411		-[[image:1747307906944-697.png]]
	409	+**<str:Codelists>**
412	412
	411	+**<str:Codelist id="CL_FREQ" agencyID="SDMX" version="1.0.0">**
	412	+
	413	+**<com:Name xml:lang="en">Standard frequency Codelist</com:Name>**
	414	+
	415	+**</str:Codelist>**
	416	+
	417	+**<str:Codelist id="CL_FREQ" agencyID="AA" version="1.0.0">**
	418	+
	419	+**<com:Name xml:lang="en">Codelist maintained by agency AA</com:Name>**
	420	+
	421	+**</str:Codelist>**
	422	+
	423	+**<str:Codelist id="CL_FREQ" agencyID="AA.CC" version="1.0.0">**
	424	+
	425	+**<com:Name xml:lang="en">Codelist maintained by the AA unit CC</com:Name>**
	426	+
	427	+**</str:Codelist>**
	428	+
	429	+**<str:Codelist id="CL_FREQ" agencyID="BB.CC" version="1.0.0">**
	430	+
	431	+**<com:Name xml:lang="en">Codelist maintained by the BB unit CC</com:Name>**
	432	+
	433	+**</str:Codelist>**
	434	+
413	413	**Figure 8: Example Showing Use of Agency Identifiers**
414	414
415	415	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.
...	...	@@ -416,16 +416,14 @@
416	416
417	417	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.
418	418
419		-=== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) ===
	441	+===== {{id name="_Toc93858"/}}6.2.2 Universal Resource Name (URN) =====
420	420
421		-==== 6.2.2.1 Introduction ====
	443	+**6.2.2.1 Introduction**
422	422
423	423	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.).
424	424
425		-==== 6.2.2.2 URN Structure ====
	447	+**6.2.2.2 URN Structure //__Case Rules for URN__//**//&nbsp;//
426	426
427		-===== **//__Case Rules for URN__//** =====
428		-
429	429	For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
430	430
431	431	SDMXprefix.SDMX-IM-package-name.class-name=agencyid:maintainedobjectid(maintainedobject-version).*containerobject-id.object-id
...	...	@@ -436,7 +436,7 @@
436	436
437	437	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.
438	438
439		-==== 6.2.2.3 Explanation of the generic structure ====
	459	+**6.2.2.3 Explanation of the generic structure**
440	440
441	441	In the explanation below the actual object that is the target of the URN is called the **actual object**.
442	442
...	...	@@ -446,32 +446,10 @@
446	446
447	447	The packages are:
448	448
449		-base
	469	+base codelist conceptscheme datastructure categoryscheme registry metadatastructure process structuremapping transformation
450	450
451		-codelist
	471	+**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. **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. **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.
452	452
453		-conceptscheme
454		-
455		-datastructure
456		-
457		-categoryscheme
458		-
459		-registry
460		-
461		-metadatastructure
462		-
463		-process
464		-
465		-structuremapping
466		-
467		-transformation
468		-
469		-**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.
470		-
471		-**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.
472		-
473		-**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.
474		-
475	475	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.
476	476
477	477	For example, the sequence is agency:DSDid(version).DimensionId and not agency:DSDid(version).DimensionDescriptorId.DimensionId.
...	...	@@ -478,7 +478,7 @@
478	478
479	479	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.
480	480
481		-===== //__**Generic Examples of the URN Structure**__// =====
	479	+//__**Generic Examples of the URN Structure**__//
482	482
483	483	__Actual object is a maintainable__
484	484
...	...	@@ -533,86 +533,85 @@
533	533
534	534	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.
535	535
536		-=== {{id name="_Toc93859"/}}6.2.3 Table of SDMX-IM Packages and Classes ===
	534	+===== {{id name="_Toc93859"/}}6.2.3 Table of SDMX-IM Packages and Classes =====
537	537
538	538	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.
539	539
540		-(% style="width:651.294px" %)
541		-|(% style="width:134px" %)**Package**|(% style="width:502px" %)**URN class name (model class name where this is different)**
542		-|(% style="width:134px" %)base|(% style="width:502px" %)Agency
543		-|(% style="width:134px" %) |(% style="width:502px" %)AgencyScheme
544		-|(% style="width:134px" %) |(% style="width:502px" %)DataConsumer
545		-|(% style="width:134px" %) |(% style="width:502px" %)DataConsumerScheme
546		-|(% style="width:134px" %) |(% style="width:502px" %)DataProvider
547		-|(% style="width:134px" %) |(% style="width:502px" %)DataProviderScheme
548		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataProvider
549		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataProviderScheme
550		-|(% style="width:134px" %) |(% style="width:502px" %)OrganisationUnit
551		-|(% style="width:134px" %) |(% style="width:502px" %)OrganisationUnitScheme
552		-|(% style="width:134px" %)datastructure|(% style="width:502px" %)AttributeDescriptor
553		-|(% style="width:134px" %) |(% style="width:502px" %)DataAttribute
554		-|(% style="width:134px" %) |(% style="width:502px" %)Dataflow
555		-|(% style="width:134px" %) |(% style="width:502px" %)DataStructure (DataStructureDefinition)
556		-|(% style="width:134px" %) |(% style="width:502px" %)Dimension
557		-|(% style="width:134px" %) |(% style="width:502px" %)DimensionDescriptor
558		-|(% style="width:134px" %) |(% style="width:502px" %)GroupDimensionDescriptor
559		-|(% style="width:134px" %) |(% style="width:502px" %)Measure
560		-|(% style="width:134px" %) |(% style="width:502px" %)MeasureDescriptor
561		-|(% style="width:134px" %) |(% style="width:502px" %)TimeDimension
562		-|(% style="width:134px" %) |(% style="width:502px" %)
563		-|(% style="width:134px" %)metadatastructure|(% style="width:502px" %)MetadataAttribute
564		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataAttributeDescriptor
565		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataStructure MetadataStructureDefinition)
566		-|(% style="width:134px" %) |(% style="width:502px" %)Metadataflow
567		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataSet
568		-|(% style="width:134px" %) |(% style="width:502px" %)
569		-|(% style="width:134px" %)process|(% style="width:502px" %)Process
570		-|(% style="width:134px" %) |(% style="width:502px" %)ProcessStep
571		-|(% style="width:134px" %) |(% style="width:502px" %)Transition
572		-|(% style="width:134px" %) |(% style="width:502px" %)
573		-|(% style="width:134px" %)registry|(% style="width:502px" %)DataConstraint
574		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataConstraint
575		-|(% style="width:134px" %) |(% style="width:502px" %)MetadataProvisionAgreement
576		-|(% style="width:134px" %) |(% style="width:502px" %)ProvisionAgreement
577		-|(% style="width:134px" %) |(% style="width:502px" %)Subscription
578		-|(% style="width:134px" %) |(% style="width:502px" %)
579		-|(% style="width:134px" %)structuremapping|(% style="width:502px" %)CategorySchemeMap
580		-|(% style="width:134px" %) |(% style="width:502px" %)ConceptSchemeMap
581		-|(% style="width:134px" %) |(% style="width:502px" %)OrganisationSchemeMap
582		-|(% style="width:134px" %) |(% style="width:502px" %)ReportingTaxonomyMap
583		-|(% style="width:134px" %) |(% style="width:502px" %)RepresentationMap
584		-|(% style="width:134px" %) |(% style="width:502px" %)StructureMap
585		-|(% style="width:134px" %) |(% style="width:502px" %)
586		-|(% style="width:134px" %)codelist|(% style="width:502px" %)Code
587		-|(% style="width:134px" %) |(% style="width:502px" %)Codelist
588		-|(% style="width:134px" %) |(% style="width:502px" %)HierarchicalCode
589		-|(% style="width:134px" %) |(% style="width:502px" %)Hierarchy
590		-|(% style="width:134px" %) |(% style="width:502px" %)HierarchyAssociation
591		-|(% style="width:134px" %) |(% style="width:502px" %)Level
592		-|(% style="width:134px" %) |(% style="width:502px" %)ValueList
593		-|(% style="width:134px" %) |(% style="width:502px" %)
594		-|(% style="width:134px" %)categoryscheme|(% style="width:502px" %)Categorisation
595		-|(% style="width:134px" %) |(% style="width:502px" %)Category
596		-|(% style="width:134px" %) |(% style="width:502px" %)CategoryScheme
597		-|(% style="width:134px" %) |(% style="width:502px" %)ReportingCategory
598		-|(% style="width:134px" %) |(% style="width:502px" %)ReportingTaxonomy
599		-|(% style="width:134px" %)conceptscheme|(% style="width:502px" %)Concept
600		-|(% style="width:134px" %) |(% style="width:502px" %)ConceptScheme
601		-|(% style="width:134px" %) |(% style="width:502px" %)
602		-|(% style="width:134px" %)transformation|(% style="width:502px" %)CustomType
603		-|(% style="width:134px" %) |(% style="width:502px" %)CustomTypeScheme
604		-|(% style="width:134px" %) |(% style="width:502px" %)NamePersonalisation
605		-|(% style="width:134px" %) |(% style="width:502px" %)NamePersonalisationScheme
606		-|(% style="width:134px" %) |(% style="width:502px" %)Ruleset
607		-|(% style="width:134px" %) |(% style="width:502px" %)RulesetScheme
608		-|(% style="width:134px" %) |(% style="width:502px" %)Transformation
609		-|(% style="width:134px" %) |(% style="width:502px" %)TransformationScheme
610		-|(% style="width:134px" %) |(% style="width:502px" %)UserDefinedOperator
611		-|(% style="width:134px" %) |(% style="width:502px" %)UserDefinedOperatorScheme
612		-|(% style="width:134px" %) |(% style="width:502px" %)VtlCodelistMapping
613		-|(% style="width:134px" %) |(% style="width:502px" %)VtlConceptMapping
614		-|(% style="width:134px" %) |(% style="width:502px" %)VtlDataflowMapping
615		-|(% style="width:134px" %) |(% style="width:502px" %)VtlMappingScheme
	538	+|**Package**|**URN class name (model class name where this is different)**
	539	+|base|Agency
	540	+||AgencyScheme
	541	+||DataConsumer
	542	+||DataConsumerScheme
	543	+||DataProvider
	544	+||DataProviderScheme
	545	+||MetadataProvider
	546	+||MetadataProviderScheme
	547	+||OrganisationUnit
	548	+||OrganisationUnitScheme
	549	+|datastructure|AttributeDescriptor
	550	+||DataAttribute
	551	+||Dataflow
	552	+||DataStructure (DataStructureDefinition)
	553	+||Dimension
	554	+||DimensionDescriptor
	555	+||GroupDimensionDescriptor
	556	+||Measure
	557	+||MeasureDescriptor
	558	+||TimeDimension
	559	+||
	560	+|metadatastructure|MetadataAttribute
	561	+||MetadataAttributeDescriptor
	562	+||MetadataStructure MetadataStructureDefinition)
	563	+||Metadataflow
	564	+||MetadataSet
	565	+||
	566	+|process|Process
	567	+||ProcessStep
	568	+||Transition
	569	+||
	570	+|registry|DataConstraint
	571	+||MetadataConstraint
	572	+||MetadataProvisionAgreement
	573	+||ProvisionAgreement
	574	+||Subscription
	575	+||
	576	+|structuremapping|CategorySchemeMap
	577	+||ConceptSchemeMap
	578	+||OrganisationSchemeMap
	579	+||ReportingTaxonomyMap
	580	+||RepresentationMap
	581	+||StructureMap
	582	+||
	583	+|codelist|Code
	584	+||Codelist
	585	+||HierarchicalCode
	586	+||Hierarchy
	587	+||HierarchyAssociation
	588	+||Level
	589	+||ValueList
	590	+||
	591	+|categoryscheme|Categorisation
	592	+||Category
	593	+||CategoryScheme
	594	+||ReportingCategory
	595	+||ReportingTaxonomy
	596	+|conceptscheme|Concept
	597	+||ConceptScheme
	598	+||
	599	+|transformation|CustomType
	600	+||CustomTypeScheme
	601	+||NamePersonalisation
	602	+||NamePersonalisationScheme
	603	+||Ruleset
	604	+||RulesetScheme
	605	+||Transformation
	606	+||TransformationScheme
	607	+||UserDefinedOperator
	608	+||UserDefinedOperatorScheme
	609	+||VtlCodelistMapping
	610	+||VtlConceptMapping
	611	+||VtlDataflowMapping
	612	+||VtlMappingScheme
616	616
617	617	**Table 2: SDMX-IM Packages and Contained Classes**
618	618
...	...	@@ -625,7 +625,7 @@
625	625	urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
626	626
627	627	|**Classname**|**Ending URN pattern**|**Example**
628		-|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
	625	+|Agency^^[[^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]]^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
629	629	|//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
630	630	|//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
631	631	|Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
...	...	@@ -778,22 +778,22 @@
778	778	The following table lists the Maintainable Artefacts.
779	779
780	780	|(% colspan="2" %)**Maintainable Artefacts**|**Content**
781		-|**Abstract Class**|**Concrete Class**|
	778	+|**Abstract Class**|**Concrete Class**|
782	782	|Item Scheme|Codelist|Code
783		-| |Concept Scheme|Concept
784		-| |Category Scheme|Category
785		-| |Organisation Unit Scheme|Organisation Unit
786		-| |Agency Scheme|Agency
787		-| |Data Provider Scheme|Data Provider
788		-| |Metadata Provider Scheme|Metadata Provider
789		-| |Data Consumer Scheme|Data Consumer
790		-| |Reporting Taxonomy|Reporting Category
791		-| |Transformation Scheme|Transformation
792		-| |Custom Type Scheme|Custom Type
793		-| |Name Personalisation Scheme|Name Personalisation
794		-| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
795		-| |Ruleset Scheme|Ruleset
796		-| |User Defined Operator Scheme|User Defined Operator
	780	+||Concept Scheme|Concept
	781	+||Category Scheme|Category
	782	+||Organisation Unit Scheme|Organisation Unit
	783	+||Agency Scheme|Agency
	784	+||Data Provider Scheme|Data Provider
	785	+||Metadata Provider Scheme|Metadata Provider
	786	+||Data Consumer Scheme|Data Consumer
	787	+||Reporting Taxonomy|Reporting Category
	788	+||Transformation Scheme|Transformation
	789	+||Custom Type Scheme|Custom Type
	790	+||Name Personalisation Scheme|Name Personalisation
	791	+||Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
	792	+||Ruleset Scheme|Ruleset
	793	+||User Defined Operator Scheme|User Defined Operator
797	797	|Enumerated List|ValueList|Value Item
798	798	|Structure|Data Structure Definition|(((
799	799	Dimension Descriptor
...	...	@@ -812,9 +812,9 @@
812	812
813	813	Measure
814	814	)))
815		-| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
816		-|Structure Usage|Dataflow|
817		-| |Metadataflow|
	812	+||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
	813	+|Structure Usage|Dataflow|
	814	+||Metadataflow|
818	818	|None|Process|Process Step
819	819	|None|Structure Map|(((
820	820	Component Map
...	...	@@ -825,14 +825,14 @@
825	825	)))
826	826	|None|Representation Map|Representation Mapping
827	827	|Item Scheme Map|Organisation Scheme Map|Item Map
828		-| |Concept Scheme Map|Item Map
829		-| |Category Scheme Map|Item Map
830		-| |Reporting Taxonomy Map|Item Map
831		-|None|Provision Agreement|
832		-|None|Metadata Provision Agreement|
	825	+||Concept Scheme Map|Item Map
	826	+||Category Scheme Map|Item Map
	827	+||Reporting Taxonomy Map|Item Map
	828	+|None|Provision Agreement|
	829	+|None|Metadata Provision Agreement|
833	833	|None|Hierarchy|Hierarchical Code
834		-|None|Hierarchy Association|
835		-|None|Categorisation|
	831	+|None|Hierarchy Association|
	832	+|None|Categorisation|
836	836
837	837	**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
838	838
...	...	@@ -842,7 +842,7 @@
842	842
843	843	• 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)
844	844
845		-• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
	842	+• All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^
846	846
847	847	• All types of Structure (Data Structure Definition, Metadata Structure Definition)
848	848
...	...	@@ -974,7 +974,7 @@
974	974
975	975	The Registration has an action attribute which takes one of the following values:
976	976
977		-:
	974	+:
978	978
979	979	(((
980	980	|**Action Attribute Value**|**Behaviour**
...	...	@@ -1001,7 +1001,7 @@
1001	1001
1002	1002	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.
1003	1003
1004		-:
	1001	+:
1005	1005
1006	1006	(((
1007	1007	|**Indexing Required**|**Registration Process Activity**
...	...	@@ -1066,7 +1066,7 @@
1066	1066	1. A selector which specifies which type of events are of interest. The set of event types is:
1067	1067
1068	1068	:
1069		-::
	1066	+::
1070	1070
1071	1071	(((
1072	1072	|**Event Type**|**Comment**
...	...	@@ -1140,7 +1140,7 @@
1140	1140
1141	1141	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:
1142	1142
1143		-:
	1140	+:
1144	1144
1145	1145	(((
1146	1146	|**Selector**|**Comment**
...	...	@@ -1187,5 +1187,3 @@
1187	1187	IMF.SubAgency1
1188	1188
1189	1189	[[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.
1190		-
1191		-{{putFootnotes/}}

1747307906944-697.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-37.9 KB

Content

SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1edb9829.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-50.9 KB

Content

SDMX 3-0-0 SECTION 5 FINAL-1.0_en_8a88db1c.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-184.8 KB

Content

SDMX 3-0-0 SECTION 5 FINAL-1.0_en_99c4cc7e.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.helena

Size

...	...	@@ -1,1 +1,0 @@
1		-126.4 KB

Content