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.28
edited by Helena
on 2025/06/23 17:30
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,629 +422,630 @@
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  
567 -Header, Query
572 +* Header, Query
573 +* Element Documentation:
568 568  
569 -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" %)
570 570  
571 -|**Name**|**Type**|**Documentation**
572 -|Header|BasicHeaderType|
573 -|Query|qry: GenericDataQueryType|
574 -
575 575  **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
576 576  
577 577  Derivation:
578 578  
579 -//MessageType// (restriction)
580 - DataQueryType (restriction)
581 - GenericDataQueryType (restriction)
582 - GenericTimeSeriesDataQueryType
584 +* //MessageType// (restriction)
585 +** DataQueryType (restriction)
586 +*** GenericDataQueryType (restriction)
587 +**** GenericTimeSeriesDataQueryType
583 583  
584 584  Content:
585 585  
586 -Header, Query
591 +* Header, Query
592 +* Element Documentation:
587 587  
588 -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" %)
589 589  
590 -|**Name**|**Type**|**Documentation**
591 -|Header|BasicHeaderType|
592 -|Query|qry: GenericTimeSeriesDat aQueryType|
593 -
594 594  **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
595 595  
596 596  Derivation:
597 597  
598 -//MessageType// (restriction)
599 - DataQueryType (restriction)
600 - StructureSpecificTimeSeriesDataQueryType
603 +* //MessageType// (restriction)
604 +** DataQueryType (restriction)
605 +*** StructureSpecificTimeSeriesDataQueryType
601 601  
602 602  Content:
603 603  
604 -Header, Query
609 +* Header, Query
610 +* Element Documentation:
605 605  
606 -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" %)
607 607  
608 -|**Name**|**Type**|**Documentation**
609 -|Header|BasicHeaderType|
610 -|Query|qry: TimeSeriesDataQueryT ype|
611 -
612 612  **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
613 613  
614 614  Derivation:
615 615  
616 -//MessageType// (restriction)
617 - MetadataQueryType
621 +* //MessageType// (restriction)
622 +** MetadataQueryType
618 618  
619 619  Content:
620 620  
621 -Header, Query
626 +* Header, Query
627 +* Element Documentation:
622 622  
623 -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" %)
624 624  
625 -|**Name**|**Type**|**Documentation**
626 -|Header|BasicHeaderType|
627 -|Query|qry: MetadataQueryType|
628 -
629 629  **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
630 630  
631 631  Derivation:
632 632  
633 -//MessageType// (restriction)
634 - DataSchemaQueryType
638 +* //MessageType// (restriction)
639 +** DataSchemaQueryType
635 635  
636 636  Content:
637 637  
638 -Header, Query
643 +* Header, Query
644 +* Element Documentation:
639 639  
640 -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" %)
641 641  
642 -|**Name**|**Type**|**Documentation**
643 -|Header|BasicHeaderType|
644 -|Query|qry: DataSchemaQueryType|
645 -
646 646  **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
647 647  
648 648  Derivation:
649 649  
650 -//MessageType// (restriction)
651 - MetadataSchemaQueryType
655 +* //MessageType// (restriction)
656 +** MetadataSchemaQueryType
652 652  
653 653  Content:
654 654  
655 -Header, Query
660 +* Header, Query
661 +* Element Documentation:
656 656  
657 -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" %)
658 658  
659 -|**Name**|**Type**|**Documentation**
660 -|Header|BasicHeaderType|
661 -|Query|qry: MetadataSchemaQueryT ype|
662 -
663 663  **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
664 664  
665 665  Derivation:
666 666  
667 -//MessageType// (restriction)
668 - StructuresQueryType
672 +* //MessageType// (restriction)
673 +** StructuresQueryType
669 669  
670 670  Content:
671 671  
672 -Header, Query
677 +* Header, Query
678 +* Element Documentation:
673 673  
674 -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" %)
675 675  
676 -|**Name**|**Type**|**Documentation**
677 -|Header|BasicHeaderType|
678 -|Query|qry: StructuresQueryType|
679 -
680 680  **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
681 681  
682 682  Derivation:
683 683  
684 -//MessageType// (restriction)
685 - DataflowQueryType
689 +* //MessageType// (restriction)
690 +** DataflowQueryType
686 686  
687 687  Content:
688 688  
689 -Header, Query
694 +* Header, Query
695 +* Element Documentation:
690 690  
691 -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" %)
692 692  
693 -|**Name**|**Type**|**Documentation**
694 -|Header|BasicHeaderType|
695 -|Query|qry: DataflowQueryType|
696 -
697 697  **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
698 698  
699 699  Derivation:
700 700  
701 -//MessageType// (restriction)
702 - MetadataflowQueryType
706 +* //MessageType// (restriction)
707 +** MetadataflowQueryType
703 703  
704 704  Content:
705 705  
706 -Header, Query
711 +* Header, Query
712 +* Element Documentation:
707 707  
708 -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" %)
709 709  
710 -|**Name**|**Type**|**Documentation**
711 -|Header|BasicHeaderType|
712 -|Query|qry: MetadataflowQueryTyp e|
713 -
714 714  **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
715 715  
716 716  Derivation:
717 717  
718 -//MessageType// (restriction)
719 - DataStructureQueryType
723 +* //MessageType// (restriction)
724 +** DataStructureQueryType
720 720  
721 721  Content:
722 722  
723 -Header, Query
728 +* Header, Query
729 +* Element Documentation:
724 724  
725 -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" %)
726 726  
727 -|**Name**|**Type**|**Documentation**
728 -|Header|BasicHeaderType|
729 -|Query|qry: DataStructureQueryTy pe|
730 -
731 731  **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
732 732  
733 733  Derivation:
734 734  
735 -//MessageType// (restriction)
736 - MetadataStructureQueryType
740 +* //MessageType// (restriction)
741 +** MetadataStructureQueryType
737 737  
738 738  Content:
739 739  
740 -Header, Query
745 +* Header, Query
746 +* Element Documentation:
741 741  
742 -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" %)
743 743  
744 -|**Name**|**Type**|**Documentation**
745 -|Header|BasicHeaderType|
746 -|Query|qry: MetadataStructureQue ryType|
747 -
748 748  **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
749 749  
750 750  Derivation:
751 751  
752 -//MessageType// (restriction)
753 - CategorySchemeQueryType
757 +* //MessageType// (restriction)
758 +** CategorySchemeQueryType
754 754  
755 755  Content:
756 756  
757 -Header, Query
762 +* Header, Query
763 +* Element Documentation:
758 758  
759 -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" %)
760 760  
761 -|**Name**|**Type**|**Documentation**
762 -|Header|BasicHeaderType|
763 -|Query|qry: CategorySchemeQueryT ype|
764 -
765 765  **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
766 766  
767 767  Derivation:
768 768  
769 -//MessageType// (restriction)
770 - ConceptSchemeQueryType
774 +* //MessageType// (restriction)
775 +** ConceptSchemeQueryType
771 771  
772 772  Content:
773 773  
774 -Header, Query
779 +* Header, Query
780 +* Element Documentation:
775 775  
776 -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" %)
777 777  
778 -|**Name**|**Type**|**Documentation**
779 -|Header|BasicHeaderType|
780 -|Query|qry: ConceptSchemeQueryTy pe|
781 -
782 782  **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
783 783  
784 784  Derivation:
785 785  
786 -//MessageType// (restriction)
787 - CodelistQueryType
791 +* //MessageType// (restriction)
792 +** CodelistQueryType
788 788  
789 789  Content:
790 790  
791 -Header, Query
796 +* Header, Query
797 +* Element Documentation:
792 792  
793 -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" %)
794 794  
795 -|**Name**|**Type**|**Documentation**
796 -|Header|BasicHeaderType|
797 -|Query|qry: CodelistQueryType|
798 -
799 799  **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
800 800  
801 801  Derivation:
802 802  
803 -//MessageType// (restriction)
804 - HierarchicalCodelistQueryType
808 +* //MessageType// (restriction)
809 +** HierarchicalCodelistQueryType
805 805  
806 806  Content:
807 807  
808 -Header, Query
813 +* Header, Query
814 +* Element Documentation:
809 809  
810 -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" %)
811 811  
812 -|**Name**|**Type**|**Documentation**
813 -|Header|BasicHeaderType|
814 -|Query|qry: HierarchicalCodelist QueryType|
815 -
816 816  **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
817 817  
818 818  Derivation:
819 819  
820 -//MessageType// (restriction)
821 - OrganisationSchemeQueryType
825 +* //MessageType// (restriction)
826 +** OrganisationSchemeQueryType
822 822  
823 823  Content:
824 824  
825 -Header, Query
830 +* Header, Query
831 +* Element Documentation:
826 826  
827 -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" %)
828 828  
829 -|**Name**|**Type**|**Documentation**
830 -|Header|BasicHeaderType|
831 -|Query|qry: OrganisationSchemeQu eryType|
832 -
833 833  **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
834 834  
835 835  Derivation:
836 836  
837 -//MessageType// (restriction)
838 - ReportingTaxonomyQueryType
842 +* //MessageType// (restriction)
843 +** ReportingTaxonomyQueryType
839 839  
840 840  Content:
841 841  
842 -Header, Query
847 +* Header, Query
848 +* Element Documentation:
843 843  
844 -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" %)
845 845  
846 -|**Name**|**Type**|**Documentation**
847 -|Header|BasicHeaderType|
848 -|Query|qry: ReportingTaxonomyQue ryType|
849 -
850 850  **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
851 851  
852 852  Derivation:
853 853  
854 -//MessageType// (restriction)
855 - StructureSetQueryType
859 +* //MessageType// (restriction)
860 +** StructureSetQueryType
856 856  
857 857  Content:
858 858  
859 -Header, Query
864 +* Header, Query
865 +* Element Documentation:
860 860  
861 -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" %)
862 862  
863 -|**Name**|**Type**|**Documentation**
864 -|Header|BasicHeaderType|
865 -|Query|qry: StructureSetQueryTyp e|
866 -
867 867  **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
868 868  
869 869  Derivation:
870 870  
871 -//MessageType// (restriction)
872 - ProcessQueryType
876 +* //MessageType// (restriction)
877 +** ProcessQueryType
873 873  
874 874  Content:
875 875  
876 -Header, Query
881 +* Header, Query
882 +* Element Documentation:
877 877  
878 -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" %)
879 879  
880 -|**Name**|**Type**|**Documentation**
881 -|Header|BasicHeaderType|
882 -|Query|qry:ProcessQueryType|
883 -
884 884  **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
885 885  
886 886  Derivation:
887 887  
888 -//MessageType// (restriction)
889 - CategorisationQueryType
893 +* //MessageType// (restriction)
894 +** CategorisationQueryType
890 890  
891 891  Content:
892 892  
893 -Header, Query
898 +* Header, Query
899 +* Element Documentation:
894 894  
895 -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" %)
896 896  
897 -|**Name**|**Type**|**Documentation**
898 -|Header|BasicHeaderType|
899 -|Query|qry: CategorisationQueryT ype|
900 -
901 901  **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
902 902  
903 903  Derivation:
904 904  
905 -//MessageType// (restriction)
906 - ProvisionAgreementQueryType
910 +* //MessageType// (restriction)
911 +** ProvisionAgreementQueryType
907 907  
908 908  Content:
909 909  
910 -Header, Query
915 +* Header, Query
916 +* Element Documentation:
911 911  
912 -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" %)
913 913  
914 -|**Name**|**Type**|**Documentation**
915 -|Header|BasicHeaderType|
916 -|Query|qry: ProvisionAgreementQu eryType|
917 -
918 918  **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
919 919  
920 920  Derivation:
921 921  
922 -//MessageType// (restriction)
923 - ConstraintQueryType
927 +* //MessageType// (restriction)
928 +** ConstraintQueryType
924 924  
925 925  Content:
926 926  
927 -Header, Query
932 +* Header, Query
933 +* Element Documentation:
928 928  
929 -Element Documentation:
935 +(% style="width:902.294px" %)
936 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
937 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
938 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
930 930  
931 -|**Name**|**Type**|**Documentation**
932 -|Header|BasicHeaderType|
933 -|Query|qry: ConstraintQueryType|
934 -
935 935  **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
936 936  
937 937  Derivation:
938 938  
939 -//MessageType// (restriction)
940 - TransformationSchemeQueryType
944 +* //MessageType// (restriction)
945 +** TransformationSchemeQueryType
941 941  
942 942  Content:
943 943  
944 -Header, Query
949 +* Header, Query
950 +* Element Documentation:
945 945  
946 -Element Documentation:
952 +(% style="width:833.294px" %)
953 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
954 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
955 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
947 947  
948 -|**Name**|**Type**|**Documentation**
949 -|Header|BasicHeaderType|
950 -|Query|qry: TransformationScheme QueryType|
951 -
952 952  **VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
953 953  
954 954  Derivation:
955 955  
956 -//MessageType// (restriction)
957 - VtlMappingSchemeQueryType
961 +* //MessageType// (restriction)
962 +** VtlMappingSchemeQueryType
958 958  
959 959  Content:
960 960  
961 -Header, Query
966 +* Header, Query
967 +* Element Documentation:
962 962  
963 -Element Documentation:
969 +(% style="width:843.294px" %)
970 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
971 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
972 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
964 964  
965 -|**Name**|**Type**|**Documentation**
966 -|Header|BasicHeaderType|
967 -|Query|qry: VtlMappingSchemeQuer yType|
968 -
969 969  **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
970 970  
971 971  Derivation:
972 972  
973 -//MessageType// (restriction)
974 - NamePersonalisationSchemeQueryType
978 +* //MessageType// (restriction)
979 +** NamePersonalisationSchemeQueryType
975 975  
976 976  Content:
977 977  
978 -Header, Query
983 +* Header, Query
984 +* Element Documentation:
979 979  
980 -Element Documentation:
986 +(% style="width:895.294px" %)
987 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
988 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
989 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
981 981  
982 -|**Name**|**Type**|**Documentation**
983 -|Header|BasicHeaderType|
984 -|Query|qry: NamePersonalisationS chemeQueryType|
985 -
986 986  **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
987 987  
988 988  Derivation:
989 989  
990 -//MessageType// (restriction)
991 - RulesetSchemeQueryType
995 +* //MessageType// (restriction)
996 +** RulesetSchemeQueryType
992 992  
993 993  Content:
994 994  
995 -Header, Query
1000 +* Header, Query
1001 +* Element Documentation:
996 996  
997 -Element Documentation:
1003 +(% style="width:886.294px" %)
1004 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
1005 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
1006 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
998 998  
999 -|**Name**|**Type**|**Documentation**
1000 -|Header|BasicHeaderType|
1001 -|Query|qry: RulesetSchemeQueryTy pe|
1002 -
1003 1003  **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1004 1004  
1005 1005  Derivation:
1006 1006  
1007 -//MessageType// (restriction)
1008 - UserDefinedOperatorSchemeQueryType
1012 +* //MessageType// (restriction)
1013 +** UserDefinedOperatorSchemeQueryType
1009 1009  
1010 1010  Content:
1011 1011  
1012 -Header, Query
1017 +* Header, Query
1018 +* Element Documentation:
1013 1013  
1014 -Element Documentation:
1020 +(% style="width:866.294px" %)
1021 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1022 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1023 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
1015 1015  
1016 -|**Name**|**Type**|**Documentation**
1017 -|Header|BasicHeaderType|
1018 -|Query|qry: UserDefinedOperatorS chemeQueryType|
1019 -
1020 1020  **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1021 1021  
1022 1022  Derivation:
1023 1023  
1024 -//MessageType// (restriction)
1025 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1029 +* //MessageType// (restriction)
1030 +** CustomTypeSchemeQueryType
1026 1026  
1027 1027  Content:
1028 1028  
1029 -Header, Query
1034 +* Header, Query
1035 +* Element Documentation:
1030 1030  
1031 -Element Documentation:
1037 +(% style="width:828.294px" %)
1038 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1039 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1040 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
1032 1032  
1033 -|**Name**|**Type**|**Documentation**
1034 -|Header|BasicHeaderType|
1035 -|Query|qry: CustomTypeSchemeQuer yType|
1036 -
1037 1037  **ErrorType: **ErrorType describes the structure of an error response.
1038 1038  
1039 1039  Content:
1040 1040  
1041 -ErrorMessage+
1046 +* ErrorMessage+
1047 +* Element Documentation:
1042 1042  
1043 -Element Documentation:
1049 +(% style="width:899.294px" %)
1050 +|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1051 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1044 1044  
1045 -|**Name**|**Type**|**Documentation**
1046 -|ErrorMessage|com: CodedStatusMessageTy pe|ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1047 -
1048 1048  **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1049 1049  
1050 1050  Content:
... ... @@ -1053,29 +1053,30 @@
1053 1053  
1054 1054  Element Documentation:
1055 1055  
1056 -|**Name**|**Type**|**Documentation**
1057 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1058 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1059 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1060 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1061 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1062 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1063 -|Structure|//com: PayloadStructureType//|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1064 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1065 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1066 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1067 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1068 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1069 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1070 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1071 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1061 +(% style="width:891.294px" %)
1062 +|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1063 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1064 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1065 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1066 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1067 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1068 +|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1069 +|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1070 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1071 +|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1072 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1073 +|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1074 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1075 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1076 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1077 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1072 1072  
1073 1073  **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1074 1074  
1075 1075  Derivation:
1076 1076  
1077 -//BaseHeaderType// (restriction)
1078 - StructureHeaderType
1083 +* //BaseHeaderType// (restriction)
1084 +** StructureHeaderType
1079 1079  
1080 1080  Content:
1081 1081  
... ... @@ -1083,21 +1083,22 @@
1083 1083  
1084 1084  Element Documentation:
1085 1085  
1086 -|**Name**|**Type**|**Documentation**
1087 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1088 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1089 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1090 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1091 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1092 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1093 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1092 +(% style="width:1099.29px" %)
1093 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1094 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1095 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1096 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1097 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1098 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1099 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1100 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
1094 1094  
1095 1095  **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1096 1096  
1097 1097  Derivation:
1098 1098  
1099 -//BaseHeaderType// (restriction)
1100 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1106 +* //BaseHeaderType// (restriction)
1107 +** GenericDataHeaderType
1101 1101  
1102 1102  Content:
1103 1103  
... ... @@ -1105,30 +1105,31 @@
1105 1105  
1106 1106  Element Documentation:
1107 1107  
1108 -|**Name**|**Type**|**Documentation**
1109 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1110 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1111 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1112 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1113 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1114 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1115 -|Structure|com: GenericDataStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1116 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1117 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1118 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1119 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1120 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1121 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1122 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1123 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1115 +(% style="width:895.294px" %)
1116 +|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1117 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1118 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1119 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1120 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1121 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1122 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1123 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1124 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1125 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1126 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1127 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1128 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1129 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1130 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1131 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1124 1124  
1125 1125  **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1126 1126  
1127 1127  Derivation:
1128 1128  
1129 -//BaseHeaderType// (restriction)
1130 - GenericDataHeaderType (restriction)
1131 - GenericTimeSeriesDataHeaderType
1137 +* //BaseHeaderType// (restriction)
1138 +** GenericDataHeaderType (restriction)
1139 +*** GenericTimeSeriesDataHeaderType
1132 1132  
1133 1133  Content:
1134 1134  
... ... @@ -1136,29 +1136,30 @@
1136 1136  
1137 1137  Element Documentation:
1138 1138  
1139 -|**Name**|**Type**|**Documentation**
1140 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1141 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1142 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1143 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1144 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1145 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1146 -|Structure|com: GenericTimeSeriesDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1147 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1148 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1149 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1150 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1151 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1152 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1153 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1154 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1147 +(% style="width:926.294px" %)
1148 +|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1149 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1150 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1151 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1152 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1153 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1154 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1155 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1156 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1157 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1158 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1159 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1160 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1161 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1162 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1163 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1155 1155  
1156 1156  **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1157 1157  
1158 1158  Derivation:
1159 1159  
1160 -//BaseHeaderType// (restriction)
1161 - StructureSpecificDataHeaderType
1169 +* //BaseHeaderType// (restriction)
1170 +** StructureSpecificDataHeaderType
1162 1162  
1163 1163  Content:
1164 1164  
... ... @@ -1166,30 +1166,31 @@
1166 1166  
1167 1167  Element Documentation:
1168 1168  
1169 -|**Name**|**Type**|**Documentation**
1170 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1171 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1172 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1173 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1174 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1175 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1176 -|Structure|com: StructureSpecificDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1177 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1178 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1179 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1180 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1181 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1182 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1183 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1184 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1178 +(% style="width:930.294px" %)
1179 +|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1180 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1181 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1182 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1183 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1184 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1185 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1186 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1187 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1188 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1189 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1190 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1191 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1192 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1193 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1194 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1185 1185  
1186 1186  **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1187 1187  
1188 1188  Derivation:
1189 1189  
1190 -//BaseHeaderType// (restriction)
1191 - StructureSpecificDataHeaderType (restriction)
1192 - StructureSpecificTimeSeriesDataHeaderType
1200 +* //BaseHeaderType// (restriction)
1201 +** StructureSpecificDataHeaderType (restriction)
1202 +*** StructureSpecificTimeSeriesDataHeaderType
1193 1193  
1194 1194  Content:
1195 1195  
... ... @@ -1197,29 +1197,30 @@
1197 1197  
1198 1198  Element Documentation:
1199 1199  
1200 -|**Name**|**Type**|**Documentation**
1201 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1202 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1203 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1204 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1205 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1206 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1207 -|Structure|com: StructureSpecificDat aTimeSeriesStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1208 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1209 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1210 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1211 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1212 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1213 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1214 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1215 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1210 +(% style="width:943.294px" %)
1211 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1212 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1213 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1214 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1215 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1216 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1217 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1218 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1219 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1220 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1221 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1222 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1223 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1224 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1225 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1226 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1216 1216  
1217 1217  **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1218 1218  
1219 1219  Derivation:
1220 1220  
1221 -//BaseHeaderType// (restriction)
1222 - GenericMetadataHeaderType
1232 +* //BaseHeaderType// (restriction)
1233 +** GenericMetadataHeaderType
1223 1223  
1224 1224  Content:
1225 1225  
... ... @@ -1227,26 +1227,27 @@
1227 1227  
1228 1228  Element Documentation:
1229 1229  
1230 -|**Name**|**Type**|**Documentation**
1231 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1232 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1233 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1234 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1235 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1236 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1237 -|Structure|com: GenericMetadataStruc tureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1238 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1239 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1240 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1241 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1242 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1241 +(% style="width:928.294px" %)
1242 +|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1243 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1244 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1245 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1246 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1247 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1248 +|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1249 +|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1250 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1251 +|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1252 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1253 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1254 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1243 1243  
1244 1244  **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1245 1245  
1246 1246  Derivation:
1247 1247  
1248 -//BaseHeaderType// (restriction)
1249 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1260 +* //BaseHeaderType// (restriction)
1261 +** StructureSpecificMetadataHeaderType
1250 1250  
1251 1251  Content:
1252 1252  
... ... @@ -1254,26 +1254,27 @@
1254 1254  
1255 1255  Element Documentation:
1256 1256  
1257 -|**Name**|**Type**|**Documentation**
1258 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1259 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1260 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1261 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1262 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1263 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1264 -|Structure|com: StructureSpecificMet adataStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1265 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1266 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1267 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1268 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1269 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1269 +(% style="width:996.294px" %)
1270 +|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1271 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1272 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1273 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1274 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1275 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1276 +|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1277 +|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1278 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1279 +|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1280 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
1281 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1282 +|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1270 1270  
1271 1271  **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1272 1272  
1273 1273  Derivation:
1274 1274  
1275 -//BaseHeaderType// (restriction)
1276 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1288 +* //BaseHeaderType// (restriction)
1289 +** BasicHeaderType
1277 1277  
1278 1278  Content:
1279 1279