Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 16.1
edited by Helena
on 2025/05/15 14:05
Change comment: There is no comment for this version
To version 21.5
edited by Helena
on 2025/05/15 14:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -1 Introduction
1 +SDMX STANDARDS: SECTION 5
Content
... ... @@ -1,14 +1,17 @@
1 -**Revision History**
1 +{{box title="**Contents**"}}
2 +{{toc/}}
3 +{{/box}}
2 2  
3 -:
5 += Revision History =
4 4  
5 5  (((
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
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
9 9  )))
10 10  
11 -= {{id name="_Toc93831"/}}1 Introduction =
14 += 1 Introduction =
12 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  
... ... @@ -30,12 +30,10 @@
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
36 +* structural metadata repository
37 +* data and metadata registration
38 +* 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 41  = {{id name="_Toc93832"/}}2 Scope and Normative Status =
... ... @@ -78,7 +78,8 @@
78 78  
79 79  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_28806f51.jpg||height="539" width="443"]]
80 80  
81 -====== Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM ======
82 +(% class="wikigeneratedid" id="HFigure1:SchematicoftheBasicStructuralArtefactsintheSDMX-IM" %)
83 +**Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM**
82 82  
83 83  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:
84 84  
... ... @@ -105,7 +105,7 @@
105 105  
106 106  Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
107 107  
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.
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.
109 109  
110 110  == {{id name="_Toc93838"/}}3.5 Discovery ==
111 111  
... ... @@ -164,9 +164,8 @@
164 164  
165 165  The registry interfaces are invoked in one of two ways:
166 166  
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.
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.
170 170  
171 171  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.
172 172  
... ... @@ -301,8 +301,8 @@
301 301  a) Be a draft version.
302 302  )))
303 303  |**Interface**|**Behaviour**
304 -||(((
305 -b) Not be explicitly^^[[^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]]^^ referenced from any other object in the Registry.
305 +| |(((
306 +b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
306 306  
307 307  4) The semantic versioning rules in the SDMX documentation MUST be obeyed.
308 308  )))
... ... @@ -334,30 +334,30 @@
334 334  * //Versionable//
335 335  * //Maintainable//
336 336  
337 -:
338 +:
338 338  
339 339  (((
340 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|
342 +|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
343 +|AnnotationType|C|string|
344 +|AnnotationURN|C|string|
345 +|AnnotationText in the form of InternationalString|C| |This can have languagespecific variants
346 +|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus| | |
347 +|id|M|string|
348 +|uri|C|string|
348 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 +|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus| | |
350 350  |Name in the form of InternationalString|M|string|This can have language specific variants.
351 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 +|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus| | |
353 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.
355 +|validFrom|C|Date/time|
356 +|validTo|C|Date/time|
357 +|//Maintainable//|All content as for //Versionable// plus| | |
358 +| |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.
359 +| |serviceURL|C|string|The url of the service that can be queried for this resource.
360 +| |structureURL|C|string|The url of the resource.
361 +| |(Maintenance) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
361 361  )))
362 362  
363 363  **Table 1: Common Attributes of Object Types**
... ... @@ -537,79 +537,79 @@
537 537  
538 538  |**Package**|**URN class name (model class name where this is different)**
539 539  |base|Agency
540 -||AgencyScheme
541 -||DataConsumer
542 -||DataConsumerScheme
543 -||DataProvider
544 -||DataProviderScheme
545 -||MetadataProvider
546 -||MetadataProviderScheme
547 -||OrganisationUnit
548 -||OrganisationUnitScheme
541 +| |AgencyScheme
542 +| |DataConsumer
543 +| |DataConsumerScheme
544 +| |DataProvider
545 +| |DataProviderScheme
546 +| |MetadataProvider
547 +| |MetadataProviderScheme
548 +| |OrganisationUnit
549 +| |OrganisationUnitScheme
549 549  |datastructure|AttributeDescriptor
550 -||DataAttribute
551 -||Dataflow
552 -||DataStructure (DataStructureDefinition)
553 -||Dimension
554 -||DimensionDescriptor
555 -||GroupDimensionDescriptor
556 -||Measure
557 -||MeasureDescriptor
558 -||TimeDimension
559 -||
551 +| |DataAttribute
552 +| |Dataflow
553 +| |DataStructure (DataStructureDefinition)
554 +| |Dimension
555 +| |DimensionDescriptor
556 +| |GroupDimensionDescriptor
557 +| |Measure
558 +| |MeasureDescriptor
559 +| |TimeDimension
560 +| |
560 560  |metadatastructure|MetadataAttribute
561 -||MetadataAttributeDescriptor
562 -||MetadataStructure MetadataStructureDefinition)
563 -||Metadataflow
564 -||MetadataSet
565 -||
562 +| |MetadataAttributeDescriptor
563 +| |MetadataStructure MetadataStructureDefinition)
564 +| |Metadataflow
565 +| |MetadataSet
566 +| |
566 566  |process|Process
567 -||ProcessStep
568 -||Transition
569 -||
568 +| |ProcessStep
569 +| |Transition
570 +| |
570 570  |registry|DataConstraint
571 -||MetadataConstraint
572 -||MetadataProvisionAgreement
573 -||ProvisionAgreement
574 -||Subscription
575 -||
572 +| |MetadataConstraint
573 +| |MetadataProvisionAgreement
574 +| |ProvisionAgreement
575 +| |Subscription
576 +| |
576 576  |structuremapping|CategorySchemeMap
577 -||ConceptSchemeMap
578 -||OrganisationSchemeMap
579 -||ReportingTaxonomyMap
580 -||RepresentationMap
581 -||StructureMap
582 -||
578 +| |ConceptSchemeMap
579 +| |OrganisationSchemeMap
580 +| |ReportingTaxonomyMap
581 +| |RepresentationMap
582 +| |StructureMap
583 +| |
583 583  |codelist|Code
584 -||Codelist
585 -||HierarchicalCode
586 -||Hierarchy
587 -||HierarchyAssociation
588 -||Level
589 -||ValueList
590 -||
585 +| |Codelist
586 +| |HierarchicalCode
587 +| |Hierarchy
588 +| |HierarchyAssociation
589 +| |Level
590 +| |ValueList
591 +| |
591 591  |categoryscheme|Categorisation
592 -||Category
593 -||CategoryScheme
594 -||ReportingCategory
595 -||ReportingTaxonomy
593 +| |Category
594 +| |CategoryScheme
595 +| |ReportingCategory
596 +| |ReportingTaxonomy
596 596  |conceptscheme|Concept
597 -||ConceptScheme
598 -||
598 +| |ConceptScheme
599 +| |
599 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
601 +| |CustomTypeScheme
602 +| |NamePersonalisation
603 +| |NamePersonalisationScheme
604 +| |Ruleset
605 +| |RulesetScheme
606 +| |Transformation
607 +| |TransformationScheme
608 +| |UserDefinedOperator
609 +| |UserDefinedOperatorScheme
610 +| |VtlCodelistMapping
611 +| |VtlConceptMapping
612 +| |VtlDataflowMapping
613 +| |VtlMappingScheme
613 613  
614 614  **Table 2: SDMX-IM Packages and Contained Classes**
615 615  
... ... @@ -622,7 +622,7 @@
622 622  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
623 623  
624 624  |**Classname**|**Ending URN pattern**|**Example**
625 -|Agency^^[[^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]]^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
626 +|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
626 626  |//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
627 627  |//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
628 628  |Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
... ... @@ -775,22 +775,22 @@
775 775  The following table lists the Maintainable Artefacts.
776 776  
777 777  |(% colspan="2" %)**Maintainable Artefacts**|**Content**
778 -|**Abstract Class**|**Concrete Class**|
779 +|**Abstract Class**|**Concrete Class**|
779 779  |Item Scheme|Codelist|Code
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
781 +| |Concept Scheme|Concept
782 +| |Category Scheme|Category
783 +| |Organisation Unit Scheme|Organisation Unit
784 +| |Agency Scheme|Agency
785 +| |Data Provider Scheme|Data Provider
786 +| |Metadata Provider Scheme|Metadata Provider
787 +| |Data Consumer Scheme|Data Consumer
788 +| |Reporting Taxonomy|Reporting Category
789 +| |Transformation Scheme|Transformation
790 +| |Custom Type Scheme|Custom Type
791 +| |Name Personalisation Scheme|Name Personalisation
792 +| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
793 +| |Ruleset Scheme|Ruleset
794 +| |User Defined Operator Scheme|User Defined Operator
794 794  |Enumerated List|ValueList|Value Item
795 795  |Structure|Data Structure Definition|(((
796 796  Dimension Descriptor
... ... @@ -809,9 +809,9 @@
809 809  
810 810  Measure
811 811  )))
812 -||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
813 -|Structure Usage|Dataflow|
814 -||Metadataflow|
813 +| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
814 +|Structure Usage|Dataflow|
815 +| |Metadataflow|
815 815  |None|Process|Process Step
816 816  |None|Structure Map|(((
817 817  Component Map
... ... @@ -822,14 +822,14 @@
822 822  )))
823 823  |None|Representation Map|Representation Mapping
824 824  |Item Scheme Map|Organisation Scheme Map|Item Map
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|
826 +| |Concept Scheme Map|Item Map
827 +| |Category Scheme Map|Item Map
828 +| |Reporting Taxonomy Map|Item Map
829 +|None|Provision Agreement|
830 +|None|Metadata Provision Agreement|
830 830  |None|Hierarchy|Hierarchical Code
831 -|None|Hierarchy Association|
832 -|None|Categorisation|
832 +|None|Hierarchy Association|
833 +|None|Categorisation|
833 833  
834 834  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
835 835  
... ... @@ -839,7 +839,7 @@
839 839  
840 840  • 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)
841 841  
842 -• All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^
843 +• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
843 843  
844 844  • All types of Structure (Data Structure Definition, Metadata Structure Definition)
845 845  
... ... @@ -971,7 +971,7 @@
971 971  
972 972  The Registration has an action attribute which takes one of the following values:
973 973  
974 -:
975 +:
975 975  
976 976  (((
977 977  |**Action Attribute Value**|**Behaviour**
... ... @@ -998,7 +998,7 @@
998 998  
999 999  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.
1000 1000  
1001 -:
1002 +:
1002 1002  
1003 1003  (((
1004 1004  |**Indexing Required**|**Registration Process Activity**
... ... @@ -1063,7 +1063,7 @@
1063 1063  1. A selector which specifies which type of events are of interest. The set of event types is:
1064 1064  
1065 1065  :
1066 -::
1067 +::
1067 1067  
1068 1068  (((
1069 1069  |**Event Type**|**Comment**
... ... @@ -1137,7 +1137,7 @@
1137 1137  
1138 1138  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:
1139 1139  
1140 -:
1141 +:
1141 1141  
1142 1142  (((
1143 1143  |**Selector**|**Comment**
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_1edb9829.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_8a88db1c.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +184.8 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_979e4862.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +274.0 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_99c4cc7e.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +126.4 KB
Content
SDMX 3-0-0 SECTION 5 FINAL-1.0_en_eaceb05e.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +33.7 KB
Content