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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 8 added, 0 removed)
  • 1747829078194-749.png
  • 1747829109466-595.png
  • 1747829139951-378.png
  • 1747829204737-370.png
  • 1747829290890-122.png
  • 1747829477882-750.png
  • 1747829554603-150.png
  • 1747829675568-610.png

Details

Page properties

Content

...	...	@@ -683,58 +683,50 @@
683	683
684	684	> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
685	685
686		-(% style="width:1038.29px" %)
687		-|(% style="width:191px" %)**SDMX Class**|(% style="width:413px" %)**Key attribute(s)**|(% style="width:431px" %)**Example of URN**
688		-|(% style="width:191px" %)Agency|(% style="width:413px" %)The URN for an Agency is shown later in this table. 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.|(% style="width:431px" %)(((
	686	+(% style="width:1091.29px" %)
	687	+|(% style="width:250px" %)**SDMX Class**|(% style="width:444px" %)**Key attribute(s)**|(% style="width:396px" %)**Example of URN**
	688	+|(% style="width:250px" %)Agency|(% style="width:444px" %)The URN for an Agency is shown later in this table. 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.|(% style="width:396px" %)(((
689	689	IMF
690		-
691		-(((
692		-Sub agency in the IMF AGENCIES
693		-
	690	+Sub agency in the IMF AGENCIES
694	694	IMF.SubAgency1
695	695	)))
696		-)))
697		-|(% style="width:191px" %)*ConceptScheme|(% style="width:413px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
698		-|(% style="width:191px" %)Concept|(% style="width:413px" %)conceptSchemeAgencyId:
699		-conceptSchemeId(version).conceptId|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
700		-|(% style="width:191px" %)*Codelist|(% style="width:413px" %)codeListAgencyId:codeListId(version)|(% style="width:431px" %)SDMX:CL_FREQ(1.0)
701		-|(% style="width:191px" %)Code|(% style="width:413px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:431px" %)SDMX:CL_FREQ(1.0).Q
702		-|(% style="width:191px" %)(((
	693	+|(% style="width:250px" %)*ConceptScheme|(% style="width:444px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
	694	+|(% style="width:250px" %)Concept|(% style="width:444px" %)conceptSchemeAgencyId:
	695	+conceptSchemeId(version).conceptId|(% style="width:396px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
	696	+|(% style="width:250px" %)*Codelist|(% style="width:444px" %)codeListAgencyId:codeListId(version)|(% style="width:396px" %)SDMX:CL_FREQ(1.0)
	697	+|(% style="width:250px" %)Code|(% style="width:444px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:396px" %)SDMX:CL_FREQ(1.0).Q
	698	+|(% style="width:250px" %)(((
703	703	*Hierarchical Codelist
704		-)))|(% style="width:413px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:431px" %)(((
	700	+)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)(((
705	705	UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
706	706	)))
707		-|(% style="width:191px" %)Hierarchy|(% style="width:413px" %)(((
	703	+|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)(((
708	708	hierachicalcodeListAgencyId:
709	709	hierarchicalcodelistId(version).Hierarchy
710		-)))|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
711		-|(% style="width:191px" %)Level|(% style="width:413px" %)(((
	706	+)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0).
	707	+H-C-GOV
	708	+|(% style="width:250px" %)Level|(% style="width:444px" %)(((
712	712	hierachicalcodeListAgencyId:
713	713	hierarchicalcodelistId(version).Hierarchy.Level
714		-)))|(% style="width:431px" %)(((
	711	+)))|(% style="width:396px" %)(((
715	715	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
716	716
717	717
718	718	)))
719		-|(% style="width:191px" %)HierarchicalCode|(% style="width:413px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
720		-|(% style="width:191px" %)*DataStructure|(% style="width:413px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:431px" %)TFFS:EXT_DEBT(1.0)
721		-|(% style="width:191px" %)(((
	716	+|(% style="width:250px" %)HierarchicalCode|(% style="width:444px" %)hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
	717	+|(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0)
	718	+|(% style="width:250px" %)(((
722	722	Dimension
723		-
724	724	Descriptor
725		-
726	726	Measure
727		-
728	728	Descriptor
729		-
730	730	Attribute
731		-
732	732	Descriptor
733		-)))|(% style="width:413px" %)(((
	725	+)))|(% style="width:444px" %)(((
734	734	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
735	735	componentListId
736	736	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
737		-)))|(% style="width:431px" %)(((
	729	+)))|(% style="width:396px" %)(((
738	738	TFFS:EXT_DEBT(1.0).DimensionDescriptor
739	739
740	740	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -741,176 +741,132 @@
741	741
742	742	TFFS:EXT_DEBT(1.0).AttributeDescriptor
743	743	)))
744		-|(% style="width:191px" %)(((
	736	+|(% style="width:250px" %)(((
745	745	GroupDimension
746		-
747	747	Descriptor
748		-)))|(% style="width:413px" %)(((
	739	+)))|(% style="width:444px" %)(((
749	749	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
750	750	groupDimensionDescriptorId
751		-)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).SIBLING
752		-|(% style="width:191px" %)Dimension|(% style="width:413px" %)(((
	742	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).SIBLING
	743	+|(% style="width:250px" %)Dimension|(% style="width:444px" %)(((
753	753	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
754	754	dimensionId
755		-)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).FREQ
756		-|(% style="width:191px" %)TimeDimension|(% style="width:413px" %)(((
	746	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).FREQ
	747	+|(% style="width:250px" %)TimeDimension|(% style="width:444px" %)(((
757	757	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
758	758	timeDimensionId
759		-)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
760		-|(% style="width:191px" %)Measure Dimension|(% style="width:413px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
761		-
762		-(% style="width:987.294px" %)
763		-|(% style="width:170px" %) |(% style="width:367px" %)measureDimensionId|(% style="width:446px" %)
764		-|(% style="width:170px" %)DataAttrribute|(% style="width:367px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
765		-|(% style="width:170px" %)PrimaryMeasure|(% style="width:367px" %)(((
	750	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
	751	+|(% style="width:250px" %)Measure Dimension|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
	752	+measureDimensionId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
	753	+|(% style="width:250px" %)DataAttrribute|(% style="width:444px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
	754	+|(% style="width:250px" %)PrimaryMeasure|(% style="width:444px" %)(((
766	766	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
767	767	primaryMeasureId
768		-)))|(% style="width:446px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
769		-|(% style="width:170px" %)(((
770		-*Category
771		-
772		-Scheme
773		-)))|(% style="width:367px" %)categorySchemeAgencyId: categorySchemeId(version)|(% style="width:446px" %)IMF:SDDS(1.0)
774		-|(% style="width:170px" %)Category|(% style="width:367px" %)categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(% style="width:446px" %)(((
	757	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
	758	+|(% style="width:250px" %)(((
	759	+*Category Scheme
	760	+)))|(% style="width:444px" %)categorySchemeAgencyId:
	761	+categorySchemeId(version)|(% style="width:396px" %)IMF:SDDS(1.0)
	762	+|(% style="width:250px" %)Category|(% style="width:444px" %)categorySchemeAgencyId:
	763	+categorySchemeId(version).
	764	+categoryId.categoryId categoryId.categoryId etc.|(% style="width:396px" %)(((
775	775	IMF:SDDS(1.0):
776		-
777	777	level_1_category.level_2_category …
778	778	)))
779		-|(% style="width:170px" %)(((
780		-*Reporting
781		-
782		-Taxonomy
783		-)))|(% style="width:367px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:446px" %) IMF:REP_1(1.0)
784		-|(% style="width:170px" %)ReportingCategory|(% style="width:367px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:446px" %)(((
	768	+|(% style="width:250px" %)(((
	769	+*Reporting Taxonomy
	770	+)))|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:396px" %) IMF:REP_1(1.0)
	771	+|(% style="width:250px" %)ReportingCategory|(% style="width:444px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:396px" %)(((
785	785	IMF:REP_1(1.0):
786		-
787	787	level_1_repcategory.level_2_repcategory …
788	788	)))
789		-|(% style="width:170px" %)*Categorisation|(% style="width:367px" %)categorisationAgencyId: categorisationId(version)|(% style="width:446px" %)IMF:cat001(1.0)
790		-|(% style="width:170px" %)(((
791		-*Organisation
	775	+|(% style="width:250px" %)*Categorisation|(% style="width:444px" %)categorisationAgencyId: categorisationId(version)|(% style="width:396px" %)IMF:cat001(1.0)
	776	+|(% style="width:250px" %)(((
	777	+*Organisation Unit Scheme
	778	+)))|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:396px" %)ECB:ORGANISATIONS(1.0)
	779	+|(% style="width:250px" %)Organisation Unit|(% style="width:444px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:396px" %)ECB:ORGANISATIONS(1.0).1F
	780	+|(% style="width:250px" %)*AgencyScheme|(% style="width:444px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:396px" %)ECB:AGENCIES(1.0)
792	792
793		-Unit Scheme
794		-)))|(% style="width:367px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:446px" %)ECB:ORGANISATIONS(1.0)
795		-|(% style="width:170px" %)Organisation Unit|(% style="width:367px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:446px" %)ECB:ORGANISATIONS(1.0).1F
796		-|(% style="width:170px" %)*AgencyScheme|(% style="width:367px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:446px" %)ECB:AGENCIES(1.0)
797		-
798		-
799		-
800		-|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
801		-|(((
802		-*DataProvider
803		-
804		-Scheme
805		-)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0)
806		-|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
807		-|(((
808		-*DataConsumer
809		-
810		-Scheme
811		-)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0)
812		-|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
813		-|(((
814		-*Metadata
815		-
816		-Structure
817		-)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0)
818		-|MetadataTarget|(((
	782	+|(% style="width:262px" %)Agency|(% style="width:369px" %)agencySchemeAgencyId: agencySchemeId(version). agencyId|(% style="width:1262px" %)ECB:AGENCY(1.0).AA
	783	+|(% style="width:262px" %)(((
	784	+*DataProvider Scheme
	785	+)))|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0)
	786	+|(% style="width:262px" %)DataProvider|(% style="width:369px" %)dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|(% style="width:1262px" %)SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
	787	+|(% style="width:262px" %)(((
	788	+*DataConsumer Scheme
	789	+)))|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0)
	790	+|(% style="width:262px" %)Data Consumer|(% style="width:369px" %)dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|(% style="width:1262px" %)SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
	791	+|(% style="width:262px" %)(((
	792	+*Metadata Structure
	793	+)))|(% style="width:369px" %)MSDAgencyId:MSDId(version)|(% style="width:1262px" %)IMF:SDDS_MSD(1.0)
	794	+|(% style="width:262px" %)MetadataTarget|(% style="width:369px" %)(((
819	819	MSDAgencyId:
820		-
821	821	MSDId(version).metadataTargetId
822		-)))|IMF:SDDS_MSD(1.0).AGENCY
823		-|(((
	797	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY
	798	+|(% style="width:262px" %)(((
824	824	Dimension
825		-
826	826	DescriptorValues
827		-
828	828	Target
829		-)))|(((
	802	+)))|(% style="width:369px" %)(((
830	830	MSDAgencyId: MSDId(version).
831		-
832	832	metadataTargetId.keyDescriptorValueTargetId
833		-)))|IMF:SDDS_MSD(1.0).AGENCY.KEY
834		-|Identifiable ObjectTarget|(((
	805	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.KEY
	806	+|(% style="width:262px" %)Identifiable Object Target|(% style="width:369px" %)(((
	807	+MSDAgencyId: MSDId(version).metadataTargetId.identifiableObjectTargetId
	808	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
	809	+|(% style="width:262px" %)DataSetTarget|(% style="width:369px" %)(((
835	835	MSDAgencyId:
	811	+MSDId(version).metadataTargetId.dataSetTargetId
	812	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.D1101
	813	+|(% style="width:262px" %)PeportPeriod Target|(% style="width:369px" %)(((
	814	+MSDAgencyId: MSDId(version).metadataTargetId.reportPeriodTargetId
	815	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY.REP_PER
836	836
837		-MSDId(version).metadataTargetId.identifiable
838		-
839		-ObjectTargetId
840		-)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
841		-|DataSetTarget|(((
842		-MSDAgencyId:
843		-
844		-MSDId(version).metadataTargetId.dataSet
845		-
846		-TargetId
847		-)))|IMF:SDDS_MSD(1.0).AGENCY.D1101
848		-|PeportPeriod Target|(((
849		-MSDAgencyId:
850		-
851		-MSDId(version).metadataTargetId.reportPeriod
852		-
853		-TargetId
854		-)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER
855		-
856		-
857		-
858		-|(((
	817	+|(% style="width:251px" %)(((
859	859	ReportStructure
860	860
861	861
862		-)))|(((
863		-MSDAgencyId:
864		-
865		-MSDId(version).reportStructureId
866		-)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT
867		-|(((
	821	+)))|(% style="width:442px" %)(((
	822	+MSDAgencyId: MSDId(version).reportStructureId
	823	+)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
	824	+|(% style="width:251px" %)(((
868	868	Metadata
869	869
870	870	Attribute
871		-)))|(((
872		-MSDAgencyId:
873		-
874		-MSDId(version).reportStructureId.metadataattri buteID
875		-)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
876		-|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0)
877		-|*Provision Agreement|(((
	828	+)))|(% style="width:442px" %)(((
	829	+MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
	830	+)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
	831	+|(% style="width:251px" %)*Dataflow|(% style="width:442px" %)dataflowAgencyId: dataflowId(version)|(% style="width:1178px" %)TFFS:CRED_EXT_DEBT(1.0)
	832	+|(% style="width:251px" %)*Provision Agreement|(% style="width:442px" %)(((
878	878	provisionAgreementAgencyId:provisionAgreem entId(version)
879		-
880		-
881		-)))|(((
	834	+)))|(% style="width:1178px" %)(((
882	882	TFFS:CRED_EXT_DEBT_AB(1.0)
883		-
884		-
885		-
886	886	)))
887		-|(((
	837	+|(% style="width:251px" %)(((
888	888	*Content
889	889
890	890	Constraint
891		-)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0)
892		-|(((
	841	+)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
	842	+|(% style="width:251px" %)(((
893	893	*Attachment
894	894
895	895	Constraint
896		-)))|(((
	846	+)))|(% style="width:442px" %)(((
897	897	constraintAgencyId:
898	898
899	899	attachmentConstraintId(version)
900		-)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
901		-|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0)
902		-|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0)
903		-|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
904		-|Component Map|(((
	850	+)))|(% style="width:1178px" %)TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
	851	+|(% style="width:251px" %)*Metadataflow|(% style="width:442px" %)metadataflowAgencyId: metadataflowId(version)|(% style="width:1178px" %)IMF:SDDS_FLOW(1.0)
	852	+|(% style="width:251px" %)*StructureSet|(% style="width:442px" %)structureSetAgencyId: structureSetId(version)|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0)
	853	+|(% style="width:251px" %)StructureMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). structureMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
	854	+|(% style="width:251px" %)Component Map|(% style="width:442px" %)(((
905	905	structureSetAgencyId: structureSetId(version).
906	906
907	907	structureMapId. componentMapId
908		-)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
909		-|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
910		-|CodeMap|structureSetAgencyId: structureSetId(version).|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
	858	+)))|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
	859	+|(% style="width:251px" %)CodelistMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version). codelistMapId|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
	860	+|(% style="width:251px" %)CodeMap|(% style="width:442px" %)structureSetAgencyId: structureSetId(version).|(% style="width:1178px" %)SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY. DE_GER
911	911
912		-
913		-
914	914	| |(((
915	915	codeListMapId.
916	916
...	...	@@ -1018,7 +1018,6 @@
1018	1018
1019	1019	7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
1020	1020
1021		-
1022	1022	= 7 Implementation Notes =
1023	1023
1024	1024	== 7.1 Structural Definition Metadata ==
...	...	@@ -1039,109 +1039,72 @@
1039	1039
1040	1040	The following table lists the Maintainable Artefacts.
1041	1041
1042		-|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**|
1043		-|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) |
1044		-|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code|
1045		-|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept|
1046		-|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category|
1047		-|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit|
1048		-|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency|
1049		-|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider|
1050		-|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer|
1051		-|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category|
1052		-|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation|
1053		-|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type|
1054		-| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**
1055		-| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %)
1056		-| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation
1057		-| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping
1058		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping
1059		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping
1060		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)(((
1061		-Vtl Concept Scheme
1062		-
1063		-Mapping
1064		-)))
1065		-| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset
1066		-| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator
1067		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
1068		-| |(% colspan="2" %)Structure|(% colspan="2" %)Data Structure Definition|(% colspan="2" %)(((
	989	+(% style="width:640.294px" %)
	990	+|(% colspan="2" rowspan="1" style="width:186px" %)**Maintainable Artefacts**|(% style="width:206px" %)**Content**
	991	+|(% style="width:171px" %)**Abstract Class**|(% style="width:232px" %)**Concrete Class**|(% style="width:206px" %)
	992	+|(% style="width:171px" %)Item Scheme|(% style="width:232px" %)Codelist|(% style="width:206px" %)Code
	993	+|(% style="width:171px" %) |(% style="width:232px" %)Concept Scheme|(% style="width:206px" %)Concept
	994	+|(% style="width:171px" %) |(% style="width:232px" %)Category Scheme|(% style="width:206px" %)Category
	995	+|(% style="width:171px" %) |(% style="width:232px" %)Organisation Unit Scheme|(% style="width:206px" %)Organisation Unit
	996	+|(% style="width:171px" %) |(% style="width:232px" %)Agency Scheme|(% style="width:206px" %)Agency
	997	+|(% style="width:171px" %) |(% style="width:232px" %)Data Provider Scheme|(% style="width:206px" %)Data Provider
	998	+|(% style="width:171px" %) |(% style="width:232px" %)Data Consumer Scheme|(% style="width:206px" %)Data Consumer
	999	+|(% style="width:171px" %) |(% style="width:232px" %)Reporting Taxonomy|(% style="width:206px" %)Reporting Category
	1000	+|(% style="width:171px" %) |(% style="width:232px" %)Transformation Scheme|(% style="width:206px" %)Transformation
	1001	+|(% style="width:171px" %) |(% style="width:232px" %)Custom Type Scheme|(% style="width:206px" %)Custom Type
	1002	+|(% style="width:171px" %) |(% style="width:232px" %)Name Personalisation Scheme|(% style="width:206px" %)Name Personalisation
	1003	+|(% style="width:171px" %) |(% style="width:232px" %)Vtl Mapping Scheme|(% style="width:206px" %)Vtl Codelist Mapping
	1004	+|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Dataflow Mapping
	1005	+|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)Vtl Concept Scheme Mapping
	1006	+|(% style="width:171px" %) |(% style="width:232px" %)Ruleset Scheme|(% style="width:206px" %)Ruleset
	1007	+|(% style="width:171px" %) |(% style="width:232px" %)User Defined Operator Scheme|(% style="width:206px" %)User Defined Operator
	1008	+|(% style="width:171px" %) |(% style="width:232px" %) |(% style="width:206px" %)User Defined Operator
	1009	+|(% style="width:171px" %)Structure|(% style="width:232px" %)Data Structure Definition|(% style="width:206px" %)(((
1069	1069	Dimension Descriptor
1070		-
1071	1071	Group Dimension
1072		-
1073	1073	Descriptor
1074		-
1075	1075	Dimension
1076		-
1077	1077	Measure Dimension
1078		-
1079	1079	Time Dimension
1080		-
1081	1081	Attribute Descriptor
1082		-
1083	1083	Data Attribute
1084		-
1085	1085	Measure Descriptor
1086		-
1087	1087	Primary Measure
1088	1088	)))
1089		-| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)(((
1090		-Metadata Target,
1091		-
1092		-Dimension Descriptor
1093		-
	1021	+|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)(((
	1022	+Metadata Target, Dimension Descriptor
1094	1094	Values Target Identifiable
1095		-
1096	1096	Object Target
1097		-
1098	1098	Report Period Target
1099		-
1100	1100	Data SetTarget
1101		-
1102	1102	Report Structure
1103		-
1104	1104	Metadata Attribute
1105	1105	)))
1106		-| |(% colspan="2" %)Structure Usage|(% colspan="2" %)Dataflow Definition|(% colspan="2" %)
1107		-| |(% colspan="2" %) |(% colspan="2" %)Metadataflow Definition|(% colspan="2" %)
1108		-| |(% colspan="2" %)None|(% colspan="2" %)Process|(% colspan="2" %)Process Step
1109		-| |(% colspan="2" %)None|(% colspan="2" %)Structure Set|(% colspan="2" %)(((
	1030	+|(% style="width:171px" %)Structure Usage|(% style="width:232px" %)Dataflow Definition|(% style="width:206px" %)
	1031	+|(% style="width:171px" %) |(% style="width:232px" %)Metadataflow Definition|(% style="width:206px" %)
	1032	+|(% style="width:171px" %)None|(% style="width:232px" %)Process|(% style="width:206px" %)Process Step
	1033	+|(% style="width:171px" %)None|(% style="width:232px" %)Structure Set|(% style="width:206px" %)(((
1110	1110	Component Map
1111		-
1112	1112	Concept Scheme Map
1113		-
1114	1114	Codelist Map
1115		-
1116	1116	Category Scheme Map
1117		-
1118	1118	Reporting Taxonomy Map
1119		-
1120	1120	Organisation Scheme Map
1121		-
1122	1122	Concept Map
1123		-
1124	1124	Code Map
1125		-
1126	1126	Category Map
1127		-
1128	1128	Organisation Map
1129		-
1130	1130	Reporting Category Map
1131		-
1132	1132	Hybrid Codelist Map
1133		-
1134	1134	Hybrid Code Map
1135	1135	)))
1136		-| |(% colspan="2" %)None|(% colspan="2" %)Provision Agreement|(% colspan="2" %)
1137		-| |(% colspan="2" %)None|(% colspan="2" %)Hierarchical Codelist|(% colspan="2" %)(((
	1048	+|(% style="width:171px" %)None|(% style="width:232px" %)Provision Agreement|(% style="width:206px" %)
	1049	+|(% style="width:171px" %)None|(% style="width:232px" %)Hierarchical Codelist|(% style="width:206px" %)(((
1138	1138	Hierarchy
1139		-
1140	1140	Hierarchical Code
1141	1141	)))
1142		-| | | | | | |
1143	1143
1144		-**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
	1054	+**able 4: Table of Maintainable Artefacts for Structural Definition Metadata**
1145	1145
1146	1146	=== 7.1.2 Item Scheme, Structure ===
1147	1147
...	...	@@ -1148,10 +1148,7 @@
1148	1148	The artefacts included in the structural definitions are:
1149	1149
1150	1150	* All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
1151		-* All types of Structure (Data Structure Definition, Metadata Structure
1152		-
1153		-Definition)
1154		-
	1061	+* All types of Structure (Data Structure Definition, Metadata Structure Definition)
1155	1155	* All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
1156	1156
1157	1157	=== 7.1.3 Structure Usage ===
...	...	@@ -1170,6 +1170,8 @@
1170	1170
1171	1171	==== 7.1.3.3 Structure Usage Model ====
1172	1172
	1080	+[[image:1747829078194-749.png]]
	1081	+
1173	1173	**Figure 10: SDMX-IM of links from Structure Usage to Category**
1174	1174
1175	1175	In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
...	...	@@ -1196,10 +1196,10 @@
1196	1196
1197	1197	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.
1198	1198
	1108	+[[image:1747829109466-595.png]]
1199	1199
1200	1200	**Figure 11: SDMX-IM of the Data Provider**
1201	1201
1202		-
1203	1203	Note that the Data Provider does not inherit the hierarchy association. The diagram below shows a logical schematic of the data model classes required to maintain provision agreements
1204	1204
1205	1205	[[image:1747824123019-181.jpeg]]
...	...	@@ -1208,8 +1208,10 @@
1208	1208
1209	1209	The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1210	1210
	1120	+[[image:1747829139951-378.png]]
1211	1211
1212		-==== Figure 13: Logical class diagram of the information contained in the Provision Agreement ====
	1122	+(% class="wikigeneratedid" id="HFigure13:LogicalclassdiagramoftheinformationcontainedintheProvisionAgreement" %)
	1123	+**Figure 13: Logical class diagram of the information contained in the Provision Agreement**
1213	1213
1214	1214	A Provision Agreement is structural metadata. Each Provision Agreement must reference a Data Provider and a Dataflow or Metadataflow Definition. The Data Provider and the Dataflow/Metadataflow Definition must exist already in order to set up a Provision Agreement.
1215	1215
...	...	@@ -1237,13 +1237,12 @@
1237	1237
1238	1238	=== 7.3.3 Data and Metadata Constraints: Model ===
1239	1239
	1151	+[[image:1747829204737-370.png]]
1240	1240
	1153	+**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1241	1241
1242		-==== Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts ====
	1155	+The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1243	1243
1244		-The class diagram above shows that DataProvider, DataflowDefinition, MetadataflowDefinition, ProvisionAgreement, DataStructureDefinition, MetadataStructureDefinition, SimpleDatasource and QueryDatasource are all concrete sub-classes of ConstrainableArtefact and can therefore have Constraints specified. Note that the actual Constraint as submitted is associated to the reference classes which inherit from ConstrainableRef: these are used to refer to the classes to which the Constraint applies.
1245		-
1246		-
1247	1247	The content of the Constraint can be found in the SDMX Information Model document.
1248	1248
1249	1249	== 7.4 Data and Metadata Registration ==
...	...	@@ -1278,11 +1278,14 @@
1278	1278
1279	1279	The Registration has an action attribute which takes one of the following values:
1280	1280
1281		-|**Action Attribute Value**|**Behaviour**
1282		-|Append|Add this Registration to the registry
1283		-|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1284		-|Delete|Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
	1191	+(% style="width:970.294px" %)
	1192	+|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour**
	1193	+|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry
	1194	+|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
	1195	+|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1285	1285
	1197	+[[image:1747829290890-122.png]]
	1198	+
1286	1286	**Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1287	1287
1288	1288	The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
...	...	@@ -1297,25 +1297,19 @@
1297	1297
1298	1298	Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints 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 Provision Agreement as shown in the table below.
1299	1299
1300		-|**Indexing Required**|**Registration Process Activity**
1301		-|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1302		-|indexDataSet|(((
1303		-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
1304		-
1305		-Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
	1213	+|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity**
	1214	+|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint.
	1215	+|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)(((
	1216	+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.
1306	1306	)))
1307		-|indexReportingPeriod|(((
	1218	+|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1308	1308	This applies only to a registered dataset.
1309		-
1310	1310	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1311	1311	)))
1312		-|indexAttributes|(((
	1222	+|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1313	1313	**Data Set**
1314		-
1315	1315	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
1316		-
1317	1317	**Metadata Set**
1318		-
1319	1319	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.
1320	1320	)))
1321	1321
...	...	@@ -1325,14 +1325,13 @@
1325	1325
1326	1326	=== 7.4.3 Registration Response ===
1327	1327
1328		-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 Submit Registration class has a status field which is either set to
	1235	+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 Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
1329	1329
1330		-“Success”, “Warning” or “Failure”.
1331		-
1332	1332	If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service.
1333	1333
1334	1334	The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
1335	1335
	1241	+[[image:1747829477882-750.png]]
1336	1336
1337	1337	**Figure 18: Logical class diagram showing the registration response**
1338	1338
...	...	@@ -1342,15 +1342,12 @@
1342	1342
1343	1343	A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry.
1344	1344
1345		-When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a
	1251	+When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a “notification”.
1346	1346
1347		-“notification”.
	1253	+=== 7.5.1Subscription Logical Class Diagram ===
1348	1348
1349		- 7.5.1Subscription Logical Class Diagram
	1255	+[[image:1747829554603-150.png]]
1350	1350
1351		-
1352		-[[image:1747824123028-257.png]]
1353		-
1354	1354	**Figure 19: Logical Class Diagram of the Subscription**
1355	1355
1356	1356	=== 7.5.2 Subscription Information ===
...	...	@@ -1357,73 +1357,58 @@
1357	1357
1358	1358	Regardless of the type of registry/repository events being observed, a subscription always contains:
1359	1359
1360		-~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.
	1263	+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.
	1264	+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.
	1265	+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.
	1266	+1. A selector which specifies which type of events are of interest. The set of event types is:
1361	1361
1362		-2. 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.
	1268	+|(% style="width:327px" %)**Event Type**|(% style="width:1545px" %)**Comment**
	1269	+|(% style="width:327px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1545px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
	1270	+|(% style="width:327px" %)DATA_REGISTRATION_EVENTS|(% style="width:1545px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
	1271	+|(% style="width:327px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1545px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
	1272	+|(% style="width:327px" %)ALL_EVENTS|(% style="width:1545px" %)All events of the specified EventType
1363	1363
1364		-3. 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.
1365		-
1366		-4. A selector which specifies which type of events are of interest. The set of event types is:
1367		-
1368		-|**Event Type**|**Comment**
1369		-|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1370		-|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1371		-|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1372		-|ALL_EVENTS|All events of the specified EventType
1373		-
1374	1374	=== 7.5.3 Wildcard Facility ===
1375	1375
1376	1376	Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise:
1377	1377
1378		- agencyID
	1278	+* agencyID
	1279	+* id
	1280	+* version
1379	1379
1380		- id
1381		-
1382		- version
1383		-
1384	1384	Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1385	1385
1386		-AgencyID = %
1387		-
	1284	+//AgencyID = %
1388	1388	Id = %
	1286	+Version = %//
1389	1389
1390		-Version = %
1391		-
1392	1392	This subscribes to all Codelists of all versions for all agencies.
1393	1393
1394		-AgencyID = AGENCY1
1395		-
	1290	+//AgencyID = AGENCY1
1396	1396	Id = CODELIST1
	1292	+Version = %//
1397	1397
1398		-Version = %
1399		-
1400	1400	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1401	1401
1402		-AGENCY1
1403		-
	1296	+//AGENCY1
1404	1404	AgencyID = AGENCY1
1405		-
1406	1406	Id = %
	1299	+Version = %//
1407	1407
1408		-Version = %
1409		-
1410	1410	This subscribes to all versions of all Codelist objects maintained by the agency
1411	1411
1412		-AGENCY1
1413		-
	1303	+//AGENCY1
1414	1414	AgencyID = %
1415		-
1416	1416	Id = CODELIST1
	1306	+Version = %//
1417	1417
1418		-Version = %
1419		-
1420	1420	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1421	1421
1422		-AGENCY1
	1310	+//AGENCY1//
1423	1423
1424	1424	Note that if the subscription is to the latest version then this can be achieved by the * character
1425	1425
1426		-i.e. Version = *
	1314	+//i.e. Version = *//
1427	1427
1428	1428	Note that a subscription using the URN mechanism cannot use wildcard characters.
1429	1429
...	...	@@ -1435,16 +1435,15 @@
1435	1435
1436	1436	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:
1437	1437
	1326	+|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
	1327	+|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification.
	1328	+|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification.
	1329	+|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
	1330	+|(% style="width:405px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
	1331	+|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment**
	1332	+|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification.
	1333	+|(% style="width:405px" %)Category|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1438	1438
1439		-|**Selector**|**Comment**
1440		-|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification.
1441		-|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification.
1442		-|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1443		-|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
1444		-|**Selector**|**Comment**
1445		-| |activate the notification.
1446		-|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1447		-
1448	1448	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1449	1449
1450	1450	== 7.6 Notification ==
...	...	@@ -1451,8 +1451,10 @@
1451	1451
1452	1452	=== 7.6.1 Logical Class Diagram ===
1453	1453
	1341	+[[image:1747829675568-610.png]]
1454	1454
1455		-==== Figure 20: Logical Class Diagram of the Notification ====
	1343	+(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
	1344	+**Figure 20: Logical Class Diagram of the Notification**
1456	1456
1457	1457	A notification is an XML document that is sent to a user via email or http POST whenever a subscription is activated. It is an asynchronous one-way message.
1458	1458
...	...	@@ -1472,5 +1472,3 @@
1472	1472	=== 7.6.3 Registration Event Component ===
1473	1473
1474	1474	The notification will contain the Registration.
1475		-
1476		-

1747829078194-749.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+40.4 KB

Content

1747829109466-595.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+30.4 KB

Content

1747829139951-378.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.1 KB

Content

1747829204737-370.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+55.8 KB

Content

1747829290890-122.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.4 KB

Content

1747829477882-750.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+24.6 KB

Content

1747829554603-150.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+99.1 KB

Content

1747829675568-610.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+31.1 KB

Content