Last modified by Artur on 2025/09/30 13:28
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Tags
-
... ... @@ -1,0 +1,1 @@ 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,6 +385,8 @@ 385 385 386 386 An example of this is shown in the XML snippet below: 387 387 388 +[[image:1749590035576-196.png]] 389 + 388 388 **Figure 8: Example Showing Use of Agency Identifiers** 389 389 390 390 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. ... ... @@ -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>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]:VLIST(1.0.0)715 +|(% style="width:297px" %)//ValueList//|(% style="width:647px" %)(% style="color:#000000" %)valuelistAgencyId:valuelistId(version)|(% style="width:737px" %)SDMX: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 ... ... @@ -932,10 +932,11 @@ 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: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 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 939 939 ))) 940 940 941 941 [[image:SDMX 3.1 Section 5_en_90b3c64a.jpg||height="434" width="579"]] ... ... @@ -1013,7 +1013,6 @@ 1013 1013 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]]. 1014 1014 1. A selector which specifies which type of events are of interest. The set of event types is: 1015 1015 1016 -((( 1017 1017 (% style="width:1061.83px" %) 1018 1018 |**Event Type**|(% style="width:660px" %)**Comment** 1019 1019 |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. ... ... @@ -1020,7 +1020,6 @@ 1020 1020 |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. 1021 1021 |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. 1022 1022 |ALL_EVENTS|(% style="width:660px" %)All events of the specified EventType 1023 -))) 1024 1024 1025 1025 === 7.5.3 Wildcard Facility === 1026 1026 ... ... @@ -1032,49 +1032,41 @@ 1032 1032 1033 1033 Examples of wildcarded identifier components for an identified object type of Codelist are shown below: 1034 1034 1035 -AgencyID = * 1036 +>(% style="font-size:18px" %) AgencyID = * 1037 +>(% style="font-size:18px" %) Id = * 1038 +>(% style="font-size:18px" %) Version = * 1036 1036 1037 -Id = * 1038 - 1039 -Version = * 1040 - 1041 1041 This subscribes to all Codelists of all versions for all agencies. 1042 1042 1043 -AgencyID = AGENCY1 1042 +> (% style="font-size:18px" %)AgencyID = AGENCY1 1043 +>(% style="font-size:18px" %) Id = CODELIST1 1044 +>(% style="font-size:18px" %) Version = * 1044 1044 1045 -Id = CODELIST1 1046 - 1047 -Version = * 1048 - 1049 1049 This subscribes to all versions of Codelist CODELIST1 maintained by the agency AGENCY1. 1050 1050 1051 -AgencyID = AGENCY1 1048 +> (% style="font-size:18px" %)AgencyID = AGENCY1 1049 +>(% style="font-size:18px" %) Id = * 1050 +>(% style="font-size:18px" %) Version = * 1052 1052 1053 -Id = * 1054 - 1055 -Version = * 1056 - 1057 1057 This subscribes to all versions of all Codelist objects maintained by the agency AGENCY1. 1058 1058 1059 -AgencyID = * 1054 +> (% style="font-size:18px" %)AgencyID = * 1055 +>(% style="font-size:18px" %) Id = CODELIST1 1056 +>(% style="font-size:18px" %) Version = * 1060 1060 1061 -Id = CODELIST1 1062 - 1063 -Version = * 1064 - 1065 1065 This subscribes to all versions of Codelist CODELIST1 maintained by any agency. 1066 1066 1067 1067 Note that if the subscription is to the latest stable version then this can be achieved by the + character, i.e.: 1068 1068 1069 -Version = + 1062 +>(% style="font-size:18px" %) Version = + 1070 1070 1071 1071 A subscription to the latest version (whether stable, draft or non-versioned) can be achieved by the ~~ character, i.e.: 1072 1072 1073 -Version = ~~ 1066 +> (% style="font-size:18px" %)Version = ~~ 1074 1074 1075 1075 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.: 1076 1076 1077 -Version = 2.3+.1 1070 +>(% style="font-size:18px" %) Version = 2.3+.1 1078 1078 1079 1079 The complete SDMX versioning syntax can be found in the SDMX Standards Section 6 “Technical Notes”, paragraph “4.3 Versioning”. 1080 1080
- 1749590035576-196.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.helena - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.8 KB - Content
- SUZ.Methodology.Code.MethodologyClass[0]
-