Changes for page Part I. Message Namespace

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

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

Summary

Details

Page properties
Content
... ... @@ -177,8 +177,8 @@
177 177  
178 178  Derivation:
179 179  
180 -//MessageType// (restriction)
181 - StructureType
180 +* //MessageType// (restriction)
181 +** StructureType
182 182  
183 183  Content:
184 184  
... ... @@ -196,8 +196,8 @@
196 196  
197 197  Derivation:
198 198  
199 -//MessageType// (restriction)
200 - GenericDataType
199 +* //MessageType// (restriction)
200 +** GenericDataType
201 201  
202 202  Content:
203 203  
... ... @@ -264,17 +264,18 @@
264 264  
265 265  Element Documentation:
266 266  
267 -|**Name**|**Type**|**Documentation**
268 -|Header|StructureSpecificTim eSeriesDataHeaderTyp e|
269 -|DataSet|//dsd: TimeSeriesDataSetTyp e//|
270 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
267 +(% style="width:839.294px" %)
268 +|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
269 +|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
270 +|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
271 +|ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
271 271  
272 272  **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
273 273  
274 274  Derivation:
275 275  
276 -//MessageType// (restriction)
277 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
277 +* //MessageType// (restriction)
278 +** GenericMetadataType
278 278  
279 279  Content:
280 280  
... ... @@ -282,17 +282,18 @@
282 282  
283 283  Element Documentation:
284 284  
285 -|**Name**|**Type**|**Documentation**
286 -|Header|GenericMetadataHeade rType|
287 -|MetadataSet|rep:MetadataSetType|
288 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
286 +(% style="width:836.294px" %)
287 +|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
288 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %)
289 +|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
290 +|(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
289 289  
290 290  **StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
291 291  
292 292  Derivation:
293 293  
294 -//MessageType// (restriction)
295 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
296 +* //MessageType// (restriction)
297 +** StructureSpecificMetadataType
296 296  
297 297  Content:
298 298  
... ... @@ -300,17 +300,18 @@
300 300  
301 301  Element Documentation:
302 302  
303 -|**Name**|**Type**|**Documentation**
304 -|Header|StructureSpecificMet adataHeaderType|
305 -|MetadataSet|//msd:MetadataSetType//|
306 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
305 +(% style="width:841.294px" %)
306 +|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
307 +|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
308 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
309 +|(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
307 307  
308 308  **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
309 309  
310 310  Derivation:
311 311  
312 -//MessageType// (restriction)
313 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
315 +* //MessageType// (restriction)
316 +** RegistryInterfaceType
314 314  
315 315  Content:
316 316  
... ... @@ -318,28 +318,29 @@
318 318  
319 319  Element Documentation:
320 320  
321 -|**Name**|**Type**|**Documentation**
322 -|Header|BasicHeaderType|
323 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
324 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
325 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
326 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
327 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
328 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
329 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
330 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
331 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
332 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
333 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
334 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
324 +(% style="width:903.294px" %)
325 +|**Name**|**Type**|(% style="width:441px" %)**Documentation**
326 +|Header|BasicHeaderType|(% style="width:441px" %)
327 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
328 +|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
329 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
330 +|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
331 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
332 +|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
333 +|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
334 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
335 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
336 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
337 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
338 +|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
335 335  
336 336  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
337 337  
338 338  Derivation:
339 339  
340 -//MessageType// (restriction)
341 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
342 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
344 +* //MessageType// (restriction)
345 +** RegistryInterfaceType (restriction)
346 +*** SubmitRegistrationsRequestType
343 343  
344 344  Content:
345 345  
... ... @@ -347,17 +347,18 @@
347 347  
348 348  Element Documentation:
349 349  
350 -|**Name**|**Type**|**Documentation**
351 -|Header|BasicHeaderType|
352 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
354 +(% style="width:844.294px" %)
355 +|**Name**|**Type**|(% style="width:377px" %)**Documentation**
356 +|Header|BasicHeaderType|(% style="width:377px" %)
357 +|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.
353 353  
354 354  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
355 355  
356 356  Derivation:
357 357  
358 -//MessageType// (restriction)
359 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
360 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
363 +* //MessageType// (restriction)
364 +** RegistryInterfaceType (restriction)
365 +*** SubmitRegistrationsResponseType
361 361  
362 362  Content:
363 363  
... ... @@ -365,18 +365,19 @@
365 365  
366 366  Element Documentation:
367 367  
368 -|**Name**|**Type**|**Documentation**
369 -|Header|BasicHeaderType|
370 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
371 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
373 +(% style="width:847.294px" %)
374 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
375 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %)
376 +|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.
377 +|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.
372 372  
373 373  **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
374 374  
375 375  Derivation:
376 376  
377 -//MessageType// (restriction)
378 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
379 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
383 +* //MessageType// (restriction)
384 +** RegistryInterfaceType (restriction)
385 +*** QueryRegistrationRequestType
380 380  
381 381  Content:
382 382  
... ... @@ -384,17 +384,18 @@
384 384  
385 385  Element Documentation:
386 386  
387 -|**Name**|**Type**|**Documentation**
388 -|Header|BasicHeaderType|
389 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
393 +(% style="width:847.294px" %)
394 +|**Name**|**Type**|(% style="width:397px" %)**Documentation**
395 +|Header|BasicHeaderType|(% style="width:397px" %)
396 +|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.
390 390  
391 391  **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
392 392  
393 393  Derivation:
394 394  
395 -//MessageType// (restriction)
396 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
397 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
402 +* //MessageType// (restriction)
403 +** RegistryInterfaceType (restriction)
404 +*** QueryRegistrationResponseType
398 398  
399 399  Content:
400 400  
... ... @@ -402,18 +402,19 @@
402 402  
403 403  Element Documentation:
404 404  
405 -|**Name**|**Type**|**Documentation**
406 -|Header|BasicHeaderType|
407 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
408 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
412 +(% style="width:856.294px" %)
413 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation**
414 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %)
415 +|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.
416 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
409 409  
410 410  **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
411 411  
412 412  Derivation:
413 413  
414 -//MessageType// (restriction)
415 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
422 +* //MessageType// (restriction)
423 +** RegistryInterfaceType (restriction)
424 +*** SubmitStructureRequestType
417 417  
418 418  Content:
419 419  
... ... @@ -421,17 +421,18 @@
421 421  
422 422  Element Documentation:
423 423  
424 -|**Name**|**Type**|**Documentation**
425 -|Header|BasicHeaderType|
426 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
432 +(% style="width:870.294px" %)
433 +|**Name**|**Type**|(% style="width:453px" %)**Documentation**
434 +|Header|BasicHeaderType|(% style="width:453px" %)
435 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
427 427  
428 428  **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
429 429  
430 430  Derivation:
431 431  
432 -//MessageType// (restriction)
433 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
434 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
441 +* //MessageType// (restriction)
442 +** RegistryInterfaceType (restriction)
443 +*** SubmitStructureResponseType
435 435  
436 436  Content:
437 437  
... ... @@ -439,18 +439,19 @@
439 439  
440 440  Element Documentation:
441 441  
442 -|**Name**|**Type**|**Documentation**
443 -|Header|BasicHeaderType|
444 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
445 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
451 +(% style="width:835.294px" %)
452 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
453 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %)
454 +|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.
455 +|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.
446 446  
447 447  **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
448 448  
449 449  Derivation:
450 450  
451 -//MessageType// (restriction)
452 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
453 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
461 +* //MessageType// (restriction)
462 +** RegistryInterfaceType (restriction)
463 +*** SubmitSubscriptionsRequestType
454 454  
455 455  Content:
456 456  
... ... @@ -458,17 +458,18 @@
458 458  
459 459  Element Documentation:
460 460  
461 -|**Name**|**Type**|**Documentation**
462 -|Header|BasicHeaderType|
463 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
471 +(% style="width:832.294px" %)
472 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
473 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
474 +|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.
464 464  
465 465  **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
466 466  
467 467  Derivation:
468 468  
469 -//MessageType// (restriction)
470 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
471 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
480 +* //MessageType// (restriction)
481 +** RegistryInterfaceType (restriction)
482 +*** SubmitSubscriptionsResponseType
472 472  
473 473  Content:
474 474  
... ... @@ -476,18 +476,19 @@
476 476  
477 477  Element Documentation:
478 478  
479 -|**Name**|**Type**|**Documentation**
480 -|Header|BasicHeaderType|
481 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
482 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
490 +(% style="width:843.294px" %)
491 +|**Name**|**Type**|(% style="width:362px" %)**Documentation**
492 +|Header|BasicHeaderType|(% style="width:362px" %)
493 +|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.
494 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
483 483  
484 484  **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
485 485  
486 486  Derivation:
487 487  
488 -//MessageType// (restriction)
489 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
490 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
500 +* //MessageType// (restriction)
501 +** RegistryInterfaceType (restriction)
502 +*** QuerySubscriptionRequestType
491 491  
492 492  Content:
493 493  
... ... @@ -495,17 +495,18 @@
495 495  
496 496  Element Documentation:
497 497  
498 -|**Name**|**Type**|**Documentation**
499 -|Header|BasicHeaderType|
500 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
510 +(% style="width:839.294px" %)
511 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
512 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
513 +|(% 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.
501 501  
502 502  **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
503 503  
504 504  Derivation:
505 505  
506 -//MessageType// (restriction)
507 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
508 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
519 +* //MessageType// (restriction)
520 +** RegistryInterfaceType (restriction)
521 +*** QuerySubscriptionResponseType
509 509  
510 510  Content:
511 511  
... ... @@ -513,18 +513,19 @@
513 513  
514 514  Element Documentation:
515 515  
516 -|**Name**|**Type**|**Documentation**
517 -|Header|BasicHeaderType|
518 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
519 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
529 +(% style="width:912.294px" %)
530 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
531 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
532 +|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.
533 +|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.
520 520  
521 521  **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
522 522  
523 523  Derivation:
524 524  
525 -//MessageType// (restriction)
526 - RegistryInterfaceType (restriction)
527 - NotifyRegistryEventType
539 +* //MessageType// (restriction)
540 +** RegistryInterfaceType (restriction)
541 +*** NotifyRegistryEventType
528 528  
529 529  Content:
530 530  
... ... @@ -532,16 +532,17 @@
532 532  
533 533  Element Documentation:
534 534  
535 -|**Name**|**Type**|**Documentation**
536 -|Header|BasicHeaderType|
537 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
549 +(% style="width:836.294px" %)
550 +|**Name**|**Type**|(% style="width:473px" %)**Documentation**
551 +|Header|BasicHeaderType|(% style="width:473px" %)
552 +|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.
538 538  
539 539  **DataQueryType: **DataQueryType defines the structure of a data query message.
540 540  
541 541  Derivation:
542 542  
543 -//MessageType// (restriction)
544 - DataQueryType
558 +* //MessageType// (restriction)
559 +** DataQueryType
545 545  
546 546  Content:
547 547  
... ... @@ -549,17 +549,18 @@
549 549  
550 550  Element Documentation:
551 551  
552 -|**Name**|**Type**|**Documentation**
553 -|Header|BasicHeaderType|
554 -|Query|qry:DataQueryType|
567 +(% style="width:839.294px" %)
568 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
569 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %)
570 +|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %)
555 555  
556 556  **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
557 557  
558 558  Derivation:
559 559  
560 -//MessageType// (restriction)
561 - DataQueryType (restriction)
562 - GenericDataQueryType
576 +* //MessageType// (restriction)
577 +** DataQueryType (restriction)
578 +*** GenericDataQueryType
563 563  
564 564  Content:
565 565  
... ... @@ -567,18 +567,19 @@
567 567  
568 568  Element Documentation:
569 569  
570 -|**Name**|**Type**|**Documentation**
571 -|Header|BasicHeaderType|
572 -|Query|qry: GenericDataQueryType|
586 +(% style="width:833.294px" %)
587 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation**
588 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %)
589 +|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %)
573 573  
574 574  **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
575 575  
576 576  Derivation:
577 577  
578 -//MessageType// (restriction)
579 - DataQueryType (restriction)
580 - GenericDataQueryType (restriction)
581 - GenericTimeSeriesDataQueryType
595 +* //MessageType// (restriction)
596 +** DataQueryType (restriction)
597 +*** GenericDataQueryType (restriction)
598 +**** GenericTimeSeriesDataQueryType
582 582  
583 583  Content:
584 584  
... ... @@ -586,17 +586,18 @@
586 586  
587 587  Element Documentation:
588 588  
589 -|**Name**|**Type**|**Documentation**
590 -|Header|BasicHeaderType|
591 -|Query|qry: GenericTimeSeriesDat aQueryType|
606 +(% style="width:909.294px" %)
607 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation**
608 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %)
609 +|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %)
592 592  
593 593  **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
594 594  
595 595  Derivation:
596 596  
597 -//MessageType// (restriction)
598 - DataQueryType (restriction)
599 - StructureSpecificTimeSeriesDataQueryType
615 +* //MessageType// (restriction)
616 +** DataQueryType (restriction)
617 +*** StructureSpecificTimeSeriesDataQueryType
600 600  
601 601  Content:
602 602  
... ... @@ -604,16 +604,17 @@
604 604  
605 605  Element Documentation:
606 606  
607 -|**Name**|**Type**|**Documentation**
608 -|Header|BasicHeaderType|
609 -|Query|qry: TimeSeriesDataQueryT ype|
625 +(% style="width:903.294px" %)
626 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation**
627 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
628 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
610 610  
611 611  **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
612 612  
613 613  Derivation:
614 614  
615 -//MessageType// (restriction)
616 - MetadataQueryType
634 +* //MessageType// (restriction)
635 +** MetadataQueryType
617 617  
618 618  Content:
619 619  
... ... @@ -621,16 +621,17 @@
621 621  
622 622  Element Documentation:
623 623  
624 -|**Name**|**Type**|**Documentation**
625 -|Header|BasicHeaderType|
626 -|Query|qry: MetadataQueryType|
643 +(% style="width:858.294px" %)
644 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation**
645 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %)
646 +|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %)
627 627  
628 628  **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
629 629  
630 630  Derivation:
631 631  
632 -//MessageType// (restriction)
633 - DataSchemaQueryType
652 +* //MessageType// (restriction)
653 +** DataSchemaQueryType
634 634  
635 635  Content:
636 636  
... ... @@ -638,16 +638,17 @@
638 638  
639 639  Element Documentation:
640 640  
641 -|**Name**|**Type**|**Documentation**
642 -|Header|BasicHeaderType|
643 -|Query|qry: DataSchemaQueryType|
661 +(% style="width:895.294px" %)
662 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation**
663 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %)
664 +|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %)
644 644  
645 645  **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
646 646  
647 647  Derivation:
648 648  
649 -//MessageType// (restriction)
650 - MetadataSchemaQueryType
670 +* //MessageType// (restriction)
671 +** MetadataSchemaQueryType
651 651  
652 652  Content:
653 653  
... ... @@ -655,16 +655,17 @@
655 655  
656 656  Element Documentation:
657 657  
658 -|**Name**|**Type**|**Documentation**
659 -|Header|BasicHeaderType|
660 -|Query|qry: MetadataSchemaQueryT ype|
679 +(% style="width:897.294px" %)
680 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation**
681 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %)
682 +|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %)
661 661  
662 662  **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
663 663  
664 664  Derivation:
665 665  
666 -//MessageType// (restriction)
667 - StructuresQueryType
688 +* //MessageType// (restriction)
689 +** StructuresQueryType
668 668  
669 669  Content:
670 670  
... ... @@ -672,16 +672,17 @@
672 672  
673 673  Element Documentation:
674 674  
675 -|**Name**|**Type**|**Documentation**
676 -|Header|BasicHeaderType|
677 -|Query|qry: StructuresQueryType|
697 +(% style="width:886.294px" %)
698 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
699 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
700 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
678 678  
679 679  **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
680 680  
681 681  Derivation:
682 682  
683 -//MessageType// (restriction)
684 - DataflowQueryType
706 +* //MessageType// (restriction)
707 +** DataflowQueryType
685 685  
686 686  Content:
687 687  
... ... @@ -689,16 +689,17 @@
689 689  
690 690  Element Documentation:
691 691  
692 -|**Name**|**Type**|**Documentation**
693 -|Header|BasicHeaderType|
694 -|Query|qry: DataflowQueryType|
715 +(% style="width:888.294px" %)
716 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
717 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
718 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
695 695  
696 696  **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
697 697  
698 698  Derivation:
699 699  
700 -//MessageType// (restriction)
701 - MetadataflowQueryType
724 +* //MessageType// (restriction)
725 +** MetadataflowQueryType
702 702  
703 703  Content:
704 704  
... ... @@ -706,16 +706,17 @@
706 706  
707 707  Element Documentation:
708 708  
709 -|**Name**|**Type**|**Documentation**
710 -|Header|BasicHeaderType|
711 -|Query|qry: MetadataflowQueryTyp e|
733 +(% style="width:886.294px" %)
734 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
735 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
736 +|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %)
712 712  
713 713  **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
714 714  
715 715  Derivation:
716 716  
717 -//MessageType// (restriction)
718 - DataStructureQueryType
742 +* //MessageType// (restriction)
743 +** DataStructureQueryType
719 719  
720 720  Content:
721 721  
... ... @@ -723,16 +723,17 @@
723 723  
724 724  Element Documentation:
725 725  
726 -|**Name**|**Type**|**Documentation**
727 -|Header|BasicHeaderType|
728 -|Query|qry: DataStructureQueryTy pe|
751 +(% style="width:901.294px" %)
752 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
753 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
754 +|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %)
729 729  
730 730  **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
731 731  
732 732  Derivation:
733 733  
734 -//MessageType// (restriction)
735 - MetadataStructureQueryType
760 +* //MessageType// (restriction)
761 +** MetadataStructureQueryType
736 736  
737 737  Content:
738 738  
... ... @@ -740,16 +740,17 @@
740 740  
741 741  Element Documentation:
742 742  
743 -|**Name**|**Type**|**Documentation**
744 -|Header|BasicHeaderType|
745 -|Query|qry: MetadataStructureQue ryType|
769 +(% style="width:904.294px" %)
770 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
771 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
772 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
746 746  
747 747  **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
748 748  
749 749  Derivation:
750 750  
751 -//MessageType// (restriction)
752 - CategorySchemeQueryType
778 +* //MessageType// (restriction)
779 +** CategorySchemeQueryType
753 753  
754 754  Content:
755 755  
... ... @@ -757,16 +757,17 @@
757 757  
758 758  Element Documentation:
759 759  
760 -|**Name**|**Type**|**Documentation**
761 -|Header|BasicHeaderType|
762 -|Query|qry: CategorySchemeQueryT ype|
787 +(% style="width:915.294px" %)
788 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
789 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
790 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
763 763  
764 764  **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
765 765  
766 766  Derivation:
767 767  
768 -//MessageType// (restriction)
769 - ConceptSchemeQueryType
796 +* //MessageType// (restriction)
797 +** ConceptSchemeQueryType
770 770  
771 771  Content:
772 772  
... ... @@ -774,276 +774,277 @@
774 774  
775 775  Element Documentation:
776 776  
777 -|**Name**|**Type**|**Documentation**
778 -|Header|BasicHeaderType|
779 -|Query|qry: ConceptSchemeQueryTy pe|
805 +(% style="width:895.294px" %)
806 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
807 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
808 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
780 780  
781 781  **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
782 782  
783 783  Derivation:
784 784  
785 -//MessageType// (restriction)
786 - CodelistQueryType
814 +* //MessageType// (restriction)
815 +** CodelistQueryType
787 787  
788 788  Content:
789 789  
790 -Header, Query
819 +* Header, Query
820 +* Element Documentation:
791 791  
792 -Element Documentation:
822 +(% style="width:911.294px" %)
823 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
824 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
825 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
793 793  
794 -|**Name**|**Type**|**Documentation**
795 -|Header|BasicHeaderType|
796 -|Query|qry: CodelistQueryType|
797 -
798 798  **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
799 799  
800 800  Derivation:
801 801  
802 -//MessageType// (restriction)
803 - HierarchicalCodelistQueryType
831 +* //MessageType// (restriction)
832 +** HierarchicalCodelistQueryType
804 804  
805 805  Content:
806 806  
807 -Header, Query
836 +* Header, Query
837 +* Element Documentation:
808 808  
809 -Element Documentation:
839 +(% style="width:906.294px" %)
840 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
841 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
842 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
810 810  
811 -|**Name**|**Type**|**Documentation**
812 -|Header|BasicHeaderType|
813 -|Query|qry: HierarchicalCodelist QueryType|
814 -
815 815  **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
816 816  
817 817  Derivation:
818 818  
819 -//MessageType// (restriction)
820 - OrganisationSchemeQueryType
848 +* //MessageType// (restriction)
849 +** OrganisationSchemeQueryType
821 821  
822 822  Content:
823 823  
824 -Header, Query
853 +* Header, Query
854 +* Element Documentation:
825 825  
826 -Element Documentation:
856 +(% style="width:891.294px" %)
857 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
858 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
859 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
827 827  
828 -|**Name**|**Type**|**Documentation**
829 -|Header|BasicHeaderType|
830 -|Query|qry: OrganisationSchemeQu eryType|
831 -
832 832  **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
833 833  
834 834  Derivation:
835 835  
836 -//MessageType// (restriction)
837 - ReportingTaxonomyQueryType
865 +* //MessageType// (restriction)
866 +** ReportingTaxonomyQueryType
838 838  
839 839  Content:
840 840  
841 -Header, Query
870 +* Header, Query
871 +* Element Documentation:
842 842  
843 -Element Documentation:
873 +(% style="width:916.294px" %)
874 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
875 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
876 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
844 844  
845 -|**Name**|**Type**|**Documentation**
846 -|Header|BasicHeaderType|
847 -|Query|qry: ReportingTaxonomyQue ryType|
848 -
849 849  **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
850 850  
851 851  Derivation:
852 852  
853 -//MessageType// (restriction)
854 - StructureSetQueryType
882 +* //MessageType// (restriction)
883 +** StructureSetQueryType
855 855  
856 856  Content:
857 857  
858 -Header, Query
887 +* Header, Query
888 +* Element Documentation:
859 859  
860 -Element Documentation:
890 +(% style="width:896.294px" %)
891 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
892 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
893 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
861 861  
862 -|**Name**|**Type**|**Documentation**
863 -|Header|BasicHeaderType|
864 -|Query|qry: StructureSetQueryTyp e|
865 -
866 866  **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
867 867  
868 868  Derivation:
869 869  
870 -//MessageType// (restriction)
871 - ProcessQueryType
899 +* //MessageType// (restriction)
900 +** ProcessQueryType
872 872  
873 873  Content:
874 874  
875 -Header, Query
904 +* Header, Query
905 +* Element Documentation:
876 876  
877 -Element Documentation:
907 +(% style="width:907.294px" %)
908 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
909 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
910 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
878 878  
879 -|**Name**|**Type**|**Documentation**
880 -|Header|BasicHeaderType|
881 -|Query|qry:ProcessQueryType|
882 -
883 883  **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
884 884  
885 885  Derivation:
886 886  
887 -//MessageType// (restriction)
888 - CategorisationQueryType
916 +* //MessageType// (restriction)
917 +** CategorisationQueryType
889 889  
890 890  Content:
891 891  
892 -Header, Query
921 +* Header, Query
922 +* Element Documentation:
893 893  
894 -Element Documentation:
924 +(% style="width:897.294px" %)
925 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
926 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
927 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
895 895  
896 -|**Name**|**Type**|**Documentation**
897 -|Header|BasicHeaderType|
898 -|Query|qry: CategorisationQueryT ype|
899 -
900 900  **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
901 901  
902 902  Derivation:
903 903  
904 -//MessageType// (restriction)
905 - ProvisionAgreementQueryType
933 +* //MessageType// (restriction)
934 +** ProvisionAgreementQueryType
906 906  
907 907  Content:
908 908  
909 -Header, Query
938 +* Header, Query
939 +* Element Documentation:
910 910  
911 -Element Documentation:
941 +(% style="width:902.294px" %)
942 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
943 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
944 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
912 912  
913 -|**Name**|**Type**|**Documentation**
914 -|Header|BasicHeaderType|
915 -|Query|qry: ProvisionAgreementQu eryType|
916 -
917 917  **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
918 918  
919 919  Derivation:
920 920  
921 -//MessageType// (restriction)
922 - ConstraintQueryType
950 +* //MessageType// (restriction)
951 +** ConstraintQueryType
923 923  
924 924  Content:
925 925  
926 -Header, Query
955 +* Header, Query
956 +* Element Documentation:
927 927  
928 -Element Documentation:
958 +(% style="width:902.294px" %)
959 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
960 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
961 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
929 929  
930 -|**Name**|**Type**|**Documentation**
931 -|Header|BasicHeaderType|
932 -|Query|qry: ConstraintQueryType|
933 -
934 934  **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
935 935  
936 936  Derivation:
937 937  
938 -//MessageType// (restriction)
939 - TransformationSchemeQueryType
967 +* //MessageType// (restriction)
968 +** TransformationSchemeQueryType
940 940  
941 941  Content:
942 942  
943 -Header, Query
972 +* Header, Query
973 +* Element Documentation:
944 944  
945 -Element Documentation:
975 +(% style="width:833.294px" %)
976 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
977 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
978 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
946 946  
947 -|**Name**|**Type**|**Documentation**
948 -|Header|BasicHeaderType|
949 -|Query|qry: TransformationScheme QueryType|
950 -
951 951  **VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
952 952  
953 953  Derivation:
954 954  
955 -//MessageType// (restriction)
956 - VtlMappingSchemeQueryType
984 +* //MessageType// (restriction)
985 +** VtlMappingSchemeQueryType
957 957  
958 958  Content:
959 959  
960 -Header, Query
989 +* Header, Query
990 +* Element Documentation:
961 961  
962 -Element Documentation:
992 +(% style="width:843.294px" %)
993 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
994 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
995 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
963 963  
964 -|**Name**|**Type**|**Documentation**
965 -|Header|BasicHeaderType|
966 -|Query|qry: VtlMappingSchemeQuer yType|
967 -
968 968  **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
969 969  
970 970  Derivation:
971 971  
972 -//MessageType// (restriction)
973 - NamePersonalisationSchemeQueryType
1001 +* //MessageType// (restriction)
1002 +** NamePersonalisationSchemeQueryType
974 974  
975 975  Content:
976 976  
977 -Header, Query
1006 +* Header, Query
1007 +* Element Documentation:
978 978  
979 -Element Documentation:
1009 +(% style="width:895.294px" %)
1010 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
1011 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
1012 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
980 980  
981 -|**Name**|**Type**|**Documentation**
982 -|Header|BasicHeaderType|
983 -|Query|qry: NamePersonalisationS chemeQueryType|
984 -
985 985  **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
986 986  
987 987  Derivation:
988 988  
989 -//MessageType// (restriction)
990 - RulesetSchemeQueryType
1018 +* //MessageType// (restriction)
1019 +** RulesetSchemeQueryType
991 991  
992 992  Content:
993 993  
994 -Header, Query
1023 +* Header, Query
1024 +* Element Documentation:
995 995  
996 -Element Documentation:
1026 +(% style="width:886.294px" %)
1027 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
1028 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
1029 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
997 997  
998 -|**Name**|**Type**|**Documentation**
999 -|Header|BasicHeaderType|
1000 -|Query|qry: RulesetSchemeQueryTy pe|
1001 -
1002 1002  **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1003 1003  
1004 1004  Derivation:
1005 1005  
1006 -//MessageType// (restriction)
1007 - UserDefinedOperatorSchemeQueryType
1035 +* //MessageType// (restriction)
1036 +** UserDefinedOperatorSchemeQueryType
1008 1008  
1009 1009  Content:
1010 1010  
1011 -Header, Query
1040 +* Header, Query
1041 +* Element Documentation:
1012 1012  
1013 -Element Documentation:
1043 +(% style="width:866.294px" %)
1044 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1045 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1046 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
1014 1014  
1015 -|**Name**|**Type**|**Documentation**
1016 -|Header|BasicHeaderType|
1017 -|Query|qry: UserDefinedOperatorS chemeQueryType|
1018 -
1019 1019  **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1020 1020  
1021 1021  Derivation:
1022 1022  
1023 -//MessageType// (restriction)
1024 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1052 +* //MessageType// (restriction)
1053 +** CustomTypeSchemeQueryType
1025 1025  
1026 1026  Content:
1027 1027  
1028 -Header, Query
1057 +* Header, Query
1058 +* Element Documentation:
1029 1029  
1030 -Element Documentation:
1060 +(% style="width:828.294px" %)
1061 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1062 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1063 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
1031 1031  
1032 -|**Name**|**Type**|**Documentation**
1033 -|Header|BasicHeaderType|
1034 -|Query|qry: CustomTypeSchemeQuer yType|
1035 -
1036 1036  **ErrorType: **ErrorType describes the structure of an error response.
1037 1037  
1038 1038  Content:
1039 1039  
1040 -ErrorMessage+
1069 +* ErrorMessage+
1070 +* Element Documentation:
1041 1041  
1042 -Element Documentation:
1072 +(% style="width:899.294px" %)
1073 +|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1074 +|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.
1043 1043  
1044 -|**Name**|**Type**|**Documentation**
1045 -|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.
1046 -
1047 1047  **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1048 1048  
1049 1049  Content:
... ... @@ -1052,29 +1052,30 @@
1052 1052  
1053 1053  Element Documentation:
1054 1054  
1055 -|**Name**|**Type**|**Documentation**
1056 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1057 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1058 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1059 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1060 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1061 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1062 -|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.
1063 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1064 -|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).
1065 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1066 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1067 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1068 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1069 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1070 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1084 +(% style="width:891.294px" %)
1085 +|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1086 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1087 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1088 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1089 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1090 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1091 +|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1092 +|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.
1093 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1094 +|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).
1095 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1096 +|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1097 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1098 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1099 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1100 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1071 1071  
1072 1072  **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1073 1073  
1074 1074  Derivation:
1075 1075  
1076 -//BaseHeaderType// (restriction)
1077 - StructureHeaderType
1106 +* //BaseHeaderType// (restriction)
1107 +** StructureHeaderType
1078 1078  
1079 1079  Content:
1080 1080  
... ... @@ -1082,21 +1082,22 @@
1082 1082  
1083 1083  Element Documentation:
1084 1084  
1085 -|**Name**|**Type**|**Documentation**
1086 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1087 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1088 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1089 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1090 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1091 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1092 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1115 +(% style="width:1099.29px" %)
1116 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1117 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1118 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1119 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1120 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1121 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1122 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1123 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
1093 1093  
1094 1094  **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1095 1095  
1096 1096  Derivation:
1097 1097  
1098 -//BaseHeaderType// (restriction)
1099 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1129 +* //BaseHeaderType// (restriction)
1130 +** GenericDataHeaderType
1100 1100  
1101 1101  Content:
1102 1102  
... ... @@ -1104,30 +1104,31 @@
1104 1104  
1105 1105  Element Documentation:
1106 1106  
1107 -|**Name**|**Type**|**Documentation**
1108 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1109 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1110 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1111 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1112 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1113 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1114 -|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.
1115 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1116 -|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).
1117 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1118 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1119 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1120 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1121 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1122 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1138 +(% style="width:895.294px" %)
1139 +|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1140 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1141 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1142 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1143 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1144 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1145 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1146 +|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.
1147 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1148 +|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).
1149 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1150 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1151 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1152 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1153 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1154 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1123 1123  
1124 1124  **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1125 1125  
1126 1126  Derivation:
1127 1127  
1128 -//BaseHeaderType// (restriction)
1129 - GenericDataHeaderType (restriction)
1130 - GenericTimeSeriesDataHeaderType
1160 +* //BaseHeaderType// (restriction)
1161 +** GenericDataHeaderType (restriction)
1162 +*** GenericTimeSeriesDataHeaderType
1131 1131  
1132 1132  Content:
1133 1133  
... ... @@ -1135,29 +1135,30 @@
1135 1135  
1136 1136  Element Documentation:
1137 1137  
1138 -|**Name**|**Type**|**Documentation**
1139 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1140 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1141 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1142 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1143 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1144 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1145 -|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.
1146 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1147 -|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).
1148 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1149 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1150 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1151 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1152 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1153 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1170 +(% style="width:926.294px" %)
1171 +|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1172 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1173 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1174 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1175 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1176 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1177 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1178 +|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.
1179 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1180 +|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).
1181 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1182 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1183 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1184 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1185 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1186 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1154 1154  
1155 1155  **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1156 1156  
1157 1157  Derivation:
1158 1158  
1159 -//BaseHeaderType// (restriction)
1160 - StructureSpecificDataHeaderType
1192 +* //BaseHeaderType// (restriction)
1193 +** StructureSpecificDataHeaderType
1161 1161  
1162 1162  Content:
1163 1163  
... ... @@ -1165,30 +1165,31 @@
1165 1165  
1166 1166  Element Documentation:
1167 1167  
1168 -|**Name**|**Type**|**Documentation**
1169 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1170 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1171 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1172 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1173 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1174 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1175 -|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.
1176 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1177 -|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).
1178 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1179 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1180 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1181 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1182 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1183 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1201 +(% style="width:930.294px" %)
1202 +|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1203 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1204 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1205 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1206 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1207 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1208 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1209 +|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.
1210 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1211 +|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).
1212 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1213 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1214 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1215 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1216 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1217 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1184 1184  
1185 1185  **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1186 1186  
1187 1187  Derivation:
1188 1188  
1189 -//BaseHeaderType// (restriction)
1190 - StructureSpecificDataHeaderType (restriction)
1191 - StructureSpecificTimeSeriesDataHeaderType
1223 +* //BaseHeaderType// (restriction)
1224 +** StructureSpecificDataHeaderType (restriction)
1225 +*** StructureSpecificTimeSeriesDataHeaderType
1192 1192  
1193 1193  Content:
1194 1194  
... ... @@ -1196,29 +1196,30 @@
1196 1196  
1197 1197  Element Documentation:
1198 1198  
1199 -|**Name**|**Type**|**Documentation**
1200 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1201 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1202 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1203 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1204 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1205 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1206 -|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.
1207 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1208 -|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).
1209 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1210 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1211 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1212 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1213 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1214 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1233 +(% style="width:943.294px" %)
1234 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1235 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1236 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1237 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1238 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1239 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1240 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1241 +|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.
1242 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1243 +|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).
1244 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1245 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1246 +|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).
1247 +|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).
1248 +|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.
1249 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1215 1215  
1216 1216  **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1217 1217  
1218 1218  Derivation:
1219 1219  
1220 -//BaseHeaderType// (restriction)
1221 - GenericMetadataHeaderType
1255 +* //BaseHeaderType// (restriction)
1256 +** GenericMetadataHeaderType
1222 1222  
1223 1223  Content:
1224 1224  
... ... @@ -1226,26 +1226,27 @@
1226 1226  
1227 1227  Element Documentation:
1228 1228  
1229 -|**Name**|**Type**|**Documentation**
1230 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1231 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1232 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1233 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1234 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1235 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1236 -|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.
1237 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1238 -|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).
1239 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1240 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1241 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1264 +(% style="width:928.294px" %)
1265 +|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1266 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1267 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1268 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1269 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1270 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1271 +|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1272 +|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.
1273 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1274 +|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).
1275 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1276 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1277 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1242 1242  
1243 1243  **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1244 1244  
1245 1245  Derivation:
1246 1246  
1247 -//BaseHeaderType// (restriction)
1248 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1283 +* //BaseHeaderType// (restriction)
1284 +** StructureSpecificMetadataHeaderType
1249 1249  
1250 1250  Content:
1251 1251  
... ... @@ -1253,26 +1253,27 @@
1253 1253  
1254 1254  Element Documentation:
1255 1255  
1256 -|**Name**|**Type**|**Documentation**
1257 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1258 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1259 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1260 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1261 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1262 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1263 -|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.
1264 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1265 -|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).
1266 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1267 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1268 -|Source|com:TextType|Source provides human-readable information about the source of the data.
1292 +(% style="width:996.294px" %)
1293 +|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1294 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1295 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1296 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1297 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1298 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1299 +|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1300 +|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.
1301 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1302 +|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).
1303 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
1304 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1305 +|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1269 1269  
1270 1270  **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1271 1271  
1272 1272  Derivation:
1273 1273  
1274 -//BaseHeaderType// (restriction)
1275 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1311 +* //BaseHeaderType// (restriction)
1312 +** BasicHeaderType
1276 1276  
1277 1277  Content:
1278 1278  
... ... @@ -1280,12 +1280,13 @@
1280 1280  
1281 1281  Element Documentation:
1282 1282  
1283 -|**Name**|**Type**|**Documentation**
1284 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1285 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1286 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1287 -|Sender|SenderType|Sender is information about the party that is transmitting the message.
1288 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1320 +(% style="width:903.294px" %)
1321 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1322 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1323 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1324 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1325 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1326 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
1289 1289  
1290 1290  **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1291 1291  
... ... @@ -1299,21 +1299,23 @@
1299 1299  
1300 1300  Attribute Documentation:
1301 1301  
1302 -|**Name**|**Type**|**Documentation**
1303 -|id|com:IDType|The id attribute holds the identification of the party.
1340 +(% style="width:739.294px" %)
1341 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
1342 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
1304 1304  
1305 1305  Element Documentation:
1306 1306  
1307 -|**Name**|**Type**|**Documentation**
1308 -|com:Name|com:TextType|Name is a human-readable name of the party.
1309 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1346 +(% style="width:751.294px" %)
1347 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
1348 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
1349 +|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message.
1310 1310  
1311 1311  **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1312 1312  
1313 1313  Derivation:
1314 1314  
1315 -PartyType (extension)
1316 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1355 +* PartyType (extension)
1356 +** SenderType
1317 1317  
1318 1318  Attributes:
1319 1319  
... ... @@ -1325,8 +1325,9 @@
1325 1325  
1326 1326  Attribute Documentation:
1327 1327  
1328 -|**Name**|**Type**|**Documentation**
1329 -|id|com:IDType|The id attribute holds the identification of the party.
1368 +(% style="width:824.294px" %)
1369 +|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
1370 +|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
1330 1330  
1331 1331  Element Documentation:
1332 1332  
... ... @@ -1353,8 +1353,8 @@
1353 1353  |URI|xs:anyURI|URI holds an information URL for the contact person.
1354 1354  |Email|xs:string|Email holds the email address for the contact person.
1355 1355  
1356 -1.
1357 -11.
1397 +1.
1398 +11.
1358 1358  111. Simple Types
1359 1359  
1360 1360  **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
... ... @@ -1363,13 +1363,13 @@
1363 1363  
1364 1364  xs:dateTime, xs:date.
1365 1365  
1366 -1.
1407 +1.
1367 1367  11. Message Footer Namespace
1368 1368  
1369 1369  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1370 1370  
1371 -1.
1372 -11.
1412 +1.
1413 +11.
1373 1373  111. Summary
1374 1374  
1375 1375  Referenced Namespaces:
... ... @@ -1384,14 +1384,14 @@
1384 1384  2 Complex Types
1385 1385  1 Simple Type
1386 1386  
1387 -1.
1388 -11.
1428 +1.
1429 +11.
1389 1389  111. Global Elements
1390 1390  
1391 1391  **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1392 1392  
1393 -1.
1394 -11.
1434 +1.
1435 +11.
1395 1395  111. Complex Types
1396 1396  
1397 1397  **FooterType: **FooterType describes the structure of a message footer. The footer is used to convey any error, information, or warning messages. This is to be used when the message has payload, but also needs to communicate additional information. If an error occurs and no payload is generated, an Error message should be returned.
... ... @@ -1410,8 +1410,8 @@
1410 1410  Derivation:
1411 1411  
1412 1412  com:StatusMessageType (restriction)
1413 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1414 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1454 +[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1455 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1415 1415  
1416 1416  Attributes:
1417 1417  
... ... @@ -1432,8 +1432,8 @@
1432 1432  |**Name**|**Type**|**Documentation**
1433 1433  |com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1434 1434  
1435 -1.
1436 -11.
1476 +1.
1477 +11.
1437 1437  111. Simple Types
1438 1438  
1439 1439  **SeverityCodeType:**