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, 7 added, 0 removed)
  • 1747829078194-749.png
  • 1747829109466-595.png
  • 1747829139951-378.png
  • 1747829204737-370.png
  • 1747829290890-122.png
  • 1747829477882-750.png
  • 1747829554603-150.png

Details

Page properties

Content

...	...	@@ -681,78 +681,52 @@
681	681
682	682	Note that for brevity the URN examples omit the prefix. All URNs have the prefix
683	683
684		-urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
	684	+> urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
685	685
686		-
687		-|**SDMX Class**|**Key attribute(s)**|**Example of URN**
688		-|Agency|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.|(((
	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	692	Sub agency in the IMF AGENCIES
693		-
694		-
695	695	IMF.SubAgency1
696	696	)))
697		-|*ConceptScheme|conceptSchemeAgencyId:conceptSchemeId(ve rsion)|SDMX:CROSS_DOMAIN_CONCEPTS(1.0)
698		-|Concept|(((
699		-conceptSchemeAgencyId:
700		-
701		-conceptSchemeId(version).conceptId
702		-)))|SDMX:CROSS_DOMAIN_CONCEPTS(1.0).FREQ
703		-|*Codelist|codeListAgencyId:codeListId(version)|SDMX:CL_FREQ(1.0)
704		-|Code|codeListAgencyId:codelistId(version).codeId|(((
705		-SDMX:CL_FREQ(1.0).Q
706		-
707		-
	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	+*Hierarchical Codelist
	700	+)))|(% style="width:444px" %)hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(% style="width:396px" %)(((
	701	+UNESCO:CL_EXP_SOURCE(1.0(% style="background-color:transparent" %))
708	708	)))
709		-
710		-
711		-
712		-|(((
713		-*Hierarchical
714		-
715		-Codelist
716		-)))|hierachicalCodelistAgencyId: hierarchicalCodelistId(version)|(((
717		-UNESCO:CL_EXP_SOURCE(1.0)
718		-
719		-
720		-)))
721		-|Hierarchy|(((
	703	+|(% style="width:250px" %)Hierarchy|(% style="width:444px" %)(((
722	722	hierachicalcodeListAgencyId:
723		-
724	724	hierarchicalcodelistId(version).Hierarchy
725		-)))|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV
726		-|Level|(((
	706	+)))|(% style="width:396px" %)UNESCO:CL_EXP_SOURCE(1.0).
	707	+H-C-GOV
	708	+|(% style="width:250px" %)Level|(% style="width:444px" %)(((
727	727	hierachicalcodeListAgencyId:
728		-
729	729	hierarchicalcodelistId(version).Hierarchy.Level
730		-)))|(((
	711	+)))|(% style="width:396px" %)(((
731	731	ESTAT:HCL_REGION(1.0).H_1.COUNTRY
732	732
733	733
734	734	)))
735		-|HierarchicalCode|hierachicalCodeListAgencyId: hierarchicalcodelistId(version).hierarchy.hierarc hicalCode|UNESCO:CL_EXP_SOURCE(1.0). H-C-GOV.GOV_CODE1
736		-|*DataStructure|dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|TFFS:EXT_DEBT(1.0)
737		-|(((
	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" %)(((
738	738	Dimension
739		-
740	740	Descriptor
741		-
742	742	Measure
743		-
744	744	Descriptor
745		-
746	746	Attribute
747		-
748	748	Descriptor
749		-)))|(((
	725	+)))|(% style="width:444px" %)(((
750	750	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
751		-
752	752	componentListId
753		-
754	754	where the componentListId is the name of the class (there is only one occurrence of each in the Data Structure Definition)
755		-)))|(((
	729	+)))|(% style="width:396px" %)(((
756	756	TFFS:EXT_DEBT(1.0).DimensionDescriptor
757	757
758	758	TFFS:EXT_DEBT(1.0).MeasureDescriptor
...	...	@@ -759,181 +759,132 @@
759	759
760	760	TFFS:EXT_DEBT(1.0).AttributeDescriptor
761	761	)))
762		-|(((
	736	+|(% style="width:250px" %)(((
763	763	GroupDimension
764		-
765	765	Descriptor
766		-)))|(((
	739	+)))|(% style="width:444px" %)(((
767	767	dataStructureDefinitionAgencyId: dataStructureDefinitionId(version).
768		-
769	769	groupDimensionDescriptorId
770		-)))|TFFS:EXT_DEBT(1.0).SIBLING
771		-|Dimension|(((
	742	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).SIBLING
	743	+|(% style="width:250px" %)Dimension|(% style="width:444px" %)(((
772	772	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
773		-
774	774	dimensionId
775		-)))|TFFS:EXT_DEBT(1.0).FREQ
776		-|TimeDimension|(((
	746	+)))|(% style="width:396px" %)TFFS:EXT_DEBT(1.0).FREQ
	747	+|(% style="width:250px" %)TimeDimension|(% style="width:444px" %)(((
777	777	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
778		-
779	779	timeDimensionId
780		-)))|TFFS:EXT_DEBT(1.0).TIME_PERIOD
781		-|Measure Dimension|dataStructureDefinitionAgencyId: dataStructureDefinition (version).|TFFS:EXT_DEBT(1.0).STOCK_FLOW
782		-
783		-
784		-
785		-| |measureDimensionId|
786		-|DataAttrribute|dataStructureDefinitionAgencyId: dataStructureDefinition (version). dataAttributeId|TFFS:EXT_DEBT(1.0).OBS_STATUS
787		-|PrimaryMeasure|(((
	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" %)(((
788	788	dataStructureDefinitionAgencyId: dataStructureDefinition (version).
789		-
790	790	primaryMeasureId
791		-)))|TFFS:EXT_DEBT(1.0).OBS_VALUE
792		-|(((
793		-*Category
794		-
795		-Scheme
796		-)))|categorySchemeAgencyId: categorySchemeId(version)|IMF:SDDS(1.0)
797		-|Category|categorySchemeAgencyId: categorySchemeId(version). categoryId.categoryId categoryId.categoryId etc.|(((
	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" %)(((
798	798	IMF:SDDS(1.0):
799		-
800	800	level_1_category.level_2_category …
801	801	)))
802		-|(((
803		-*Reporting
804		-
805		-Taxonomy
806		-)))|reportingTaxonomyAgencyId: reportingTaxonomyId(version)| IMF:REP_1(1.0)
807		-|ReportingCategory|reportingTaxonomyAgencyId: reportingTaxonomyId(version) reportingcategoryId.reportingcategoryId|(((
	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" %)(((
808	808	IMF:REP_1(1.0):
809		-
810	810	level_1_repcategory.level_2_repcategory …
811	811	)))
812		-|*Categorisation|categorisationAgencyId: categorisationId(version)|IMF:cat001(1.0)
813		-|(((
814		-*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)
815	815
816		-Unit Scheme
817		-)))|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version)|ECB:ORGANISATIONS(1.0)
818		-|Organisation Unit|organisationUnitSchemeAgencyId: organisationUnitSchemeId(version). organisationUnitId|ECB:ORGANISATIONS(1.0).1F
819		-|*AgencyScheme|agencySchemeAgencyId: agencySchemeId(version)|ECB:AGENCIES(1.0)
820		-
821		-
822		-
823		-|Agency|agencySchemeAgencyId: agencySchemeId(version). agencyId|ECB:AGENCY(1.0).AA
824		-|(((
825		-*DataProvider
826		-
827		-Scheme
828		-)))|dataProviderSchemeAgencyId: dataProviderSchemeId(version)|SDMX:DATA_PROVIDERS(1.0)
829		-|DataProvider|dataProviderSchemeAgencyId: dataProviderSchemeId(version) dataProviderId|SDMX:DATA_PROVIDERS(1.0).PROVIDER_1
830		-|(((
831		-*DataConsumer
832		-
833		-Scheme
834		-)))|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version)|SDMX:DATA_CONSUMERS(1.0)
835		-|Data Consumer|dataConsumerSchemeAgencyId: dataConsumerSchemeId(version) dataConsumerId|SDMX:DATA_CONSUMERS(1.0).CONSUMER_1
836		-|(((
837		-*Metadata
838		-
839		-Structure
840		-)))|MSDAgencyId:MSDId(version)|IMF:SDDS_MSD(1.0)
841		-|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" %)(((
842	842	MSDAgencyId:
843		-
844	844	MSDId(version).metadataTargetId
845		-)))|IMF:SDDS_MSD(1.0).AGENCY
846		-|(((
	797	+)))|(% style="width:1262px" %)IMF:SDDS_MSD(1.0).AGENCY
	798	+|(% style="width:262px" %)(((
847	847	Dimension
848		-
849	849	DescriptorValues
850		-
851	851	Target
852		-)))|(((
	802	+)))|(% style="width:369px" %)(((
853	853	MSDAgencyId: MSDId(version).
854		-
855	855	metadataTargetId.keyDescriptorValueTargetId
856		-)))|IMF:SDDS_MSD(1.0).AGENCY.KEY
857		-|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" %)(((
858	858	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
859	859
860		-MSDId(version).metadataTargetId.identifiable
861		-
862		-ObjectTargetId
863		-)))|IMF:SDDS_MSD(1.0).AGENCY.STR-OBJECT
864		-|DataSetTarget|(((
865		-MSDAgencyId:
866		-
867		-MSDId(version).metadataTargetId.dataSet
868		-
869		-TargetId
870		-)))|IMF:SDDS_MSD(1.0).AGENCY.D1101
871		-|PeportPeriod Target|(((
872		-MSDAgencyId:
873		-
874		-MSDId(version).metadataTargetId.reportPeriod
875		-
876		-TargetId
877		-)))|IMF:SDDS_MSD(1.0).AGENCY.REP_PER
878		-
879		-
880		-
881		-|(((
	817	+|(% style="width:251px" %)(((
882	882	ReportStructure
883	883
884	884
885		-)))|(((
886		-MSDAgencyId:
887		-
888		-MSDId(version).reportStructureId
889		-)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT
890		-|(((
	821	+)))|(% style="width:442px" %)(((
	822	+MSDAgencyId: MSDId(version).reportStructureId
	823	+)))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
	824	+|(% style="width:251px" %)(((
891	891	Metadata
892	892
893	893	Attribute
894		-)))|(((
895		-MSDAgencyId:
896		-
897		-MSDId(version).reportStructureId.metadataattri buteID
898		-)))|IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
899		-|*Dataflow|dataflowAgencyId: dataflowId(version)|TFFS:CRED_EXT_DEBT(1.0)
900		-|*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" %)(((
901	901	provisionAgreementAgencyId:provisionAgreem entId(version)
902		-
903		-
904		-)))|(((
	834	+)))|(% style="width:1178px" %)(((
905	905	TFFS:CRED_EXT_DEBT_AB(1.0)
906		-
907		-
908		-
909	909	)))
910		-|(((
	837	+|(% style="width:251px" %)(((
911	911	*Content
912	912
913	913	Constraint
914		-)))|constraintAgencyId:ContentConstraintId(versio n)|TFFS:CREDITOR_DATA_CONTENT(1.0)
915		-|(((
	841	+)))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
	842	+|(% style="width:251px" %)(((
916	916	*Attachment
917	917
918	918	Constraint
919		-)))|(((
	846	+)))|(% style="width:442px" %)(((
920	920	constraintAgencyId:
921	921
922	922	attachmentConstraintId(version)
923		-)))|TFFS:CREDITOR_DATA_ATTACHMENT_CONSTRAINT_ONE(1.0)
924		-|*Metadataflow|metadataflowAgencyId: metadataflowId(version)|IMF:SDDS_FLOW(1.0)
925		-|*StructureSet|structureSetAgencyId: structureSetId(version)|SDMX:BOP_STRUCTURES(1.0)
926		-|StructureMap|structureSetAgencyId: structureSetId(version). structureMapId|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2
927		-|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" %)(((
928	928	structureSetAgencyId: structureSetId(version).
929	929
930	930	structureMapId. componentMapId
931		-)))|SDMX:BOP_STRUCTURES(1.0).TABLE1_TABLE2. REFAREA_REPCOUNTRY
932		-|CodelistMap|structureSetAgencyId: structureSetId(version). codelistMapId|SDMX:BOP_STRUCTURES(1.0).CLREFAREA_CLREPCOUNTRY
933		-|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
934	934
935		-
936		-
937	937	| |(((
938	938	codeListMapId.
939	939
...	...	@@ -1041,7 +1041,6 @@
1041	1041
1042	1042	7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
1043	1043
1044		-
1045	1045	= 7 Implementation Notes =
1046	1046
1047	1047	== 7.1 Structural Definition Metadata ==
...	...	@@ -1062,109 +1062,72 @@
1062	1062
1063	1063	The following table lists the Maintainable Artefacts.
1064	1064
1065		-|(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**|
1066		-|(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %) |
1067		-|(% colspan="2" %)Item Scheme|(% colspan="2" %)Codelist|(% colspan="2" %)Code|
1068		-|(% colspan="2" %) |(% colspan="2" %)Concept Scheme|(% colspan="2" %)Concept|
1069		-|(% colspan="2" %) |(% colspan="2" %)Category Scheme|(% colspan="2" %)Category|
1070		-|(% colspan="2" %) |(% colspan="2" %)Organisation Unit Scheme|(% colspan="2" %)Organisation Unit|
1071		-|(% colspan="2" %) |(% colspan="2" %)Agency Scheme|(% colspan="2" %)Agency|
1072		-|(% colspan="2" %) |(% colspan="2" %)Data Provider Scheme|(% colspan="2" %)Data Provider|
1073		-|(% colspan="2" %) |(% colspan="2" %)Data Consumer Scheme|(% colspan="2" %)Data Consumer|
1074		-|(% colspan="2" %) |(% colspan="2" %)Reporting Taxonomy|(% colspan="2" %)Reporting Category|
1075		-|(% colspan="2" %) |(% colspan="2" %)Transformation Scheme|(% colspan="2" %)Transformation|
1076		-|(% colspan="2" %) |(% colspan="2" %)Custom Type Scheme|(% colspan="2" %)Custom Type|
1077		-| |(% colspan="4" %)**Maintainable Artefacts**|(% colspan="2" %)**Content**
1078		-| |(% colspan="2" %)**Abstract Class**|(% colspan="2" %)**Concrete Class**|(% colspan="2" %)
1079		-| |(% colspan="2" %) |(% colspan="2" %)Name Personalisation Scheme|(% colspan="2" %)Name Personalisation
1080		-| |(% colspan="2" %) |(% colspan="2" %)Vtl Mapping Scheme|(% colspan="2" %)Vtl Codelist Mapping
1081		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Concept Mapping
1082		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)Vtl Dataflow Mapping
1083		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)(((
1084		-Vtl Concept Scheme
1085		-
1086		-Mapping
1087		-)))
1088		-| |(% colspan="2" %) |(% colspan="2" %)Ruleset Scheme|(% colspan="2" %)Ruleset
1089		-| |(% colspan="2" %) |(% colspan="2" %)User Defined Operator Scheme|(% colspan="2" %)User Defined Operator
1090		-| |(% colspan="2" %) |(% colspan="2" %) |(% colspan="2" %)
1091		-| |(% 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" %)(((
1092	1092	Dimension Descriptor
1093		-
1094	1094	Group Dimension
1095		-
1096	1096	Descriptor
1097		-
1098	1098	Dimension
1099		-
1100	1100	Measure Dimension
1101		-
1102	1102	Time Dimension
1103		-
1104	1104	Attribute Descriptor
1105		-
1106	1106	Data Attribute
1107		-
1108	1108	Measure Descriptor
1109		-
1110	1110	Primary Measure
1111	1111	)))
1112		-| |(% colspan="2" %) |(% colspan="2" %)Metadata Structure Definition|(% colspan="2" %)(((
1113		-Metadata Target,
1114		-
1115		-Dimension Descriptor
1116		-
	1021	+|(% style="width:171px" %) |(% style="width:232px" %)Metadata Structure Definition|(% style="width:206px" %)(((
	1022	+Metadata Target, Dimension Descriptor
1117	1117	Values Target Identifiable
1118		-
1119	1119	Object Target
1120		-
1121	1121	Report Period Target
1122		-
1123	1123	Data SetTarget
1124		-
1125	1125	Report Structure
1126		-
1127	1127	Metadata Attribute
1128	1128	)))
1129		-| |(% colspan="2" %)Structure Usage|(% colspan="2" %)Dataflow Definition|(% colspan="2" %)
1130		-| |(% colspan="2" %) |(% colspan="2" %)Metadataflow Definition|(% colspan="2" %)
1131		-| |(% colspan="2" %)None|(% colspan="2" %)Process|(% colspan="2" %)Process Step
1132		-| |(% 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" %)(((
1133	1133	Component Map
1134		-
1135	1135	Concept Scheme Map
1136		-
1137	1137	Codelist Map
1138		-
1139	1139	Category Scheme Map
1140		-
1141	1141	Reporting Taxonomy Map
1142		-
1143	1143	Organisation Scheme Map
1144		-
1145	1145	Concept Map
1146		-
1147	1147	Code Map
1148		-
1149	1149	Category Map
1150		-
1151	1151	Organisation Map
1152		-
1153	1153	Reporting Category Map
1154		-
1155	1155	Hybrid Codelist Map
1156		-
1157	1157	Hybrid Code Map
1158	1158	)))
1159		-| |(% colspan="2" %)None|(% colspan="2" %)Provision Agreement|(% colspan="2" %)
1160		-| |(% 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" %)(((
1161	1161	Hierarchy
1162		-
1163	1163	Hierarchical Code
1164	1164	)))
1165		-| | | | | | |
1166	1166
1167		-**Table 4: Table of Maintainable Artefacts for Structural Definition Metadata**
	1054	+**able 4: Table of Maintainable Artefacts for Structural Definition Metadata**
1168	1168
1169	1169	=== 7.1.2 Item Scheme, Structure ===
1170	1170
...	...	@@ -1171,10 +1171,7 @@
1171	1171	The artefacts included in the structural definitions are:
1172	1172
1173	1173	* All types of Item Scheme (Codelist, Concept Scheme, Category Scheme, Organisation Scheme - Agency Scheme, Data Provider Scheme, Data Consumer Scheme, Organisation Unit Scheme)
1174		-* All types of Structure (Data Structure Definition, Metadata Structure
1175		-
1176		-Definition)
1177		-
	1061	+* All types of Structure (Data Structure Definition, Metadata Structure Definition)
1178	1178	* All types of Structure Usage (Dataflow Definition, Metadataflow Definition)
1179	1179
1180	1180	=== 7.1.3 Structure Usage ===
...	...	@@ -1193,6 +1193,8 @@
1193	1193
1194	1194	==== 7.1.3.3 Structure Usage Model ====
1195	1195
	1080	+[[image:1747829078194-749.png]]
	1081	+
1196	1196	**Figure 10: SDMX-IM of links from Structure Usage to Category**
1197	1197
1198	1198	In addition to the maintenance of the Dataflow Definition and the Metadataflow Definition the following links must be maintained in the registry:
...	...	@@ -1219,10 +1219,10 @@
1219	1219
1220	1220	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.
1221	1221
	1108	+[[image:1747829109466-595.png]]
1222	1222
1223	1223	**Figure 11: SDMX-IM of the Data Provider**
1224	1224
1225		-
1226	1226	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
1227	1227
1228	1228	[[image:1747824123019-181.jpeg]]
...	...	@@ -1231,8 +1231,10 @@
1231	1231
1232	1232	The diagram below is a logical representation of the data required in order to maintain Provision Agreements.
1233	1233
	1120	+[[image:1747829139951-378.png]]
1234	1234
1235		-==== 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**
1236	1236
1237	1237	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.
1238	1238
...	...	@@ -1260,13 +1260,12 @@
1260	1260
1261	1261	=== 7.3.3 Data and Metadata Constraints: Model ===
1262	1262
	1151	+[[image:1747829204737-370.png]]
1263	1263
	1153	+**Figure 15: Logical class diagram showing inheritance between and reference to constrainable artifacts**
1264	1264
1265		-==== 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.
1266	1266
1267		-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.
1268		-
1269		-
1270	1270	The content of the Constraint can be found in the SDMX Information Model document.
1271	1271
1272	1272	== 7.4 Data and Metadata Registration ==
...	...	@@ -1301,11 +1301,14 @@
1301	1301
1302	1302	The Registration has an action attribute which takes one of the following values:
1303	1303
1304		-|**Action Attribute Value**|**Behaviour**
1305		-|Append|Add this Registration to the registry
1306		-|Replace|Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1307		-|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
1308	1308
	1197	+[[image:1747829290890-122.png]]
	1198	+
1309	1309	**Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1310	1310
1311	1311	The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
...	...	@@ -1320,25 +1320,19 @@
1320	1320
1321	1321	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.
1322	1322
1323		-|**Indexing Required**|**Registration Process Activity**
1324		-|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1325		-|indexDataSet|(((
1326		-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
1327		-
1328		-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.
1329	1329	)))
1330		-|indexReportingPeriod|(((
	1218	+|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1331	1331	This applies only to a registered dataset.
1332		-
1333	1333	Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1334	1334	)))
1335		-|indexAttributes|(((
	1222	+|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1336	1336	**Data Set**
1337		-
1338	1338	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
1339		-
1340	1340	**Metadata Set**
1341		-
1342	1342	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.
1343	1343	)))
1344	1344
...	...	@@ -1348,14 +1348,13 @@
1348	1348
1349	1349	=== 7.4.3 Registration Response ===
1350	1350
1351		-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”.
1352	1352
1353		-“Success”, “Warning” or “Failure”.
1354		-
1355	1355	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.
1356	1356
1357	1357	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:
1358	1358
	1241	+[[image:1747829477882-750.png]]
1359	1359
1360	1360	**Figure 18: Logical class diagram showing the registration response**
1361	1361
...	...	@@ -1365,15 +1365,12 @@
1365	1365
1366	1366	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.
1367	1367
1368		-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”.
1369	1369
1370		-“notification”.
	1253	+=== 7.5.1Subscription Logical Class Diagram ===
1371	1371
1372		- 7.5.1Subscription Logical Class Diagram
	1255	+[[image:1747829554603-150.png]]
1373	1373
1374		-
1375		-[[image:1747824123028-257.png]]
1376		-
1377	1377	**Figure 19: Logical Class Diagram of the Subscription**
1378	1378
1379	1379	=== 7.5.2 Subscription Information ===
...	...	@@ -1380,73 +1380,58 @@
1380	1380
1381	1381	Regardless of the type of registry/repository events being observed, a subscription always contains:
1382	1382
1383		-~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:
1384	1384
1385		-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
1386	1386
1387		-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.
1388		-
1389		-4. A selector which specifies which type of events are of interest. The set of event types is:
1390		-
1391		-|**Event Type**|**Comment**
1392		-|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1393		-|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1394		-|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1395		-|ALL_EVENTS|All events of the specified EventType
1396		-
1397	1397	=== 7.5.3 Wildcard Facility ===
1398	1398
1399	1399	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:
1400	1400
1401		- agencyID
	1278	+* agencyID
	1279	+* id
	1280	+* version
1402	1402
1403		- id
1404		-
1405		- version
1406		-
1407	1407	Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1408	1408
1409		-AgencyID = %
1410		-
	1284	+//AgencyID = %
1411	1411	Id = %
	1286	+Version = %//
1412	1412
1413		-Version = %
1414		-
1415	1415	This subscribes to all Codelists of all versions for all agencies.
1416	1416
1417		-AgencyID = AGENCY1
1418		-
	1290	+//AgencyID = AGENCY1
1419	1419	Id = CODELIST1
	1292	+Version = %//
1420	1420
1421		-Version = %
1422		-
1423	1423	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1424	1424
1425		-AGENCY1
1426		-
	1296	+//AGENCY1
1427	1427	AgencyID = AGENCY1
1428		-
1429	1429	Id = %
	1299	+Version = %//
1430	1430
1431		-Version = %
1432		-
1433	1433	This subscribes to all versions of all Codelist objects maintained by the agency
1434	1434
1435		-AGENCY1
1436		-
	1303	+//AGENCY1
1437	1437	AgencyID = %
1438		-
1439	1439	Id = CODELIST1
	1306	+Version = %//
1440	1440
1441		-Version = %
1442		-
1443	1443	This subscribes to all versions of Codelist CODELIST1 maintained by the agency
1444	1444
1445		-AGENCY1
	1310	+//AGENCY1//
1446	1446
1447	1447	Note that if the subscription is to the latest version then this can be achieved by the * character
1448	1448
1449		-i.e. Version = *
	1314	+//i.e. Version = *//
1450	1450
1451	1451	Note that a subscription using the URN mechanism cannot use wildcard characters.
1452	1452

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