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

Summary

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

Details

Page properties

Content

...	...	@@ -329,12 +329,14 @@
329	329
330	330	The table below shows the identification and related data attributes to be stored in a registry for objects that are one of:
331	331
332		-* //nnotable//
	332	+* //Annotable//
333	333	* //Identifiable//
334	334	* //Nameable//
335	335	* //Versionable//
336	336	* //Maintainable//
337	337
	338	+:
	339	+
338	338	(((
339	339	(% style="width:1052.29px" %)
340	340	|**Object Type**|(% style="width:241px" %)**Data Attributes**|(% style="width:156px" %)**Status**|**Data type**|(% style="width:457px" %)**Notes**
...	...	@@ -362,9 +362,9 @@
362	362
363	363	**Table 1: Common Attributes of Object Types**
364	364
365		-== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ==
	367	+=== {{id name="_Toc93856"/}}6.2 Unique identification of SDMX objects ===
366	366
367		-=== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers ===
	369	+===== {{id name="_Toc93857"/}}6.2.1 Agencies and Metadata Providers =====
368	368
369	369	The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
370	370
...	...	@@ -502,7 +502,7 @@
502	502
503	503	SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id
504	504
505		-===== //__**Concrete Examples of the URN Structure**__// =====
	507	+//__**Concrete Examples of the URN Structure**__//
506	506
507	507	The Data Structure Definition CRED_EXT_DEBT of legacy version 2.1 maintained by the toplevel Agency TFFS would have the URN:
508	508
...	...	@@ -622,118 +622,136 @@
622	622
623	623	urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
624	624
625		-(% style="width:1311.29px" %)
626		-|(% style="width:252px" %)**Classname**|(% style="width:639px" %)**Ending URN pattern**|(% style="width:418px" %)**Example**
627		-|(% style="width:252px" %)Agency{{footnote}}The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical. For example, a sub-agency of IMF is referred like this: IMF.SubAgency1{{/footnote}}|(% style="width:639px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:418px" %)ECB:**AGENCIES**(**1.0**).AA
628		-|(% style="width:252px" %)//AgencyScheme//|(% style="width:639px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:418px" %)ECB:**AGENCIES**(**1.0**)
629		-|(% style="width:252px" %)//Categorisation//|(% style="width:639px" %)categorisationAgencyId:categorisationId(version)|(% style="width:418px" %)IMF:cat001(1.0.0)
630		-|(% style="width:252px" %)Category|(% style="width:639px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:418px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category …
631		-|(% style="width:252px" %)//CategoryScheme//|(% style="width:639px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:418px" %)IMF:SDDS(1.0.0)
	627	+|**Classname**|**Ending URN pattern**|**Example**
	628	+|Agency^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^|agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|ECB:**AGENCIES**(**1.0**).AA
	629	+|//AgencyScheme//|agencySchemeAgencyId:**AGENCIES**(**1.0**)|ECB:**AGENCIES**(**1.0**)
	630	+|//Categorisation//|categorisationAgencyId:categorisationId(version)|IMF:cat001(1.0.0)
	631	+|Category|categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|IMF:SDDS(1.0.0):level_1_category.level_2_category …
	632	+|//CategoryScheme//|categorySchemeAgencyId:categorySchemeId(versi on)|IMF:SDDS(1.0.0)
632	632
633		-|(% style="width:250px" %)**Classname**|(% style="width:639px" %)**Ending URN pattern**|(% style="width:1049px" %)**Example**
634		-|(% style="width:250px" %)//CategorySchemeMap//|(% style="width:639px" %)(((
635		-catSchemeMapAgencyId:catSchemeMapId(version)
636		-)))|(% style="width:1049px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
637		-|(% style="width:250px" %)Code|(% style="width:639px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:1049px" %)SDMX:CL_FREQ(1.0.0).Q
638		-|(% style="width:250px" %)//Codelist//|(% style="width:639px" %)codeListAgencyId:codeListId(version)|(% style="width:1049px" %)SDMX:CL_FREQ(1.0.0)
639		-|(% style="width:250px" %)ComponentMap|(% style="width:639px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:1049px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
640		-|(% style="width:250px" %)Concept|(% style="width:639px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:1049px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
641		-|(% style="width:250px" %)//ConceptScheme//|(% style="width:639px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:1049px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
642		-|(% style="width:250px" %)//ConceptSchemeMap//|(% style="width:639px" %)(((
	634	+|**Classname**|**Ending URN pattern**|**Example**
	635	+|//CategorySchemeMap//|(((
	636	+catSchemeMapAgencyId:catSchemeMapId(version
	637	+
	638	+)
	639	+)))|SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
	640	+|Code|codeListAgencyId:codelistId(version).codeId|SDMX:CL_FREQ(1.0.0).Q
	641	+|//Codelist//|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0.0)
	642	+|ComponentMap|structureMapAgencyId:structureMap(version).com ponentMapId|SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
	643	+|Concept|conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
	644	+|//ConceptScheme//|conceptSchemeAgencyId:conceptSchemeId(versio n)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
	645	+|//ConceptSchemeMap//|(((
643	643	conceptSchemeMapAgencyId:conceptSchemeMap
	647	+
644	644	Id(version)
645		-)))|(% style="width:1049px" %)SDMX:CONCEPT_MAP(1.0.0)
646		-|(% style="width:250px" %)CustomType|(% style="width:639px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:1049px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
647		-|(% style="width:250px" %)//CustomTypeScheme//|(% style="width:639px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:1049px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0)
648		-|(% style="width:250px" %)DataAttrribute|(% style="width:639px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:1049px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS
649		-|(% style="width:250px" %)//DataConstraint//|(% style="width:639px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:1049px" %)TFFS:CREDITOR_DATA_CONTENT(1.0.0)
	649	+)))|SDMX:CONCEPT_MAP(1.0.0)
	650	+|CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
	651	+|//CustomTypeScheme//|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0.0)
	652	+|DataAttrribute|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|TFFS:EXT_DEBT(1.0.0).OBS_STATUS
	653	+|//DataConstraint//|dataConstraintAgencyId:dataConstraintId(version)|TFFS:CREDITOR_DATA_CONTENT(1.0.0)
650	650
651		-|(% style="width:248px" %)**Classname**|(% style="width:643px" %)**Ending URN pattern**|(% style="width:1047px" %)**Example**
652		-|(% style="width:248px" %)DataConsumer|(% style="width:643px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:1047px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
653		-|(% style="width:248px" %)//DataConsumerScheme//|(% style="width:643px" %)(((
654		-dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**)
655		-)))|(% style="width:1047px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
656		-|(% style="width:248px" %)//Dataflow//|(% style="width:643px" %)dataflowAgencyId:dataflowId(version)|(% style="width:1047px" %)TFFS:CRED_EXT_DEBT(1.0.0)
657		-|(% style="width:248px" %)DataProvider|(% style="width:643px" %)(((
658		-dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**).dataProviderId
659		-)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
660		-|(% style="width:248px" %)//DataProviderScheme//|(% style="width:643px" %)(((
661		-dataProviderSchemeAgencyId:**DATA_PROVIDERS**(**1.0**)
662		-)))|(% style="width:1047px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
663		-|(% style="width:248px" %)//DataStructure//|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0)
664		-|(% style="width:248px" %)Dimension|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0).FREQ
665		-|(% style="width:248px" %)(((
	655	+|**Classname**|**Ending URN pattern**|**Example**
	656	+|DataConsumer|dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
	657	+|//DataConsumerScheme//|(((
	658	+dataConsumerSchemeAgencyId:**DATA_CONSUME**
	659	+
	660	+**RS**(**1.0**)
	661	+)))|SDMX:**DATA_CONSUMERS**(**1.0**)
	662	+|//Dataflow//|dataflowAgencyId:dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0.0)
	663	+|DataProvider|(((
	664	+dataProviderSchemeAgencyId:**DATA_PROVIDERS**(
	665	+
	666	+**1.0**).dataProviderId
	667	+)))|SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
	668	+|//DataProviderScheme//|(((
	669	+dataProviderSchemeAgencyId:**DATA_PROVIDERS**(
	670	+
	671	+**1.0**)
	672	+)))|SDMX:**DATA_PROVIDERS**(**1.0**)
	673	+|//DataStructure//|dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|TFFS:EXT_DEBT(1.0.0)
	674	+|Dimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|TFFS:EXT_DEBT(1.0.0).FREQ
	675	+|(((
666	666	DimensionDescriptor
	677	+
667	667	MeasureDescriptor
	679	+
668	668	AttributeDescriptor
669		-)))|(% style="width:643px" %)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)|(% style="width:1047px" %)(((
	681	+)))|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)|(((
670	670	TFFS:EXT_DEBT(1.0.0).DimensionDescriptor
	683	+
671	671	TFFS:EXT_DEBT(1.0.0).MeasureDescriptor
	685	+
672	672	TFFS:EXT_DEBT(1.0.0).AttributeDescriptor
673	673	)))
674		-|(% style="width:248px" %)GroupDimensionDescriptor|(% style="width:643px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:1047px" %)TFFS:EXT_DEBT(1.0.0).SIBLING
675		-|(% style="width:248px" %)HierarchicalCode|(% style="width:643px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:1047px" %)UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
	688	+|GroupDimensionDescriptor|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|TFFS:EXT_DEBT(1.0.0).SIBLING
	689	+|HierarchicalCode|hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|UNESCO:H-C-GOV(1.0.0).GOV_CODE1.GOV_CODE1_1
676	676
677		-|(% style="width:248px" %)**Classname**|(% style="width:646px" %)**Ending URN pattern**|(% style="width:1044px" %)**Example**
678		-|(% style="width:248px" %)//Hierarchy//|(% style="width:646px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:1044px" %)UNESCO:H-C-GOV(1.0.0)
679		-|(% style="width:248px" %)//HierarchyAssociation//|(% style="width:646px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:1044px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
680		-|(% style="width:248px" %)Level|(% style="width:646px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:1044px" %)UNESCO:H-C-GOV(1.0.0).LVL1
681		-|(% style="width:248px" %)Measure|(% style="width:646px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:1044px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE
682		-|(% style="width:248px" %)MetadataAttribute|(% style="width:646px" %)(((
	691	+|**Classname**|**Ending URN pattern**|**Example**
	692	+|//Hierarchy//|hierarchyAgencyId:hierarchyId(version)|UNESCO:H-C-GOV(1.0.0)
	693	+|//HierarchyAssociation//|hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|UNESCO:CL_EXP_SOURCE(1.0.0)
	694	+|Level|hierarchyAgencyId:hierarchyId(version).level|UNESCO:H-C-GOV(1.0.0).LVL1
	695	+|Measure|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|TFFS:EXT_DEBT(1.0.0).OBS_VALUE
	696	+|MetadataAttribute|(((
683	683	msdAgencyId:msdId(version).metadataAttributeId.
	698	+
684	684	metadataAttributeId
685		-)))|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
686		-|(% style="width:248px" %)MetadataAttributeDescriptor|(% style="width:646px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
687		-|(% style="width:248px" %)//MetadataConstraint//|(% style="width:646px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:1044px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
688		-|(% style="width:248px" %)//Metadataflow//|(% style="width:646px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:1044px" %)IMF:SDDS_MDF(1.0.0)
689		-|(% style="width:248px" %)MetadataProvider|(% style="width:646px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:1044px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
690		-|(% style="width:248px" %)//MetadataProviderScheme//|(% style="width:646px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:1044px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
691		-|(% style="width:248px" %)//MetadataProvisionAgreement//|(% style="width:646px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:1044px" %)IMF:SDDS_MDF_AB(1.0.0)
692		-|(% style="width:248px" %)//MetadataSet//|(% style="width:646px" %)metadataProviderId:metadataSetId(version)|(% style="width:1044px" %)MD_PROVIDER:METADATASET(1.0.0)
693		-|(% style="width:248px" %)//MetadataStructure//|(% style="width:646px" %)msdAgencyId:msdId(version)|(% style="width:1044px" %)IMF:SDDS_MSD(1.0.0)
	700	+)))|IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
	701	+|MetadataAttributeDescriptor|msdAgencyId:msdId(version).metadataAttributeDe scriptorId|IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
	702	+|//MetadataConstraint//|metadataConstraintAgencyId:metadataConstraintI d(version)|TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
	703	+|//Metadataflow//|metadataflowAgencyId:metadataflowId(version)|IMF:SDDS_MDF(1.0.0)
	704	+|MetadataProvider|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
	705	+|//MetadataProviderScheme//|metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|SDMX:**METADATA_PROVIDERS**(**1.0**)
	706	+|//MetadataProvisionAgreement//|metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|IMF:SDDS_MDF_AB(1.0.0)
	707	+|//MetadataSet//|metadataProviderId:metadataSetId(version)|MD_PROVIDER:METADATASET(1.0.0)
	708	+|//MetadataStructure//|msdAgencyId:msdId(version)|IMF:SDDS_MSD(1.0.0)
694	694
695		-|(% style="width:248px" %)**Classname**|(% style="width:629px" %)**Ending URN pattern**|(% style="width:1061px" %)**Example**
696		-|(% style="width:248px" %)NamePersonalisation|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0).PSN1234
697		-|(% style="width:248px" %)//NamePersonalisationScheme//|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0)
698		-|(% style="width:248px" %)//OrganisationSchemeMap//|(% style="width:629px" %)orgSchemeMapAgencyId:orgSchemeMapId(versio n)|(% style="width:1061px" %)SDMX:AGENCIES_PROVIDERS(1.0.0)
699		-|(% style="width:248px" %)OrganisationUnit|(% style="width:629px" %)organisationUnitSchemeAgencyId:organisationUnitSchemeId(version).organisationUnitId|(% style="width:1061px" %)ECB:ORGANISATIONS(1.0.0).1F
700		-|(% style="width:248px" %)//OrganisationUnitScheme//|(% style="width:629px" %)organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|(% style="width:1061px" %)ECB:ORGANISATIONS(1.0.0)
701		-|(% style="width:248px" %)//Process//|(% style="width:629px" %)processAgencyId:processId{version)|(% style="width:1061px" %)BIS:PROCESS1(1.0.0)
702		-|(% style="width:248px" %)ProcessStep|(% style="width:629px" %)(((
	710	+|**Classname**|**Ending URN pattern**|**Example**
	711	+|NamePersonalisation|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0.0).PSN1234
	712	+|//NamePersonalisationScheme//|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0.0)
	713	+|//OrganisationSchemeMap//|orgSchemeMapAgencyId:orgSchemeMapId(versio n)|SDMX:AGENCIES_PROVIDERS(1.0.0)
	714	+|OrganisationUnit|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version).organisationUnitId|ECB:ORGANISATIONS(1.0.0).1F
	715	+|//OrganisationUnitScheme//|organisationUnitSchemeAgencyId:organisationUni tSchemeId(version)|ECB:ORGANISATIONS(1.0.0)
	716	+|//Process//|processAgencyId:processId{version)|BIS:PROCESS1(1.0.0)
	717	+|ProcessStep|(((
703	703	processAgencyId:processId(version).processStepId.
	719	+
704	704	processStepId
705		-)))|(% style="width:1061px" %)BIS:PROCESS1(1.0.0).STEP1.STEP1_1
706		-|(% style="width:248px" %)//ProvisionAgreement//|(% style="width:629px" %)provisionAgreementAgencyId:provisionAgreement Id(version)|(% style="width:1061px" %)TFFS:CRED_EXT_DEBT_AB(1.0.0)
707		-|(% style="width:248px" %)ReportingCategory|(% style="width:629px" %)(((
	721	+)))|BIS:PROCESS1(1.0.0).STEP1.STEP1_1
	722	+|//ProvisionAgreement//|provisionAgreementAgencyId:provisionAgreement Id(version)|TFFS:CRED_EXT_DEBT_AB(1.0.0)
	723	+|ReportingCategory|(((
708	708	reportingTaxonomyAgencyId:
	725	+
709	709	reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId
710		-)))|(% style="width:1061px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
711		-|(% style="width:248px" %)//ReportingTaxonomy//|(% style="width:629px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:1061px" %)IMF:REP_1(1.0.0)
712		-|(% style="width:248px" %)//ReportingTaxonomyMap//|(% style="width:629px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:1061px" %)SDMX:RT_MAP(1.0.0)
	727	+)))|IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
	728	+|//ReportingTaxonomy//|reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|IMF:REP_1(1.0.0)
	729	+|//ReportingTaxonomyMap//|repTaxonomyAgencyId:repTaxonomyId(version)|SDMX:RT_MAP(1.0.0)
713	713
714		-|(% style="width:247px" %)**Classname**|(% style="width:649px" %)**Ending URN pattern**|(% style="width:1042px" %)**Example**
715		-|(% style="width:247px" %)//RepresentationMap//|(% style="width:649px" %)repMapAgencyId:repMapId(version)|(% style="width:1042px" %)SDMX:REF_AREA_MAPPING(1.0.0)
716		-|(% style="width:247px" %)Ruleset|(% style="width:649px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:1042px" %)ECB:RULESET_23(1.0.0).SET111
717		-|(% style="width:247px" %)//RulesetScheme//|(% style="width:649px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:1042px" %)ECB:RULESET_23(1.0.0)
718		-|(% style="width:247px" %)//StructureMap//|(% style="width:649px" %)structureMapAgencyId:structureMap(version)|(% style="width:1042px" %)SDMX:BOP_STRUCTURES(1.0.0)
719		-|(% style="width:247px" %)Subscription|(% style="width:649px" %)(((
	731	+|**Classname**|**Ending URN pattern**|**Example**
	732	+|//RepresentationMap//|repMapAgencyId:repMapId(version)|SDMX:REF_AREA_MAPPING(1.0.0)
	733	+|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0.0).SET111
	734	+|//RulesetScheme//|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0.0)
	735	+|//StructureMap//|structureMapAgencyId:structureMap(version)|SDMX:BOP_STRUCTURES(1.0.0)
	736	+|Subscription|(((
720	720	The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure.
	738	+
721	721	The name of the URN is registryURN There is no pre-determined format.
722		-)))|(% style="width:1042px" %)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.
723		-|(% style="width:247px" %)TimeDimension|(% style="width:649px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|(% style="width:1042px" %)TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
724		-|(% style="width:247px" %)Transformation|(% style="width:649px" %)transformationSchemeAgencyId transformationSchemeId(version) transformationId|(% style="width:1042px" %)ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
725		-|(% style="width:247px" %)//TransformationScheme//|(% style="width:649px" %)transformationSchemeAgencyId transformationSchemeId(version)|(% style="width:1042px" %)ECB: TRANSFORMATION_SCHEME(1.0.0)
726		-|(% style="width:247px" %)Transition|(% style="width:649px" %)(((
	740	+)))|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.
	741	+|TimeDimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
	742	+|Transformation|transformationSchemeAgencyId transformationSchemeId(version) transformationId|ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
	743	+|//TransformationScheme//|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0.0)
	744	+|**Classname**|**Ending URN pattern**|**Example**
	745	+|Transition|(((
727	727	processAgencyId:processId(version).processStepId.
	747	+
728	728	transitionId
729		-)))|(% style="width:1042px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
730		-|(% style="width:247px" %)UserDefinedOperator|(% style="width:649px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:1042px" %)ECB:OS_CALC(1.2.0).OS267
731		-|(% style="width:247px" %)//UserDefinedOperatorScheme//|(% style="width:649px" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:1042px" %)ECB:OS_CALC(1.2.0)
732		-|(% style="width:247px" %)//ValueList//|(% style="width:649px" %)valuelistAgencyId:valuelistId(version)|(% style="width:1042px" %)SDMX:VLIST(1.0.0)
733		-|(% style="width:247px" %)VtlCodelistMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:1042px" %)ECB:CLIST_MP(2.0.0).ABZ
734		-|(% style="width:247px" %)VtlConceptMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:1042px" %)ECB:CLIST_MP(1.0.0).XYA
735		-|(% style="width:247px" %)VtlDataflowMapping|(% style="width:649px" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:1042px" %)ECB:CLIST_MP(1.0.0).MOQ
736		-|(% style="width:247px" %)//VtlMappingScheme//|(% style="width:649px" %)vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|(% style="width:1042px" %)ECB:CLIST_MP(2.0.0)
	749	+)))|BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
	750	+|UserDefinedOperator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2.0).OS267
	751	+|//UserDefinedOperatorScheme//|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2.0)
	752	+|//ValueList//|valuelistAgencyId:valuelistId(version)|SDMX:VLIST(1.0.0)
	753	+|VtlCodelistMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0.0).ABZ
	754	+|VtlConceptMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0.0).XYA
	755	+|VtlDataflowMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0.0).MOQ
	756	+|//VtlMappingScheme//|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0.0)
737	737
738	738	**Table 3: Table of identification components for SDMX Identifiable Artefacts**
739	739
...	...	@@ -741,7 +741,7 @@
741	741
742	742	=== {{id name="_Toc93862"/}}7.1 Structural Definition Metadata ===
743	743
744		-=== {{id name="_Toc93863"/}}7.1.1 Introduction ===
	764	+===== {{id name="_Toc93863"/}}7.1.1 Introduction =====
745	745
746	746	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.)
747	747
...	...	@@ -757,79 +757,90 @@
757	757
758	758	The following table lists the Maintainable Artefacts.
759	759
760		-(% style="width:881.294px" %)
761		-|(% colspan="2" style="width:522px" %)**Maintainable Artefacts**|(% style="width:490px" %)**Content**
762		-|(% style="width:198px" %)**Abstract Class**|(% style="width:324px" %)**Concrete Class**|(% style="width:490px" %)
763		-|(% style="width:198px" %)Item Scheme|(% style="width:324px" %)Codelist|(% style="width:490px" %)Code
764		-|(% style="width:198px" %) |(% style="width:324px" %)Concept Scheme|(% style="width:490px" %)Concept
765		-|(% style="width:198px" %) |(% style="width:324px" %)Category Scheme|(% style="width:490px" %)Category
766		-|(% style="width:198px" %) |(% style="width:324px" %)Organisation Unit Scheme|(% style="width:490px" %)Organisation Unit
767		-|(% style="width:198px" %) |(% style="width:324px" %)Agency Scheme|(% style="width:490px" %)Agency
768		-|(% style="width:198px" %) |(% style="width:324px" %)Data Provider Scheme|(% style="width:490px" %)Data Provider
769		-|(% style="width:198px" %) |(% style="width:324px" %)Metadata Provider Scheme|(% style="width:490px" %)Metadata Provider
770		-|(% style="width:198px" %) |(% style="width:324px" %)Data Consumer Scheme|(% style="width:490px" %)Data Consumer
771		-|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy|(% style="width:490px" %)Reporting Category
772		-|(% style="width:198px" %) |(% style="width:324px" %)Transformation Scheme|(% style="width:490px" %)Transformation
773		-|(% style="width:198px" %) |(% style="width:324px" %)Custom Type Scheme|(% style="width:490px" %)Custom Type
774		-|(% style="width:198px" %) |(% style="width:324px" %)Name Personalisation Scheme|(% style="width:490px" %)Name Personalisation
775		-|(% style="width:198px" %) |(% style="width:324px" %)Vtl Mapping Scheme|(% style="width:490px" %)Vtl Codelist Mapping Vtl Concept Mapping
776		-|(% style="width:198px" %) |(% style="width:324px" %)Ruleset Scheme|(% style="width:490px" %)Ruleset
777		-|(% style="width:198px" %) |(% style="width:324px" %)User Defined Operator Scheme|(% style="width:490px" %)User Defined Operator
778		-|(% style="width:198px" %)Enumerated List|(% style="width:324px" %)ValueList|(% style="width:490px" %)Value Item
779		-|(% style="width:198px" %)Structure|(% style="width:324px" %)Data Structure Definition|(% style="width:490px" %)(((
	780	+|(% colspan="2" %)**Maintainable Artefacts**|**Content**
	781	+|**Abstract Class**|**Concrete Class**|
	782	+|Item Scheme|Codelist|Code
	783	+| |Concept Scheme|Concept
	784	+| |Category Scheme|Category
	785	+| |Organisation Unit Scheme|Organisation Unit
	786	+| |Agency Scheme|Agency
	787	+| |Data Provider Scheme|Data Provider
	788	+| |Metadata Provider Scheme|Metadata Provider
	789	+| |Data Consumer Scheme|Data Consumer
	790	+| |Reporting Taxonomy|Reporting Category
	791	+| |Transformation Scheme|Transformation
	792	+| |Custom Type Scheme|Custom Type
	793	+| |Name Personalisation Scheme|Name Personalisation
	794	+| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
	795	+| |Ruleset Scheme|Ruleset
	796	+| |User Defined Operator Scheme|User Defined Operator
	797	+|Enumerated List|ValueList|Value Item
	798	+|Structure|Data Structure Definition|(((
780	780	Dimension Descriptor
	800	+
781	781	Group Dimension Descriptor
	802	+
782	782	Dimension
	804	+
783	783	Time Dimension
	806	+
784	784	Attribute Descriptor
	808	+
785	785	Data Attribute
	810	+
786	786	Measure Descriptor
	812	+
787	787	Measure
788	788	)))
789		-|(% style="width:198px" %) |(% style="width:324px" %)Metadata Structure Definition|(% style="width:490px" %)Metadata Attribute Descriptor Metadata Attribute
790		-|(% style="width:198px" %)Structure Usage|(% style="width:324px" %)Dataflow|(% style="width:490px" %)
791		-|(% style="width:198px" %) |(% style="width:324px" %)Metadataflow|(% style="width:490px" %)
792		-|(% style="width:198px" %)None|(% style="width:324px" %)Process|(% style="width:490px" %)Process Step
793		-|(% style="width:198px" %)None|(% style="width:324px" %)Structure Map|(% style="width:490px" %)(((
	815	+| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
	816	+|Structure Usage|Dataflow|
	817	+| |Metadataflow|
	818	+|None|Process|Process Step
	819	+|None|Structure Map|(((
794	794	Component Map
	821	+
795	795	Epoch Map
	823	+
796	796	Date Pattern Map
797	797	)))
798		-|(% style="width:198px" %)None|(% style="width:324px" %)Representation Map|(% style="width:490px" %)Representation Mapping
799		-|(% style="width:198px" %)Item Scheme Map|(% style="width:324px" %)Organisation Scheme Map|(% style="width:490px" %)Item Map
800		-|(% style="width:198px" %) |(% style="width:324px" %)Concept Scheme Map|(% style="width:490px" %)Item Map
801		-|(% style="width:198px" %) |(% style="width:324px" %)Category Scheme Map|(% style="width:490px" %)Item Map
802		-|(% style="width:198px" %) |(% style="width:324px" %)Reporting Taxonomy Map|(% style="width:490px" %)Item Map
803		-|(% style="width:198px" %)None|(% style="width:324px" %)Provision Agreement|(% style="width:490px" %)
804		-|(% style="width:198px" %)None|(% style="width:324px" %)Metadata Provision Agreement|(% style="width:490px" %)
805		-|(% style="width:198px" %)None|(% style="width:324px" %)Hierarchy|(% style="width:490px" %)Hierarchical Code
806		-|(% style="width:198px" %)None|(% style="width:324px" %)Hierarchy Association|(% style="width:490px" %)
807		-|(% style="width:198px" %)None|(% style="width:324px" %)Categorisation|(% style="width:490px" %)
	826	+|None|Representation Map|Representation Mapping
	827	+|Item Scheme Map|Organisation Scheme Map|Item Map
	828	+| |Concept Scheme Map|Item Map
	829	+| |Category Scheme Map|Item Map
	830	+| |Reporting Taxonomy Map|Item Map
	831	+|None|Provision Agreement|
	832	+|None|Metadata Provision Agreement|
	833	+|None|Hierarchy|Hierarchical Code
	834	+|None|Hierarchy Association|
	835	+|None|Categorisation|
808	808
809	809	**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
810	810
811		-=== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure ===
	839	+===== {{id name="_Toc93864"/}}7.1.2 Item Scheme, Structure =====
812	812
813	813	The artefacts included in the structural definitions are:
814	814
815		-* 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)
816		-* All types of Enumerated List (ValueList){{footnote}}Note that Codelist is also an EnumeratedList.{{/footnote}}
817		-* All types of Structure (Data Structure Definition, Metadata Structure Definition)
818		-* All types of Structure Usage (Dataflow, Metadataflow)
	843	+• All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme, Agency Scheme, Data Provider Scheme, Metadata Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme, Transformation Scheme, Name Personalisation Scheme, Custom Type Scheme, Vtl Mapping Scheme, Ruleset Scheme, User Defined Operator Scheme)
819	819
820		-=== {{id name="_Toc93865"/}}7.1.3 Structure Usage ===
	845	+• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
821	821
822		-==== 7.1.3.1 Structure Usage: Basic Concepts ====
	847	+• All types of Structure (Data Structure Definition, Metadata Structure Definition)
823	823
	849	+• All types of Structure Usage (Dataflow, Metadataflow)
	850	+
	851	+===== {{id name="_Toc93865"/}}7.1.3 Structure Usage =====
	852	+
	853	+**7.1.3.1 Structure Usage: Basic Concepts**
	854	+
824	824	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.
825	825
826		-==== 7.1.3.2 Structure Usage Schematic ====
	857	+**7.1.3.2 Structure Usage Schematic**
827	827
828	828	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_52097ab5.jpg||height="246" width="438"]]
829	829
830	830	**Figure 9: Schematic of Linking the Data and Metadata Flows to Categories and Structure Definitions**
831	831
832		-==== 7.1.3.3 Structure Usage Model ====
	863	+**7.1.3.3 Structure Usage Model**
833	833
834	834	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_302cc1a2.jpg||height="548" width="578"]]
835	835
...	...	@@ -845,9 +845,9 @@
845	845	* Categorisation to Dataflow and Category
846	846	* Categorisation to Metadataflow and Category
847	847
848		-== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ==
	879	+=== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ===
849	849
850		-=== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts ===
	881	+===== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts =====
851	851
852	852	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.
853	853
...	...	@@ -855,7 +855,7 @@
855	855
856	856	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.
857	857
858		-=== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case ===
	889	+===== {{id name="_Toc93868"/}}7.2.2 Provisioning Agreement Model – pull use case =====
859	859
860	860	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.
861	861
...	...	@@ -877,9 +877,9 @@
877	877
878	878	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.
879	879
880		-== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ==
	911	+=== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ===
881	881
882		-=== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts ===
	913	+===== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts =====
883	883
884	884	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.
885	885
...	...	@@ -943,14 +943,17 @@
943	943
944	944	The Registration has an action attribute which takes one of the following values:
945	945
	977	+:
	978	+
946	946	(((
947		-(% style="width:761.294px" %)
948		-|(% style="width:196px" %)**Action Attribute Value**|(% style="width:561px" %)**Behaviour**
949		-|(% style="width:196px" %)Append|(% style="width:561px" %)Add this Registration to the registry
950		-|(% style="width:196px" %)Replace|(% style="width:561px" %)(((
951		-Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
	980	+|**Action Attribute Value**|**Behaviour**
	981	+|Append|Add this Registration to the registry
	982	+|Replace|(((
	983	+Replace the existing Registration with identified by the id in the
	984	+
	985	+Registration of the SubmitRegistrationRequest
952	952	)))
953		-|(% style="width:196px" %)Delete|(% style="width:561px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
	987	+|Delete|Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
954	954	)))
955	955
956	956	[[image:SDMX 3-0-0 SECTION 5 FINAL-1.0_en_bc1dcdec.jpg||height="575" width="579"]]
...	...	@@ -967,20 +967,27 @@
967	967
968	968	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.
969	969
	1004	+:
	1005	+
970	970	(((
971		-(% style="width:678.294px" %)
972		-|**Indexing Required**|(% style="width:504px" %)**Registration Process Activity**
973		-|indexTimeSeries|(% style="width:504px" %)Extract all the series keys and create a KeySet(s) Constraint.
974		-|indexDataSet|(% style="width:504px" %)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.
975		-|indexReportingPeriod|(% style="width:504px" %)(((
	1007	+|**Indexing Required**|**Registration Process Activity**
	1008	+|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
	1009	+|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.
	1010	+|indexReportingPeriod|(((
976	976	This applies only to a registered __dataset__.
	1012	+
977	977	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
978	978	)))
979		-|**Indexing Required**|(% style="width:504px" %)**Registration Process Activity**
980		-|indexAttributes|(% style="width:504px" %)(((
	1015	+|**Indexing Required**|**Registration Process Activity**
	1016	+|indexAttributes|(((
981	981	**Data Set**
982		-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
	1018	+
	1019	+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
	1020	+
	1021	+SDMXIM, and the associated Selection Value
	1022	+
983	983	**Metadata Set**
	1024	+
984	984	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 SDMX-IM. Note that the content is not stored in the Selection Value.
985	985	)))
986	986	)))
...	...	@@ -989,7 +989,7 @@
989	989
990	990	The Registration must reference the ProvisionAgreement or MetadataProvisionAgreement to which it relates.
991	991
992		-=== {{id name="_Toc93876"/}}7.4.3 Registration Response ===
	1033	+===== {{id name="_Toc93876"/}}7.4.3 Registration Response =====
993	993
994	994	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”.
995	995
...	...	@@ -1019,18 +1019,20 @@
1019	1019
1020	1020	Regardless of the type of registry/repository events being observed, a subscription always contains:
1021	1021
1022		-1. set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
	1063	+1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
1023	1023	1. A user-defined identifier, which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
1024	1024	1. 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.
1025	1025	1. A selector which specifies which type of events are of interest. The set of event types is:
1026	1026
	1068	+:
	1069	+::
	1070	+
1027	1027	(((
1028		-(% style="width:856.294px" %)
1029		-|(% style="width:320px" %)**Event Type**|(% style="width:532px" %)**Comment**
1030		-|(% style="width:320px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:532px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1031		-|(% style="width:320px" %)DATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1032		-|(% style="width:320px" %)METADATA_REGISTRATION_EVENTS|(% style="width:532px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1033		-|(% style="width:320px" %)ALL_EVENTS|(% style="width:532px" %)All events of the specified EventType
	1072	+|**Event Type**|**Comment**
	1073	+|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
	1074	+|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
	1075	+|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
	1076	+|ALL_EVENTS|All events of the specified EventType
1034	1034	)))
1035	1035
1036	1036	=== {{id name="_Toc93880"/}}7.5.3 Wildcard Facility ===
...	...	@@ -1097,14 +1097,15 @@
1097	1097
1098	1098	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:
1099	1099
	1143	+:
	1144	+
1100	1100	(((
1101		-(% style="width:1126.29px" %)
1102		-|(% style="width:382px" %)**Selector**|(% style="width:740px" %)**Comment**
1103		-|(% style="width:382px" %)DataProvider & MetadataProvider|(% style="width:740px" %)Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
1104		-|(% style="width:382px" %)ProvisionAgreement & MetadataProvisionAgreement|(% style="width:740px" %)Any datasets or metadata sets registered for the agreement will activate the notification.
1105		-|(% style="width:382px" %)Dataflow & Metadataflow|(% style="width:740px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1106		-|(% style="width:382px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:740px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification
1107		-|(% style="width:382px" %)Category|(% style="width:740px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
	1146	+|**Selector**|**Comment**
	1147	+|DataProvider & MetadataProvider|Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
	1148	+|ProvisionAgreement & MetadataProvisionAgreement|Any datasets or metadata sets registered for the agreement will activate the notification.
	1149	+|Dataflow & Metadataflow|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
	1150	+|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification
	1151	+|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1108	1108	)))
1109	1109
1110	1110	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
...	...	@@ -1136,6 +1136,12 @@
1136	1136
1137	1137	The notification will contain the Registration.
1138	1138
1139		-----
	1183	+[[1>>path:#sdfootnote1anc||name="sdfootnote1sym"]] With semantic versioning, it is allowed to reference a range of artefacts, e.g., a DSD referencing a Codelist with version 1.2.3+ means all patch versions greater than 1.2.3. This means that deleting 1.2.4draft does not break integrity of the aforementioned DSD.
1140	1140
	1185	+[[2>>path:#sdfootnote2anc||name="sdfootnote2sym"]] The identification of an Agency in the URN structure for the maintainable object is by means of the agencyId. The AgencyScheme is not identified as SDMX has a mechanism for identifying an Agency uniquely by its Id. Note that this Id may be hierarchical. For example, a sub-agency of IMF is referred like this:
	1186	+
	1187	+IMF.SubAgency1
	1188	+
	1189	+[[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.
	1190	+
1141	1141	{{putFootnotes/}}