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