Last modified by Artur on 2025/09/30 13:28
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Tags
-
... ... @@ -1,1 +1,0 @@ 1 -Agency scheme|Artefact|Attribute|Category|Category scheme|Code|Code list|Component|Concept scheme|Data consumer|Data consumer scheme|Data provider|Data provider scheme|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchy|Identifiable artefact|Item scheme|Maintainable artefact|Maintenance agency|Measure|Member selection|Metadata repository|Metadata set|Metadata structure definition|Metadataflow|Nameable artefact|Notification|Organisation unit scheme|Provision agreement|Reference metadata|Reference period|Representation|SDMX Information Model|SDMX Registry|SDMX-JSON|SDMX-ML|Series key|Statistical data and metadata exchange|Structural metadata|Subscription|Time period|Timeliness|Validation and transformation language|Versionable artefact|isExternalReference - Content
-
... ... @@ -385,8 +385,6 @@ 385 385 386 386 An example of this is shown in the XML snippet below: 387 387 388 -[[image:1749590035576-196.png]] 389 - 390 390 **Figure 8: Example Showing Use of Agency Identifiers** 391 391 392 392 Each of these [[maintenance agencies>>doc:sdmx:Glossary.Maintenance agency.WebHome]] has an identical [[Code list>>doc:sdmx:Glossary.Code list.WebHome]] with the Id CL_BOP. However, each is uniquely identified by means of the hierarchic agency structure. ... ... @@ -712,7 +712,7 @@ 712 712 )))|(% style="width:737px" %)BIS:PROCESS1(1.0.0).STEP1.TRANSITION1 713 713 |(% style="width:297px" %)UserDefinedOperator|(% style="width:647px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version) usserDefinedOperatorId|(% style="width:737px" %)ECB:OS_CALC(1.2.0).OS267 714 714 |(% style="width:297px" %)//UserDefinedOperatorScheme//|(% style="width:647px" %)(% style="color:#000000" %)userDefinedOperatorSchemeAgencyId userDefinedOperatorSchemeId(version)|(% style="width:737px" %)ECB:OS_CALC(1.2.0) 715 -|(% 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) 716 716 |(% style="width:297px" %)VtlCodelistMapping|(% style="width:647px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlCodelistMappingId|(% style="width:737px" %)ECB:CLIST_MP(2.0.0).ABZ 717 717 |(% style="width:297px" %)VtlConceptMapping|(% style="width:647px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlConceptMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).XYA 718 718 |(% style="width:297px" %)VtlDataflowMapping|(% style="width:647px" %)(% style="color:#000000" %)vtlMappingSchemeAgencyId vtlMappingSchemeId(version) vtlDataflowMappingId|(% style="width:737px" %)ECB:CLIST_MP(1.0.0).MOQ ... ... @@ -934,11 +934,10 @@ 934 934 The Registration has an action [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] which takes one of the following values: 935 935 936 936 ((( 937 -(% style="width:918.835px" %) 938 -|(% style="width:224px" %)**Action Attribute Value**|(% style="width:692px" %)**Behaviour** 939 -|(% style="width:224px" %)Append|(% style="width:692px" %)Add this Registration to the registry 940 -|(% style="width:224px" %)Replace|(% style="width:692px" %)Replace the existing Registration with identified by the id in the Registration of the SubmitRegistrationRequest 941 -|(% 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 942 942 ))) 943 943 944 944 [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]] ... ... @@ -1016,6 +1016,7 @@ 1016 1016 1. A validity period which defines both when the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] becomes active and expires. The subscriber may be sent a [[notification>>doc:sdmx:Glossary.Notification.WebHome]] on expiration of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]. 1017 1017 1. A selector which specifies which type of events are of interest. The set of event types is: 1018 1018 1016 +((( 1019 1019 (% style="width:1061.83px" %) 1020 1020 |**Event Type**|(% style="width:660px" %)**Comment** 1021 1021 |STRUCTURAL_REPOSITORY_EVENTS|(% style="width:660px" %)Life-cycle changes to [[Maintainable Artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]] in the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] repository. ... ... @@ -1022,6 +1022,7 @@ 1022 1022 |DATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published [[dataset>>doc:sdmx:Glossary.Data set.WebHome]] is registered. This can be either a SDMXML data file or an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant database. 1023 1023 |METADATA_REGISTRATION_EVENTS|(% style="width:660px" %)Whenever a published metadataset is registered. This can be either a SDMXML [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] file or an [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] conformant database. 1024 1024 |ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType 1023 +))) 1025 1025 1026 1026 === 7.5.3 Wildcard Facility === 1027 1027 ... ... @@ -1033,41 +1033,49 @@ 1033 1033 1034 1034 Examples of wildcarded identifier components for an identified object type of Codelist are shown below: 1035 1035 1036 ->(% style="font-size:18px" %) AgencyID = * 1037 ->(% style="font-size:18px" %) Id = * 1038 ->(% style="font-size:18px" %) Version = * 1035 +AgencyID = * 1039 1039 1037 +Id = * 1038 + 1039 +Version = * 1040 + 1040 1040 This subscribes to all Codelists of all versions for all agencies. 1041 1041 1042 -> (% style="font-size:18px" %)AgencyID = AGENCY1 1043 ->(% style="font-size:18px" %) Id = CODELIST1 1044 ->(% style="font-size:18px" %) Version = * 1043 +AgencyID = AGENCY1 1045 1045 1045 +Id = CODELIST1 1046 + 1047 +Version = * 1048 + 1046 1046 This subscribes to all versions of Codelist CODELIST1 maintained by the agency AGENCY1. 1047 1047 1048 -> (% style="font-size:18px" %)AgencyID = AGENCY1 1049 ->(% style="font-size:18px" %) Id = * 1050 ->(% style="font-size:18px" %) 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 -> (% style="font-size:18px" %)AgencyID = * 1055 ->(% style="font-size:18px" %) Id = CODELIST1 1056 ->(% style="font-size:18px" %) 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 - >(% style="font-size:18px" %)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 - > (% style="font-size:18px" %)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 - >(% style="font-size:18px" %)Version = 2.3+.11077 +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
- 1749590035576-196.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.8 KB - Content
- SUZ.Methodology.Code.MethodologyClass[0]
-