Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -SDMX 2.1 Standards. Section 5. Registry Specification :Logical Interfaces1 +SDMX 2.1 Standards. Section 5. Registry Specification – Logical Interfaces - Content
-
... ... @@ -16,19 +16,19 @@ 16 16 17 17 1. **Problem** 18 18 19 -Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the [[Provision Agreement>>doc:sdmx:Glossary.Provisionagreement.WebHome]] as it was identified in[[version>>doc:sdmx:Glossary.Version.WebHome]]2.0, and not as it is identified in[[version>>doc:sdmx:Glossary.Version.WebHome]]2.1.19 +Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Provision Agreement as it was identified in version 2.0, and not as it is identified in version 2.1. 20 20 21 21 **Rectification** 22 22 23 - [[Provision Agreement>>doc:sdmx:Glossary.Provisionagreement.WebHome]]is a[[Maintainable Artefact>>doc:sdmx:Glossary.Maintainableartefact.WebHome]]at [[version>>doc:sdmx:Glossary.Version.WebHome]]2.1 and so the relationship is shown directly to the[[Provision Agreement>>doc:sdmx:Glossary.Provisionagreement.WebHome]]class and not indirectly to the[[Provision Agreement>>doc:sdmx:Glossary.Provisionagreement.WebHome]]via a ProvisionAgreementRef class.23 +Provision Agreement is a Maintainable Artefact at version 2.1 and so the relationship is shown directly to the Provision Agreement class and not indirectly to the Provision Agreement via a ProvisionAgreementRef class. 24 24 25 25 **~1. Problem** 26 26 27 -Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Registration class without the indexAttributes [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].27 +Figure 17 - Logical Class Diagram of Registration of Data and Metadata – shows the Registration class without the indexAttributes attribute. 28 28 29 29 **Rectification** 30 30 31 -The [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]indexAttribute[[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]is added to the Registration class and a description is of its purpose is given in the table at line 916.31 +The attribute indexAttribute attribute is added to the Registration class and a description is of its purpose is given in the table at line 916. 32 32 33 33 **2. Problem** 34 34 ... ... @@ -36,11 +36,11 @@ 36 36 37 37 The reference to AGENCY_SCHEME is changed to AGENCIES. 38 38 39 -**Adoption of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validationand transformationlanguage.WebHome]] in2020**39 +**Adoption of the Validation and Transformation Language in 2020** 40 40 41 -The [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]specifications dated July 2011 envisaged the adoption of a language aimed at defining algorithms for the derivation of the data and presented a basic framework requiring however further elaboration for its actual use.41 +The SDMX specifications dated July 2011 envisaged the adoption of a language aimed at defining algorithms for the derivation of the data and presented a basic framework requiring however further elaboration for its actual use. 42 42 43 -Following the adoption of the [[Validation and Transformation Language>>doc:sdmx:Glossary.Validationand transformation language.WebHome]]([[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]])[[version>>doc:sdmx:Glossary.Version.WebHome]]2.0 and its application to[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]2.1, this section of the[[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]specifications has been integrated by introducing the[[VTL>>doc:sdmx:Glossary.Validationand transformation language.WebHome]]package,[[maintainable artefacts>>doc:sdmx:Glossary.Maintainable artefact.WebHome]],[[nameable artefacts>>doc:sdmx:Glossary.Nameableartefact.WebHome]]to the sections 5.2.3, 6.2.2, 6.2.3, 6.2.4 and 7.1.1.43 +Following the adoption of the Validation and Transformation Language (VTL) version 2.0 and its application to SDMX 2.1, this section of the SDMX specifications has been integrated by introducing the VTL package, maintainable artefacts, nameable artefacts to the sections 5.2.3, 6.2.2, 6.2.3, 6.2.4 and 7.1.1. 44 44 45 45 = 1 Introduction = 46 46 ... ... @@ -1154,11 +1154,11 @@ 1154 1154 1155 1155 The Registration has an action attribute which takes one of the following values: 1156 1156 1157 -(% style="width: 798.294px" %)1158 -|(% style="width:212px" %)**Action Attribute Value**|(% style="width:5 82px" %)**Behaviour**1159 -|(% style="width:212px" %)Append|(% style="width:5 82px" %)Add this Registration to the registry1160 -|(% style="width:212px" %)Replace|(% style="width:5 82px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request1161 -|(% style="width:212px" %)Delete|(% style="width:5 82px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request1157 +(% style="width:970.294px" %) 1158 +|(% style="width:212px" %)**Action Attribute Value**|(% style="width:756px" %)**Behaviour** 1159 +|(% style="width:212px" %)Append|(% style="width:756px" %)Add this Registration to the registry 1160 +|(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request 1161 +|(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request 1162 1162 1163 1163 [[image:1747829290890-122.png]] 1164 1164 ... ... @@ -1176,17 +1176,16 @@ 1176 1176 1177 1177 Information in the data or metadata set is extracted and placed in one or more Content Constraints (see the Constraints model in the SDMX Information Model – Section 2 of the SDMX Standards). The information to be extracted is indicated by the Boolean values set on the Provision Agreement as shown in the table below. 1178 1178 1179 -(% style="width:860.294px" %) 1180 -|(% style="width:185px" %)**Indexing Required**|(% style="width:672px" %)**Registration Process Activity** 1181 -|(% style="width:185px" %)indexTimeSeries|(% style="width:672px" %)Extract all the series keys and create a KeySet(s) Constraint. 1182 -|(% style="width:185px" %)indexDataSet|(% style="width:672px" %)((( 1179 +|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity** 1180 +|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint. 1181 +|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)((( 1183 1183 Extract all the codes and other content of the Key value of the Series Key in a Data Set and create one or more Cube Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value. 1184 1184 ))) 1185 -|(% style="width:185px" %)indexReportingPeriod|(% style="width:6 72px" %)(((1184 +|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)((( 1186 1186 This applies only to a registered dataset. 1187 1187 Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint. 1188 1188 ))) 1189 -|(% style="width:185px" %)indexAttributes|(% style="width:6 72px" %)(((1188 +|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)((( 1190 1190 **Data Set** 1191 1191 Extract the content of the Attribute Values in a Data Set and create one or more Cube Regions containing Member Selections of Data Attribute Components of the Constraints model in the SDMXIM, and the associated Selection Value 1192 1192 **Metadata Set** ... ... @@ -1232,12 +1232,11 @@ 1232 1232 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. 1233 1233 1. A selector which specifies which type of events are of interest. The set of event types is: 1234 1234 1235 -(% style="width:1031.29px" %) 1236 -|(% style="width:319px" %)**Event Type**|(% style="width:678px" %)**Comment** 1237 -|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:678px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository. 1238 -|(% style="width:319px" %)DATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database. 1239 -|(% style="width:319px" %)METADATA_REGISTRATION_EVENTS|(% style="width:678px" %)Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database. 1240 -|(% style="width:319px" %)ALL_EVENTS|(% style="width:678px" %)All events of the specified EventType 1234 +|(% style="width:319px" %)**Event Type**|(% style="width:1553px" %)**Comment** 1235 +|(% style="width:319px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1553px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository. 1236 +|(% 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. 1237 +|(% 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. 1238 +|(% style="width:319px" %)ALL_EVENTS|(% style="width:1553px" %)All events of the specified EventType 1241 1241 1242 1242 === 7.5.3 Wildcard Facility === 1243 1243 ... ... @@ -1291,13 +1291,14 @@ 1291 1291 1292 1292 Whenever a dataset or metadata-set is registered a registration event is created. A subscription may be observing all data or metadata registrations, or it may focus on specific registrations as shown in the table below: 1293 1293 1294 -(% style="width:974.294px" %) 1295 -|(% style="width:295px" %)**Selector**|(% style="width:677px" %)**Comment** 1296 -|(% style="width:295px" %)DataProvider|(% style="width:677px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification. 1297 -|(% style="width:295px" %)ProvisionAgreement|(% style="width:677px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification. 1298 -|(% style="width:295px" %)Dataflow (&Metadataflow)|(% style="width:677px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1299 -|(% style="width:295px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will activate the notification. 1300 -|(% style="width:295px" %)Category|(% style="width:677px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1292 +|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment** 1293 +|(% style="width:405px" %)DataProvider|(% style="width:1467px" %)Any datasets or metadata sets registered by the specified data provider will activate the notification. 1294 +|(% style="width:405px" %)ProvisionAgreement|(% style="width:1467px" %)Any datasets or metadata sets registered for the provision agreement will activate the notification. 1295 +|(% style="width:405px" %)Dataflow (&Metadataflow)|(% style="width:1467px" %)Any datasets or metadata sets registered for the specified dataflow (or metadataflow) will activate the notification. 1296 +|(% style="width:405px" %)DataStructureDefinition & MetadataStructureDefinition|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows (or metadataflows) that are based on the specified Data Structure Definition will 1297 +|(% style="width:405px" %)**Selector**|(% style="width:1467px" %)**Comment** 1298 +|(% style="width:405px" %) |(% style="width:1467px" %)activate the notification. 1299 +|(% style="width:405px" %)Category|(% style="width:1467px" %)Any datasets or metadata sets registered for those dataflows, metadataflows, provision agreements that are categorised by the category. 1301 1301 1302 1302 The event will also capture the semantic of the registration: deletion or replacement of an existing registration or a new registration. 1303 1303
- SKMS.Methodology.Code.MethodologyClass[0]
-
- SUZ.Methodology.Code.MethodologyClass[0]
-