Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 9.3
edited by Helena
on 2025/05/23 13:00
Change comment: There is no comment for this version
To version 3.3
edited by Helena
on 2025/05/21 15:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SDMX 2.1 Standards. Section 5. Registry Specification – Logical Interfaces
1 +SDMX 2.1 Standards. Section. 5. Registry Specification – Logical Interfaces
Content
... ... @@ -4,11 +4,10 @@
4 4  
5 5  **Revision History**
6 6  
7 -(% style="width:833.294px" %)
8 -|(% style="width:122px" %)**Revision**|(% style="width:126px" %)**Date**|(% style="width:581px" %)**Contents**
9 -|(% style="width:122px" %) |(% style="width:126px" %)April 2011|(% style="width:581px" %)Initial release
10 -|(% style="width:122px" %)1.0|(% style="width:126px" %)July 2011|(% style="width:581px" %)Rectification of problems of the specifications dated April 2011
11 -|(% style="width:122px" %)2.0|(% style="width:126px" %)July 2020|(% style="width:581px" %)Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
7 +|**Revision**|**Date**|**Contents**
8 +| |April 2011|Initial release
9 +|1.0|July 2011|Rectification of problems of the specifications dated April 2011
10 +|2.0|July 2020|Addition of VTL (Validation and Transformation Language) package, maintainable artefacts, nameable artefacts to 5.2.3, 6.2.2, 6.2.3, 6.2.4, 7.1.1
12 12  
13 13  **Corrigendum**
14 14  
... ... @@ -291,20 +291,23 @@
291 291  * that the correct Data Structure Definition or Metadata Structure Definition is used by the registered data that the components (Dimensions, Attributes, Measures, Identifier Components etc.) are consistent with the Data Structure Definition or Metadata Structure Definition
292 292  * that the valid representations of the concepts to which these components correspond conform to the definition in the Data Structure Definition or Metadata Structure Definition
293 293  
294 -The Registration has an action attribute which takes one of the following values:
293 +3The Registration has an action attribute which takes one of the following values:
295 295  
296 -|(% style="width:219px" %)**Action Attribute Value**|(% style="width:1652px" %)**Behaviour**
297 -|(% style="width:219px" %)Append|(% style="width:1652px" %)Add this registration to the registry
298 -|(% style="width:219px" %)Replace|(% style="width:1652px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
299 -|(% style="width:219px" %)Delete|(% style="width:1652px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
300 -
295 +(% style="margin-left:auto; margin-right:auto" %)
296 +|(% style="width:200px" %)(((
297 +**Action Attribute Value**
298 +)))|(% style="width:1672px" %)**Behaviour**
299 +|(% style="width:200px" %)Append|(% style="width:1672px" %)Add this registration to the registry
300 +|(% style="width:200px" %)Replace|(% style="width:1672px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
301 +|(% style="width:200px" %)Delete|(% style="width:1672px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
301 301  The Registration has three Boolean attributes which may be present to determine how an SDMX compliant Dataset or Metadata Set indexing application must index the Datasets or Metadata Set upon registration. The indexing application behaviour is as follows:
302 -
303 -|(% style="width:228px" %)**Boolean Attribute**|(% style="width:1644px" %)**Behaviour if Value is “true”**
304 -|(% style="width:228px" %)indexTimeSeries|(% style="width:1644px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
305 -|(% style="width:228px" %)indexDataSet|(% style="width:1644px" %)A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
303 +|(% style="width:200px" %)**Boolean Attribute**|(% style="width:1672px" %)**Behaviour if Value is “true”**
304 +|(% style="width:200px" %)indexTimeSeries|(% style="width:1672px" %)A compliant indexing application must index all the time series keys (for a Dataset registration) or metadata target values (for a Metadata Set registration)
305 +|(% style="width:200px" %)indexDataSet|(% style="width:1672px" %)(((
306 +A compliant indexing application must index the range of actual (present) values for each dimension of the Dataset (for a Dataset registration) or the range of actual (present) values for each Metadata Attribute which takes an enumerated value.
306 306  Note that for data this requires much less storage than full key indexing, but this method cannot guarantee that a specific combination of Dimension values (the Key) is actually present in the Dataset
307 -|(% style="width:228px" %)indexReportingPeriod|(% style="width:1644px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
308 +)))
309 +|(% style="width:200px" %)indexReportingPeriod|(% style="width:1672px" %)A compliant indexing application must index the time period range(s) for which data are present in the Dataset or Metadata Set
308 308  
309 309  === 5.2.5 Data and Reference Metadata Discovery ===
310 310  
... ... @@ -326,7 +326,7 @@
326 326  Subscription management involves a user submitting a subscription request which contains:
327 327  
328 328  * a query or constraint expression in terms of a filter which defines the events for which the user is interested (e.g. new data for a specific dataflow, or for a domain category, or changes to a Data Structure Definition).
329 -* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto : ) and HTTP POST (a normal http:~/~/ address)
331 +* a list of URIs or end-points to which an XML notification message can be sent. Supported end-point types will be email (mailto~:) and HTTP POST (a normal http:~/~/ address)
330 330  * request for a list of submitted subscriptions
331 331  * deletion of a subscription
332 332  
... ... @@ -427,8 +427,6 @@
427 427  
428 428  The Maintenance Agency in SDMX is maintained in an Agency Scheme which itself is a sub class of Organisation Scheme – this is shown in the class diagram below.
429 429  
430 -[[image:1747994320263-112.png]]
431 -
432 432  **Figure 6: Agency Scheme Model**
433 433  
434 434  The Agency in SDMX is extremely important. The Agency Id system used in SDMX is an n-level structure. The top level of this structure is maintained by SDMX. Any Agency in this top level can declare sub agencies and any sub agency can also declare sub agencies. The Agency Scheme has a fixed id and version and is never declared explicitly in the SDMX object identification mechanism.
... ... @@ -450,7 +450,7 @@
450 450  
451 451  [[image:1747824123012-527.jpeg]]
452 452  
453 -**Figure 7: Example of Hierarchic Structure of Agencies**
453 +==== Figure 7: Example of Hierarchic Structure of Agencies ====
454 454  
455 455  The following organizations maintain an Agency Scheme.
456 456  
... ... @@ -465,8 +465,9 @@
465 465  
466 466  An example of this is shown in the XML snippet below.
467 467  
468 -[[image:1747832400104-286.png]]
468 +[[image:1747824123013-196.jpeg||height="309" width="446"]]
469 469  
470 +(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
470 470  **Figure 8: Example Showing Use of Agency Identifiers**
471 471  
472 472  Each of these maintenance agencies has an identical Code list with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure.
... ... @@ -479,8 +479,7 @@
479 479  
480 480  ==== 6.2.2.2 URN Structure ====
481 481  
482 -(% class="wikigeneratedid" id="HCaseRulesforURN" %)
483 -//Case Rules for URN//
483 +===== //Case Rules for URN// =====
484 484  
485 485  For the URN, all parts of the string are case sensitive. The Id of any object must be UPPER CASE. Therefore, CRED_ext_Debt is invalid and it should be CRED_EXT_DEBT.
486 486  
... ... @@ -706,6 +706,8 @@
706 706  hierarchicalcodelistId(version).Hierarchy.Level
707 707  )))|(% style="width:396px" %)(((
708 708  ESTAT:HCL_REGION(1.0).H_1.COUNTRY
709 +
710 +
709 709  )))
710 710  |(% 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
711 711  |(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0)
... ... @@ -810,11 +810,15 @@
810 810  
811 811  |(% style="width:251px" %)(((
812 812  ReportStructure
815 +
816 +
813 813  )))|(% style="width:442px" %)(((
814 814  MSDAgencyId: MSDId(version).reportStructureId
815 815  )))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
816 816  |(% style="width:251px" %)(((
817 -Metadata Attribute
821 +Metadata
822 +
823 +Attribute
818 818  )))|(% style="width:442px" %)(((
819 819  MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
820 820  )))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
... ... @@ -825,10 +825,14 @@
825 825  TFFS:CRED_EXT_DEBT_AB(1.0)
826 826  )))
827 827  |(% style="width:251px" %)(((
828 -*Content Constraint
834 +*Content
835 +
836 +Constraint
829 829  )))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
830 830  |(% style="width:251px" %)(((
831 -*Attachment Constraint
839 +*Attachment
840 +
841 +Constraint
832 832  )))|(% style="width:442px" %)(((
833 833  constraintAgencyId:
834 834  
... ... @@ -851,7 +851,9 @@
851 851  codeMapId
852 852  )))|
853 853  |(((
854 -CategorySchemeMap
864 +Category
865 +
866 +SchemeMap
855 855  )))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
856 856  |CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP
857 857  |Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
... ... @@ -865,53 +865,71 @@
865 865  structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
866 866  
867 867  conceptMapId
880 +
868 868  
869 869  )))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
870 870  |(((
871 -ReportingTaxonomyMap
884 +Reporting
885 +
886 +TaxonomyMap
872 872  )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
873 873  |(((
874 -ReportingCategoryMap
889 +Reporting
890 +
891 +CategoryMap
875 875  )))|(((
876 876  structureSetAgencyId: structureSetId(version).
894 +
877 877  reportngCategoryId
878 878  )))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
879 879  
898 +
899 +
880 880  |(((
881 -HybridCodelistMap
882 -)))|structureSetAgencyId: structureSetId(version).
883 -hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
901 +HybridCodelist
902 +
903 +Map
904 +)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
884 884  |HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
885 885  |*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0)
886 886  |ProcessStep|(((
887 887  processAgencyId: processId(version).
909 +
888 888  processStepId
889 889  )))|BIS:PROCESS1(1.0).STEP1
890 890  |Transition|(((
891 891  processAgencyId: processId(version).
914 +
892 892  processStepId transitionId
893 893  )))|BIS:PROCESS1(1.0).STEP1.TRANSITION1
894 894  |Subscription|The Subscription is not itself an Identifiable Artefact and therefore it does not follow the rules for URN structure, The name of the URN is registryURN There is no pre-determined format.|This cannot be generated by a common mechanism as subscriptions, although maintainable in the sense that they can be submitted and deleted, are not mandated to be created by a maintenance agency, and have no versioning mechanism. It is therefore the responsibility of the target registry to generate a unique Id for the Subscription, and for the application creating the subscription to store the registryURN that is returned from the registry in the subscription response message.
895 895  |(((
896 -*Transformation Scheme
919 +*Transformation
920 +
921 +Scheme
897 897  )))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0)
898 898  |Transformation|(((
899 899  transformationSchemeAgencyId transformationSchemeId(version)
925 +
900 900  transformationId
901 901  )))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
902 902  |CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0)
903 903  
930 +
931 +
904 904  |CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
905 905  |(((
906 906  Name
935 +
907 907  Personalisation
937 +
908 908  Scheme
909 909  )))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0)
910 910  |(((
911 911  Name
942 +
912 912  Personalisation
913 -)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
914 -namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
944 +)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
915 915  |VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0)
916 916  |VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ
917 917  |VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA
... ... @@ -924,11 +924,13 @@
924 924  |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
925 925  |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
926 926  |(((
927 -UserDefinedOperatorScheme
957 +UserDefined
958 +
959 +OperatorScheme
928 928  )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
929 929  |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
930 930  
931 -**Table 3: Table of identification components for SDMX Identifiable Artefacts**
963 +7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
932 932  
933 933  = 7 Implementation Notes =
934 934  
... ... @@ -1229,11 +1229,11 @@
1229 1229  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.
1230 1230  1. A selector which specifies which type of events are of interest. The set of event types is:
1231 1231  
1232 -|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
1233 -|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1234 -|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1235 -|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:1553px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1236 -|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
1264 +|(% style="width:327px" %)**Event Type**|(% style="width:1545px" %)**Comment**
1265 +|(% style="width:327px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1545px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1266 +|(% 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.
1267 +|(% 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.
1268 +|(% style="width:327px" %)ALL_EVENTS|(% style="width:1545px" %)All events of the specified EventType
1237 1237  
1238 1238  === 7.5.3 Wildcard Facility ===
1239 1239  
1747832400104-286.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -172.3 KB
Content
1747994320263-112.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -13.9 KB
Content