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

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

From 21.1 to 20.1 From 21.6 to 21.5

From version 21.5

edited by Helena
on 2025/05/15 14:09

Change comment: There is no comment for this version

To version 21.1

edited by Helena
on 2025/05/15 14:05

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

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

Content

@@ -1,17 +1,14 @@
--{{box title="**Contents**"}}
--{{toc/}}
--{{/box}}
++**Revision History**
--= Revision History =
++:
  (((
--(% style="width:838.294px" %)
--|(% style="width:188px" %)**Revision**|(% style="width:205px" %)**Date**|(% style="width:441px" %)**Contents**
--|(% style="width:188px" %)DRAFT 1.0|(% style="width:205px" %)May 2021|(% style="width:441px" %)Draft release updated for SDMX 3.0 for public consultation
--|(% style="width:188px" %)1.0|(% style="width:205px" %)October 2021|(% style="width:441px" %)Public release for SDMX 3.0
++|**Revision**|**Date**|**Contents**
++|DRAFT 1.0|May 2021|Draft release updated for SDMX 3.0 for public consultation
++|1.0|October 2021|Public release for SDMX 3.0
  )))
--= 1 Introduction =
++= {{id name="_Toc93831"/}}1 Introduction =
  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:
@@ -33,10 +33,12 @@
  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:
--* structural metadata repository
--* data and metadata registration
--* query
++• structural metadata repository
++• data and metadata registration
++
++• query
++
  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.
  = {{id name="_Toc93832"/}}2 Scope and Normative Status =
@@ -79,8 +79,7 @@
  [[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_28806f51.jpg||height="539" width="443"]]
--(% class="wikigeneratedid" id="HFigure1:SchematicoftheBasicStructuralArtefactsintheSDMX-IM" %)
--**Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM**
++====== Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM ======
  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:
@@ -107,7 +107,7 @@
  Notifying interested parties of newly published or re-published data, reference metadata or changes in structural metadata involves:
--* 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.
++• 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.
  == {{id name="_Toc93838"/}}3.5 Discovery ==
@@ -166,8 +166,9 @@
  The registry interfaces are invoked in one of two ways:
--1. The interface is the name of the root node of the SDMX-ML document
--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.
++*
++*1. The interface is the name of the root node of the SDMX-ML document
++*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.
  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.
@@ -302,8 +302,8 @@
  a) Be a draft version.
  )))
  |**Interface**|**Behaviour**
--| |(((
--b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
++||(((
++b) Not be explicitly^^[[^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]]^^ referenced from any other object in the Registry.
 ) The semantic versioning rules in the SDMX documentation MUST be obeyed.
  )))
@@ -335,30 +335,30 @@
  * //Versionable//
  * //Maintainable//
--:
++:
  (((
  |**Object Type**|**Data Attributes**|**Status**|**Data type**|**Notes**
--|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
--|AnnotationType|C|string|
--|AnnotationURN|C|string|
--|AnnotationText in the form of InternationalString|C| |This can have languagespecific variants
--|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus| | |
--|id|M|string|
--|uri|C|string|
++|(% rowspan="4" %)//Annotable//|AnnotationTitle|C|string|
++|AnnotationType|C|string|
++|AnnotationURN|C|string|
++|AnnotationText in the form of InternationalString|C||This can have languagespecific variants
++|(% rowspan="4" %)//Identifiable//|All content as for //Annotable// plus|||
++|id|M|string|
++|uri|C|string|
  |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.
--|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus| | |
++|(% rowspan="3" %)//Nameable//|All content as for //Identifiable// plus|||
  |Name in the form of InternationalString|M|string|This can have language specific variants.
  |Description in the form of InternationalString|C|string|This can have language specific variants.
--|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus| | |
++|(% rowspan="4" %)//Versionable//|All content as for //Identifiable// plus|||
  |version|M|string|This is the version number according to SDMX versioning rules.
--|validFrom|C|Date/time|
--|validTo|C|Date/time|
--|//Maintainable//|All content as for //Versionable// plus| | |
--| |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.
--| |serviceURL|C|string|The url of the service that can be queried for this resource.
--| |structureURL|C|string|The url of the resource.
--| |(Maintenance) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
++|validFrom|C|Date/time|
++|validTo|C|Date/time|
++|//Maintainable//|All content as for //Versionable// plus|||
++||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.
++|\\|serviceURL|C|string|The url of the service that can be queried for this resource.
++||structureURL|C|string|The url of the resource.
++||(Maintenance) organisationId|M|string|The object must be linked to a maintenance organisation, i.e., Agency or Metadata Provider.
  )))
  **Table 1: Common Attributes of Object Types**
@@ -538,79 +538,79 @@
  |**Package**|**URN class name (model class name where this is different)**
  |base|Agency
--| |AgencyScheme
--| |DataConsumer
--| |DataConsumerScheme
--| |DataProvider
--| |DataProviderScheme
--| |MetadataProvider
--| |MetadataProviderScheme
--| |OrganisationUnit
--| |OrganisationUnitScheme
++||AgencyScheme
++||DataConsumer
++||DataConsumerScheme
++||DataProvider
++||DataProviderScheme
++||MetadataProvider
++||MetadataProviderScheme
++||OrganisationUnit
++||OrganisationUnitScheme
  |datastructure|AttributeDescriptor
--| |DataAttribute
--| |Dataflow
--| |DataStructure (DataStructureDefinition)
--| |Dimension
--| |DimensionDescriptor
--| |GroupDimensionDescriptor
--| |Measure
--| |MeasureDescriptor
--| |TimeDimension
--| |
++||DataAttribute
++||Dataflow
++||DataStructure (DataStructureDefinition)
++||Dimension
++||DimensionDescriptor
++||GroupDimensionDescriptor
++||Measure
++||MeasureDescriptor
++||TimeDimension
++||
  |metadatastructure|MetadataAttribute
--| |MetadataAttributeDescriptor
--| |MetadataStructure MetadataStructureDefinition)
--| |Metadataflow
--| |MetadataSet
--| |
++||MetadataAttributeDescriptor
++||MetadataStructure MetadataStructureDefinition)
++||Metadataflow
++||MetadataSet
++||
  |process|Process
--| |ProcessStep
--| |Transition
--| |
++||ProcessStep
++||Transition
++||
  |registry|DataConstraint
--| |MetadataConstraint
--| |MetadataProvisionAgreement
--| |ProvisionAgreement
--| |Subscription
--| |
++||MetadataConstraint
++||MetadataProvisionAgreement
++||ProvisionAgreement
++||Subscription
++||
  |structuremapping|CategorySchemeMap
--| |ConceptSchemeMap
--| |OrganisationSchemeMap
--| |ReportingTaxonomyMap
--| |RepresentationMap
--| |StructureMap
--| |
++||ConceptSchemeMap
++||OrganisationSchemeMap
++||ReportingTaxonomyMap
++||RepresentationMap
++||StructureMap
++||
  |codelist|Code
--| |Codelist
--| |HierarchicalCode
--| |Hierarchy
--| |HierarchyAssociation
--| |Level
--| |ValueList
--| |
++||Codelist
++||HierarchicalCode
++||Hierarchy
++||HierarchyAssociation
++||Level
++||ValueList
++||
  |categoryscheme|Categorisation
--| |Category
--| |CategoryScheme
--| |ReportingCategory
--| |ReportingTaxonomy
++||Category
++||CategoryScheme
++||ReportingCategory
++||ReportingTaxonomy
  |conceptscheme|Concept
--| |ConceptScheme
--| |
++||ConceptScheme
++||
  |transformation|CustomType
--| |CustomTypeScheme
--| |NamePersonalisation
--| |NamePersonalisationScheme
--| |Ruleset
--| |RulesetScheme
--| |Transformation
--| |TransformationScheme
--| |UserDefinedOperator
--| |UserDefinedOperatorScheme
--| |VtlCodelistMapping
--| |VtlConceptMapping
--| |VtlDataflowMapping
--| |VtlMappingScheme
++||CustomTypeScheme
++||NamePersonalisation
++||NamePersonalisationScheme
++||Ruleset
++||RulesetScheme
++||Transformation
++||TransformationScheme
++||UserDefinedOperator
++||UserDefinedOperatorScheme
++||VtlCodelistMapping
++||VtlConceptMapping
++||VtlDataflowMapping
++||VtlMappingScheme
  **Table 2: SDMX-IM Packages and Contained Classes**
@@ -623,7 +623,7 @@
  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
  |**Classname**|**Ending URN pattern**|**Example**
--|Agency^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
++|Agency^^[[^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]]^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
  |//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
  |//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
  |Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
@@ -776,22 +776,22 @@
  The following table lists the Maintainable Artefacts.
  |(% colspan="2" %)**Maintainable Artefacts**|**Content**
--|**Abstract Class**|**Concrete Class**|
++|**Abstract Class**|**Concrete Class**|
  |Item Scheme|Codelist|Code
--| |Concept Scheme|Concept
--| |Category Scheme|Category
--| |Organisation Unit Scheme|Organisation Unit
--| |Agency Scheme|Agency
--| |Data Provider Scheme|Data Provider
--| |Metadata Provider Scheme|Metadata Provider
--| |Data Consumer Scheme|Data Consumer
--| |Reporting Taxonomy|Reporting Category
--| |Transformation Scheme|Transformation
--| |Custom Type Scheme|Custom Type
--| |Name Personalisation Scheme|Name Personalisation
--| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
--| |Ruleset Scheme|Ruleset
--| |User Defined Operator Scheme|User Defined Operator
++||Concept Scheme|Concept
++||Category Scheme|Category
++||Organisation Unit Scheme|Organisation Unit
++||Agency Scheme|Agency
++||Data Provider Scheme|Data Provider
++||Metadata Provider Scheme|Metadata Provider
++||Data Consumer Scheme|Data Consumer
++||Reporting Taxonomy|Reporting Category
++||Transformation Scheme|Transformation
++||Custom Type Scheme|Custom Type
++||Name Personalisation Scheme|Name Personalisation
++||Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
++||Ruleset Scheme|Ruleset
++||User Defined Operator Scheme|User Defined Operator
  |Enumerated List|ValueList|Value Item
  |Structure|Data Structure Definition|(((
  Dimension Descriptor
@@ -810,9 +810,9 @@
  Measure
  )))
--| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
--|Structure Usage|Dataflow|
--| |Metadataflow|
++||Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
++|Structure Usage|Dataflow|
++||Metadataflow|
  |None|Process|Process Step
  |None|Structure Map|(((
  Component Map
@@ -823,14 +823,14 @@
  )))
  |None|Representation Map|Representation Mapping
  |Item Scheme Map|Organisation Scheme Map|Item Map
--| |Concept Scheme Map|Item Map
--| |Category Scheme Map|Item Map
--| |Reporting Taxonomy Map|Item Map
--|None|Provision Agreement|
--|None|Metadata Provision Agreement|
++||Concept Scheme Map|Item Map
++||Category Scheme Map|Item Map
++||Reporting Taxonomy Map|Item Map
++|None|Provision Agreement|
++|None|Metadata Provision Agreement|
  |None|Hierarchy|Hierarchical Code
--|None|Hierarchy Association|
--|None|Categorisation|
++|None|Hierarchy Association|
++|None|Categorisation|
  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
@@ -840,7 +840,7 @@
  • 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)
--• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
++• All types of Enumerated List (ValueList)^^[[^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]]^^
  • All types of Structure (Data Structure Definition, Metadata Structure Definition)
@@ -972,7 +972,7 @@
  The Registration has an action attribute which takes one of the following values:
--:
++:
  (((
  |**Action Attribute Value**|**Behaviour**
@@ -999,7 +999,7 @@
  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.
--:
++:
  (((
  |**Indexing Required**|**Registration Process Activity**
@@ -1064,7 +1064,7 @@
 . A selector which specifies which type of events are of interest. The set of event types is:
  :
--::
++::
  (((
  |**Event Type**|**Comment**
@@ -1138,7 +1138,7 @@
  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:
--:
++:
  (((
  |**Selector**|**Comment**