Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 9.1
edited by Helena
on 2025/05/23 01:07
Change comment: There is no comment for this version
To version 3.5
edited by Helena
on 2025/05/21 15:31
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
... ... @@ -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:
294 +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 -
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
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.
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.
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
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
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)
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)
330 330  * request for a list of submitted subscriptions
331 331  * deletion of a subscription
332 332  
... ... @@ -448,8 +448,7 @@
448 448  
449 449  [[image:1747824123012-527.jpeg]]
450 450  
451 -*
452 -** Figure 7: Example of Hierarchic Structure of Agencies
454 +==== Figure 7: Example of Hierarchic Structure of Agencies ====
453 453  
454 454  The following organizations maintain an Agency Scheme.
455 455  
... ... @@ -464,8 +464,9 @@
464 464  
465 465  An example of this is shown in the XML snippet below.
466 466  
467 -[[image:1747832400104-286.png]]
469 +[[image:1747824123013-196.jpeg||height="309" width="446"]]
468 468  
471 +(% class="wikigeneratedid" id="HFigure8:ExampleShowingUseofAgencyIdentifiers" %)
469 469  **Figure 8: Example Showing Use of Agency Identifiers**
470 470  
471 471  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.
... ... @@ -478,8 +478,7 @@
478 478  
479 479  ==== 6.2.2.2 URN Structure ====
480 480  
481 -(% class="wikigeneratedid" id="HCaseRulesforURN" %)
482 -//Case Rules for URN//
484 +===== //Case Rules for URN// =====
483 483  
484 484  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.
485 485  
... ... @@ -705,6 +705,8 @@
705 705  hierarchicalcodelistId(version).Hierarchy.Level
706 706  )))|(% style="width:396px" %)(((
707 707  ESTAT:HCL_REGION(1.0).H_1.COUNTRY
710 +
711 +
708 708  )))
709 709  |(% 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
710 710  |(% style="width:250px" %)*DataStructure|(% style="width:444px" %)dataStructureDefintitionAgencyId: dataStructureDefintitionId(version)|(% style="width:396px" %)TFFS:EXT_DEBT(1.0)
... ... @@ -809,11 +809,15 @@
809 809  
810 810  |(% style="width:251px" %)(((
811 811  ReportStructure
816 +
817 +
812 812  )))|(% style="width:442px" %)(((
813 813  MSDAgencyId: MSDId(version).reportStructureId
814 814  )))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT
815 815  |(% style="width:251px" %)(((
816 -Metadata Attribute
822 +Metadata
823 +
824 +Attribute
817 817  )))|(% style="width:442px" %)(((
818 818  MSDAgencyId: MSDId(version).reportStructureId.metadataattri buteID
819 819  )))|(% style="width:1178px" %)IMF:SDDS_MSD(1.0).AGENCY_REPORT.COMPILATION
... ... @@ -824,10 +824,14 @@
824 824  TFFS:CRED_EXT_DEBT_AB(1.0)
825 825  )))
826 826  |(% style="width:251px" %)(((
827 -*Content Constraint
835 +*Content
836 +
837 +Constraint
828 828  )))|(% style="width:442px" %)constraintAgencyId:ContentConstraintId(versio n)|(% style="width:1178px" %)TFFS:CREDITOR_DATA_CONTENT(1.0)
829 829  |(% style="width:251px" %)(((
830 -*Attachment Constraint
840 +*Attachment
841 +
842 +Constraint
831 831  )))|(% style="width:442px" %)(((
832 832  constraintAgencyId:
833 833  
... ... @@ -850,7 +850,9 @@
850 850  codeMapId
851 851  )))|
852 852  |(((
853 -CategorySchemeMap
865 +Category
866 +
867 +SchemeMap
854 854  )))|structureSetAgencyId: structureSetId(version). categorySchemeMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT
855 855  |CategoryMap|structureSetAgencyId: structureSetId(version). categorySchemeMapId. categoryMapId|SDMX:BOP_STRUCTURES(1.0).SDMX_EUROSTAT.TOURISM_M AP
856 856  |Organisation SchemeMap|structureSetAgencyId: structureSetId(version). organisationSchemeMapId|SDMX:BOP_STRUCTURES(1.0).DATA_PROVIDER_MAP
... ... @@ -864,53 +864,71 @@
864 864  structureSetAgencyId: structureSetId(version). conceptSchemeMapId.
865 865  
866 866  conceptMapId
881 +
867 867  
868 868  )))|SDMX:BOP_STRUCTURES(1.0).SDMX_OECD.COVERAGE_AVAI LABILITY
869 869  |(((
870 -ReportingTaxonomyMap
885 +Reporting
886 +
887 +TaxonomyMap
871 871  )))|structureSetAgencyId: structureSetId(version). reportingTaxonomyMapId|SDMX:BOP_STRUCTURES(1.0).TAXMAP
872 872  |(((
873 -ReportingCategoryMap
890 +Reporting
891 +
892 +CategoryMap
874 874  )))|(((
875 875  structureSetAgencyId: structureSetId(version).
895 +
876 876  reportngCategoryId
877 877  )))|SDMX:BOP_STRUCTURES(1.0).TAXMAP.TOPCAT
878 878  
899 +
900 +
879 879  |(((
880 -HybridCodelistMap
881 -)))|structureSetAgencyId: structureSetId(version).
882 -hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
902 +HybridCodelist
903 +
904 +Map
905 +)))|structureSetAgencyId: structureSetId(version). hybridCodelistMapId.|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP
883 883  |HybridCodeMap|structureSetAgencyId: structureSetId(version). hybridCodelistMapId. hybridCodeMapId|SDMX:BOP_STRUCTURES(1.0).COUNTRY_HIERARCHYMAP.CO DEMAP1
884 884  |*Process|processAgencyId: processId{version]|BIS:PROCESS1(1.0)
885 885  |ProcessStep|(((
886 886  processAgencyId: processId(version).
910 +
887 887  processStepId
888 888  )))|BIS:PROCESS1(1.0).STEP1
889 889  |Transition|(((
890 890  processAgencyId: processId(version).
915 +
891 891  processStepId transitionId
892 892  )))|BIS:PROCESS1(1.0).STEP1.TRANSITION1
893 893  |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.
894 894  |(((
895 -*Transformation Scheme
920 +*Transformation
921 +
922 +Scheme
896 896  )))|transformationSchemeAgencyId transformationSchemeId(version)|ECB: TRANSFORMATION_SCHEME(1.0)
897 897  |Transformation|(((
898 898  transformationSchemeAgencyId transformationSchemeId(version)
926 +
899 899  transformationId
900 900  )))|ECB:TRANSFORMATION_SCHEME(1.0).TRANS_1
901 901  |CustomType Scheme|customTypeSchemeAgencyId customTypeSchemeId(version)|ECB:CUSTOM_TYPE_SCHEME(1.0)
902 902  
931 +
932 +
903 903  |CustomType|customTypeSchemeAgencyId customTypeSchemeId(version) customTypeId|ECB: CUSTOM_TYPE_SCHEME(1.0).CUSTOM_TYPE_1
904 904  |(((
905 905  Name
936 +
906 906  Personalisation
938 +
907 907  Scheme
908 908  )))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)|ECB:PSN_SCHEME(1.0)
909 909  |(((
910 910  Name
943 +
911 911  Personalisation
912 -)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version)
913 -namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
945 +)))|namePersonalisationSchemeAgencyId namePersonalisationSchemeId(version) namePersonalisationId|ECB:PSN_SCHEME(1.0).PSN1234
914 914  |VtlMapping Scheme|vtlMappingSchemeAgencyId VtlMappingSchemeId(version)|ECB:CLIST_MP(2.0)
915 915  |VtlCodelist Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|ECB:CLIST_MP(2.0).ABZ
916 916  |VtlConcept Mapping|vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|ECB:CLIST_MP(1.0).XYA
... ... @@ -923,11 +923,13 @@
923 923  |RulesetScheme|rulesetSchemeAgencyId rulesetSchemeId(version)|ECB:RULESET_23(1.0)
924 924  |Ruleset|rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|ECB:RULESET_23(1.0).SET111
925 925  |(((
926 -UserDefinedOperatorScheme
958 +UserDefined
959 +
960 +OperatorScheme
927 927  )))|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|ECB:OS_CALC(1.2)
928 928  |UserDefined Operator|userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|ECB:OS_CALC(1.2).OS267
929 929  
930 -**Table 3: Table of identification components for SDMX Identifiable Artefacts**
964 +7**Table 3: Table of identification components for SDMX Identifiable Artefacts**
931 931  
932 932  = 7 Implementation Notes =
933 933  
... ... @@ -1228,11 +1228,11 @@
1228 1228  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.
1229 1229  1. A selector which specifies which type of events are of interest. The set of event types is:
1230 1230  
1231 -|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment**
1232 -|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1233 -|(% 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.
1234 -|(% 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.
1235 -|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType
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
1236 1236  
1237 1237  === 7.5.3 Wildcard Facility ===
1238 1238  
1747832400104-286.png
Author
... ... @@ -1,1 +1,0 @@
1 -xwiki:XWiki.helena
Size
... ... @@ -1,1 +1,0 @@
1 -172.3 KB
Content