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,39 +683,39 @@
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	690	Sub agency in the IMF AGENCIES
691	691	IMF.SubAgency1
692	692	)))
693		-|(% style="width:191px" %)*ConceptScheme|(% style="width:413px" %)conceptSchemeAgencyId:conceptSchemeId(ve rsion)|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
694		-|(% style="width:191px" %)Concept|(% style="width:413px" %)conceptSchemeAgencyId:
695		-conceptSchemeId(version).conceptId|(% style="width:431px" %)SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
696		-|(% style="width:191px" %)*Codelist|(% style="width:413px" %)codeListAgencyId:codeListId(version)|(% style="width:431px" %)SDMX:CL_FREQ(1.0)
697		-|(% style="width:191px" %)Code|(% style="width:413px" %)codeListAgencyId:codelistId(version).codeId|(% style="width:431px" %)SDMX:CL_FREQ(1.0).Q
698		-|(% 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" %)(((
699	699	*Hierarchical Codelist
700		-)))|(% style="width:413px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:431px" %)(((
	700	+)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)(((
701	701	UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
702	702	)))
703		-|(% style="width:191px" %)Hierarchy|(% style="width:413px" %)(((
	703	+|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)(((
704	704	hierachicalcodeListAgencyId:
705	705	hierarchicalcodelistId(version).Hierarchy
706		-)))|(% style="width:431px" %)UNESCO:CL_EXP_SOURCE(1.0).
	706	+)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0).
707	707	H-C-GOV
708		-|(% style="width:191px" %)Level|(% style="width:413px" %)(((
	708	+|(% style="width:250px" %)Level|(% style="width:444px" %)(((
709	709	hierachicalcodeListAgencyId:
710	710	hierarchicalcodelistId(version).Hierarchy.Level
711		-)))|(% style="width:431px" %)(((
	711	+)))|(% style="width:396px" %)(((
712	712	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
713	713
714	714
715	715	)))
716		-|(% 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
717		-|(% style="width:191px" %)*DataStructure|(% style="width:413px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:431px" %)TFFS:EXT_DEBT(1.0)
718		-|(% 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" %)(((
719	719	Dimension
720	720	Descriptor
721	721	Measure
...	...	@@ -722,11 +722,11 @@
722	722	Descriptor
723	723	Attribute
724	724	Descriptor
725		-)))|(% style="width:413px" %)(((
	725	+)))|(% style="width:444px" %)(((
726	726	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
727	727	componentListId
728	728	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
729		-)))|(% style="width:431px" %)(((
	729	+)))|(% style="width:396px" %)(((
730	730	TFFS:EXT_DEBT(1.0).DimensionDescriptor
731	731
732	732	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -733,168 +733,132 @@
733	733
734	734	TFFS:EXT_DEBT(1.0).AttributeDescriptor
735	735	)))
736		-|(% style="width:191px" %)(((
	736	+|(% style="width:250px" %)(((
737	737	GroupDimension
738	738	Descriptor
739		-)))|(% style="width:413px" %)(((
	739	+)))|(% style="width:444px" %)(((
740	740	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
741	741	groupDimensionDescriptorId
742		-)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).SIBLING
743		-|(% 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" %)(((
744	744	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
745	745	dimensionId
746		-)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).FREQ
747		-|(% 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" %)(((
748	748	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
749	749	timeDimensionId
750		-)))|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).TIME_PERIOD
751		-|(% style="width:191px" %)Measure Dimension|(% style="width:413px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version).
752		-measureDimensionId|(% style="width:431px" %)TFFS:EXT_DEBT(1.0).STOCK_FLOW
753		-|(% style="width:191px" %)DataAttrribute|(% style="width:415px" %)dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|(% style="width:429px" %)TFFS:EXT_DEBT(1.0).OBS_STATUS
754		-|(% style="width:191px" %)PrimaryMeasure|(% style="width:415px" %)(((
	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" %)(((
755	755	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
756	756	primaryMeasureId
757		-)))|(% style="width:429px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
758		-|(% style="width:191px" %)(((
	757	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).OBS_VALUE
	758	+|(% style="width:250px" %)(((
759	759	*Category Scheme
760		-)))|(% style="width:415px" %)categorySchemeAgencyId:
761		-categorySchemeId(version)|(% style="width:429px" %)IMF:SDDS(1.0)
762		-|(% style="width:191px" %)Category|(% style="width:415px" %)categorySchemeAgencyId:
	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	763	categorySchemeId(version).
764		-categoryId.categoryId categoryId.categoryId etc.|(% style="width:429px" %)(((
	764	+categoryId.categoryId categoryId.categoryId etc.|(% style="width:396px" %)(((
765	765	IMF:SDDS(1.0):
766	766	level_1_category.level_2_category …
767	767	)))
768		-|(% style="width:191px" %)(((
	768	+|(% style="width:250px" %)(((
769	769	*Reporting Taxonomy
770		-)))|(% style="width:415px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version)|(% style="width:429px" %) IMF:REP_1(1.0)
771		-|(% style="width:191px" %)ReportingCategory|(% style="width:415px" %)reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(% style="width:429px" %)(((
	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" %)(((
772	772	IMF:REP_1(1.0):
773	773	level_1_repcategory.level_2_repcategory …
774	774	)))
775		-|(% style="width:191px" %)*Categorisation|(% style="width:415px" %)categorisationAgencyId: categorisationId(version)|(% style="width:429px" %)IMF:cat001(1.0)
776		-|(% style="width:191px" %)(((
	775	+|(% style="width:250px" %)*Categorisation|(% style="width:444px" %)categorisationAgencyId: categorisationId(version)|(% style="width:396px" %)IMF:cat001(1.0)
	776	+|(% style="width:250px" %)(((
777	777	*Organisation Unit Scheme
778		-)))|(% style="width:415px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|(% style="width:429px" %)ECB:ORGANISATIONS(1.0)
779		-|(% style="width:191px" %)Organisation Unit|(% style="width:415px" %)organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|(% style="width:429px" %)ECB:ORGANISATIONS(1.0).1F
780		-|(% style="width:191px" %)*AgencyScheme|(% style="width:415px" %)agencySchemeAgencyId: agencySchemeId(version)|(% style="width:429px" %)ECB:AGENCIES(1.0)
	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)
781	781
782		-
783		-
784		-|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
785		-|(((
786		-*DataProvider
787		-
788		-Scheme
789		-)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0)
790		-|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
791		-|(((
792		-*DataConsumer
793		-
794		-Scheme
795		-)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0)
796		-|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
797		-|(((
798		-*Metadata
799		-
800		-Structure
801		-)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0)
802		-|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" %)(((
803	803	MSDAgencyId:
804		-
805	805	MSDId(version).metadataTargetId
806		-)))|IMF:SDDS_MSD(1.0).AGENCY
807		-|(((
	797	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY
	798	+|(% style="width:262px" %)(((
808	808	Dimension
809		-
810	810	DescriptorValues
811		-
812	812	Target
813		-)))|(((
	802	+)))|(% style="width:369px" %)(((
814	814	MSDAgencyId: MSDId(version).
815		-
816	816	metadataTargetId.keyDescriptorValueTargetId
817		-)))|IMF:SDDS_MSD(1.0).AGENCY.KEY
818		-|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" %)(((
819	819	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
820	820
821		-MSDId(version).metadataTargetId.identifiable
822		-
823		-ObjectTargetId
824		-)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
825		-|DataSetTarget|(((
826		-MSDAgencyId:
827		-
828		-MSDId(version).metadataTargetId.dataSet
829		-
830		-TargetId
831		-)))|IMF:SDDS_MSD(1.0).AGENCY.D1101
832		-|PeportPeriod Target|(((
833		-MSDAgencyId:
834		-
835		-MSDId(version).metadataTargetId.reportPeriod
836		-
837		-TargetId
838		-)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER
839		-
840		-
841		-
842		-|(((
	817	+|(% style="width:251px" %)(((
843	843	ReportStructure
844	844
845	845
846		-)))|(((
847		-MSDAgencyId:
848		-
849		-MSDId(version).reportStructureId
850		-)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT
851		-|(((
	821	+)))|(% style="width:442px" %)(((
	822	+MSDAgencyId: MSDId(version).reportStructureId
	823	+)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
	824	+|(% style="width:251px" %)(((
852	852	Metadata
853	853
854	854	Attribute
855		-)))|(((
856		-MSDAgencyId:
857		-
858		-MSDId(version).reportStructureId.metadataattri buteID
859		-)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
860		-|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0)
861		-|*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" %)(((
862	862	provisionAgreementAgencyId:provisionAgreem entId(version)
863		-
864		-
865		-)))|(((
	834	+)))|(% style="width:1178px" %)(((
866	866	TFFS:CRED_EXT_DEBT_AB(1.0)
867		-
868		-
869		-
870	870	)))
871		-|(((
	837	+|(% style="width:251px" %)(((
872	872	*Content
873	873
874	874	Constraint
875		-)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0)
876		-|(((
	841	+)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
	842	+|(% style="width:251px" %)(((
877	877	*Attachment
878	878
879	879	Constraint
880		-)))|(((
	846	+)))|(% style="width:442px" %)(((
881	881	constraintAgencyId:
882	882
883	883	attachmentConstraintId(version)
884		-)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
885		-|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0)
886		-|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0)
887		-|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
888		-|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" %)(((
889	889	structureSetAgencyId: structureSetId(version).
890	890
891	891	structureMapId. componentMapId
892		-)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
893		-|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
894		-|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
895	895
896		-
897		-
898	898	| |(((
899	899	codeListMapId.
900	900
...	...	@@ -1002,7 +1002,6 @@
1002	1002
1003	1003	7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
1004	1004
1005		-
1006	1006	= 7 Implementation Notes =
1007	1007
1008	1008	== 7.1 Structural Definition Metadata ==
...	...	@@ -1023,109 +1023,72 @@
1023	1023
1024	1024	The following table lists the Maintainable Artefacts.
1025	1025
1026		-|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**|
1027		-|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) |
1028		-|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code|
1029		-|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept|
1030		-|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category|
1031		-|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit|
1032		-|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency|
1033		-|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider|
1034		-|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer|
1035		-|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category|
1036		-|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation|
1037		-|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type|
1038		-| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**
1039		-| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %)
1040		-| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation
1041		-| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping
1042		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping
1043		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping
1044		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)(((
1045		-Vtl Concept Scheme
1046		-
1047		-Mapping
1048		-)))
1049		-| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset
1050		-| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator
1051		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
1052		-| |(% 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" %)(((
1053	1053	Dimension Descriptor
1054		-
1055	1055	Group Dimension
1056		-
1057	1057	Descriptor
1058		-
1059	1059	Dimension
1060		-
1061	1061	Measure Dimension
1062		-
1063	1063	Time Dimension
1064		-
1065	1065	Attribute Descriptor
1066		-
1067	1067	Data Attribute
1068		-
1069	1069	Measure Descriptor
1070		-
1071	1071	Primary Measure
1072	1072	)))
1073		-| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)(((
1074		-Metadata Target,
1075		-
1076		-Dimension Descriptor
1077		-
	1021	+|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)(((
	1022	+Metadata Target, Dimension Descriptor
1078	1078	Values Target Identifiable
1079		-
1080	1080	Object Target
1081		-
1082	1082	Report Period Target
1083		-
1084	1084	Data SetTarget
1085		-
1086	1086	Report Structure
1087		-
1088	1088	Metadata Attribute
1089	1089	)))
1090		-| |(% colspan="2" %)Structure Usage|(% colspan="2" %)Dataflow Definition|(% colspan="2" %)
1091		-| |(% colspan="2" %) |(% colspan="2" %)Metadataflow Definition|(% colspan="2" %)
1092		-| |(% colspan="2" %)None|(% colspan="2" %)Process|(% colspan="2" %)Process Step
1093		-| |(% 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" %)(((
1094	1094	Component Map
1095		-
1096	1096	Concept Scheme Map
1097		-
1098	1098	Codelist Map
1099		-
1100	1100	Category Scheme Map
1101		-
1102	1102	Reporting Taxonomy Map
1103		-
1104	1104	Organisation Scheme Map
1105		-
1106	1106	Concept Map
1107		-
1108	1108	Code Map
1109		-
1110	1110	Category Map
1111		-
1112	1112	Organisation Map
1113		-
1114	1114	Reporting Category Map
1115		-
1116	1116	Hybrid Codelist Map
1117		-
1118	1118	Hybrid Code Map
1119	1119	)))
1120		-| |(% colspan="2" %)None|(% colspan="2" %)Provision Agreement|(% colspan="2" %)
1121		-| |(% 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" %)(((
1122	1122	Hierarchy
1123		-
1124	1124	Hierarchical Code
1125	1125	)))
1126		-| | | | | | |
1127	1127
1128		-**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
	1054	+**able 4: Table of Maintainable Artefacts for Structural Definition Metadata**
1129	1129
1130	1130	=== 7.1.2 Item Scheme, Structure ===
1131	1131
...	...	@@ -1132,10 +1132,7 @@
1132	1132	The artefacts included in the structural definitions are:
1133	1133
1134	1134	* All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
1135		-* All types of Structure (Data Structure Definition, Metadata Structure
1136		-
1137		-Definition)
1138		-
	1061	+* All types of Structure (Data Structure Definition, Metadata Structure Definition)
1139	1139	* All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
1140	1140
1141	1141	=== 7.1.3 Structure Usage ===
...	...	@@ -1154,6 +1154,8 @@
1154	1154
1155	1155	==== 7.1.3.3 Structure Usage Model ====
1156	1156
	1080	+[[image:1747829078194-749.png]]
	1081	+
1157	1157	**Figure 10: SDMX-IM of links from Structure Usage to Category**
1158	1158
1159	1159	In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
...	...	@@ -1180,10 +1180,10 @@
1180	1180
1181	1181	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.
1182	1182
	1108	+[[image:1747829109466-595.png]]
1183	1183
1184	1184	**Figure 11: SDMX-IM of the Data Provider**
1185	1185
1186		-
1187	1187	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
1188	1188
1189	1189	[[image:1747824123019-181.jpeg]]
...	...	@@ -1192,8 +1192,10 @@
1192	1192
1193	1193	The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1194	1194
	1120	+[[image:1747829139951-378.png]]
1195	1195
1196		-==== 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**
1197	1197
1198	1198	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.
1199	1199
...	...	@@ -1221,13 +1221,12 @@
1221	1221
1222	1222	=== 7.3.3 Data and Metadata Constraints: Model ===
1223	1223
	1151	+[[image:1747829204737-370.png]]
1224	1224
	1153	+**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1225	1225
1226		-==== 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.
1227	1227
1228		-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.
1229		-
1230		-
1231	1231	The content of the Constraint can be found in the SDMX Information Model document.
1232	1232
1233	1233	== 7.4 Data and Metadata Registration ==
...	...	@@ -1262,11 +1262,14 @@
1262	1262
1263	1263	The Registration has an action attribute which takes one of the following values:
1264	1264
1265		-|**Action Attribute Value**|**Behaviour**
1266		-|Append|Add this Registration to the registry
1267		-|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1268		-|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
1269	1269
	1197	+[[image:1747829290890-122.png]]
	1198	+
1270	1270	**Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1271	1271
1272	1272	The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
...	...	@@ -1281,25 +1281,19 @@
1281	1281
1282	1282	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.
1283	1283
1284		-|**Indexing Required**|**Registration Process Activity**
1285		-|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1286		-|indexDataSet|(((
1287		-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
1288		-
1289		-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.
1290	1290	)))
1291		-|indexReportingPeriod|(((
	1218	+|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1292	1292	This applies only to a registered dataset.
1293		-
1294	1294	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1295	1295	)))
1296		-|indexAttributes|(((
	1222	+|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1297	1297	**Data Set**
1298		-
1299	1299	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
1300		-
1301	1301	**Metadata Set**
1302		-
1303	1303	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.
1304	1304	)))
1305	1305
...	...	@@ -1309,14 +1309,13 @@
1309	1309
1310	1310	=== 7.4.3 Registration Response ===
1311	1311
1312		-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”.
1313	1313
1314		-“Success”, “Warning” or “Failure”.
1315		-
1316	1316	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.
1317	1317
1318	1318	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:
1319	1319
	1241	+[[image:1747829477882-750.png]]
1320	1320
1321	1321	**Figure 18: Logical class diagram showing the registration response**
1322	1322
...	...	@@ -1326,15 +1326,12 @@
1326	1326
1327	1327	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.
1328	1328
1329		-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”.
1330	1330
1331		-“notification”.
	1253	+=== 7.5.1Subscription Logical Class Diagram ===
1332	1332
1333		- 7.5.1Subscription Logical Class Diagram
	1255	+[[image:1747829554603-150.png]]
1334	1334
1335		-
1336		-[[image:1747824123028-257.png]]
1337		-
1338	1338	**Figure 19: Logical Class Diagram of the Subscription**
1339	1339
1340	1340	=== 7.5.2 Subscription Information ===
...	...	@@ -1341,73 +1341,58 @@
1341	1341
1342	1342	Regardless of the type of registry/repository events being observed, a subscription always contains:
1343	1343
1344		-~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:
1345	1345
1346		-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
1347	1347
1348		-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.
1349		-
1350		-4. A selector which specifies which type of events are of interest. The set of event types is:
1351		-
1352		-|**Event Type**|**Comment**
1353		-|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1354		-|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1355		-|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1356		-|ALL_EVENTS|All events of the specified EventType
1357		-
1358	1358	=== 7.5.3 Wildcard Facility ===
1359	1359
1360	1360	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:
1361	1361
1362		- agencyID
	1278	+* agencyID
	1279	+* id
	1280	+* version
1363	1363
1364		- id
1365		-
1366		- version
1367		-
1368	1368	Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1369	1369
1370		-AgencyID = %
1371		-
	1284	+//AgencyID = %
1372	1372	Id = %
	1286	+Version = %//
1373	1373
1374		-Version = %
1375		-
1376	1376	This subscribes to all Codelists of all versions for all agencies.
1377	1377
1378		-AgencyID = AGENCY1
1379		-
	1290	+//AgencyID = AGENCY1
1380	1380	Id = CODELIST1
	1292	+Version = %//
1381	1381
1382		-Version = %
1383		-
1384	1384	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1385	1385
1386		-AGENCY1
1387		-
	1296	+//AGENCY1
1388	1388	AgencyID = AGENCY1
1389		-
1390	1390	Id = %
	1299	+Version = %//
1391	1391
1392		-Version = %
1393		-
1394	1394	This subscribes to all versions of all Codelist objects maintained by the agency
1395	1395
1396		-AGENCY1
1397		-
	1303	+//AGENCY1
1398	1398	AgencyID = %
1399		-
1400	1400	Id = CODELIST1
	1306	+Version = %//
1401	1401
1402		-Version = %
1403		-
1404	1404	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1405	1405
1406		-AGENCY1
	1310	+//AGENCY1//
1407	1407
1408	1408	Note that if the subscription is to the latest version then this can be achieved by the * character
1409	1409
1410		-i.e. Version = *
	1314	+//i.e. Version = *//
1411	1411
1412	1412	Note that a subscription using the URN mechanism cannot use wildcard characters.
1413	1413
...	...	@@ -1419,16 +1419,15 @@
1419	1419
1420	1420	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:
1421	1421
	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.
1422	1422
1423		-|**Selector**|**Comment**
1424		-|DataProvider|Any datasets or metadata sets registered by the specified data provider will activate the notification.
1425		-|ProvisionAgreement|Any datasets or metadata sets registered for the provision agreement will activate the notification.
1426		-|Dataflow (&Metadataflow)|Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification.
1427		-|DataStructureDefinition & MetadataStructureDefinition|Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will
1428		-|**Selector**|**Comment**
1429		-| |activate the notification.
1430		-|Category|Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category.
1431		-
1432	1432	The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration.
1433	1433
1434	1434	== 7.6 Notification ==
...	...	@@ -1435,8 +1435,10 @@
1435	1435
1436	1436	=== 7.6.1 Logical Class Diagram ===
1437	1437
	1341	+[[image:1747829675568-610.png]]
1438	1438
1439		-==== Figure 20: Logical Class Diagram of the Notification ====
	1343	+(% class="wikigeneratedid" id="HFigure20:LogicalClassDiagramoftheNotification" %)
	1344	+**Figure 20: Logical Class Diagram of the Notification**
1440	1440
1441	1441	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.
1442	1442
...	...	@@ -1456,5 +1456,3 @@
1456	1456	=== 7.6.3 Registration Event Component ===
1457	1457
1458	1458	The notification will contain the Registration.
1459		-
1460		-

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