Changes for page Part I. Message Namespace

Last modified by Artur on 2025/09/10 11:19

From version 3.4
edited by Helena
on 2025/06/23 17:05
Change comment: There is no comment for this version
To version 3.13
edited by Helena
on 2025/06/23 17:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -264,17 +264,18 @@
264 264  
265 265  Element Documentation:
266 266  
267 -|**Name**|**Type**|**Documentation**
268 -|Header|StructureSpecificTim eSeriesDataHeaderTyp e|
269 -|DataSet|//dsd: TimeSeriesDataSetTyp e//|
270 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
267 +(% style="width:839.294px" %)
268 +|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
269 +|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
270 +|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
271 +|ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
271 271  
272 272  **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
273 273  
274 274  Derivation:
275 275  
276 -//MessageType// (restriction)
277 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
277 +* //MessageType// (restriction)
278 +** GenericMetadataType
278 278  
279 279  Content:
280 280  
... ... @@ -282,17 +282,18 @@
282 282  
283 283  Element Documentation:
284 284  
285 -|**Name**|**Type**|**Documentation**
286 -|Header|GenericMetadataHeade rType|
287 -|MetadataSet|rep:MetadataSetType|
288 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
286 +(% style="width:836.294px" %)
287 +|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
288 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %)
289 +|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
290 +|(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
289 289  
290 290  **StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
291 291  
292 292  Derivation:
293 293  
294 -//MessageType// (restriction)
295 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
296 +* //MessageType// (restriction)
297 +** StructureSpecificMetadataType
296 296  
297 297  Content:
298 298  
... ... @@ -300,17 +300,18 @@
300 300  
301 301  Element Documentation:
302 302  
303 -|**Name**|**Type**|**Documentation**
304 -|Header|StructureSpecificMet adataHeaderType|
305 -|MetadataSet|//msd:MetadataSetType//|
306 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
305 +(% style="width:841.294px" %)
306 +|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
307 +|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
308 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
309 +|(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
307 307  
308 308  **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
309 309  
310 310  Derivation:
311 311  
312 -//MessageType// (restriction)
313 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
315 +* //MessageType// (restriction)
316 +** RegistryInterfaceType
314 314  
315 315  Content:
316 316  
... ... @@ -318,83 +318,84 @@
318 318  
319 319  Element Documentation:
320 320  
321 -|**Name**|**Type**|**Documentation**
322 -|Header|BasicHeaderType|
323 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
324 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
325 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
326 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
327 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
328 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
329 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
330 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
331 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
332 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
333 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
334 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
324 +(% style="width:903.294px" %)
325 +|**Name**|**Type**|(% style="width:441px" %)**Documentation**
326 +|Header|BasicHeaderType|(% style="width:441px" %)
327 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
328 +|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
329 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
330 +|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
331 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
332 +|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
333 +|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
334 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
335 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
336 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
337 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
338 +|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
335 335  
336 336  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
337 337  
338 338  Derivation:
339 339  
340 -//MessageType// (restriction)
341 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
342 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
344 +* //MessageType// (restriction)
345 +** RegistryInterfaceType (restriction)
346 +*** SubmitRegistrationsRequestType
343 343  
344 344  Content:
345 345  
346 -Header, SubmitRegistrationsRequest
350 +* Header, SubmitRegistrationsRequest
351 +* Element Documentation:
347 347  
348 -Element Documentation:
353 +(% style="width:844.294px" %)
354 +|**Name**|**Type**|(% style="width:377px" %)**Documentation**
355 +|Header|BasicHeaderType|(% style="width:377px" %)
356 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
349 349  
350 -|**Name**|**Type**|**Documentation**
351 -|Header|BasicHeaderType|
352 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
353 -
354 354  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
355 355  
356 356  Derivation:
357 357  
358 -//MessageType// (restriction)
359 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
360 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
362 +* //MessageType// (restriction)
363 +** RegistryInterfaceType (restriction)
364 +*** SubmitRegistrationsResponseType
361 361  
362 362  Content:
363 363  
364 -Header, SubmitRegistrationsResponse, ftr:Footer?
368 +* Header, SubmitRegistrationsResponse, ftr:Footer?
369 +* Element Documentation:
365 365  
366 -Element Documentation:
371 +(% style="width:847.294px" %)
372 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
373 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %)
374 +|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
375 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
367 367  
368 -|**Name**|**Type**|**Documentation**
369 -|Header|BasicHeaderType|
370 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
371 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
372 -
373 373  **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
374 374  
375 375  Derivation:
376 376  
377 -//MessageType// (restriction)
378 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
379 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
381 +* //MessageType// (restriction)
382 +** RegistryInterfaceType (restriction)
383 +*** QueryRegistrationRequestType
380 380  
381 381  Content:
382 382  
383 -Header, QueryRegistrationRequest
387 +* Header, QueryRegistrationRequest
388 +* Element Documentation:
384 384  
385 -Element Documentation:
390 +(% style="width:847.294px" %)
391 +|**Name**|**Type**|(% style="width:397px" %)**Documentation**
392 +|Header|BasicHeaderType|(% style="width:397px" %)
393 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
386 386  
387 -|**Name**|**Type**|**Documentation**
388 -|Header|BasicHeaderType|
389 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
390 -
391 391  **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
392 392  
393 393  Derivation:
394 394  
395 -//MessageType// (restriction)
396 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
397 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
399 +* //MessageType// (restriction)
400 +** RegistryInterfaceType (restriction)
401 +*** QueryRegistrationResponseType
398 398  
399 399  Content:
400 400  
... ... @@ -402,18 +402,19 @@
402 402  
403 403  Element Documentation:
404 404  
405 -|**Name**|**Type**|**Documentation**
406 -|Header|BasicHeaderType|
407 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
408 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
409 +(% style="width:856.294px" %)
410 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation**
411 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %)
412 +|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
413 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
409 409  
410 410  **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
411 411  
412 412  Derivation:
413 413  
414 -//MessageType// (restriction)
415 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
419 +* //MessageType// (restriction)
420 +** RegistryInterfaceType (restriction)
421 +*** SubmitStructureRequestType
417 417  
418 418  Content:
419 419  
... ... @@ -421,43 +421,43 @@
421 421  
422 422  Element Documentation:
423 423  
424 -|**Name**|**Type**|**Documentation**
425 -|Header|BasicHeaderType|
426 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
429 +(% style="width:870.294px" %)
430 +|**Name**|**Type**|(% style="width:453px" %)**Documentation**
431 +|Header|BasicHeaderType|(% style="width:453px" %)
432 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
427 427  
428 428  **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
429 429  
430 430  Derivation:
431 431  
432 -//MessageType// (restriction)
433 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
434 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
438 +* //MessageType// (restriction)
439 +** RegistryInterfaceType (restriction)
440 +*** SubmitStructureResponseType
435 435  
436 436  Content:
437 437  
438 -Header, SubmitStructureResponse, ftr:Footer?
444 +* Header, SubmitStructureResponse, ftr:Footer?
445 +* Element Documentation:
439 439  
440 -Element Documentation:
447 +(% style="width:835.294px" %)
448 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
449 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %)
450 +|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
451 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
441 441  
442 -|**Name**|**Type**|**Documentation**
443 -|Header|BasicHeaderType|
444 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
445 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
446 -
447 447  **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
448 448  
449 449  Derivation:
450 450  
451 -//MessageType// (restriction)
452 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
453 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
457 +* //MessageType// (restriction)
458 +** RegistryInterfaceType (restriction)
459 +*** SubmitSubscriptionsRequestType
454 454  
455 455  Content:
456 456  
457 -Header, SubmitSubscriptionsRequest
463 +* Header, SubmitSubscriptionsRequest
464 +* Element Documentation:
458 458  
459 -Element Documentation:
460 -
461 461  |**Name**|**Type**|**Documentation**
462 462  |Header|BasicHeaderType|
463 463  |SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.