Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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="-"]]GenericMetadataType277 +* //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="-"]]StructureSpecificMetadataType296 +* //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="-"]]RegistryInterfaceType315 +* //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="-"]]SubmitRegistrationsRequestType344 +* //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="-"]]SubmitRegistrationsResponseType362 +* //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="-"]]QueryRegistrationRequestType381 +* //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="-"]]QueryRegistrationResponseType399 +* //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="-"]]SubmitStructureRequestType419 +* //MessageType// (restriction) 420 +** RegistryInterfaceType (restriction) 421 +*** SubmitStructureRequestType 417 417 418 418 Content: 419 419 ... ... @@ -421,499 +421,500 @@ 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="-"]]SubmitStructureResponseType438 +* //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="-"]]SubmitSubscriptionsRequestType457 +* //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: 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. 460 460 461 -|**Name**|**Type**|**Documentation** 462 -|Header|BasicHeaderType| 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. 464 - 465 465 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document. 466 466 467 467 Derivation: 468 468 469 -//MessageType// (restriction) 470 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)471 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsResponseType475 +* //MessageType// (restriction) 476 +** RegistryInterfaceType (restriction) 477 +*** SubmitSubscriptionsResponseType 472 472 473 473 Content: 474 474 475 -Header, SubmitSubscriptionsResponse, ftr:Footer? 481 +* Header, SubmitSubscriptionsResponse, ftr:Footer? 482 +* Element Documentation: 476 476 477 -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. 478 478 479 -|**Name**|**Type**|**Documentation** 480 -|Header|BasicHeaderType| 481 -|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. 482 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 483 - 484 484 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document. 485 485 486 486 Derivation: 487 487 488 -//MessageType// (restriction) 489 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)490 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionRequestType494 +* //MessageType// (restriction) 495 +** RegistryInterfaceType (restriction) 496 +*** QuerySubscriptionRequestType 491 491 492 492 Content: 493 493 494 -Header, QuerySubscriptionRequest 500 +* Header, QuerySubscriptionRequest 501 +* Element Documentation: 495 495 496 -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. 497 497 498 -|**Name**|**Type**|**Documentation** 499 -|Header|BasicHeaderType| 500 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 501 - 502 502 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document. 503 503 504 504 Derivation: 505 505 506 -//MessageType// (restriction) 507 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)508 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionResponseType512 +* //MessageType// (restriction) 513 +** RegistryInterfaceType (restriction) 514 +*** QuerySubscriptionResponseType 509 509 510 510 Content: 511 511 512 -Header, QuerySubscriptionResponse, ftr:Footer? 518 +* Header, QuerySubscriptionResponse, ftr:Footer? 519 +* Element Documentation: 513 513 514 -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. 515 515 516 -|**Name**|**Type**|**Documentation** 517 -|Header|BasicHeaderType| 518 -|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. 519 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 520 - 521 521 **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document. 522 522 523 523 Derivation: 524 524 525 -//MessageType// (restriction) 526 - 527 - 531 +* //MessageType// (restriction) 532 +** RegistryInterfaceType (restriction) 533 +*** NotifyRegistryEventType 528 528 529 529 Content: 530 530 531 -Header, NotifyRegistryEvent 537 +* Header, NotifyRegistryEvent 538 +* Element Documentation: 532 532 533 -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. 534 534 535 -|**Name**|**Type**|**Documentation** 536 -|Header|BasicHeaderType| 537 -|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. 538 - 539 539 **DataQueryType: **DataQueryType defines the structure of a data query message. 540 540 541 541 Derivation: 542 542 543 -//MessageType// (restriction) 544 - 549 +* //MessageType// (restriction) 550 +** DataQueryType 545 545 546 546 Content: 547 547 548 -Header, Query 554 +* Header, Query 555 +* Element Documentation: 549 549 550 -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" %) 551 551 552 -|**Name**|**Type**|**Documentation** 553 -|Header|BasicHeaderType| 554 -|Query|qry:DataQueryType| 555 - 556 556 **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message. 557 557 558 558 Derivation: 559 559 560 -//MessageType// (restriction) 561 - 562 - 566 +* //MessageType// (restriction) 567 +** DataQueryType (restriction) 568 +*** GenericDataQueryType 563 563 564 564 Content: 565 565 566 -Header, Query 572 +* Header, Query 573 +* Element Documentation: 567 567 568 -Element Documentation: 575 +(% style="width:833.294px" %) 576 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 577 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) 578 +|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %) 569 569 570 -|**Name**|**Type**|**Documentation** 571 -|Header|BasicHeaderType| 572 -|Query|qry: GenericDataQueryType| 573 - 574 574 **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message. 575 575 576 576 Derivation: 577 577 578 -//MessageType// (restriction) 579 - 580 - 581 - 584 +* //MessageType// (restriction) 585 +** DataQueryType (restriction) 586 +*** GenericDataQueryType (restriction) 587 +**** GenericTimeSeriesDataQueryType 582 582 583 583 Content: 584 584 585 -Header, Query 591 +* Header, Query 592 +* Element Documentation: 586 586 587 -Element Documentation: 594 +(% style="width:909.294px" %) 595 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 596 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) 597 +|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %) 588 588 589 -|**Name**|**Type**|**Documentation** 590 -|Header|BasicHeaderType| 591 -|Query|qry: GenericTimeSeriesDat aQueryType| 592 - 593 593 **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message. 594 594 595 595 Derivation: 596 596 597 -//MessageType// (restriction) 598 - 599 - 603 +* //MessageType// (restriction) 604 +** DataQueryType (restriction) 605 +*** StructureSpecificTimeSeriesDataQueryType 600 600 601 601 Content: 602 602 603 -Header, Query 609 +* Header, Query 610 +* Element Documentation: 604 604 605 -Element Documentation: 612 +(% style="width:903.294px" %) 613 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 614 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %) 615 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %) 606 606 607 -|**Name**|**Type**|**Documentation** 608 -|Header|BasicHeaderType| 609 -|Query|qry: TimeSeriesDataQueryT ype| 610 - 611 611 **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message. 612 612 613 613 Derivation: 614 614 615 -//MessageType// (restriction) 616 - 621 +* //MessageType// (restriction) 622 +** MetadataQueryType 617 617 618 618 Content: 619 619 620 -Header, Query 626 +* Header, Query 627 +* Element Documentation: 621 621 622 -Element Documentation: 629 +(% style="width:858.294px" %) 630 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 631 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) 632 +|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %) 623 623 624 -|**Name**|**Type**|**Documentation** 625 -|Header|BasicHeaderType| 626 -|Query|qry: MetadataQueryType| 627 - 628 628 **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message. 629 629 630 630 Derivation: 631 631 632 -//MessageType// (restriction) 633 - 638 +* //MessageType// (restriction) 639 +** DataSchemaQueryType 634 634 635 635 Content: 636 636 637 -Header, Query 643 +* Header, Query 644 +* Element Documentation: 638 638 639 -Element Documentation: 646 +(% style="width:895.294px" %) 647 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 648 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) 649 +|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %) 640 640 641 -|**Name**|**Type**|**Documentation** 642 -|Header|BasicHeaderType| 643 -|Query|qry: DataSchemaQueryType| 644 - 645 645 **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message. 646 646 647 647 Derivation: 648 648 649 -//MessageType// (restriction) 650 - 655 +* //MessageType// (restriction) 656 +** MetadataSchemaQueryType 651 651 652 652 Content: 653 653 654 -Header, Query 660 +* Header, Query 661 +* Element Documentation: 655 655 656 -Element Documentation: 663 +(% style="width:897.294px" %) 664 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 665 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) 666 +|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %) 657 657 658 -|**Name**|**Type**|**Documentation** 659 -|Header|BasicHeaderType| 660 -|Query|qry: MetadataSchemaQueryT ype| 661 - 662 662 **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message. 663 663 664 664 Derivation: 665 665 666 -//MessageType// (restriction) 667 - 672 +* //MessageType// (restriction) 673 +** StructuresQueryType 668 668 669 669 Content: 670 670 671 -Header, Query 677 +* Header, Query 678 +* Element Documentation: 672 672 673 -Element Documentation: 680 +(% style="width:886.294px" %) 681 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 682 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %) 683 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %) 674 674 675 -|**Name**|**Type**|**Documentation** 676 -|Header|BasicHeaderType| 677 -|Query|qry: StructuresQueryType| 678 - 679 679 **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message. 680 680 681 681 Derivation: 682 682 683 -//MessageType// (restriction) 684 - 689 +* //MessageType// (restriction) 690 +** DataflowQueryType 685 685 686 686 Content: 687 687 688 -Header, Query 694 +* Header, Query 695 +* Element Documentation: 689 689 690 -Element Documentation: 697 +(% style="width:888.294px" %) 698 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 699 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %) 700 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %) 691 691 692 -|**Name**|**Type**|**Documentation** 693 -|Header|BasicHeaderType| 694 -|Query|qry: DataflowQueryType| 695 - 696 696 **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message. 697 697 698 698 Derivation: 699 699 700 -//MessageType// (restriction) 701 - 706 +* //MessageType// (restriction) 707 +** MetadataflowQueryType 702 702 703 703 Content: 704 704 705 -Header, Query 711 +* Header, Query 712 +* Element Documentation: 706 706 707 -Element Documentation: 714 +(% style="width:886.294px" %) 715 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 716 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) 717 +|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %) 708 708 709 -|**Name**|**Type**|**Documentation** 710 -|Header|BasicHeaderType| 711 -|Query|qry: MetadataflowQueryTyp e| 712 - 713 713 **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message. 714 714 715 715 Derivation: 716 716 717 -//MessageType// (restriction) 718 - 723 +* //MessageType// (restriction) 724 +** DataStructureQueryType 719 719 720 720 Content: 721 721 722 -Header, Query 728 +* Header, Query 729 +* Element Documentation: 723 723 724 -Element Documentation: 731 +(% style="width:901.294px" %) 732 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 733 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) 734 +|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %) 725 725 726 -|**Name**|**Type**|**Documentation** 727 -|Header|BasicHeaderType| 728 -|Query|qry: DataStructureQueryTy pe| 729 - 730 730 **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message. 731 731 732 732 Derivation: 733 733 734 -//MessageType// (restriction) 735 - 740 +* //MessageType// (restriction) 741 +** MetadataStructureQueryType 736 736 737 737 Content: 738 738 739 -Header, Query 745 +* Header, Query 746 +* Element Documentation: 740 740 741 -Element Documentation: 748 +(% style="width:904.294px" %) 749 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 750 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %) 751 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %) 742 742 743 -|**Name**|**Type**|**Documentation** 744 -|Header|BasicHeaderType| 745 -|Query|qry: MetadataStructureQue ryType| 746 - 747 747 **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message. 748 748 749 749 Derivation: 750 750 751 -//MessageType// (restriction) 752 - 757 +* //MessageType// (restriction) 758 +** CategorySchemeQueryType 753 753 754 754 Content: 755 755 756 -Header, Query 762 +* Header, Query 763 +* Element Documentation: 757 757 758 -Element Documentation: 765 +(% style="width:915.294px" %) 766 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 767 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %) 768 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %) 759 759 760 -|**Name**|**Type**|**Documentation** 761 -|Header|BasicHeaderType| 762 -|Query|qry: CategorySchemeQueryT ype| 763 - 764 764 **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message. 765 765 766 766 Derivation: 767 767 768 -//MessageType// (restriction) 769 - 774 +* //MessageType// (restriction) 775 +** ConceptSchemeQueryType 770 770 771 771 Content: 772 772 773 -Header, Query 779 +* Header, Query 780 +* Element Documentation: 774 774 775 -Element Documentation: 782 +(% style="width:895.294px" %) 783 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 784 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %) 785 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %) 776 776 777 -|**Name**|**Type**|**Documentation** 778 -|Header|BasicHeaderType| 779 -|Query|qry: ConceptSchemeQueryTy pe| 780 - 781 781 **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message. 782 782 783 783 Derivation: 784 784 785 -//MessageType// (restriction) 786 - 791 +* //MessageType// (restriction) 792 +** CodelistQueryType 787 787 788 788 Content: 789 789 790 -Header, Query 796 +* Header, Query 797 +* Element Documentation: 791 791 792 -Element Documentation: 799 +(% style="width:911.294px" %) 800 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation** 801 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %) 802 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %) 793 793 794 -|**Name**|**Type**|**Documentation** 795 -|Header|BasicHeaderType| 796 -|Query|qry: CodelistQueryType| 797 - 798 798 **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message. 799 799 800 800 Derivation: 801 801 802 -//MessageType// (restriction) 803 - 808 +* //MessageType// (restriction) 809 +** HierarchicalCodelistQueryType 804 804 805 805 Content: 806 806 807 -Header, Query 813 +* Header, Query 814 +* Element Documentation: 808 808 809 -Element Documentation: 816 +(% style="width:906.294px" %) 817 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation** 818 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %) 819 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %) 810 810 811 -|**Name**|**Type**|**Documentation** 812 -|Header|BasicHeaderType| 813 -|Query|qry: HierarchicalCodelist QueryType| 814 - 815 815 **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message. 816 816 817 817 Derivation: 818 818 819 -//MessageType// (restriction) 820 - 825 +* //MessageType// (restriction) 826 +** OrganisationSchemeQueryType 821 821 822 822 Content: 823 823 824 -Header, Query 830 +* Header, Query 831 +* Element Documentation: 825 825 826 -Element Documentation: 833 +(% style="width:891.294px" %) 834 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation** 835 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %) 836 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %) 827 827 828 -|**Name**|**Type**|**Documentation** 829 -|Header|BasicHeaderType| 830 -|Query|qry: OrganisationSchemeQu eryType| 831 - 832 832 **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message. 833 833 834 834 Derivation: 835 835 836 -//MessageType// (restriction) 837 - 842 +* //MessageType// (restriction) 843 +** ReportingTaxonomyQueryType 838 838 839 839 Content: 840 840 841 -Header, Query 847 +* Header, Query 848 +* Element Documentation: 842 842 843 -Element Documentation: 850 +(% style="width:916.294px" %) 851 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation** 852 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %) 853 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %) 844 844 845 -|**Name**|**Type**|**Documentation** 846 -|Header|BasicHeaderType| 847 -|Query|qry: ReportingTaxonomyQue ryType| 848 - 849 849 **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message. 850 850 851 851 Derivation: 852 852 853 -//MessageType// (restriction) 854 - 859 +* //MessageType// (restriction) 860 +** StructureSetQueryType 855 855 856 856 Content: 857 857 858 -Header, Query 864 +* Header, Query 865 +* Element Documentation: 859 859 860 -Element Documentation: 867 +(% style="width:896.294px" %) 868 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation** 869 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %) 870 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %) 861 861 862 -|**Name**|**Type**|**Documentation** 863 -|Header|BasicHeaderType| 864 -|Query|qry: StructureSetQueryTyp e| 865 - 866 866 **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message. 867 867 868 868 Derivation: 869 869 870 -//MessageType// (restriction) 871 - 876 +* //MessageType// (restriction) 877 +** ProcessQueryType 872 872 873 873 Content: 874 874 875 -Header, Query 881 +* Header, Query 882 +* Element Documentation: 876 876 877 -Element Documentation: 884 +(% style="width:907.294px" %) 885 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation** 886 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %) 887 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %) 878 878 879 -|**Name**|**Type**|**Documentation** 880 -|Header|BasicHeaderType| 881 -|Query|qry:ProcessQueryType| 882 - 883 883 **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message. 884 884 885 885 Derivation: 886 886 887 -//MessageType// (restriction) 888 - 893 +* //MessageType// (restriction) 894 +** CategorisationQueryType 889 889 890 890 Content: 891 891 892 -Header, Query 898 +* Header, Query 899 +* Element Documentation: 893 893 894 -Element Documentation: 901 +(% style="width:897.294px" %) 902 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation** 903 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %) 904 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %) 895 895 896 -|**Name**|**Type**|**Documentation** 897 -|Header|BasicHeaderType| 898 -|Query|qry: CategorisationQueryT ype| 899 - 900 900 **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message. 901 901 902 902 Derivation: 903 903 904 -//MessageType// (restriction) 905 - 910 +* //MessageType// (restriction) 911 +** ProvisionAgreementQueryType 906 906 907 907 Content: 908 908 909 -Header, Query 915 +* Header, Query 916 +* Element Documentation: 910 910 911 -Element Documentation: 918 +(% style="width:902.294px" %) 919 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation** 920 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %) 921 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %) 912 912 913 -|**Name**|**Type**|**Documentation** 914 -|Header|BasicHeaderType| 915 -|Query|qry: ProvisionAgreementQu eryType| 916 - 917 917 **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message. 918 918 919 919 Derivation: