Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 3.3
edited by Helena
on 2025/05/21 15:27
Change comment: There is no comment for this version
To version 9.2
edited by Helena
on 2025/05/23 12:58
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,10 +4,11 @@
4 4  
5 5  **Revision History**
6 6  
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
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
11 11  
12 12  **Corrigendum**
13 13  
... ... @@ -290,23 +290,20 @@
290 290  * 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
291 291  * 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
292 292  
293 -3The Registration has an action attribute which takes one of the following values:
294 +The Registration has an action attribute which takes one of the following values:
294 294  
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
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 +
302 302  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:
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.
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.
307 307  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
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
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
310 310  
311 311  === 5.2.5 Data and Reference Metadata Discovery ===
312 312  
... ... @@ -328,7 +328,7 @@
328 328  Subscription management involves a user submitting a subscription request which contains:
329 329  
330 330  * 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).
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)
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)
332 332  * request for a list of submitted subscriptions
333 333  * deletion of a subscription
334 334  
... ... @@ -429,6 +429,8 @@
429 429  
430 430  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.
431 431  
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,8 @@
450 450  
451 451  [[image:1747824123012-527.jpeg]]
452 452  
453 -==== Figure 7: Example of Hierarchic Structure of Agencies ====
453 +*
454 +** Figure 7: Example of Hierarchic Structure of Agencies
454 454  
455 455  The following organizations maintain an Agency Scheme.
456 456  
... ... @@ -465,9 +465,8 @@
465 465  
466 466  An example of this is shown in the XML snippet below.
467 467  
468 -[[image:1747824123013-196.jpeg||height="309" width="446"]]
469 +[[image:1747832400104-286.png]]
469 469  
470 -(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
471 471  **Figure 8: Example Showing Use of Agency Identifiers**
472 472  
473 473  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.
... ... @@ -480,7 +480,8 @@
480 480  
481 481  ==== 6.2.2.2 URN Structure ====
482 482  
483 -===== //Case Rules for URN// =====
483 +(% class="wikigeneratedid" id="HCaseRulesforURN" %)
484 +//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,8 +706,6 @@
706 706  hierarchicalcodelistId(version).Hierarchy.Level
707 707  )))|(% style="width:396px" %)(((
708 708  ESTAT:HCL_REGION(1.0).H_1.COUNTRY
709 -
710 -
711 711  )))
712 712  |(% 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
713 713  |(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0)
... ... @@ -812,15 +812,11 @@
812 812  
813 813  |(% style="width:251px" %)(((
814 814  ReportStructure
815 -
816 -
817 817  )))|(% style="width:442px" %)(((
818 818  MSDAgencyId: MSDId(version).reportStructureId
819 819  )))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
820 820  |(% style="width:251px" %)(((
821 -Metadata
822 -
823 -Attribute
818 +Metadata Attribute
824 824  )))|(% style="width:442px" %)(((
825 825  MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
826 826  )))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
... ... @@ -831,14 +831,10 @@
831 831  TFFS:CRED_EXT_DEBT_AB(1.0)
832 832  )))
833 833  |(% style="width:251px" %)(((
834 -*Content
835 -
836 -Constraint
829 +*Content Constraint
837 837  )))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
838 838  |(% style="width:251px" %)(((
839 -*Attachment
840 -
841 -Constraint
832 +*Attachment Constraint
842 842  )))|(% style="width:442px" %)(((
843 843  constraintAgencyId:
844 844  
... ... @@ -861,9 +861,7 @@
861 861  codeMapId
862 862  )))|
863 863  |(((
864 -Category
865 -
866 -SchemeMap
855 +CategorySchemeMap
867 867  )))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
868 868  |CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP
869 869  |Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
... ... @@ -877,71 +877,53 @@
877 877  structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
878 878  
879 879  conceptMapId
880 -
881 881  
882 882  )))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
883 883  |(((
884 -Reporting
885 -
886 -TaxonomyMap
872 +ReportingTaxonomyMap
887 887  )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
888 888  |(((
889 -Reporting
890 -
891 -CategoryMap
875 +ReportingCategoryMap
892 892  )))|(((
893 893  structureSetAgencyId: structureSetId(version).
894 -
895 895  reportngCategoryId
896 896  )))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
897 897  
898 -
899 -
900 900  |(((
901 -HybridCodelist
902 -
903 -Map
904 -)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
882 +HybridCodelistMap
883 +)))|structureSetAgencyId: structureSetId(version).
884 +hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
905 905  |HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
906 906  |*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0)
907 907  |ProcessStep|(((
908 908  processAgencyId: processId(version).
909 -
910 910  processStepId
911 911  )))|BIS:PROCESS1(1.0).STEP1
912 912  |Transition|(((
913 913  processAgencyId: processId(version).
914 -
915 915  processStepId transitionId
916 916  )))|BIS:PROCESS1(1.0).STEP1.TRANSITION1
917 917  |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.
918 918  |(((
919 -*Transformation
920 -
921 -Scheme
897 +*Transformation Scheme
922 922  )))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0)
923 923  |Transformation|(((
924 924  transformationSchemeAgencyId transformationSchemeId(version)
925 -
926 926  transformationId
927 927  )))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
928 928  |CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0)
929 929  
930 -
931 -
932 932  |CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
933 933  |(((
934 934  Name
935 -
936 936  Personalisation
937 -
938 938  Scheme
939 939  )))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0)
940 940  |(((
941 941  Name
942 -
943 943  Personalisation
944 -)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
914 +)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
915 +namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
945 945  |VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0)
946 946  |VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ
947 947  |VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA
... ... @@ -954,13 +954,11 @@
954 954  |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
955 955  |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
956 956  |(((
957 -UserDefined
958 -
959 -OperatorScheme
928 +UserDefinedOperatorScheme
960 960  )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
961 961  |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
962 962  
963 -7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
932 +**Table 3: Table of identification components for SDMX Identifiable Artefacts**
964 964  
965 965  = 7 Implementation Notes =
966 966  
... ... @@ -1261,11 +1261,11 @@
1261 1261  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.
1262 1262  1. A selector which specifies which type of events are of interest. The set of event types is:
1263 1263  
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
1233 +|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
1234 +|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1235 +|(% 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.
1236 +|(% 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.
1237 +|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
1269 1269  
1270 1270  === 7.5.3 Wildcard Facility ===
1271 1271  
1747832400104-286.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +172.3 KB
Content
1747994320263-112.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content