Changes for page Part I. Message Namespace

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

From version 3.5
edited by Helena
on 2025/06/23 17:05
Change comment: There is no comment for this version
To version 3.16
edited by Helena
on 2025/06/23 17:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -274,8 +274,8 @@
274 274  
275 275  Derivation:
276 276  
277 -//MessageType// (restriction)
278 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
277 +* //MessageType// (restriction)
278 +** GenericMetadataType
279 279  
280 280  Content:
281 281  
... ... @@ -283,17 +283,18 @@
283 283  
284 284  Element Documentation:
285 285  
286 -|**Name**|**Type**|**Documentation**
287 -|Header|GenericMetadataHeade rType|
288 -|MetadataSet|rep:MetadataSetType|
289 -|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.
290 290  
291 291  **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.
292 292  
293 293  Derivation:
294 294  
295 -//MessageType// (restriction)
296 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
296 +* //MessageType// (restriction)
297 +** StructureSpecificMetadataType
297 297  
298 298  Content:
299 299  
... ... @@ -301,17 +301,18 @@
301 301  
302 302  Element Documentation:
303 303  
304 -|**Name**|**Type**|**Documentation**
305 -|Header|StructureSpecificMet adataHeaderType|
306 -|MetadataSet|//msd:MetadataSetType//|
307 -|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.
308 308  
309 309  **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
310 310  
311 311  Derivation:
312 312  
313 -//MessageType// (restriction)
314 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
315 +* //MessageType// (restriction)
316 +** RegistryInterfaceType
315 315  
316 316  Content:
317 317  
... ... @@ -319,83 +319,84 @@
319 319  
320 320  Element Documentation:
321 321  
322 -|**Name**|**Type**|**Documentation**
323 -|Header|BasicHeaderType|
324 -|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.
325 -|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.
326 -|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.
327 -|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.
328 -|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.
329 -|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.
330 -|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.
331 -|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.
332 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
333 -|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.
334 -|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.
335 -|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.
336 336  
337 337  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
338 338  
339 339  Derivation:
340 340  
341 -//MessageType// (restriction)
342 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
343 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
344 +* //MessageType// (restriction)
345 +** RegistryInterfaceType (restriction)
346 +*** SubmitRegistrationsRequestType
344 344  
345 345  Content:
346 346  
347 -Header, SubmitRegistrationsRequest
350 +* Header, SubmitRegistrationsRequest
351 +* Element Documentation:
348 348  
349 -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.
350 350  
351 -|**Name**|**Type**|**Documentation**
352 -|Header|BasicHeaderType|
353 -|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.
354 -
355 355  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
356 356  
357 357  Derivation:
358 358  
359 -//MessageType// (restriction)
360 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
361 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
362 +* //MessageType// (restriction)
363 +** RegistryInterfaceType (restriction)
364 +*** SubmitRegistrationsResponseType
362 362  
363 363  Content:
364 364  
365 -Header, SubmitRegistrationsResponse, ftr:Footer?
368 +* Header, SubmitRegistrationsResponse, ftr:Footer?
369 +* Element Documentation:
366 366  
367 -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.
368 368  
369 -|**Name**|**Type**|**Documentation**
370 -|Header|BasicHeaderType|
371 -|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.
372 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
373 -
374 374  **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
375 375  
376 376  Derivation:
377 377  
378 -//MessageType// (restriction)
379 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
380 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
381 +* //MessageType// (restriction)
382 +** RegistryInterfaceType (restriction)
383 +*** QueryRegistrationRequestType
381 381  
382 382  Content:
383 383  
384 -Header, QueryRegistrationRequest
387 +* Header, QueryRegistrationRequest
388 +* Element Documentation:
385 385  
386 -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.
387 387  
388 -|**Name**|**Type**|**Documentation**
389 -|Header|BasicHeaderType|
390 -|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.
391 -
392 392  **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
393 393  
394 394  Derivation:
395 395  
396 -//MessageType// (restriction)
397 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
398 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
399 +* //MessageType// (restriction)
400 +** RegistryInterfaceType (restriction)
401 +*** QueryRegistrationResponseType
399 399  
400 400  Content:
401 401  
... ... @@ -403,18 +403,19 @@
403 403  
404 404  Element Documentation:
405 405  
406 -|**Name**|**Type**|**Documentation**
407 -|Header|BasicHeaderType|
408 -|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.
409 -|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.
410 410  
411 411  **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
412 412  
413 413  Derivation:
414 414  
415 -//MessageType// (restriction)
416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
417 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
419 +* //MessageType// (restriction)
420 +** RegistryInterfaceType (restriction)
421 +*** SubmitStructureRequestType
418 418  
419 419  Content:
420 420  
... ... @@ -422,145 +422,146 @@
422 422  
423 423  Element Documentation:
424 424  
425 -|**Name**|**Type**|**Documentation**
426 -|Header|BasicHeaderType|
427 -|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.
428 428  
429 429  **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
430 430  
431 431  Derivation:
432 432  
433 -//MessageType// (restriction)
434 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
435 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
438 +* //MessageType// (restriction)
439 +** RegistryInterfaceType (restriction)
440 +*** SubmitStructureResponseType
436 436  
437 437  Content:
438 438  
439 -Header, SubmitStructureResponse, ftr:Footer?
444 +* Header, SubmitStructureResponse, ftr:Footer?
445 +* Element Documentation:
440 440  
441 -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.
442 442  
443 -|**Name**|**Type**|**Documentation**
444 -|Header|BasicHeaderType|
445 -|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.
446 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
447 -
448 448  **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
449 449  
450 450  Derivation:
451 451  
452 -//MessageType// (restriction)
453 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
454 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
457 +* //MessageType// (restriction)
458 +** RegistryInterfaceType (restriction)
459 +*** SubmitSubscriptionsRequestType
455 455  
456 456  Content:
457 457  
458 -Header, SubmitSubscriptionsRequest
463 +* Header, SubmitSubscriptionsRequest
464 +* Element Documentation:
459 459  
460 -Element Documentation:
466 +(% style="width:832.294px" %)
467 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
468 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
469 +|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
461 461  
462 -|**Name**|**Type**|**Documentation**
463 -|Header|BasicHeaderType|
464 -|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.
465 -
466 466  **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
467 467  
468 468  Derivation:
469 469  
470 -//MessageType// (restriction)
471 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
472 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
475 +* //MessageType// (restriction)
476 +** RegistryInterfaceType (restriction)
477 +*** SubmitSubscriptionsResponseType
473 473  
474 474  Content:
475 475  
476 -Header, SubmitSubscriptionsResponse, ftr:Footer?
481 +* Header, SubmitSubscriptionsResponse, ftr:Footer?
482 +* Element Documentation:
477 477  
478 -Element Documentation:
484 +(% style="width:843.294px" %)
485 +|**Name**|**Type**|(% style="width:362px" %)**Documentation**
486 +|Header|BasicHeaderType|(% style="width:362px" %)
487 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)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.
488 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
479 479  
480 -|**Name**|**Type**|**Documentation**
481 -|Header|BasicHeaderType|
482 -|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.
483 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
484 -
485 485  **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
486 486  
487 487  Derivation:
488 488  
489 -//MessageType// (restriction)
490 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
491 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
494 +* //MessageType// (restriction)
495 +** RegistryInterfaceType (restriction)
496 +*** QuerySubscriptionRequestType
492 492  
493 493  Content:
494 494  
495 -Header, QuerySubscriptionRequest
500 +* Header, QuerySubscriptionRequest
501 +* Element Documentation:
496 496  
497 -Element Documentation:
503 +(% style="width:839.294px" %)
504 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
505 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
506 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
498 498  
499 -|**Name**|**Type**|**Documentation**
500 -|Header|BasicHeaderType|
501 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
502 -
503 503  **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
504 504  
505 505  Derivation:
506 506  
507 -//MessageType// (restriction)
508 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
509 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
512 +* //MessageType// (restriction)
513 +** RegistryInterfaceType (restriction)
514 +*** QuerySubscriptionResponseType
510 510  
511 511  Content:
512 512  
513 -Header, QuerySubscriptionResponse, ftr:Footer?
518 +* Header, QuerySubscriptionResponse, ftr:Footer?
519 +* Element Documentation:
514 514  
515 -Element Documentation:
521 +(% style="width:912.294px" %)
522 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
523 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
524 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)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.
525 +|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
516 516  
517 -|**Name**|**Type**|**Documentation**
518 -|Header|BasicHeaderType|
519 -|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.
520 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
521 -
522 522  **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
523 523  
524 524  Derivation:
525 525  
526 -//MessageType// (restriction)
527 - RegistryInterfaceType (restriction)
528 - NotifyRegistryEventType
531 +* //MessageType// (restriction)
532 +** RegistryInterfaceType (restriction)
533 +*** NotifyRegistryEventType
529 529  
530 530  Content:
531 531  
532 -Header, NotifyRegistryEvent
537 +* Header, NotifyRegistryEvent
538 +* Element Documentation:
533 533  
534 -Element Documentation:
540 +(% style="width:836.294px" %)
541 +|**Name**|**Type**|(% style="width:473px" %)**Documentation**
542 +|Header|BasicHeaderType|(% style="width:473px" %)
543 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)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.
535 535  
536 -|**Name**|**Type**|**Documentation**
537 -|Header|BasicHeaderType|
538 -|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.
539 -
540 540  **DataQueryType: **DataQueryType defines the structure of a data query message.
541 541  
542 542  Derivation:
543 543  
544 -//MessageType// (restriction)
545 - DataQueryType
549 +* //MessageType// (restriction)
550 +** DataQueryType
546 546  
547 547  Content:
548 548  
549 -Header, Query
554 +* Header, Query
555 +* Element Documentation:
550 550  
551 -Element Documentation:
557 +(% style="width:839.294px" %)
558 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
559 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %)
560 +|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %)
552 552  
553 -|**Name**|**Type**|**Documentation**
554 -|Header|BasicHeaderType|
555 -|Query|qry:DataQueryType|
556 -
557 557  **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
558 558  
559 559  Derivation:
560 560  
561 -//MessageType// (restriction)
562 - DataQueryType (restriction)
563 - GenericDataQueryType
566 +* //MessageType// (restriction)
567 +** DataQueryType (restriction)
568 +*** GenericDataQueryType
564 564  
565 565  Content:
566 566