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

Summary

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  
... ... @@ -623,74 +623,74 @@
623 623  urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
624 624  
625 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)
628 +|(% style="width:252px" %)**Classname**|(% style="width:619px" %)**Ending URN pattern**|(% style="width:438px" %)**Example**
629 +|(% 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:619px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**).agencyId|(% style="width:438px" %)ECB:**AGENCIES**(**1.0**).AA
630 +|(% style="width:252px" %)//AgencyScheme//|(% style="width:619px" %)agencySchemeAgencyId:**AGENCIES**(**1.0**)|(% style="width:438px" %)ECB:**AGENCIES**(**1.0**)
631 +|(% style="width:252px" %)//Categorisation//|(% style="width:619px" %)categorisationAgencyId:categorisationId(version)|(% style="width:438px" %)IMF:cat001(1.0.0)
632 +|(% style="width:252px" %)Category|(% style="width:619px" %)categorySchemeAgencyId:categorySchemeId(versi on).categoryId.categoryId.categoryId etc.|(% style="width:438px" %)IMF:SDDS(1.0.0):level_1_category.level_2_category …
633 +|(% style="width:252px" %)//CategoryScheme//|(% style="width:619px" %)categorySchemeAgencyId:categorySchemeId(versi on)|(% style="width:438px" %)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 +|(% style="width:250px" %)**Classname**|(% style="width:624px" %)**Ending URN pattern**|(% style="width:1064px" %)**Example**
636 +|(% style="width:250px" %)//CategorySchemeMap//|(% style="width:624px" %)(((
635 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" %)(((
638 +)))|(% style="width:1064px" %)SDMX:EUROSTAT_SUBJECT_DOMAIN(1.0.0)
639 +|(% style="width:250px" %)Code|(% style="width:624px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:1064px" %)SDMX:CL_FREQ(1.0.0).Q
640 +|(% style="width:250px" %)//Codelist//|(% style="width:624px" %)codeListAgencyId:codeListId(version)|(% style="width:1064px" %)SDMX:CL_FREQ(1.0.0)
641 +|(% style="width:250px" %)ComponentMap|(% style="width:624px" %)structureMapAgencyId:structureMap(version).com ponentMapId|(% style="width:1064px" %)SDMX:BOP_STRUCTURES(1.0.0).REF_AREA_TO_COUNT RY
642 +|(% style="width:250px" %)Concept|(% style="width:624px" %)conceptSchemeAgencyId:conceptSchemeId(versio n).conceptId|(% style="width:1064px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0).FREQ
643 +|(% style="width:250px" %)//ConceptScheme//|(% style="width:624px" %)conceptSchemeAgencyId:conceptSchemeId(versio n)|(% style="width:1064px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0.0)
644 +|(% style="width:250px" %)//ConceptSchemeMap//|(% style="width:624px" %)(((
643 643  conceptSchemeMapAgencyId:conceptSchemeMap
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)
647 +)))|(% style="width:1064px" %)SDMX:CONCEPT_MAP(1.0.0)
648 +|(% style="width:250px" %)CustomType|(% style="width:624px" %)customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|(% style="width:1064px" %)ECB: CUSTOM_TYPE_SCHEME(1.0.0).CUSTOM_TYPE_1
649 +|(% style="width:250px" %)//CustomTypeScheme//|(% style="width:624px" %)customTypeSchemeAgencyId customTypeSchemeId(version)|(% style="width:1064px" %)ECB:CUSTOM_TYPE_SCHEME(1.0.0)
650 +|(% style="width:250px" %)DataAttrribute|(% style="width:624px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dataAttributeId|(% style="width:1064px" %)TFFS:EXT_DEBT(1.0.0).OBS_STATUS
651 +|(% style="width:250px" %)//DataConstraint//|(% style="width:624px" %)dataConstraintAgencyId:dataConstraintId(version)|(% style="width:1064px" %)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" %)(((
653 +|(% style="width:248px" %)**Classname**|(% style="width:628px" %)**Ending URN pattern**|(% style="width:1062px" %)**Example**
654 +|(% style="width:248px" %)DataConsumer|(% style="width:628px" %)dataConsumerSchemeAgencyId:**DATA_CONSUME RS**(**1.0**).dataConsumerId|(% style="width:1062px" %)SDMX:**DATA_CONSUMERS**(**1.0**).CONSUMER_1
655 +|(% style="width:248px" %)//DataConsumerScheme//|(% style="width:628px" %)(((
654 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" %)(((
657 +)))|(% style="width:1062px" %)SDMX:**DATA_CONSUMERS**(**1.0**)
658 +|(% style="width:248px" %)//Dataflow//|(% style="width:628px" %)dataflowAgencyId:dataflowId(version)|(% style="width:1062px" %)TFFS:CRED_EXT_DEBT(1.0.0)
659 +|(% style="width:248px" %)DataProvider|(% style="width:628px" %)(((
658 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 +)))|(% style="width:1062px" %)SDMX:**DATA_PROVIDERS**(**1.0**).PROVIDER_1
662 +|(% style="width:248px" %)//DataProviderScheme//|(% style="width:628px" %)(((
661 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
664 +)))|(% style="width:1062px" %)SDMX:**DATA_PROVIDERS**(**1.0**)
665 +|(% style="width:248px" %)//DataStructure//|(% style="width:628px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version)|(% style="width:1062px" %)TFFS:EXT_DEBT(1.0.0)
666 +|(% style="width:248px" %)Dimension|(% style="width:628px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).dimensionId|(% style="width:1062px" %)TFFS:EXT_DEBT(1.0.0).FREQ
665 665  |(% style="width:248px" %)(((
666 666  DimensionDescriptor
667 667  MeasureDescriptor
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" %)(((
671 +)))|(% style="width:628px" %)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:1062px" %)(((
670 670  TFFS:EXT_DEBT(1.0.0).DimensionDescriptor
671 671  TFFS:EXT_DEBT(1.0.0).MeasureDescriptor
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
676 +|(% style="width:248px" %)GroupDimensionDescriptor|(% style="width:628px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).groupDimensionDescriptorId|(% style="width:1062px" %)TFFS:EXT_DEBT(1.0.0).SIBLING
677 +|(% style="width:248px" %)HierarchicalCode|(% style="width:628px" %)hierarchyAgencyId:hierarchyId(version).hierarchica lCode.hierarchicalCode|(% style="width:1062px" %)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" %)(((
679 +|(% style="width:248px" %)**Classname**|(% style="width:629px" %)**Ending URN pattern**|(% style="width:1061px" %)**Example**
680 +|(% style="width:248px" %)//Hierarchy//|(% style="width:629px" %)hierarchyAgencyId:hierarchyId(version)|(% style="width:1061px" %)UNESCO:H-C-GOV(1.0.0)
681 +|(% style="width:248px" %)//HierarchyAssociation//|(% style="width:629px" %)hierarchyAssociationAgencyId:hierarchyAssociatio nId(version)|(% style="width:1061px" %)UNESCO:CL_EXP_SOURCE(1.0.0)
682 +|(% style="width:248px" %)Level|(% style="width:629px" %)hierarchyAgencyId:hierarchyId(version).level|(% style="width:1061px" %)UNESCO:H-C-GOV(1.0.0).LVL1
683 +|(% style="width:248px" %)Measure|(% style="width:629px" %)dataStructureDefinitionAgencyId:dataStructureDef initionId(version).measureId|(% style="width:1061px" %)TFFS:EXT_DEBT(1.0.0).OBS_VALUE
684 +|(% style="width:248px" %)MetadataAttribute|(% style="width:629px" %)(((
683 683  msdAgencyId:msdId(version).metadataAttributeId.
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)
687 +)))|(% style="width:1061px" %)IMF:SDDS_MSD(1.0.0).COMPILATION.METHOD
688 +|(% style="width:248px" %)MetadataAttributeDescriptor|(% style="width:629px" %)msdAgencyId:msdId(version).metadataAttributeDe scriptorId|(% style="width:1061px" %)IMF:SDDS_MSD(1.0.0).MetadataAttributeDescriptor
689 +|(% style="width:248px" %)//MetadataConstraint//|(% style="width:629px" %)metadataConstraintAgencyId:metadataConstraintI d(version)|(% style="width:1061px" %)TFFS:CREDITOR_METADATA_CONTENT(1.0.0)
690 +|(% style="width:248px" %)//Metadataflow//|(% style="width:629px" %)metadataflowAgencyId:metadataflowId(version)|(% style="width:1061px" %)IMF:SDDS_MDF(1.0.0)
691 +|(% style="width:248px" %)MetadataProvider|(% style="width:629px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**).metadataProviderId|(% style="width:1061px" %)SDMX:**METADATA_PROVIDERS**(**1.0**).MD_PROVIDER_1
692 +|(% style="width:248px" %)//MetadataProviderScheme//|(% style="width:629px" %)metadataProviderSchemeAgencyId:**METADATA_P ROVIDERS**(**1.0**)|(% style="width:1061px" %)SDMX:**METADATA_PROVIDERS**(**1.0**)
693 +|(% style="width:248px" %)//MetadataProvisionAgreement//|(% style="width:629px" %)metadataProvisionAgreementAgencyId:metadataP rovisionAgreementId(version)|(% style="width:1061px" %)IMF:SDDS_MDF_AB(1.0.0)
694 +|(% style="width:248px" %)//MetadataSet//|(% style="width:629px" %)metadataProviderId:metadataSetId(version)|(% style="width:1061px" %)MD_PROVIDER:METADATASET(1.0.0)
695 +|(% style="width:248px" %)//MetadataStructure//|(% style="width:629px" %)msdAgencyId:msdId(version)|(% style="width:1061px" %)IMF:SDDS_MSD(1.0.0)
694 694  
695 695  |(% style="width:248px" %)**Classname**|(% style="width:629px" %)**Ending URN pattern**|(% style="width:1061px" %)**Example**
696 696  |(% style="width:248px" %)NamePersonalisation|(% style="width:629px" %)namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|(% style="width:1061px" %)ECB:PSN_SCHEME(1.0.0).PSN1234
... ... @@ -711,29 +711,32 @@
711 711  |(% style="width:248px" %)//ReportingTaxonomy//|(% style="width:629px" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:1061px" %)IMF:REP_1(1.0.0)
712 712  |(% style="width:248px" %)//ReportingTaxonomyMap//|(% style="width:629px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:1061px" %)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" %)(((
716 +|**Classname**|**Ending URN pattern**|**Example**
717 +|//RepresentationMap//|repMapAgencyId:repMapId(version)|SDMX:REF_AREA_MAPPING(1.0.0)
718 +|Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0.0).SET111
719 +|//RulesetScheme//|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0.0)
720 +|//StructureMap//|structureMapAgencyId:structureMap(version)|SDMX:BOP_STRUCTURES(1.0.0)
721 +|Subscription|(((
720 720  The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure.
723 +
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" %)(((
725 +)))|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.
726 +|TimeDimension|dataStructureDefinitionAgencyId:dataStructureDef initionId(version).timeDimensionId|TFFS:EXT_DEBT(1.0.0).TIME_PERIOD
727 +|Transformation|transformationSchemeAgencyId transformationSchemeId(version) transformationId|ECB:TRANSFORMATION_SCHEME(1.0.0).TRANS_1
728 +|//TransformationScheme//|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0.0)
729 +|**Classname**|**Ending URN pattern**|**Example**
730 +|Transition|(((
727 727  processAgencyId:processId(version).processStepId.
732 +
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)
734 +)))|BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
735 +|UserDefinedOperator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2.0).OS267
736 +|//UserDefinedOperatorScheme//|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2.0)
737 +|//ValueList//|valuelistAgencyId:valuelistId(version)|SDMX:VLIST(1.0.0)
738 +|VtlCodelistMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0.0).ABZ
739 +|VtlConceptMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0.0).XYA
740 +|VtlDataflowMapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|ECB:CLIST_MP(1.0.0).MOQ
741 +|//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  
... ... @@ -757,54 +757,62 @@
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" %)(((
765 +|(% colspan="2" %)**Maintainable Artefacts**|**Content**
766 +|**Abstract Class**|**Concrete Class**|
767 +|Item Scheme|Codelist|Code
768 +| |Concept Scheme|Concept
769 +| |Category Scheme|Category
770 +| |Organisation Unit Scheme|Organisation Unit
771 +| |Agency Scheme|Agency
772 +| |Data Provider Scheme|Data Provider
773 +| |Metadata Provider Scheme|Metadata Provider
774 +| |Data Consumer Scheme|Data Consumer
775 +| |Reporting Taxonomy|Reporting Category
776 +| |Transformation Scheme|Transformation
777 +| |Custom Type Scheme|Custom Type
778 +| |Name Personalisation Scheme|Name Personalisation
779 +| |Vtl Mapping Scheme|Vtl Codelist Mapping Vtl Concept Mapping
780 +| |Ruleset Scheme|Ruleset
781 +| |User Defined Operator Scheme|User Defined Operator
782 +|Enumerated List|ValueList|Value Item
783 +|Structure|Data Structure Definition|(((
780 780  Dimension Descriptor
785 +
781 781  Group Dimension Descriptor
787 +
782 782  Dimension
789 +
783 783  Time Dimension
791 +
784 784  Attribute Descriptor
793 +
785 785  Data Attribute
795 +
786 786  Measure Descriptor
797 +
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" %)(((
800 +| |Metadata Structure Definition|Metadata Attribute Descriptor Metadata Attribute
801 +|Structure Usage|Dataflow|
802 +| |Metadataflow|
803 +|None|Process|Process Step
804 +|None|Structure Map|(((
794 794  Component Map
806 +
795 795  Epoch Map
808 +
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" %)
811 +|None|Representation Map|Representation Mapping
812 +|Item Scheme Map|Organisation Scheme Map|Item Map
813 +| |Concept Scheme Map|Item Map
814 +| |Category Scheme Map|Item Map
815 +| |Reporting Taxonomy Map|Item Map
816 +|None|Provision Agreement|
817 +|None|Metadata Provision Agreement|
818 +|None|Hierarchy|Hierarchical Code
819 +|None|Hierarchy Association|
820 +|None|Categorisation|
808 808  
809 809  **Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
810 810  
... ... @@ -812,11 +812,14 @@
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)
828 +• 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  
830 +• All types of Enumerated List (ValueList)^^[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)^^3^^>>path:#sdfootnote3sym||name="sdfootnote3anc"]](%%)^^
831 +
832 +• All types of Structure (Data Structure Definition, Metadata Structure Definition)
833 +
834 +• All types of Structure Usage (Dataflow, Metadataflow)
835 +
820 820  ===== {{id name="_Toc93865"/}}7.1.3 Structure Usage =====
821 821  
822 822  **7.1.3.1 Structure Usage: Basic Concepts**
... ... @@ -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 ==
864 +=== {{id name="_Toc93866"/}}7.2 Data and Metadata Provisioning ===
849 849  
850 -=== {{id name="_Toc93867"/}}7.2.1 Provisioning Agreement: Basic concepts ===
866 +===== {{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 ===
874 +===== {{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 ==
896 +=== {{id name="_Toc93869"/}}7.3 Data and Metadata Constraints ===
881 881  
882 -=== {{id name="_Toc93870"/}}7.3.1 Data and Metadata Constraints: Basic Concepts ===
898 +===== {{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  
962 +:
963 +
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
965 +|**Action Attribute Value**|**Behaviour**
966 +|Append|Add this Registration to the registry
967 +|Replace|(((
968 +Replace the existing Registration with identified by the id in the
969 +
970 +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
972 +|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  
989 +:
990 +
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" %)(((
992 +|**Indexing Required**|**Registration Process Activity**
993 +|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
994 +|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.
995 +|indexReportingPeriod|(((
976 976  This applies only to a registered __dataset__.
997 +
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" %)(((
1000 +|**Indexing Required**|**Registration Process Activity**
1001 +|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
1003 +
1004 +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
1005 +
1006 +SDMXIM, and the associated Selection Value
1007 +
983 983  **Metadata Set**
1009 +
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 ===
1018 +===== {{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.
1048 +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  
1053 +:
1054 +::
1055 +
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
1057 +|**Event Type**|**Comment**
1058 +|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1059 +|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1060 +|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1061 +|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  
1128 +:
1129 +
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.
1131 +|**Selector**|**Comment**
1132 +|DataProvider & MetadataProvider|Any datasets or metadata sets registered by the specified data or metadata provider will activate the notification.
1133 +|ProvisionAgreement & MetadataProvisionAgreement|Any datasets or metadata sets registered for the agreement will activate the notification.
1134 +|Dataflow & Metadataflow|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1135 +|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
1136 +|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 -----
1168 +[[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  
1170 +[[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:
1171 +
1172 +IMF.SubAgency1
1173 +
1174 +[[3>>path:#sdfootnote3anc||name="sdfootnote3sym"]] Note that Codelist is also an EnumeratedList.
1175 +
1141 1141  {{putFootnotes/}}