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

Last modified by Artur on 2025/09/30 13:28

From 21.7 to 21.8 From 22.3 to 22.4

From version 21.8

edited by Helena
on 2025/06/08 16:32

Change comment: There is no comment for this version

To version 22.3

edited by Helena
on 2025/06/08 16:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -163,9 +163,8 @@
  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.
@@ -181,7 +181,7 @@
  === 5.2.2 Structure Submission Service ===
--The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: __[[https:~~/~~/github.com/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[twg/sdmx>>url:https://github.com/sdmx-twg/sdmx-rest]][[->>url:https://github.com/sdmx-twg/sdmx-rest]][[rest>>url:https://github.com/sdmx-twg/sdmx-rest]]__[[)>>url:https://github.com/sdmx-twg/sdmx-rest]]. In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
++The registry must support a mechanism for submitting structural metadata. This mechanism can be the SDMX REST interface for structural metadata (this is defined in the corresponding GitHub project, dedicated to the SDMX REST API: [[__https:~~/~~/github.com/sdmx-twg/sdmx-rest__>>https://https:github.comsdmx-twgsdmx-rest]]). In order for the architecture to be scalable, the finest-grained piece of structural metadata that can be processed by the SDMX-RR is a MaintainableArtefact, with the exception of Item Schemes, where changes at an Item level is also possible (see next section on the SDMX Information Model).
  === 5.2.3 Structure Query Service ===
@@ -271,7 +271,7 @@
 . 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:
  a) Be a draft version.
--b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
++b) Not be explicitly^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^1^^>>path:#sdfootnote1sym||name="sdfootnote1anc"]](%%)^^ referenced from any other object in the Registry.
 ) The semantic versioning rules in the SDMX documentation MUST be obeyed.
  )))
@@ -384,14 +384,11 @@
  The following organizations maintain an Agency Scheme.
--• SDMX – contains Agencies AA, BB
++* SDMX – contains Agencies AA, BB
++* AA – contains Agencies CC, DD
++* BB – contains Agencies CC, DD
++* DD – Contains Agency EE
--• AA – contains Agencies CC, DD
--
--• BB – contains Agencies CC, DD
--
--• DD – Contains Agency EE
--
  Each agency is identified by its full hierarchy excluding SDMX.
  e.g., the id of EE as an agencyID is AA.DD.EE
@@ -404,13 +404,13 @@
  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.
--===== {{id name="_Toc90807"/}}6.2.2 Universal Resource Name (URN) =====
++=== 6.2.2 Universal Resource Name (URN) ===
--**6.2.2.1 Introduction**
++==== 6.2.2.1 Introduction ====
  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.).
--**6.2.2.2 URN Structure //__Case Rules for URN__//**//&nbsp;//
++==== 6.2.2.2 URN Structure //__Case Rules for URN__// ====
  For the URN, all parts of the string are case sensitive. The generic structure of the URN is as follows:
@@ -422,7 +422,7 @@
  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.
--**6.2.2.3 Explanation of the generic structure**
++==== 6.2.2.3 Explanation of the generic structure ====
  In the explanation below the actual object that is the target of the URN is called the **actual object**.
@@ -501,103 +501,103 @@
  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.
--===== {{id name="_Toc90808"/}}6.2.3 Table of SDMX-IM Packages and Classes =====
++=== 6.2.3 Table of SDMX-IM Packages and Classes ===
  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.
--|**Package**|**URN class name (model class name where this is different)**
--|base|Agency
--| |AgencyScheme
--| |DataConsumer
--| |DataConsumerScheme
--| |DataProvider
--| |DataProviderScheme
--| |MetadataProvider
--| |MetadataProviderScheme
--| |OrganisationUnit
--| |OrganisationUnitScheme
--| |
--|datastructure|AttributeDescriptor
--| |DataAttribute
--| |Dataflow
--| |DataStructure (DataStructureDefinition)
--| |Dimension
--| |DimensionDescriptor
--| |GroupDimensionDescriptor
--| |Measure
--| |MeasureDescriptor
--| |TimeDimension
--| |
--|metadatastructure|MetadataAttribute
--| |MetadataAttributeDescriptor
--| |(((
++(% style="width:750.835px" %)
++|(% style="width:222px" %)**Package**|(% style="width:526px" %)**URN class name (model class name where this is different)**
++|(% style="width:222px" %)base|(% style="width:526px" %)Agency
++|(% style="width:222px" %) |(% style="width:526px" %)AgencyScheme
++|(% style="width:222px" %) |(% style="width:526px" %)DataConsumer
++|(% style="width:222px" %) |(% style="width:526px" %)DataConsumerScheme
++|(% style="width:222px" %) |(% style="width:526px" %)DataProvider
++|(% style="width:222px" %) |(% style="width:526px" %)DataProviderScheme
++|(% style="width:222px" %) |(% style="width:526px" %)MetadataProvider
++|(% style="width:222px" %) |(% style="width:526px" %)MetadataProviderScheme
++|(% style="width:222px" %) |(% style="width:526px" %)OrganisationUnit
++|(% style="width:222px" %) |(% style="width:526px" %)OrganisationUnitScheme
++|(% style="width:222px" %) |(% style="width:526px" %)
++|(% style="width:222px" %)datastructure|(% style="width:526px" %)AttributeDescriptor
++|(% style="width:222px" %) |(% style="width:526px" %)DataAttribute
++|(% style="width:222px" %) |(% style="width:526px" %)Dataflow
++|(% style="width:222px" %) |(% style="width:526px" %)DataStructure (DataStructureDefinition)
++|(% style="width:222px" %) |(% style="width:526px" %)Dimension
++|(% style="width:222px" %) |(% style="width:526px" %)DimensionDescriptor
++|(% style="width:222px" %) |(% style="width:526px" %)GroupDimensionDescriptor
++|(% style="width:222px" %) |(% style="width:526px" %)Measure
++|(% style="width:222px" %) |(% style="width:526px" %)MeasureDescriptor
++|(% style="width:222px" %) |(% style="width:526px" %)TimeDimension
++|(% style="width:222px" %) |(% style="width:526px" %)
++|(% style="width:222px" %)metadatastructure|(% style="width:526px" %)MetadataAttribute
++|(% style="width:222px" %) |(% style="width:526px" %)MetadataAttributeDescriptor
++|(% style="width:222px" %) |(% style="width:526px" %)(((
  MetadataStructure
  (MetadataStructureDefinition)
  )))
--:
--
  (((
--|**Package**|**URN class name (model class name where this is different)**
--| |Metadataflow
--| |MetadataSet
--| |
--|process|Process
--| |ProcessStep
--| |Transition
--| |
--|registry|DataConstraint
--| |MetadataConstraint
--| |MetadataProvisionAgreement
--| |ProvisionAgreement
--| |Subscription
--| |
--|structuremapping|CategorySchemeMap
--| |ConceptSchemeMap
--| |OrganisationSchemeMap
--| |ReportingTaxonomyMap
--| |RepresentationMap
--| |StructureMap
--| |
--|codelist|Code
--| |Codelist
--| |HierarchicalCode
--| |Hierarchy
--| |HierarchyAssociation
--| |Level
--| |ValueList
--| |
--|categoryscheme|Categorisation
--| |Category
--| |CategoryScheme
--| |ReportingCategory
--| |ReportingTaxonomy
--|**Package**|**URN class name (model class name where this is different)**
--| |
--|conceptscheme|Concept
--| |ConceptScheme
--| |
--|transformation|CustomType
--| |CustomTypeScheme
--| |NamePersonalisation
--| |NamePersonalisationScheme
--| |Ruleset
--| |RulesetScheme
--| |Transformation
--| |TransformationScheme
--| |UserDefinedOperator
--| |UserDefinedOperatorScheme
--| |VtlCodelistMapping
--| |VtlConceptMapping
--| |VtlDataflowMapping
--| |VtlMappingScheme
--| |
++(% style="width:751.835px" %)
++|(% style="width:221px" %)**Package**|(% style="width:528px" %)**URN class name (model class name where this is different)**
++|(% style="width:221px" %) |(% style="width:528px" %)Metadataflow
++|(% style="width:221px" %) |(% style="width:528px" %)MetadataSet
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)process|(% style="width:528px" %)Process
++|(% style="width:221px" %) |(% style="width:528px" %)ProcessStep
++|(% style="width:221px" %) |(% style="width:528px" %)Transition
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)registry|(% style="width:528px" %)DataConstraint
++|(% style="width:221px" %) |(% style="width:528px" %)MetadataConstraint
++|(% style="width:221px" %) |(% style="width:528px" %)MetadataProvisionAgreement
++|(% style="width:221px" %) |(% style="width:528px" %)ProvisionAgreement
++|(% style="width:221px" %) |(% style="width:528px" %)Subscription
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)structuremapping|(% style="width:528px" %)CategorySchemeMap
++|(% style="width:221px" %) |(% style="width:528px" %)ConceptSchemeMap
++|(% style="width:221px" %) |(% style="width:528px" %)OrganisationSchemeMap
++|(% style="width:221px" %) |(% style="width:528px" %)ReportingTaxonomyMap
++|(% style="width:221px" %) |(% style="width:528px" %)RepresentationMap
++|(% style="width:221px" %) |(% style="width:528px" %)StructureMap
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)codelist|(% style="width:528px" %)Code
++|(% style="width:221px" %) |(% style="width:528px" %)Codelist
++|(% style="width:221px" %) |(% style="width:528px" %)HierarchicalCode
++|(% style="width:221px" %) |(% style="width:528px" %)Hierarchy
++|(% style="width:221px" %) |(% style="width:528px" %)HierarchyAssociation
++|(% style="width:221px" %) |(% style="width:528px" %)Level
++|(% style="width:221px" %) |(% style="width:528px" %)ValueList
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)categoryscheme|(% style="width:528px" %)Categorisation
++|(% style="width:221px" %) |(% style="width:528px" %)Category
++|(% style="width:221px" %) |(% style="width:528px" %)CategoryScheme
++|(% style="width:221px" %) |(% style="width:528px" %)ReportingCategory
++|(% style="width:221px" %) |(% style="width:528px" %)ReportingTaxonomy
++|(% style="width:221px" %)**Package**|(% style="width:528px" %)**URN class name (model class name where this is different)**
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)conceptscheme|(% style="width:528px" %)Concept
++|(% style="width:221px" %) |(% style="width:528px" %)ConceptScheme
++|(% style="width:221px" %) |(% style="width:528px" %)
++|(% style="width:221px" %)transformation|(% style="width:528px" %)CustomType
++|(% style="width:221px" %) |(% style="width:528px" %)CustomTypeScheme
++|(% style="width:221px" %) |(% style="width:528px" %)NamePersonalisation
++|(% style="width:221px" %) |(% style="width:528px" %)NamePersonalisationScheme
++|(% style="width:221px" %) |(% style="width:528px" %)Ruleset
++|(% style="width:221px" %) |(% style="width:528px" %)RulesetScheme
++|(% style="width:221px" %) |(% style="width:528px" %)Transformation
++|(% style="width:221px" %) |(% style="width:528px" %)TransformationScheme
++|(% style="width:221px" %) |(% style="width:528px" %)UserDefinedOperator
++|(% style="width:221px" %) |(% style="width:528px" %)UserDefinedOperatorScheme
++|(% style="width:221px" %) |(% style="width:528px" %)VtlCodelistMapping
++|(% style="width:221px" %) |(% style="width:528px" %)VtlConceptMapping
++|(% style="width:221px" %) |(% style="width:528px" %)VtlDataflowMapping
++|(% style="width:221px" %) |(% style="width:528px" %)VtlMappingScheme
++|(% style="width:221px" %) |(% style="width:528px" %)
  )))
  **Table 2: SDMX-IM Packages and Contained Classes**
--===== {{id name="_Toc90809"/}}6.2.4 URN Identification components of SDMX objects =====
++=== 6.2.4 URN Identification components of SDMX objects ===
  The table below describes the identification components for all SDMX object types that have identification. Note the actual attributes are all ‘id’ but have been prefixed by their class name or multiple class names to show navigation, e.g., ‘conceptSchemeAgencyId’ is really the ‘Id’ attribute of the Agency class that is associated to the ConceptScheme.
@@ -605,67 +605,56 @@
  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
--|**Classname**|**Ending URN pattern**|**Example**
--|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^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 …
--|//CategoryScheme//|categorySchemeAgencyId:categorySchemeId(versi on)|IMF:SDDS(1.0.0)
++(% style="width:1272.83px" %)
++|(% style="width:290px" %)**Classname**|(% style="width:649px" %)**Ending URN pattern**|(% style="width:332px" %)**Example**
++|(% style="width:290px" %)Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|(% style="width:649px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:332px" %)ECB:**AGENCIES**(**1.0**).AA
++|(% style="width:290px" %)//AgencyScheme//|(% style="width:649px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:332px" %)ECB:**AGENCIES**(**1.0**)
++|(% style="width:290px" %)//Categorisation//|(% style="width:649px" %)categorisationAgencyId:categorisationId(version)|(% style="width:332px" %)IMF:cat001(1.0.0)
++|(% style="width:290px" %)Category|(% style="width:649px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:332px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category …
++|(% style="width:290px" %)//CategoryScheme//|(% style="width:649px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:332px" %)IMF:SDDS(1.0.0)
--|**Classname**|**Ending URN pattern**|**Example**
--|//CategorySchemeMap//|(((
--catSchemeMapAgencyId:catSchemeMapId(version
++|(% style="width:292px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:742px" %)**Example**
++|(% style="width:292px" %)//CategorySchemeMap//|(% style="width:647px" %)(((
++catSchemeMapAgencyId:catSchemeMapId(version)
++)))|(% style="width:742px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
++|(% style="width:292px" %)Code|(% style="width:647px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:742px" %)SDMX:CL_FREQ(1.0.0).Q
++|(% style="width:292px" %)//Codelist//|(% style="width:647px" %)codeListAgencyId:codeListId(version)|(% style="width:742px" %)SDMX:CL_FREQ(1.0.0)
++|(% style="width:292px" %)ComponentMap|(% style="width:647px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:742px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
++|(% style="width:292px" %)Concept|(% style="width:647px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:742px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
++|(% style="width:292px" %)//ConceptScheme//|(% style="width:647px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:742px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
++|(% style="width:292px" %)//ConceptSchemeMap//|(% style="width:647px" %)(((
++conceptSchemeMapAgencyId:conceptSchemeMap Id(version)
++)))|(% style="width:742px" %)SDMX:CONCEPT_MAP(1.0.0)
++|(% style="width:292px" %)CustomType|(% style="width:647px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:742px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
++|(% style="width:292px" %)//CustomTypeScheme//|(% style="width:647px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:742px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0)
++|(% style="width:292px" %)DataAttrribute|(% style="width:647px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS
++|(% style="width:292px" %)//DataConstraint//|(% style="width:647px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:742px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0)
--)
--)))|SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
--|Code|codeListAgencyId:codelistId(version).codeId|SDMX:CL_FREQ(1.0.0).Q
--|//Codelist//|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0.0)
--|ComponentMap|structureMapAgencyId:structureMap(version).com ponentMapId|SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
--|Concept|conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
--|//ConceptScheme//|conceptSchemeAgencyId:conceptSchemeId(versio n)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
--|//ConceptSchemeMap//|(((
--conceptSchemeMapAgencyId:conceptSchemeMap
--
--Id(version)
--)))|SDMX:CONCEPT_MAP(1.0.0)
--|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
--|//CustomTypeScheme//|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0.0)
--|DataAttrribute|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|TFFS:EXT_DEBT(1.0.0).OBS_STATUS
--|//DataConstraint//|dataConstraintAgencyId:dataConstraintId(version)|TFFS:CREDITOR_DATA_CONTENT(1.0.0)
--
--|**Classname**|**Ending URN pattern**|**Example**
--|DataConsumer|dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
--|//DataConsumerScheme//|(((
--dataConsumerSchemeAgencyId:**DATA_CONSUME**
--
--**RS**(**1.0**)
--)))|SDMX:**DATA_CONSUMERS**(**1.0**)
--|//Dataflow//|dataflowAgencyId:dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0.0)
--|DataProvider|(((
--dataProviderSchemeAgencyId:**DATA_PROVIDERS**(
--
--**1.0**).dataProviderId
--)))|SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
--|//DataProviderScheme//|(((
--dataProviderSchemeAgencyId:**DATA_PROVIDERS**(
--
--**1.0**)
--)))|SDMX:**DATA_PROVIDERS**(**1.0**)
--|//DataStructure//|dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|TFFS:EXT_DEBT(1.0.0)
--|Dimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|TFFS:EXT_DEBT(1.0.0).FREQ
--|(((
++|(% style="width:294px" %)**Classname**|(% style="width:645px" %)**Ending URN pattern**|(% style="width:742px" %)**Example**
++|(% style="width:294px" %)DataConsumer|(% style="width:645px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:742px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
++|(% style="width:294px" %)//DataConsumerScheme//|(% style="width:645px" %)(((
++dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**)
++)))|(% style="width:742px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
++|(% style="width:294px" %)//Dataflow//|(% style="width:645px" %)dataflowAgencyId:dataflowId(version)|(% style="width:742px" %)TFFS:CRED_EXT_DEBT(1.0.0)
++|(% style="width:294px" %)DataProvider|(% style="width:645px" %)(((
++dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId
++)))|(% style="width:742px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
++|(% style="width:294px" %)//DataProviderScheme//|(% style="width:645px" %)(((
++dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**)
++)))|(% style="width:742px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
++|(% style="width:294px" %)//DataStructure//|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0)
++|(% style="width:294px" %)Dimension|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0).FREQ
++|(% style="width:294px" %)(((
  DimensionDescriptor
  MeasureDescriptor
  AttributeDescriptor
--)))|(((
++)))|(% style="width:645px" %)(((
  dataStructureDefinitionAgencyId:dataStructureDef initionId(version).componentListId
--where the componentListId is the name of the class (there is only one occurrence of each in the
--
--Data Structure Definition)
--)))|(((
++where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
++)))|(% style="width:742px" %)(((
  TFFS:EXT_DEBT(1.0.0).DimensionDescriptor
  TFFS:EXT_DEBT(1.0.0).MeasureDescriptor
@@ -672,83 +672,81 @@
  TFFS:EXT_DEBT(1.0.0).AttributeDescriptor
  )))
--|GroupDimensionDescriptor|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|TFFS:EXT_DEBT(1.0.0).SIBLING
--|HierarchicalCode|hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
++|(% style="width:294px" %)GroupDimensionDescriptor|(% style="width:645px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:742px" %)TFFS:EXT_DEBT(1.0.0).SIBLING
++|(% style="width:294px" %)HierarchicalCode|(% style="width:645px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:742px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
--|**Classname**|**Ending URN pattern**|**Example**
--|//Hierarchy//|hierarchyAgencyId:hierarchyId(version)|UNESCO:H-C-GOV(1.0.0)
--|//HierarchyAssociation//|hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|UNESCO:CL_EXP_SOURCE(1.0.0)
--|Level|hierarchyAgencyId:hierarchyId(version).level|UNESCO:H-C-GOV(1.0.0).LVL1
--|Measure|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|TFFS:EXT_DEBT(1.0.0).OBS_VALUE
--|MetadataAttribute|(((
++|**Classname**|(% style="width:644px" %)**Ending URN pattern**|(% style="width:743px" %)**Example**
++|//Hierarchy//|(% style="width:644px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:743px" %)UNESCO:H-C-GOV(1.0.0)
++|//HierarchyAssociation//|(% style="width:644px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:743px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
++|Level|(% style="width:644px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:743px" %)UNESCO:H-C-GOV(1.0.0).LVL1
++|Measure|(% style="width:644px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:743px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE
++|MetadataAttribute|(% style="width:644px" %)(((
  msdAgencyId:msdId(version).metadataAttributeId.
  metadataAttributeId
--)))|IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
--|MetadataAttributeDescriptor|msdAgencyId:msdId(version).metadataAttributeDe scriptorId|IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
--|//MetadataConstraint//|metadataConstraintAgencyId:metadataConstraintI d(version)|TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
--|//Metadataflow//|metadataflowAgencyId:metadataflowId(version)|IMF:SDDS_MDF(1.0.0)
--|MetadataProvider|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
--|//MetadataProviderScheme//|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|SDMX:**METADATA_PROVIDERS**(**1.0**)
--|//MetadataProvisionAgreement//|metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|IMF:SDDS_MDF_AB(1.0.0)
--|//MetadataSet//|metadataProviderId:metadataSetId(version)|MD_PROVIDER:METADATASET(1.0.0)
--|//MetadataStructure//|msdAgencyId:msdId(version)|IMF:SDDS_MSD(1.0.0)
++)))|(% style="width:743px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
++|MetadataAttributeDescriptor|(% style="width:644px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:743px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
++|//MetadataConstraint//|(% style="width:644px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:743px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
++|//Metadataflow//|(% style="width:644px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:743px" %)IMF:SDDS_MDF(1.0.0)
++|MetadataProvider|(% style="width:644px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:743px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
++|//MetadataProviderScheme//|(% style="width:644px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:743px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
++|//MetadataProvisionAgreement//|(% style="width:644px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:743px" %)IMF:SDDS_MDF_AB(1.0.0)
++|//MetadataSet//|(% style="width:644px" %)metadataProviderId:metadataSetId(version)|(% style="width:743px" %)MD_PROVIDER:METADATASET(1.0.0)
++|//MetadataStructure//|(% style="width:644px" %)msdAgencyId:msdId(version)|(% style="width:743px" %)IMF:SDDS_MSD(1.0.0)
--|**Classname**|**Ending URN pattern**|**Example**
--|NamePersonalisation|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0.0).PSN1234
--|//NamePersonalisationScheme//|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0.0)
--|//OrganisationSchemeMap//|orgSchemeMapAgencyId:orgSchemeMapId(versio n)|SDMX:AGENCIES_PROVIDERS(1.0.0)
--|OrganisationUnit|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version).organisationUnitId|ECB:ORGANISATIONS(1.0.0).1F
--|//OrganisationUnitScheme//|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|ECB:ORGANISATIONS(1.0.0)
--|//Process//|processAgencyId:processId{version)|BIS:PROCESS1(1.0.0)
--|ProcessStep|(((
++|(% style="width:296px" %)**Classname**|(% style="width:646px" %)**Ending URN pattern**|(% style="width:739px" %)**Example**
++|(% style="width:296px" %)NamePersonalisation|(% style="width:646px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:739px" %)ECB:PSN_SCHEME(1.0.0).PSN1234
++|(% style="width:296px" %)//NamePersonalisationScheme//|(% style="width:646px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:739px" %)ECB:PSN_SCHEME(1.0.0)
++|(% style="width:296px" %)//OrganisationSchemeMap//|(% style="width:646px" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:739px" %)SDMX:AGENCIES_PROVIDERS(1.0.0)
++|(% style="width:296px" %)OrganisationUnit|(% style="width:646px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version).organisationUnitId|(% style="width:739px" %)ECB:ORGANISATIONS(1.0.0).1F
++|(% style="width:296px" %)//OrganisationUnitScheme//|(% style="width:646px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:739px" %)ECB:ORGANISATIONS(1.0.0)
++|(% style="width:296px" %)//Process//|(% style="width:646px" %)processAgencyId:processId{version)|(% style="width:739px" %)BIS:PROCESS1(1.0.0)
++|(% style="width:296px" %)ProcessStep|(% style="width:646px" %)(((
  processAgencyId:processId(version).processStepId.
  processStepId
--)))|BIS:PROCESS1(1.0.0).STEP1.STEP1_1
--|//ProvisionAgreement//|provisionAgreementAgencyId:provisionAgreement Id(version)|TFFS:CRED_EXT_DEBT_AB(1.0.0)
--|ReportingCategory|(((
++)))|(% style="width:739px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1
++|(% style="width:296px" %)//ProvisionAgreement//|(% style="width:646px" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:739px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0)
++|(% style="width:296px" %)ReportingCategory|(% style="width:646px" %)(((
  reportingTaxonomyAgencyId:
  reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId
--)))|IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
--|//ReportingTaxonomy//|reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|IMF:REP_1(1.0.0)
--|//ReportingTaxonomyMap//|repTaxonomyAgencyId:repTaxonomyId(version)|SDMX:RT_MAP(1.0.0)
++)))|(% style="width:739px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
++|(% style="width:296px" %)//ReportingTaxonomy//|(% style="width:646px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:739px" %)IMF:REP_1(1.0.0)
++|(% style="width:296px" %)//ReportingTaxonomyMap//|(% style="width:646px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:739px" %)SDMX:RT_MAP(1.0.0)
--|**Classname**|**Ending URN pattern**|**Example**
--|//RepresentationMap//|repMapAgencyId:repMapId(version)|SDMX:REF_AREA_MAPPING(1.0.0)
--|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0.0).SET111
--|//RulesetScheme//|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0.0)
--|//StructureMap//|structureMapAgencyId:structureMap(version)|SDMX:BOP_STRUCTURES(1.0.0)
--|Subscription|(((
++|(% style="width:297px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:737px" %)**Example**
++|(% style="width:297px" %)//RepresentationMap//|(% style="width:647px" %)repMapAgencyId:repMapId(version)|(% style="width:737px" %)SDMX:REF_AREA_MAPPING(1.0.0)
++|(% style="width:297px" %)Ruleset|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:737px" %)ECB:RULESET_23(1.0.0).SET111
++|(% style="width:297px" %)//RulesetScheme//|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:737px" %)ECB:RULESET_23(1.0.0)
++|(% style="width:297px" %)//StructureMap//|(% style="width:647px" %)structureMapAgencyId:structureMap(version)|(% style="width:737px" %)SDMX:BOP_STRUCTURES(1.0.0)
++|(% style="width:297px" %)Subscription|(% style="width:647px" %)(((
  The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure.
--
  The name of the URN is registryURN There is no pre-determined format.
--)))|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registry URN that is returned from the registry in the subscription response message.
--|TimeDimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
--|Transformation|transformationSchemeAgencyId transformationSchemeId(version) transformationId|ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
--|//TransformationScheme//|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0.0)
--|**Classname**|**Ending URN pattern**|**Example**
--|Transition|(((
++)))|(% style="width:737px" %)This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registry URN that is returned from the registry in the subscription response message.
++|(% style="width:297px" %)TimeDimension|(% style="width:647px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:737px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
++|(% style="width:297px" %)Transformation|(% style="width:647px" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:737px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
++|(% style="width:297px" %)//TransformationScheme//|(% style="width:647px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:737px" %)ECB: TRANSFORMATION_SCHEME(1.0.0)
++|(% style="width:297px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:737px" %)**Example**
++|(% style="width:297px" %)Transition|(% style="width:647px" %)(((
  processAgencyId:processId(version).processStepId.
--
  transitionId
--)))|BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
--|UserDefinedOperator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2.0).OS267
--|//UserDefinedOperatorScheme//|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2.0)
--|//ValueList//|valuelistAgencyId:valuelistId(version)|SDMX:VLIST(1.0.0)
--|VtlCodelistMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0.0).ABZ
--|VtlConceptMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0.0).XYA
--|VtlDataflowMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0.0).MOQ
--|//VtlMappingScheme//|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0.0)
++)))|(% style="width:737px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
++|(% style="width:297px" %)UserDefinedOperator|(% style="width:647px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:737px" %)ECB:OS_CALC(1.2.0).OS267
++|(% style="width:297px" %)//UserDefinedOperatorScheme//|(% style="width:647px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:737px" %)ECB:OS_CALC(1.2.0)
++|(% style="width:297px" %)//ValueList//|(% style="width:647px" %)valuelistAgencyId:valuelistId(version)|(% style="width:737px" %)SDMX:VLIST(1.0.0)
++|(% style="width:297px" %)VtlCodelistMapping|(% style="width:647px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:737px" %)ECB:CLIST_MP(2.0.0).ABZ
++|(% style="width:297px" %)VtlConceptMapping|(% style="width:647px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).XYA
++|(% style="width:297px" %)VtlDataflowMapping|(% style="width:647px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).MOQ
++|(% style="width:297px" %)//VtlMappingScheme//|(% style="width:647px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:737px" %)ECB:CLIST_MP(2.0.0)
 **Table 3: Table of identification components for SDMX Identifiable Artefacts**
--= {{id name="_Toc90810"/}}7 Implementation Notes =
++= 7 Implementation Notes =
--=== {{id name="_Toc90811"/}}7.1 Structural Definition Metadata ===
++== 7.1 Structural Definition Metadata ==
--===== {{id name="_Toc90812"/}}7.1.1 Introduction =====
++=== 7.1.1 Introduction ===
  The SDMX Registry must have the ability to support agencies in their role of defining and disseminating structural metadata artefacts. These artefacts include data structure definitions, code lists, concepts etc. and are fully defined in the SDMX-IM. An authenticated agency may submit valid structural metadata definitions which must be stored in the registry. Note that the term “structural metadata” refers as a general term to all structural components (Data Structure Definitions, Metadata Structure Definitions, Code Lists, Concept Schemes, etc.)
@@ -764,46 +764,40 @@
  The following table lists the Maintainable Artefacts.
--|(% colspan="2" %)**Maintainable Artefacts**|**Content**
--|**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
--|Enumerated List|ValueList|Value Item
--|Structure|Data Structure Definition|(((
++(% style="width:825.835px" %)
++|(% colspan="2" style="width:455px" %)**Maintainable Artefacts**|(% style="width:367px" %)**Content**
++|(% style="width:160px" %)**Abstract Class**|(% style="width:295px" %)**Concrete Class**|(% style="width:367px" %)
++|(% style="width:160px" %)Item Scheme|(% style="width:295px" %)Codelist|(% style="width:367px" %)Code
++|(% style="width:160px" %) |(% style="width:295px" %)Concept Scheme|(% style="width:367px" %)Concept
++|(% style="width:160px" %) |(% style="width:295px" %)Category Scheme|(% style="width:367px" %)Category
++|(% style="width:160px" %) |(% style="width:295px" %)Organisation Unit Scheme|(% style="width:367px" %)Organisation Unit
++|(% style="width:160px" %) |(% style="width:295px" %)Agency Scheme|(% style="width:367px" %)Agency
++|(% style="width:160px" %) |(% style="width:295px" %)Data Provider Scheme|(% style="width:367px" %)Data Provider
++|(% style="width:160px" %) |(% style="width:295px" %)Metadata Provider Scheme|(% style="width:367px" %)Metadata Provider
++|(% style="width:160px" %) |(% style="width:295px" %)Data Consumer Scheme|(% style="width:367px" %)Data Consumer
++|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy|(% style="width:367px" %)Reporting Category
++|(% style="width:160px" %) |(% style="width:295px" %)Transformation Scheme|(% style="width:367px" %)Transformation
++|(% style="width:160px" %) |(% style="width:295px" %)Custom Type Scheme|(% style="width:367px" %)Custom Type
++|(% style="width:160px" %) |(% style="width:295px" %)Name Personalisation Scheme|(% style="width:367px" %)Name Personalisation
++|(% style="width:160px" %) |(% style="width:295px" %)Vtl Mapping Scheme|(% style="width:367px" %)Vtl Codelist Mapping Vtl Concept Mapping
++|(% style="width:160px" %) |(% style="width:295px" %)Ruleset Scheme|(% style="width:367px" %)Ruleset
++|(% style="width:160px" %) |(% style="width:295px" %)User Defined Operator Scheme|(% style="width:367px" %)User Defined Operator
++|(% style="width:160px" %)Enumerated List|(% style="width:295px" %)ValueList|(% style="width:367px" %)Value Item
++|(% style="width:160px" %)Structure|(% style="width:295px" %)Data Structure Definition|(% style="width:367px" %)(((
  Dimension Descriptor
--
  Group Dimension Descriptor
--
  Dimension
--
  Time Dimension
--
  Attribute Descriptor
--
  Data Attribute
--
  Measure Descriptor
--
  Measure
  )))
--| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
--|Structure Usage|Dataflow|
--| |Metadataflow|
--|None|Process|Process Step
--|None|Structure Map|(((
++|(% style="width:160px" %) |(% style="width:295px" %)Metadata Structure Definition|(% style="width:367px" %)Metadata Attribute Descriptor Metadata Attribute
++|(% style="width:160px" %)Structure Usage|(% style="width:295px" %)Dataflow|(% style="width:367px" %)
++|(% style="width:160px" %) |(% style="width:295px" %)Metadataflow|(% style="width:367px" %)
++|(% style="width:160px" %)None|(% style="width:295px" %)Process|(% style="width:367px" %)Process Step
++|(% style="width:160px" %)None|(% style="width:295px" %)Structure Map|(% style="width:367px" %)(((
  Component Map
  Epoch Map
@@ -810,44 +810,44 @@
  Date Pattern Map
  )))
--|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|
--|None|Hierarchy|Hierarchical Code
--|None|Hierarchy Association|
--|None|Categorisation|
--|Constraint|Data Constraint|DataKeySet
--| | |CubeRegion
--|Constraint|Metadata Constraint|MetadataTargetRegion
++|(% style="width:160px" %)None|(% style="width:295px" %)Representation Map|(% style="width:367px" %)Representation Mapping
++|(% style="width:160px" %)Item Scheme Map|(% style="width:295px" %)Organisation Scheme Map|(% style="width:367px" %)Item Map
++|(% style="width:160px" %) |(% style="width:295px" %)Concept Scheme Map|(% style="width:367px" %)Item Map
++|(% style="width:160px" %) |(% style="width:295px" %)Category Scheme Map|(% style="width:367px" %)Item Map
++|(% style="width:160px" %) |(% style="width:295px" %)Reporting Taxonomy Map|(% style="width:367px" %)Item Map
++|(% style="width:160px" %)None|(% style="width:295px" %)Provision Agreement|(% style="width:367px" %)
++|(% style="width:160px" %)None|(% style="width:295px" %)Metadata Provision Agreement|(% style="width:367px" %)
++|(% style="width:160px" %)None|(% style="width:295px" %)Hierarchy|(% style="width:367px" %)Hierarchical Code
++|(% style="width:160px" %)None|(% style="width:295px" %)Hierarchy Association|(% style="width:367px" %)
++|(% style="width:160px" %)None|(% style="width:295px" %)Categorisation|(% style="width:367px" %)
++|(% style="width:160px" %)Constraint|(% style="width:295px" %)Data Constraint|(% style="width:367px" %)DataKeySet
++|(% style="width:160px" %) |(% style="width:295px" %) |(% style="width:367px" %)CubeRegion
++|(% style="width:160px" %)Constraint|(% style="width:295px" %)Metadata Constraint|(% style="width:367px" %)MetadataTargetRegion
  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
--===== {{id name="_Toc90813"/}}7.1.2 Item Scheme, Structure =====
++=== 7.1.2 Item Scheme, Structure ===
  The artefacts included in the structural definitions are:
  * 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 wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
++* All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
  * All types of Structure (Data Structure Definition, Metadata Structure Definition)
  * All types of Structure Usage (Dataflow, Metadataflow)
--===== {{id name="_Toc90814"/}}7.1.3 Structure Usage =====
++=== 7.1.3 Structure Usage ===
--**7.1.3.1 Structure Usage: Basic Concepts**
++==== 7.1.3.1 Structure Usage: Basic Concepts ====
  The Structure Usage defines, in its concrete classes of Dataflow and Metadataflow, which flows of data and metadata use which specific Structure, and importantly for the support of data and metadata discovery, the Structure Usage can be linked to one or more Category in one or more Category Scheme using the Categorisation mechanism. This gives the ability for an application to discover data and metadata by “drilling down” the Category Schemes.
--**7.1.3.2 Structure Usage Schematic**
++==== 7.1.3.2 Structure Usage Schematic ====
  [[image:SDMX 3.1 Section 5_en_9b750e13.jpg||height="246" width="438"]]
  **Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions**
--**7.1.3.3 Structure Usage Model**
++==== 7.1.3.3 Structure Usage Model ====
  [[image:SDMX 3.1 Section 5_en_1c94cbe.jpg||height="548" width="578"]]
@@ -855,19 +855,19 @@
  In addition to the maintenance of the Dataflow and the Metadataflow, the following links must be maintained in the registry:
--1.
++1.
 *. Dataflow to Data Structure Definition
 *. Metadataflow to Metadata Structure Definition
  The following links may be created by means of a Categorisation
--1.
++1.
 *. Categorisation to Dataflow and Category
 *. Categorisation to Metadataflow and Category
--=== {{id name="_Toc90815"/}}7.2 Data and Metadata Provisioning ===
++== 7.2 Data and Metadata Provisioning ==
--===== {{id name="_Toc90816"/}}7.2.1 Provisioning Agreement: Basic concepts =====
++=== 7.2.1 Provisioning Agreement: Basic concepts ===
  Data/Metadata provisioning defines a framework in which the provision of different types of statistical data and metadata by various data/metadata providers can be specified and controlled. This framework is the basis on which the existence of data can be made known to the SDMX-enabled community and hence the basis on which data can subsequently be discovered. Such a framework can be used to regulate the data content to facilitate the building of intelligent applications. It can also be used to facilitate the processing implied by service level agreements, or other provisioning agreements in those scenarios that are based on legal directives. Additionally, quality and timeliness metadata can be supported by this framework which makes it practical to implement information supply chain monitoring.
@@ -875,7 +875,7 @@
  Although the Provision Agreement directly supports the data-sharing “pull” model, it is also useful in “push” exchanges (bilateral and gateway scenarios), or in a dissemination environment. It should be noted, too, that in any exchange scenario, the registry functions as a repository of structural metadata.
--===== {{id name="_Toc90817"/}}7.2.2 Provisioning Agreement Model – pull use case =====
++=== 7.2.2 Provisioning Agreement Model – pull use case ===
  An organisation which publishes statistical data or reference metadata and wishes to make it available to an SDMX enabled community is called a Data Provider. In terms of the SDMX Information Model, the Data Provider is maintained in a Data Provider Scheme.
@@ -897,9 +897,9 @@
  A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider or Metadata Provider and a Dataflow or Metadataflow Definition. The Data/Metadata Provider and the Dataflow/Metadataflow must exist already in order to set up a Metadata Provision or Provision Agreement.
--=== {{id name="_Toc90818"/}}7.3 Data and Metadata Constraints ===
++== 7.3 Data and Metadata Constraints ==
--===== {{id name="_Toc90819"/}}7.3.1 Data and Metadata Constraints: Basic Concepts =====
++=== 7.3.1 Data and Metadata Constraints: Basic Concepts ===
  Constraints are, effectively, lists of the valid or actual content of data and metadata. Constraints can be used to specify a subset of the theoretical content of data set or metadata set which can be derived from the specification of the DSD or MSD. A Constraint can comprise a list of keys or a list of content (usually code values) of a specific component such as a dimension or attribute.
@@ -913,13 +913,13 @@
  In addition, DataAvailabilityConstraints can be extremely useful in a data visualisation system, such as dissemination of statistics on a website. In such a system a Cube Region can be used to specify the Dimension codes that actually exist in a data source (these can be used to build relevant selection tables).
--===== {{id name="_Toc90820"/}}7.3.2 Data and Metadata Constraints: Schematic =====
++=== 7.3.2 Data and Metadata Constraints: Schematic ===
  [[image:SDMX 3.1 Section 5_en_28d0cadc.jpg||height="326" width="580"]]
  **Figure 14: Schematic of the Constraint and the Artefacts that can be constrained**
--===== {{id name="_Toc90821"/}}7.3.3 Data and Metadata Constraints: Model =====
++=== 7.3.3 Data and Metadata Constraints: Model ===
  [[image:SDMX 3.1 Section 5_en_a3184f6a.jpg||height="298" width="579"]]
@@ -935,9 +935,9 @@
  The content of the Constraint can be found in the SDMX Information Model document.
--=== {{id name="_Toc90822"/}}7.4 Data Registration ===
++== 7.4 Data Registration ==
--===== {{id name="_Toc90823"/}}7.4.1 Basic Concepts =====
++=== 7.4.1 Basic Concepts ===
  A Data Provider has published a new dataset conforming to an existing Dataflow (and hence Data Structure Definition). This is implemented as either a web-accessible SDMXML file, or in a database which has a web-services interface capable of responding to an SDMX RESTful query with an SDMX-ML data stream.
@@ -947,15 +947,15 @@
  SDMX-RR supports dataset registration via the Registration Request, which can be created by the Data Provider (giving the Data Provider maximum control). The registry responds to the registration request with a registration response which indicates if the registration was successful. In the event of an error, the error messages are returned as a registry exception within the response.
--===== {{id name="_Toc90824"/}}7.4.2 The Registration Request =====
++=== 7.4.2 The Registration Request ===
--**7.4.2.1 Registration Request Schematic**
++==== 7.4.2.1 Registration Request Schematic ====
  [[image:SDMX 3.1 Section 5_en_293a2ea6.jpg||height="337" width="554"]]
  **Figure 16: Schematic of the Objects Concerned with Registration**
--**7.4.2.2 Registration Request Model**
++==== 7.4.2.2 Registration Request Model ====
  The following UML diagram shows the composition of the registration request. Each request is made up of one or more Registrations, one per dataset to be registered. The Registration can optionally have information, which has been extracted from the Registration:
@@ -967,13 +967,11 @@
  The Registration has an action attribute which takes one of the following values:
--:
--
  (((
--|**Action Attribute Value**|**Behaviour**
--|Append|Add this Registration to the registry
--|Replace|Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
--|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
++|(% style="width:224px" %)**Action Attribute Value**|(% style="width:1457px" %)**Behaviour**
++|(% style="width:224px" %)Append|(% style="width:1457px" %)Add this Registration to the registry
++|(% style="width:224px" %)Replace|(% style="width:1457px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
++|(% style="width:224px" %)Delete|(% style="width:1457px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
  )))
  [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]]
@@ -992,30 +992,24 @@
  https:~/~/github.com/sdmx-twg/sdmx-rest/blob/master/doc/availability.md
--:
--
  (((
--|**Indexing Required**|**Registration Process Activity**
--|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
--|indexDataSet|Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
--|indexReportingPeriod|(((
++(% style="width:918.835px" %)
++|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
++|indexTimeSeries|(% style="width:745px" %)Extract all the series keys and create a KeySet(s) Constraint.
++|indexDataSet|(% style="width:745px" %)Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
++|indexReportingPeriod|(% style="width:745px" %)(((
  This applies only to a registered __dataset__.
--
  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
  )))
--|indexAttributes|(((
++|indexAttributes|(% style="width:745px" %)(((
  **Data Set**
--
  Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value
  **Metadata Set**
--
--Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute
--
--Components of the Constraints model in the
++Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the
  )))
--|**Indexing Required**|**Registration Process Activity**
--| |SDMX-IM. Note that the content is not stored in the Selection Value.
++|**Indexing Required**|(% style="width:745px" %)**Registration Process Activity**
++| |(% style="width:745px" %)SDMX-IM. Note that the content is not stored in the Selection Value.
  )))
  Constraints that specify the contents of a //QueryDatasource// are submitted to the Registry via the structure submission service (i.e., the RESTful API).
@@ -1022,7 +1022,7 @@
  The Registration must reference the ProvisionAgreement to which it relates.
--===== {{id name="_Toc90825"/}}7.4.3 Registration Response =====
++=== 7.4.3 Registration Response ===
  After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The SubmitRegistration class has a status field, which is either set to “Success”, “Warning” or “Failure”.
@@ -1034,7 +1034,7 @@
  **Figure 18: Logical class diagram showing the registration response**
--=== {{id name="_Toc90826"/}}7.5 Subscription and Notification Service ===
++== 7.5 Subscription and Notification Service ==
  The contents of the SDMX Registry/Repository will change regularly: new code lists and key families will be published and new datasets and metadata-sets will be registered. To obviate the need for users to repeatedly query the registry to see when new information is available, a mechanism is provided to allow users to be notified when these events happen.
@@ -1042,13 +1042,13 @@
  When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a “notification”.
--===== {{id name="_Toc90827"/}}7.5.1 Subscription Logical Class Diagram =====
++=== 7.5.1 Subscription Logical Class Diagram ===
  [[image:SDMX 3.1 Section 5_en_1433df5d.jpg||height="680" width="587"]]
  **Figure 19: Logical Class Diagram of the Subscription**
--===== {{id name="_Toc90828"/}}7.5.2 Subscription Information =====
++=== 7.5.2 Subscription Information ===
  Regardless of the type of registry/repository events being observed, a subscription always contains:
@@ -1057,18 +1057,16 @@
 . A validity period which defines both when the subscription becomes active and expires. The subscriber may be sent a notification on expiration of the subscription.
 . A selector which specifies which type of events are of interest. The set of event types is:
--:
--::
--
  (((
--|**Event Type**|**Comment**
--|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
--|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
--|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
--|ALL_EVENTS|All events of the specified EventType
++(% style="width:1061.83px" %)
++|**Event Type**|(% style="width:660px" %)**Comment**
++|STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
++|DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
++|METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
++|ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType
  )))
--===== {{id name="_Toc90829"/}}7.5.3 Wildcard Facility =====
++=== 7.5.3 Wildcard Facility ===
  Subscription notification supports wildcarded identifier components URNs, which are identifiers which have some or all of their component parts replaced by the wildcard character `*`. Identifier components comprise:
@@ -1124,30 +1124,29 @@
  The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
--===== {{id name="_Toc90830"/}}7.5.4 Structural Repository Events =====
++=== 7.5.4 Structural Repository Events ===
  Whenever a maintainable artefact (data structure definition, concept scheme, codelist, metadata structure definition, category scheme, etc.) is added to, deleted from, or modified in the structural metadata repository, a structural metadata event is triggered. Subscriptions may be set up to monitor all such events, or focus on specific artefacts such as a Data Structure Definition.
--===== {{id name="_Toc90831"/}}7.5.5 Registration Events =====
++=== 7.5.5 Registration Events ===
  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**
--|DataProvider|Any datasets registered by the specified dataprovider will activate the notification.
--|ProvisionAgreement|Any datasets for the agreement will activate the notification.
--|Dataflow|Any datasets for the specified dataflow will activate the notification.
--|DataStructureDefinition|Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification
--|Category|Any datasets registered for those dataflows, provision agreements that are categorised by the category.
++(% style="width:1082.83px" %)
++|(% style="width:230px" %)**Selector**|(% style="width:850px" %)**Comment**
++|(% style="width:230px" %)DataProvider|(% style="width:850px" %)Any datasets registered by the specified dataprovider will activate the notification.
++|(% style="width:230px" %)ProvisionAgreement|(% style="width:850px" %)Any datasets for the agreement will activate the notification.
++|(% style="width:230px" %)Dataflow|(% style="width:850px" %)Any datasets for the specified dataflow will activate the notification.
++|(% style="width:230px" %)DataStructureDefinition|(% style="width:850px" %)Any datasets for those dataflows that are based on the specified Data Structure Definition will activate the notification
++|(% style="width:230px" %)Category|(% style="width:850px" %)Any datasets registered for those dataflows, provision agreements that are categorised by the category.
  )))
  The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
--== {{id name="_Toc90832"/}}7.6 Notification ==
++== 7.6 Notification ==
--==== {{id name="_Toc90833"/}}7.6.1 Logical Class Diagram ====
++=== 7.6.1 Logical Class Diagram ===
  [[image:SDMX 3.1 Section 5_en_8bc1b889.jpg||height="379" width="579"]]
@@ -1164,11 +1164,11 @@
  Additionally, supplementary information may be contained in the notification as detailed below.
--==== {{id name="_Toc90834"/}}7.6.2 Structural Event Component ====
++=== 7.6.2 Structural Event Component ===
  The notification will contain the MaintainableArtefact that triggered the event in a form similar to the SDMX-ML structural message (using elements from that namespace).
--==== {{id name="_Toc90835"/}}7.6.3 Registration Event Component ====
++=== 7.6.3 Registration Event Component ===
  The notification will contain the Registration.