Changes for page SDMX 3.1 Standards. Section 5. Registry Specification: Logical Interfaces

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • SDMX 3.1 Section 5_en_c63d10ab.jpg

Details

Page properties

Title

...	...	@@ -1,1 +1,0 @@
1		-1 Introduction

Content

...	...	@@ -1,15 +1,16 @@
	1	+{{box title="**Contents**"}}
	2	+{{toc/}}
	3	+{{/box}}
	4	+
1	1	**Revision History**
2	2
3		-:
	7	+(% style="width:824.835px" %)
	8	+|(% style="width:184px" %)**Revision**|(% style="width:195px" %)**Date**|(% style="width:442px" %)**Contents**
	9	+|(% style="width:184px" %)DRAFT 1.0|(% style="width:195px" %)December 2024|(% style="width:442px" %)Draft release updated for SDMX 3.1 for public consultation
	10	+|(% style="width:184px" %)1.0|(% style="width:195px" %)May 2025|(% style="width:442px" %)Public release for SDMX 3.1
4	4
5		-(((
6		-|**Revision**|**Date**|**Contents**
7		-|DRAFT 1.0|December 2024|Draft release updated for SDMX 3.1 for public consultation
8		-|1.0|May 2025|Public release for SDMX 3.1
9		-)))
	12	+= 1 Introduction =
10	10
11		-= {{id name="_Toc90780"/}}1 Introduction =
12		-
13	13	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:
14	14
15	15	* the availability of an abstract information model capable of supporting time series and cross-sectional data, structural metadata, and reference metadata (SDMX-IM)
...	...	@@ -30,15 +30,13 @@
30	30
31	31	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:
32	32
33		-• structural metadata repository
	34	+* structural metadata repository
	35	+* data and metadata registration
	36	+* query
34	34
35		-• data and metadata registration
36		-
37		-• query
38		-
39	39	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.
40	40
41		-= {{id name="_Toc90781"/}}2 Scope and Normative Status =
	40	+= 2 Scope and Normative Status =
42	42
43	43	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.
44	44
...	...	@@ -55,9 +55,9 @@
55	55
56	56	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.
57	57
58		-= {{id name="_Toc90782"/}}3 Scope of the SDMX Registry/Repository =
	57	+= 3 Scope of the SDMX Registry/Repository =
59	59
60		-=== {{id name="_Toc90783"/}}3.1 Objective ===
	59	+== 3.1 Objective ==
61	61
62	62	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:
63	63
...	...	@@ -64,7 +64,7 @@
64	64	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.
65	65	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.
66	66
67		-=== {{id name="_Toc90784"/}}3.2 Structural Metadata ===
	66	+== 3.2 Structural Metadata ==
68	68
69	69	Setting up structural metadata and the exchange context (referred to as “data provisioning”) involves the following steps for maintenance agencies:
70	70
...	...	@@ -271,7 +271,7 @@
271	271
272	272	1. Be a draft version.
273	273
274		-b) Not be explicitly^^[[^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]]^^ referenced from any other object in the Registry.
	273	+b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
275	275
276	276	4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
277	277	)))
...	...	@@ -309,47 +309,47 @@
309	309
310	310	• //Maintainable//
311	311
312		-||(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
313		-||(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
314		-||(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
315		-||(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
316		-||(% colspan="2" %)(((
	311	+| |(% colspan="2" %)**Object Type**|(% colspan="2" %)**Data Attributes**|(% colspan="2" %)**Status**|(% colspan="2" %)**Data type**|(% colspan="2" %)**Notes**
	312	+| |(% colspan="2" rowspan="4" %)//Annotable//|(% colspan="2" %)AnnotationTitle|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
	313	+| |(% colspan="2" %)AnnotationType|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
	314	+| |(% colspan="2" %)AnnotationURN|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
	315	+| |(% colspan="2" %)(((
317	317	AnnotationText in the form of
318	318
319	319	InternationalString
320		-)))|(% colspan="2" %)C|(% colspan="2" %)|(% colspan="2" %)This can have languagespecific variants
321		-||(% colspan="2" rowspan="4" %)//Identifiable//|(% colspan="2" %)All content as for //Annotable// plus|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)
322		-||(% colspan="2" %)id|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)
323		-||(% colspan="2" %)uri|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
324		-||(% colspan="2" %)urn|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)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.
325		-||(% colspan="2" rowspan="3" %)//Nameable//|(% colspan="2" %)(((
	319	+)))|(% colspan="2" %)C|(% colspan="2" %) |(% colspan="2" %)This can have languagespecific variants
	320	+| |(% colspan="2" rowspan="4" %)//Identifiable//|(% colspan="2" %)All content as for //Annotable// plus|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
	321	+| |(% colspan="2" %)id|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)
	322	+| |(% colspan="2" %)uri|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)
	323	+| |(% colspan="2" %)urn|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)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.
	324	+| |(% colspan="2" rowspan="3" %)//Nameable//|(% colspan="2" %)(((
326	326	All content as for
327	327
328	328	//Identifiable// plus
329		-)))|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)
330		-||(% colspan="2" %)(((
	328	+)))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
	329	+| |(% colspan="2" %)(((
331	331	Name in the form of
332	332
333	333	InternationalString
334	334	)))|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants.
335		-||(% colspan="2" %)(((
	334	+| |(% colspan="2" %)(((
336	336	Description in the form of
337	337
338	338	InternationalString
339	339	)))|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)This can have language specific variants.
340		-||(% colspan="2" rowspan="4" %)//Versionable//|(% colspan="2" %)(((
	339	+| |(% colspan="2" rowspan="4" %)//Versionable//|(% colspan="2" %)(((
341	341	All content as for
342	342
343	343	//Identifiable// plus
344		-)))|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)
345		-||(% colspan="2" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the version number according to SDMX versioning rules.
346		-||(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
347		-||(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
348		-|(% colspan="2" rowspan="5" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %)|(% colspan="2" %)|(% colspan="2" %)|
349		-|(% colspan="2" %)isExternalReference|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid SDMX-ML file.|
350		-|(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource.|
351		-|(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.|
352		-|(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.|
	343	+)))|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
	344	+| |(% colspan="2" %)version|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)This is the version number according to SDMX versioning rules.
	345	+| |(% colspan="2" %)validFrom|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
	346	+| |(% colspan="2" %)validTo|(% colspan="2" %)C|(% colspan="2" %)Date/time|(% colspan="2" %)
	347	+|(% colspan="2" rowspan="5" %)//Maintainable//|(% colspan="2" %)All content as for //Versionable// plus|(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %) |
	348	+|(% colspan="2" %)isExternalReference|(% colspan="2" %)C|(% colspan="2" %)boolean|(% colspan="2" %)Value of “true” indicates that the actual resource is held outside of this registry. The actual reference is given in the registry URI or the structureURL, each of which must return a valid SDMX-ML file.|
	349	+|(% colspan="2" %)serviceURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the service that can be queried for this resource.|
	350	+|(% colspan="2" %)structureURL|(% colspan="2" %)C|(% colspan="2" %)string|(% colspan="2" %)The url of the resource.|
	351	+|(% colspan="2" %)(Maintenance) organisationId|(% colspan="2" %)M|(% colspan="2" %)string|(% colspan="2" %)The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.|
353	353
354	354	**Table 1: Common Attributes of Object Types**
355	355
...	...	@@ -511,92 +511,92 @@
511	511
512	512	|**Package**|**URN class name (model class name where this is different)**
513	513	|base|Agency
514		-||AgencyScheme
515		-||DataConsumer
516		-||DataConsumerScheme
517		-||DataProvider
518		-||DataProviderScheme
519		-||MetadataProvider
520		-||MetadataProviderScheme
521		-||OrganisationUnit
522		-||OrganisationUnitScheme
523		-||
	513	+| |AgencyScheme
	514	+| |DataConsumer
	515	+| |DataConsumerScheme
	516	+| |DataProvider
	517	+| |DataProviderScheme
	518	+| |MetadataProvider
	519	+| |MetadataProviderScheme
	520	+| |OrganisationUnit
	521	+| |OrganisationUnitScheme
	522	+| |
524	524	|datastructure|AttributeDescriptor
525		-||DataAttribute
526		-||Dataflow
527		-||DataStructure (DataStructureDefinition)
528		-||Dimension
529		-||DimensionDescriptor
530		-||GroupDimensionDescriptor
531		-||Measure
532		-||MeasureDescriptor
533		-||TimeDimension
534		-||
	524	+| |DataAttribute
	525	+| |Dataflow
	526	+| |DataStructure (DataStructureDefinition)
	527	+| |Dimension
	528	+| |DimensionDescriptor
	529	+| |GroupDimensionDescriptor
	530	+| |Measure
	531	+| |MeasureDescriptor
	532	+| |TimeDimension
	533	+| |
535	535	|metadatastructure|MetadataAttribute
536		-||MetadataAttributeDescriptor
537		-||(((
	535	+| |MetadataAttributeDescriptor
	536	+| |(((
538	538	MetadataStructure
539	539
540	540	(MetadataStructureDefinition)
541	541	)))
542	542
543		-:
	542	+:
544	544
545	545	(((
546	546	|**Package**|**URN class name (model class name where this is different)**
547		-||Metadataflow
548		-||MetadataSet
549		-||
	546	+| |Metadataflow
	547	+| |MetadataSet
	548	+| |
550	550	|process|Process
551		-||ProcessStep
552		-||Transition
553		-||
	550	+| |ProcessStep
	551	+| |Transition
	552	+| |
554	554	|registry|DataConstraint
555		-||MetadataConstraint
556		-||MetadataProvisionAgreement
557		-||ProvisionAgreement
558		-||Subscription
559		-||
	554	+| |MetadataConstraint
	555	+| |MetadataProvisionAgreement
	556	+| |ProvisionAgreement
	557	+| |Subscription
	558	+| |
560	560	|structuremapping|CategorySchemeMap
561		-||ConceptSchemeMap
562		-||OrganisationSchemeMap
563		-||ReportingTaxonomyMap
564		-||RepresentationMap
565		-||StructureMap
566		-||
	560	+| |ConceptSchemeMap
	561	+| |OrganisationSchemeMap
	562	+| |ReportingTaxonomyMap
	563	+| |RepresentationMap
	564	+| |StructureMap
	565	+| |
567	567	|codelist|Code
568		-||Codelist
569		-||HierarchicalCode
570		-||Hierarchy
571		-||HierarchyAssociation
572		-||Level
573		-||ValueList
574		-||
	567	+| |Codelist
	568	+| |HierarchicalCode
	569	+| |Hierarchy
	570	+| |HierarchyAssociation
	571	+| |Level
	572	+| |ValueList
	573	+| |
575	575	|categoryscheme|Categorisation
576		-||Category
577		-||CategoryScheme
578		-||ReportingCategory
579		-||ReportingTaxonomy
	575	+| |Category
	576	+| |CategoryScheme
	577	+| |ReportingCategory
	578	+| |ReportingTaxonomy
580	580	|**Package**|**URN class name (model class name where this is different)**
581		-||
	580	+| |
582	582	|conceptscheme|Concept
583		-||ConceptScheme
584		-||
	582	+| |ConceptScheme
	583	+| |
585	585	|transformation|CustomType
586		-||CustomTypeScheme
587		-||NamePersonalisation
588		-||NamePersonalisationScheme
589		-||Ruleset
590		-||RulesetScheme
591		-||Transformation
592		-||TransformationScheme
593		-||UserDefinedOperator
594		-||UserDefinedOperatorScheme
595		-||VtlCodelistMapping
596		-||VtlConceptMapping
597		-||VtlDataflowMapping
598		-||VtlMappingScheme
599		-||
	585	+| |CustomTypeScheme
	586	+| |NamePersonalisation
	587	+| |NamePersonalisationScheme
	588	+| |Ruleset
	589	+| |RulesetScheme
	590	+| |Transformation
	591	+| |TransformationScheme
	592	+| |UserDefinedOperator
	593	+| |UserDefinedOperatorScheme
	594	+| |VtlCodelistMapping
	595	+| |VtlConceptMapping
	596	+| |VtlDataflowMapping
	597	+| |VtlMappingScheme
	598	+| |
600	600	)))
601	601
602	602	**Table 2: SDMX-IM Packages and Contained Classes**
...	...	@@ -610,7 +610,7 @@
610	610	urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
611	611
612	612	|**Classname**|**Ending URN pattern**|**Example**
613		-|Agency^^[[^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]]^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
	612	+|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
614	614	|//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
615	615	|//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
616	616	|Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
...	...	@@ -769,22 +769,22 @@
769	769	The following table lists the Maintainable Artefacts.
770	770
771	771	|(% colspan="2" %)**Maintainable Artefacts**|**Content**
772		-|**Abstract Class**|**Concrete Class**|
	771	+|**Abstract Class**|**Concrete Class**|
773	773	|Item Scheme|Codelist|Code
774		-||Concept Scheme|Concept
775		-||Category Scheme|Category
776		-||Organisation Unit Scheme|Organisation Unit
777		-||Agency Scheme|Agency
778		-||Data Provider Scheme|Data Provider
779		-||Metadata Provider Scheme|Metadata Provider
780		-||Data Consumer Scheme|Data Consumer
781		-||Reporting Taxonomy|Reporting Category
782		-||Transformation Scheme|Transformation
783		-||Custom Type Scheme|Custom Type
784		-||Name Personalisation Scheme|Name Personalisation
785		-||Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
786		-||Ruleset Scheme|Ruleset
787		-||User Defined Operator Scheme|User Defined Operator
	773	+| |Concept Scheme|Concept
	774	+| |Category Scheme|Category
	775	+| |Organisation Unit Scheme|Organisation Unit
	776	+| |Agency Scheme|Agency
	777	+| |Data Provider Scheme|Data Provider
	778	+| |Metadata Provider Scheme|Metadata Provider
	779	+| |Data Consumer Scheme|Data Consumer
	780	+| |Reporting Taxonomy|Reporting Category
	781	+| |Transformation Scheme|Transformation
	782	+| |Custom Type Scheme|Custom Type
	783	+| |Name Personalisation Scheme|Name Personalisation
	784	+| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
	785	+| |Ruleset Scheme|Ruleset
	786	+| |User Defined Operator Scheme|User Defined Operator
788	788	|Enumerated List|ValueList|Value Item
789	789	|Structure|Data Structure Definition|(((
790	790	Dimension Descriptor
...	...	@@ -803,9 +803,9 @@
803	803
804	804	Measure
805	805	)))
806		-||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
807		-|Structure Usage|Dataflow|
808		-||Metadataflow|
	805	+| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
	806	+|Structure Usage|Dataflow|
	807	+| |Metadataflow|
809	809	|None|Process|Process Step
810	810	|None|Structure Map|(((
811	811	Component Map
...	...	@@ -816,16 +816,16 @@
816	816	)))
817	817	|None|Representation Map|Representation Mapping
818	818	|Item Scheme Map|Organisation Scheme Map|Item Map
819		-||Concept Scheme Map|Item Map
820		-||Category Scheme Map|Item Map
821		-||Reporting Taxonomy Map|Item Map
822		-|None|Provision Agreement|
823		-|None|Metadata Provision Agreement|
	818	+| |Concept Scheme Map|Item Map
	819	+| |Category Scheme Map|Item Map
	820	+| |Reporting Taxonomy Map|Item Map
	821	+|None|Provision Agreement|
	822	+|None|Metadata Provision Agreement|
824	824	|None|Hierarchy|Hierarchical Code
825		-|None|Hierarchy Association|
826		-|None|Categorisation|
	824	+|None|Hierarchy Association|
	825	+|None|Categorisation|
827	827	|Constraint|Data Constraint|DataKeySet
828		-|||CubeRegion
	827	+| | |CubeRegion
829	829	|Constraint|Metadata Constraint|MetadataTargetRegion
830	830
831	831	**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
...	...	@@ -835,7 +835,7 @@
835	835	The artefacts included in the structural definitions are:
836	836
837	837	* 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)
838		-* All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^
	837	+* All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
839	839	* All types of Structure (Data Structure Definition, Metadata Structure Definition)
840	840	* All types of Structure Usage (Dataflow, Metadataflow)
841	841
...	...	@@ -971,7 +971,7 @@
971	971
972	972	The Registration has an action attribute which takes one of the following values:
973	973
974		-:
	973	+:
975	975
976	976	(((
977	977	|**Action Attribute Value**|**Behaviour**
...	...	@@ -996,7 +996,7 @@
996	996
997	997	https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md
998	998
999		-:
	998	+:
1000	1000
1001	1001	(((
1002	1002	|**Indexing Required**|**Registration Process Activity**
...	...	@@ -1019,7 +1019,7 @@
1019	1019	Components of the Constraints model in the
1020	1020	)))
1021	1021	|**Indexing Required**|**Registration Process Activity**
1022		-||SDMX-IM. Note that the content is not stored in the Selection Value.
	1021	+| |SDMX-IM. Note that the content is not stored in the Selection Value.
1023	1023	)))
1024	1024
1025	1025	Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
...	...	@@ -1062,7 +1062,7 @@
1062	1062	1. A selector which specifies which type of events are of interest. The set of event types is:
1063	1063
1064	1064	:
1065		-::
	1064	+::
1066	1066
1067	1067	(((
1068	1068	|**Event Type**|**Comment**
...	...	@@ -1136,7 +1136,7 @@
1136	1136
1137	1137	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:
1138	1138
1139		-:
	1138	+:
1140	1140
1141	1141	(((
1142	1142	|**Selector**|**Comment**

SDMX 3.1 Section 5_en_c63d10ab.jpg

Author

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

Size

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

Content