Skip to Content
Last modified by Artur on 2025/09/30 13:28
From version 24.6
edited by Helena
on 2025/06/08 21:41
Change comment: There is no comment for this version
To version 23.1
edited by Helena
on 2025/06/08 17:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -77,7 +77,7 @@
77 77  
78 78  [[image:SDMX 3.1 Section 5_en_c485399b.jpg||height="539" width="443"]]
79 79  
80 -**Figure 1: Schematic of the Basic Structural Artefacts in the SDMX-IM**
80 +**Figure 1: Schematic of the Basic Structural [[Artefacts>>doc:sdmx:Glossary.Artefact.WebHome]] in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]**
81 81  
82 82  Note that in Figure 1 (but also most of the relevant subsequent figures) terms that include both data and metadata have been used. For example:
83 83  
... ... @@ -98,13 +98,13 @@
98 98  
99 99  [[image:SDMX 3.1 Section 5_en_6e468656.jpg||height="407" width="553"]]
100 100  
101 -**Figure 2: Schematic of Registered Data and Metadata Sources in the SDMX-IM**
101 +**Figure 2: Schematic of Registered Data and Metadata Sources in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]**
102 102  
103 103  == 3.4 Notification ==
104 104  
105 105  Notifying interested parties of newly published or re-published data, [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] or changes in [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] involves:
106 106  
107 -* registry support of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]-based [[notification>>doc:sdmx:Glossary.Notification.WebHome]] service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request.
107 +• registry support of a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]-based [[notification>>doc:sdmx:Glossary.Notification.WebHome]] service which sends an email or notifies an HTTP address announcing all published data that meets the criteria contained in the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request.
108 108  
109 109  == 3.5 Discovery ==
110 110  
... ... @@ -116,7 +116,7 @@
116 116  
117 117  [[image:SDMX 3.1 Section 5_en_6c6c7b74.jpg||height="328" width="554"]]
118 118  
119 -**Figure 3: Schematic of Data and Metadata Discovery and Query in the SDMX-IM**
119 +**Figure 3: Schematic of Data and Metadata Discovery and Query in the [[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]**
120 120  
121 121  = 4 SDMX Registry/Repository Architecture =
122 122  
... ... @@ -214,7 +214,7 @@
214 214  The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values:
215 215  
216 216  (% style="width:893.835px" %)
217 -|(% style="width:241px" %)**Action Attribute Value**|(% style="width:650px" %)**Behaviour**
217 +|(% style="width:241px" %)**Action [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Value**|(% style="width:650px" %)**Behaviour**
218 218  |(% style="width:241px" %)Append|(% style="width:650px" %)Add this registration to the registry
219 219  |(% style="width:241px" %)Replace|(% style="width:650px" %)Replace the existing Registration with this Registration identified by the id in the Registration of the Submit Registration Request
220 220  |(% style="width:241px" %)Delete|(% style="width:650px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
... ... @@ -437,27 +437,27 @@
437 437  
438 438  __Actual object is a maintainable__
439 439  
440 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version)
440 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%))
441 441  
442 442  __Actual object is contained in a maintained object with no intermediate containing object__
443 443  
444 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).object-id
444 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).object-id
445 445  
446 446  __Actual object is contained in a maintained object with an intermediate containing object__
447 447  
448 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
448 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).contained-object-id.object-id
449 449  
450 450  __Actual object is contained in a maintained object with no intermediate containing__ __object but__ __the object type itself is hierarchical__
451 451  
452 452  In this case the object id may not be unique in itself but only within the context of the [[hierarchy>>doc:sdmx:Glossary.Hierarchy.WebHome]]. In the general syntax of the URN all intermediary objects in the structure (with the exception, of course, of the maintained object) are shown as a contained object. An example here would be a [[Category>>doc:sdmx:Glossary.Category.WebHome]] in a CategoryScheme. The [[Category>>doc:sdmx:Glossary.Category.WebHome]] is hierarchical, and all intermediate [[Categories>>doc:sdmx:Glossary.Category.WebHome]] are shown as a contained object. The example below shows the generic structure for CategoryScheme/ [[Category>>doc:sdmx:Glossary.Category.WebHome]]/ [[Category>>doc:sdmx:Glossary.Category.WebHome]].
453 453  
454 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.object-id
454 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).contained-object-id.object-id
455 455  
456 456  Actual object is contained in a maintained object with an intermediate containing object and the object type itself is hierarchical
457 457  
458 458  In this case the generic syntax is the same as for the example above as the parent object is regarded as a containing object, even if it is of the same type. An example here is a MetadataAttribute where the contained objects are MetadataAttributeDescriptor (first contained object id) and MetadataAttribute (subsequent contained object ids). The example below shows the generic structure for [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]/ MetadataAttributeDescriptor/ MetadataAttribute/ MetadataAttribute
459 459  
460 -SDMXPrefix.SDMX-IM-package-name.classname=agencyid:maintained-objectid(version).contained-object-id.contained-object-id contained-objectid.object-id
460 +SDMXPrefix.[[SDMX-IM>>doc:sdmx:Glossary.SDMX Information Model.WebHome]]-package-name.classname=agencyid:maintained-objectid((% style="color:#e74c3c" %)version(%%)).contained-object-id.contained-object-id contained-objectid.object-id
461 461  
462 462  //__**Concrete Examples of the URN Structure**__//
463 463  
... ... @@ -590,7 +590,7 @@
590 590  
591 591  Note that for brevity the URN examples omit the prefix (classnames in italics indicate maintainable objects, keywords in bold indicate fixed value) All URNs have the prefix:
592 592  
593 -urn:sdmx.org.sdmx.infomodel.{package}.{classname}=
593 +urn:[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].org.[[sdmx>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].infomodel.{package}.{classname}=
594 594  
595 595  (% style="width:1272.83px" %)
596 596  |(% style="width:289px" %)**Classname**|(% style="width:600px" %)**Ending URN pattern**|(% style="width:383px" %)**Example**
... ... @@ -689,13 +689,13 @@
689 689  (% style="color:#000000" %)reportingTaxonomyId(version).reportingCategoryI d.reportingCategoryId
690 690  )))|(% style="width:739px" %)IMF:REP_1(1.0.0):LVL1_REP_CAT.LVL2_REP_CAT
691 691  |(% style="width:296px" %)//ReportingTaxonomy//|(% style="width:646px" %)(% style="color:#000000" %)reportingTaxonomyAgencyId:reportingTaxonomyI d(version)|(% style="width:739px" %)IMF:REP_1(1.0.0)
692 -|(% style="width:296px" %)//ReportingTaxonomyMap//|(% style="width:646px" %)repTaxonomyAgencyId:repTaxonomyId(version)|(% style="width:739px" %)SDMX:RT_MAP(1.0.0)
692 +|(% style="width:296px" %)//ReportingTaxonomyMap//|(% style="width:646px" %)repTaxonomyAgencyId:repTaxonomyId((% style="color:#e74c3c" %)version(%%))|(% style="width:739px" %)[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:RT_MAP(1.0.0)
693 693  
694 694  |(% style="width:297px" %)**Classname**|(% style="width:647px" %)**Ending URN pattern**|(% style="width:737px" %)**Example**
695 -|(% style="width:297px" %)//RepresentationMap//|(% style="width:647px" %)repMapAgencyId:repMapId(version)|(% style="width:737px" %)SDMX:REF_AREA_MAPPING(1.0.0)
696 -|(% style="width:297px" %)Ruleset|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId(version) rulesetId|(% style="width:737px" %)ECB:RULESET_23(1.0.0).SET111
697 -|(% style="width:297px" %)//RulesetScheme//|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId(version)|(% style="width:737px" %)ECB:RULESET_23(1.0.0)
698 -|(% style="width:297px" %)//StructureMap//|(% style="width:647px" %)structureMapAgencyId:structureMap(version)|(% style="width:737px" %)SDMX:BOP_STRUCTURES(1.0.0)
695 +|(% style="width:297px" %)//RepresentationMap//|(% style="width:647px" %)repMapAgencyId:repMapId((% style="color:#e74c3c" %)version(%%))|(% style="width:737px" %)[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:REF_AREA_MAPPING(1.0.0)
696 +|(% style="width:297px" %)Ruleset|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId((% style="color:#e74c3c" %)version(%%)) rulesetId|(% style="width:737px" %)ECB:RULESET_23(1.0.0).SET111
697 +|(% style="width:297px" %)//RulesetScheme//|(% style="width:647px" %)rulesetSchemeAgencyId rulesetSchemeId((% style="color:#e74c3c" %)version(%%))|(% style="width:737px" %)ECB:RULESET_23(1.0.0)
698 +|(% style="width:297px" %)//StructureMap//|(% style="width:647px" %)structureMapAgencyId:structureMap((% style="color:#e74c3c" %)version(%%))|(% style="width:737px" %)[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:BOP_STRUCTURES(1.0.0)
699 699  |(% style="width:297px" %)[[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]]|(% style="width:647px" %)(((
700 700  The [[Subscription>>doc:sdmx:Glossary.Subscription.WebHome]] is not itself an [[Identifiable Artefact>>doc:sdmx:Glossary.Identifiable artefact.WebHome]] and therefore it does not follow the rules for URN structure.
701 701  The name of the URN is registryURN There is no pre-determined format.
... ... @@ -710,7 +710,7 @@
710 710  )))|(% style="width:737px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1
711 711  |(% style="width:297px" %)UserDefinedOperator|(% style="width:647px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:737px" %)ECB:OS_CALC(1.2.0).OS267
712 712  |(% style="width:297px" %)//UserDefinedOperatorScheme//|(% style="width:647px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:737px" %)ECB:OS_CALC(1.2.0)
713 -|(% style="width:297px" %)//ValueList//|(% style="width:647px" %)(% style="color:#000000" %)valuelistAgencyId:valuelistId(version)|(% style="width:737px" %)SDMX:VLIST(1.0.0)
713 +|(% style="width:297px" %)//ValueList//|(% style="width:647px" %)(% style="color:#000000" %)valuelistAgencyId:valuelistId(version)|(% style="width:737px" %)[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:VLIST(1.0.0)
714 714  |(% style="width:297px" %)VtlCodelistMapping|(% style="width:647px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:737px" %)ECB:CLIST_MP(2.0.0).ABZ
715 715  |(% style="width:297px" %)VtlConceptMapping|(% style="width:647px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).XYA
716 716  |(% style="width:297px" %)VtlDataflowMapping|(% style="width:647px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).MOQ
... ... @@ -739,7 +739,7 @@
739 739  The following table lists the [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]].
740 740  
741 741  (% style="width:825.835px" %)
742 -|(% colspan="2" style="width:455px" %)**Maintainable Artefacts**|(% style="width:367px" %)**Content**
742 +|(% colspan="2" style="width:455px" %)**[[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]]**|(% style="width:367px" %)**Content**
743 743  |(% style="width:160px" %)**Abstract Class**|(% style="width:295px" %)**Concrete Class**|(% style="width:367px" %)
744 744  |(% style="width:160px" %)[[Item Scheme>>doc:sdmx:Glossary.Item scheme.WebHome]]|(% style="width:295px" %)Codelist|(% style="width:367px" %)[[Code>>doc:sdmx:Glossary.Code.WebHome]]
745 745  |(% style="width:160px" %) |(% style="width:295px" %)[[Concept Scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]]|(% style="width:367px" %)(% style="color:#e74c3c" %)Concept
... ... @@ -932,11 +932,10 @@
932 932  The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values:
933 933  
934 934  (((
935 -(% style="width:918.835px" %)
936 -|(% style="width:224px" %)**Action Attribute Value**|(% style="width:692px" %)**Behaviour**
937 -|(% style="width:224px" %)Append|(% style="width:692px" %)Add this Registration to the registry
938 -|(% style="width:224px" %)Replace|(% style="width:692px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
939 -|(% style="width:224px" %)Delete|(% style="width:692px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
935 +|(% style="width:224px" %)**Action Attribute Value**|(% style="width:1457px" %)**Behaviour**
936 +|(% style="width:224px" %)Append|(% style="width:1457px" %)Add this Registration to the registry
937 +|(% style="width:224px" %)Replace|(% style="width:1457px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest
938 +|(% style="width:224px" %)Delete|(% style="width:1457px" %)Delete the existing Registration identified by the id in the Registration of the SubmitRegistrationRequest
940 940  )))
941 941  
942 942  [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]]
... ... @@ -1034,40 +1034,48 @@
1034 1034  Examples of wildcarded identifier components for an identified object type of Codelist are shown below:
1035 1035  
1036 1036  AgencyID = *
1036 +
1037 1037  Id = *
1038 +
1038 1038  Version = *
1039 1039  
1040 1040  This subscribes to all Codelists of all versions for all agencies.
1041 1041  
1042 1042  AgencyID = AGENCY1
1044 +
1043 1043  Id = CODELIST1
1046 +
1044 1044  Version = *
1045 1045  
1046 1046  This subscribes to all versions of Codelist CODELIST1 maintained by the agency AGENCY1.
1047 1047  
1048 -> AgencyID = AGENCY1
1049 -> Id = *
1050 -> Version = *
1051 +AgencyID = AGENCY1
1051 1051  
1053 +Id = *
1054 +
1055 +Version = *
1056 +
1052 1052  This subscribes to all versions of all Codelist objects maintained by the agency AGENCY1.
1053 1053  
1054 -> AgencyID = *
1055 -> Id = CODELIST1
1056 -> Version = *
1059 +AgencyID = *
1057 1057  
1061 +Id = CODELIST1
1062 +
1063 +Version = *
1064 +
1058 1058  This subscribes to all versions of Codelist CODELIST1 maintained by any agency.
1059 1059  
1060 1060  Note that if the subscription is to the latest stable version then this can be achieved by the + character, i.e.:
1061 1061  
1062 -> Version = +
1069 +Version = +
1063 1063  
1064 1064  A subscription to the latest version (whether stable, draft or non-versioned) can be achieved by the ~~ character, i.e.:
1065 1065  
1066 -> Version = ~~
1073 +Version = ~~
1067 1067  
1068 1068  A subscription to the latest stable version within major version 2 starting with version 2.3.1 can be achieved by adding the + character after the minor version number, i.e.:
1069 1069  
1070 -> Version = 2.3+.1
1077 +Version = 2.3+.1
1071 1071  
1072 1072  The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”.
1073 1073