Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 2.14
edited by Helena
on 2025/05/21 15:07
Change comment: There is no comment for this version
To version 2.17
edited by Helena
on 2025/05/21 15:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1194,6 +1194,8 @@
1194 1194  |(% style="width:212px" %)Replace|(% style="width:756px" %)Replace the existing Registration with identified by the id in the Registration of the Submit Registration Request
1195 1195  |(% style="width:212px" %)Delete|(% style="width:756px" %)Delete the existing Registration identified by the id in the Registration of the Submit Registration Request
1196 1196  
1197 +[[image:1747829290890-122.png]]
1198 +
1197 1197  **Figure 17: Logical Class Diagram of Registration of Data and Metadata**
1198 1198  
1199 1199  The Query Datasource is an abstract class that represents a data source which can understand an SDMX-ML query (SOAPDatasource) or RESTful query
... ... @@ -1208,25 +1208,19 @@
1208 1208  
1209 1209  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.
1210 1210  
1211 -|**Indexing Required**|**Registration Process Activity**
1212 -|indexTimeSeries|Extract all the series keys and create a KeySet(s) Constraint.
1213 -|indexDataSet|(((
1214 -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
1215 -
1216 -Regions containing Member Selections of Dimension Components of the Constraints model in the SDMX-IM, and the associated Selection Value.
1213 +|(% style="width:185px" %)**Indexing Required**|(% style="width:1686px" %)**Registration Process Activity**
1214 +|(% style="width:185px" %)indexTimeSeries|(% style="width:1686px" %)Extract all the series keys and create a KeySet(s) Constraint.
1215 +|(% style="width:185px" %)indexDataSet|(% style="width:1686px" %)(((
1216 +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.
1217 1217  )))
1218 -|indexReportingPeriod|(((
1218 +|(% style="width:185px" %)indexReportingPeriod|(% style="width:1686px" %)(((
1219 1219  This applies only to a registered dataset.
1220 -
1221 1221  Extract the Reporting Begin and Reporting End from the Header of the Message containing the data set, and create a Reference Period constraint.
1222 1222  )))
1223 -|indexAttributes|(((
1222 +|(% style="width:185px" %)indexAttributes|(% style="width:1686px" %)(((
1224 1224  **Data Set**
1225 -
1226 1226  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
1227 -
1228 1228  **Metadata Set**
1229 -
1230 1230  Indicate the presence of a Reported Attribute by creating one or more Cube Regions containing Member Selections of Metadata Attribute Components of the Constraints model in the SDMX-IM. Note that the content is not stored in the Selection Value.
1231 1231  )))
1232 1232  
... ... @@ -1236,14 +1236,13 @@
1236 1236  
1237 1237  === 7.4.3 Registration Response ===
1238 1238  
1239 -After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to
1235 +After a registration request has been submitted to the registry, a response is returned to the submitter indicating success or failure. Given that a registration request can hold many Registrations, then there must be a registration status for each Registration. The Submit Registration class has a status field which is either set to “Success”, “Warning” or “Failure”.
1240 1240  
1241 -“Success”, “Warning” or “Failure”.
1242 -
1243 1243  If the registration has succeeded, a Registration will be returned - this holds the Registry-allocated Id of the newly registered Datasource plus a Datasource holding the URL to access the dataset, metadataset, or query service.
1244 1244  
1245 1245  The Registration Response returns set of registration status (one for each registration submitted) in terms of a Status Message (this is common to all Registry Responses) that indicates success or failure. In the event of registration failure, a set of Message Text are returned, giving the error messages that occurred during registration. It is entirely possible when registering a batch of datasets, that the response will contain some successful and some failed statuses. The logical model for the Registration Response is shown below:
1246 1246  
1241 +[[image:1747829477882-750.png]]
1247 1247  
1248 1248  **Figure 18: Logical class diagram showing the registration response**
1249 1249  
... ... @@ -1253,15 +1253,12 @@
1253 1253  
1254 1254  A user can submit a subscription in the registry that defines which events are of interest, and either an email and/or an HTTP address to which a notification of qualifying events will be delivered. The subscription will be identified in the registry by a URN which is returned to the user when the subscription is created. If the user wants to delete the subscription at a later point, the subscription URN is used as identification. Subscriptions have a validity period expressed as a date range (startDate, endDate) and the registry may delete any expired subscriptions, and will notify the subscriber on expiry.
1255 1255  
1256 -When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a
1251 +When a registry/repository artefact is modified, any subscriptions which are observing the object are activated, and either an email or HTTP POST is instigated to report details of the changes to the user specified in the subscription. This is called a “notification”.
1257 1257  
1258 -“notification”.
1253 +=== 7.5.1Subscription Logical Class Diagram ===
1259 1259  
1260 - 7.5.1Subscription Logical Class Diagram
1255 +[[image:1747829554603-150.png]]
1261 1261  
1262 -
1263 -[[image:1747824123028-257.png]]
1264 -
1265 1265  **Figure 19: Logical Class Diagram of the Subscription**
1266 1266  
1267 1267  === 7.5.2 Subscription Information ===
... ... @@ -1268,30 +1268,25 @@
1268 1268  
1269 1269  Regardless of the type of registry/repository events being observed, a subscription always contains:
1270 1270  
1271 -~1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
1263 +1. A set of URIs describing the end-points to which notifications must be sent if the subscription is activated. The URIs can be either mailto~: or http: protocol. In the former case an email notification is sent; in the latter an HTTP POST notification is sent.
1264 +1. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
1265 +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.
1266 +1. A selector which specifies which type of events are of interest. The set of event types is:
1272 1272  
1273 -2. A user-defined identifier which is returned in the response to the subscription request. This helps with asynchronous processing and is NOT stored in the Registry.
1268 +|(% style="width:327px" %)**Event Type**|(% style="width:1545px" %)**Comment**
1269 +|(% style="width:327px" %)STRUCTURAL_REPOSITORY_EVENTS|(% style="width:1545px" %)Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1270 +|(% 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.
1271 +|(% 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.
1272 +|(% style="width:327px" %)ALL_EVENTS|(% style="width:1545px" %)All events of the specified EventType
1274 1274  
1275 -3. 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.
1276 -
1277 -4. A selector which specifies which type of events are of interest. The set of event types is:
1278 -
1279 -|**Event Type**|**Comment**
1280 -|STRUCTURAL_REPOSITORY_EVENTS|Life-cycle changes to Maintainable Artefacts in the structural metadata repository.
1281 -|DATA_REGISTRATION_EVENTS|Whenever a published dataset is registered. This can be either a SDMXML data file or an SDMX conformant database.
1282 -|METADATA_REGISTRATION_EVENTS|Whenever a published metadataset is registered. This can be either a SDMXML reference metadata file or an SDMX conformant database.
1283 -|ALL_EVENTS|All events of the specified EventType
1284 -
1285 1285  === 7.5.3 Wildcard Facility ===
1286 1286  
1287 1287  Subscription notification supports wildcarded identifier components URNs, which are identiiers which have some or all of their component parts replaced by the wildcard character `%`. Identifier components comprise:
1288 1288  
1289 - agencyID
1278 +* agencyID
1279 +* id
1280 +* version
1290 1290  
1291 - id
1292 -
1293 - version
1294 -
1295 1295  Examples of wildcarded identifier components for an identified object type of Codelist are shown below.
1296 1296  
1297 1297  AgencyID = %
1747829290890-122.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +41.4 KB
Content
1747829477882-750.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
1747829554603-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +99.1 KB
Content