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 7.5
edited by Helena
on 2025/06/30 22:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Attribute|Category scheme|Code|Code list|Concept scheme|Contact phone number|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchical code list|Metadata set|Metadata structure definition|Metadataflow|Notification|Provision agreement|Reference metadata|Reference period|Reporting taxonomy|SDMX Registry|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Structure set|Subscription|Time period|Validation and transformation language
Content
... ... @@ -8,7 +8,7 @@
8 8  
9 9  **~1. Problem**
10 10  
11 -Various parts of the the documentation refer to stand-alone concepts, which were part of earlier draft releases but ultimately excluded from the final release of the standard.
11 +Various parts of the the documentation refer to stand-alone (% style="color:#e74c3c" %)concepts(%%), which were part of earlier draft releases but ultimately excluded from the final release of the standard.
12 12  
13 13  **Rectification**
14 14  
... ... @@ -16,11 +16,11 @@
16 16  
17 17  = 1. Introduction =
18 18  
19 -At the core of the SDMX XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in SDMX.
19 +At the core of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
20 20  
21 -There are two namespaces associated with the messages. The main namespace schema which defines every message in SDMX is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted.
21 +There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer (% style="color:#e74c3c" %)level(%%) information that is available in messages which might require non-standard payload information to be transmitted.
22 22  
23 -In general, every message in SDMX follows common format of:
23 +In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of:
24 24  
25 25  * Header
26 26  * Payload (0..n)
... ... @@ -52,7 +52,6 @@
52 52  |(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs
53 53  
54 54  Contents:
55 -
56 56  50 Global Elements
57 57  62 Complex Types
58 58  1 Simple Type
... ... @@ -59,103 +59,103 @@
59 59  
60 60  === 2.1.2 Global Elements ===
61 61  
62 -**Structure (StructureType): **Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), constraints (attachment and content) data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, and structure sets.
61 +**Structure (StructureType): **Structure is a message that contains [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. It may contain any of the following; categorisations, [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) ([[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]), (% style="color:#e74c3c" %)constraints(%%) (attachment and content) [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], organisation schemes, processes, [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]], and structure sets.
63 63  
64 -**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. Data sets in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation dimension).
63 +**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. [[Data sets>>doc:sdmx:Glossary.Data set.WebHome]] in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]).
65 65  
66 -**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
65 +**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
67 67  
68 -**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to data structure definition. The payload of this message (i.e. the data sets) will be based on XML schemas which are specific to the data structure definition and the orientation (i.e. the observation dimension) of the data.
67 +**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The payload of this message (i.e. the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]) will be based on XML schemas which are specific to the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and the orientation (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data.
69 69  
70 -**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
69 +**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
71 71  
72 -**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
71 +**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
73 73  
74 -**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the metadata structure definitions which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each metadata set provided will be based on a metadata structure specific schema.
73 +**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] provided will be based on a metadata structure specific schema.
75 75  
76 -**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
75 +**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services.
77 77  
78 -**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on 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.
77 +**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
79 79  
80 80  **SubmitRegistrationsResponse (SubmitRegistrationsResponseType): **SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a registration requests. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
81 81  
82 -**QueryRegistrationRequest (QueryRegistrationRequestType): **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.
81 +**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
83 83  
84 84  **QueryRegistrationResponse (QueryRegistrationResponseType): **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.
85 85  
86 -**SubmitStructureRequest (SubmitStructureRequestType): **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.
85 +**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
87 87  
88 88  **SubmitStructureResponse (SubmitStructureResponseType): **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.
89 89  
90 90  **SubmitSubscriptionsRequest (SubmitSubscriptionsRequestType): **SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
91 91  
92 -**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **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.
91 +**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
93 93  
94 -**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
93 +**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
95 95  
96 -**QuerySubscriptionResponse (QuerySubscriptionResponseType): **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.
95 +**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
97 97  
98 -**NotifyRegistryEvent (NotifyRegistryEventType): **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.
97 +**NotifyRegistryEvent (NotifyRegistryEventType): **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>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
99 99  
100 -**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data.
99 +**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure specific data.
101 101  
102 -**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query SDMX compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
101 +**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
103 103  
104 -**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
103 +**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
105 105  
106 -**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
105 +**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
107 107  
108 -**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata.
107 +**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic format [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
109 109  
110 -**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata.
109 +**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
111 111  
112 -**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query SDMX compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
111 +**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
113 113  
114 -**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query SDMX compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
113 +**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
115 115  
116 -**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query SDMX compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
115 +**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
117 117  
118 -**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows.
117 +**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for dataflows.
119 119  
120 -**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows.
119 +**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]].
121 121  
122 -**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions.
121 +**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structures definitions.
123 123  
124 -**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions.
123 +**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
125 125  
126 -**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes.
125 +**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]].
127 127  
128 -**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes.
127 +**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]].
129 129  
130 -**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists.
129 +**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for codelists.
131 131  
132 -**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists.
131 +**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for hierarchical codelists.
133 133  
134 -**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes.
133 +**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for organisation schemes.
135 135  
136 -**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies.
135 +**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]].
137 137  
138 -**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets.
137 +**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure sets.
139 139  
140 -**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes.
139 +**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for processes.
141 141  
142 -**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations.
141 +**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for categorisations.
143 143  
144 -**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements.
143 +**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for provision agreements.
145 145  
146 -**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints.
145 +**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for (% style="color:#e74c3c" %)constraints(%%).
147 147  
148 -**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes.
147 +**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for transformation schemes.
149 149  
150 -**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes.
149 +**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes.
151 151  
152 -**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes.
151 +**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for name personalisation schemes.
153 153  
154 -**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes.
153 +**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for ruleset schemes.
155 155  
156 -**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes.
155 +**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for user defined schemes.
157 157  
158 -**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes.
157 +**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for custom type schemes.
159 159  
160 160  **Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages.
161 161  
... ... @@ -169,19 +169,19 @@
169 169  
170 170  Element Documentation:
171 171  
172 -|**Name**|**Type**|**Documentation**
173 -|Header|//BaseHeaderType//|
174 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
171 +(% style="width:1004.83px" %)
172 +|**Name**|**Type**|(% style="width:631px" %)**Documentation**
173 +|Header|//BaseHeaderType//|(% style="width:631px" %)
174 +|ftr:Footer|ftr:FooterType|(% style="width:631px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
175 175  
176 176  **StructureType: **StructureType defines the contents of a structure message. The payload is optional since this message may be returned from a web service with only information in the footer.
177 177  
178 178  Derivation:
179 179  
180 -//MessageType// (restriction)
181 - StructureType
180 +* //MessageType// (restriction)
181 +** StructureType
182 182  
183 183  Content:
184 -
185 185  Header, Structures?, ftr:Footer?
186 186  
187 187  Element Documentation:
... ... @@ -196,19 +196,18 @@
196 196  
197 197  Derivation:
198 198  
199 -//MessageType// (restriction)
200 - GenericDataType
198 +* //MessageType// (restriction)
199 +** GenericDataType
201 201  
202 202  Content:
202 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
203 203  
204 -Header, DataSet*, ftr:Footer?
205 -
206 206  Element Documentation:
207 207  
208 208  (% style="width:847.294px" %)
209 209  |**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation**
210 210  |Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %)
211 -|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
209 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
212 212  |ftr:Footer|(% style="width:227px" %)ftr:FooterType|(% style="width:450px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
213 213  
214 214  **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
... ... @@ -220,18 +220,17 @@
220 220  *** GenericTimeSeriesDataType
221 221  
222 222  Content:
221 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
223 223  
224 -Header, DataSet*, ftr:Footer?
225 -
226 226  Element Documentation:
227 227  
228 228  (% style="width:856.294px" %)
229 229  |**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation**
230 230  |Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %)
231 -|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
228 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
232 232  |ftr:Footer|(% style="width:239px" %)ftr:FooterType|(% style="width:458px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
233 233  
234 -**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data 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.
231 +**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] 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.
235 235  
236 236  Derivation:
237 237  
... ... @@ -239,15 +239,14 @@
239 239  ** StructureSpecificDataType
240 240  
241 241  Content:
239 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
242 242  
243 -Header, DataSet*, ftr:Footer?
244 -
245 245  Element Documentation:
246 246  
247 247  (% style="width:828.294px" %)
248 248  |**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation**
249 249  |Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %)
250 -|DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
246 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
251 251  |ftr:Footer|(% style="width:247px" %)ftr:FooterType|(% style="width:420px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
252 252  
253 253  **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
... ... @@ -259,1033 +259,1033 @@
259 259  *** StructureSpecificTimeSeriesDataType
260 260  
261 261  Content:
258 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
262 262  
263 -Header, DataSet*, ftr:Footer?
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.
262 +(% style="width:839.294px" %)
263 +|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
264 +|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
265 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
266 +|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
272 +* //MessageType// (restriction)
273 +** GenericMetadataType
278 278  
279 279  Content:
280 -
281 281  Header, MetadataSet*, ftr:Footer?
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.
280 +(% style="width:836.294px" %)
281 +|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
282 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeaderType|(% style="width:427px" %)
283 +|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
284 +|(% 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 -**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.
286 +**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] 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
290 +* //MessageType// (restriction)
291 +** StructureSpecificMetadataType
296 296  
297 297  Content:
298 -
299 299  Header, MetadataSet*, ftr:Footer?
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.
298 +(% style="width:841.294px" %)
299 +|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
300 +|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMetadataHeaderType|(% style="width:428px" %)
301 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
302 +|(% 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
308 +* //MessageType// (restriction)
309 +** RegistryInterfaceType
314 314  
315 315  Content:
316 -
317 317  Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, ftr:Footer?
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.
316 +(% style="width:1000.83px" %)
317 +|**Name**|(% style="width:317px" %)**Type**|(% style="width:491px" %)**Documentation**
318 +|Header|(% style="width:317px" %)BasicHeaderType|(% style="width:491px" %)
319 +|SubmitRegistrationsRequest|(% style="width:317px" %)ref: SubmitRegistrationsRequestType|(% style="width:491px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
320 +|SubmitRegistrationsResponse|(% style="width:317px" %)ref: SubmitRegistrationsResponseType|(% style="width:491px" %)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.
321 +|QueryRegistrationRequest|(% style="width:317px" %)ref: QueryRegistrationRequestType|(% style="width:491px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
322 +|QueryRegistrationResponse|(% style="width:317px" %)ref: QueryRegistrationResponseType|(% style="width:491px" %)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.
323 +|SubmitStructureRequest|(% style="width:317px" %)ref: SubmitStructureRequestType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
324 +|SubmitStructureResponse|(% style="width:317px" %)ref: SubmitStructureResponseType|(% style="width:491px" %)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.
325 +|SubmitSubscriptionsRequest|(% style="width:317px" %)ref: SubmitSubscriptionsRequestType|(% style="width:491px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
326 +|SubmitSubscriptionsResponse|(% style="width:317px" %)ref: SubmitSubscriptionsResponseType|(% style="width:491px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
327 +|QuerySubscriptionRequest|(% style="width:317px" %)ref: QuerySubscriptionRequestType|(% style="width:491px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
328 +|QuerySubscriptionResponse|(% style="width:317px" %)ref: QuerySubscriptionResponseType|(% style="width:491px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
329 +|NotifyRegistryEvent|(% style="width:317px" %)ref: NotifyRegistryEventType|(% style="width:491px" %)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>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
330 +|ftr:Footer|(% style="width:317px" %)ftr:FooterType|(% style="width:491px" %)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
336 +* //MessageType// (restriction)
337 +** RegistryInterfaceType (restriction)
338 +*** SubmitRegistrationsRequestType
343 343  
344 344  Content:
345 -
346 346  Header, SubmitRegistrationsRequest
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.
345 +(% style="width:966.835px" %)
346 +|**Name**|**Type**|(% style="width:490px" %)**Documentation**
347 +|Header|BasicHeaderType|(% style="width:490px" %)
348 +|SubmitRegistrationsRequest|ref: SubmitRegistrationsRequestType|(% style="width:490px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] 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
354 +* //MessageType// (restriction)
355 +** RegistryInterfaceType (restriction)
356 +*** SubmitRegistrationsResponseType
361 361  
362 362  Content:
363 -
364 364  Header, SubmitRegistrationsResponse, ftr:Footer?
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.
363 +(% style="width:974.835px" %)
364 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:473px" %)**Documentation**
365 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:473px" %)
366 +|SubmitRegistrationsResponse|(% style="width:210px" %)ref: SubmitRegistrationsResponseType|(% style="width:473px" %)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.
367 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:473px" %)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
373 +* //MessageType// (restriction)
374 +** RegistryInterfaceType (restriction)
375 +*** QueryRegistrationRequestType
380 380  
381 381  Content:
382 -
383 383  Header, QueryRegistrationRequest
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.
382 +(% style="width:971.835px" %)
383 +|**Name**|(% style="width:288px" %)**Type**|(% style="width:476px" %)**Documentation**
384 +|Header|(% style="width:288px" %)BasicHeaderType|(% style="width:476px" %)
385 +|QueryRegistrationRequest|(% style="width:288px" %)ref: QueryRegistrationRequestType|(% style="width:476px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], 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
391 +* //MessageType// (restriction)
392 +** RegistryInterfaceType (restriction)
393 +*** QueryRegistrationResponseType
398 398  
399 399  Content:
400 -
401 401  Header, QueryRegistrationResponse, ftr:Footer?
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.
400 +(% style="width:969.835px" %)
401 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:496px" %)**Documentation**
402 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:496px" %)
403 +|QueryRegistrationResponse|(% style="width:235px" %)ref: QueryRegistrationResponseType|(% style="width:496px" %)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.
404 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:496px" %)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
410 +* //MessageType// (restriction)
411 +** RegistryInterfaceType (restriction)
412 +*** SubmitStructureRequestType
417 417  
418 418  Content:
419 -
420 420  Header, SubmitStructureRequest
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.
419 +(% style="width:970.835px" %)
420 +|**Name**|(% style="width:286px" %)**Type**|(% style="width:491px" %)**Documentation**
421 +|Header|(% style="width:286px" %)BasicHeaderType|(% style="width:491px" %)
422 +|SubmitStructureRequest|(% style="width:286px" %)ref: SubmitStructureRequestType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] 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
428 +* //MessageType// (restriction)
429 +** RegistryInterfaceType (restriction)
430 +*** SubmitStructureResponseType
435 435  
436 436  Content:
437 -
438 438  Header, SubmitStructureResponse, ftr:Footer?
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.
437 +(% style="width:969.835px" %)
438 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:498px" %)**Documentation**
439 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:498px" %)
440 +|SubmitStructureResponse|(% style="width:246px" %)ref: SubmitStructureResponseType|(% style="width:498px" %)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.
441 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:498px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
446 446  
447 -**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
443 +**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] 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
447 +* //MessageType// (restriction)
448 +** RegistryInterfaceType (restriction)
449 +*** SubmitSubscriptionsRequestType
454 454  
455 455  Content:
456 -
457 457  Header, SubmitSubscriptionsRequest
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.
456 +(% style="width:960.835px" %)
457 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:445px" %)**Documentation**
458 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:445px" %)
459 +|SubmitSubscriptionsRequest|(% style="width:227px" %)ref: SubmitSubscriptionsRequestType|(% style="width:445px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
464 464  
465 -**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
461 +**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] 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
465 +* //MessageType// (restriction)
466 +** RegistryInterfaceType (restriction)
467 +*** SubmitSubscriptionsResponseType
472 472  
473 473  Content:
474 -
475 475  Header, SubmitSubscriptionsResponse, ftr:Footer?
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.
474 +(% style="width:965.835px" %)
475 +|**Name**|**Type**|(% style="width:482px" %)**Documentation**
476 +|Header|BasicHeaderType|(% style="width:482px" %)
477 +|SubmitSubscriptionsResponse|ref: SubmitSubscriptionsResponseType|(% style="width:482px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
478 +|ftr:Footer|ftr:FooterType|(% style="width:482px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
483 483  
484 -**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
480 +**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] 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
484 +* //MessageType// (restriction)
485 +** RegistryInterfaceType (restriction)
486 +*** QuerySubscriptionRequestType
491 491  
492 492  Content:
493 -
494 494  Header, QuerySubscriptionRequest
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.
493 +(% style="width:970.835px" %)
494 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:483px" %)**Documentation**
495 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:483px" %)
496 +|(% style="width:230px" %)QuerySubscriptionRequest|(% style="width:254px" %)ref: QuerySubscriptionRequestType|(% style="width:483px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
501 501  
502 -**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
498 +**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] 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
502 +* //MessageType// (restriction)
503 +** RegistryInterfaceType (restriction)
504 +*** QuerySubscriptionResponseType
509 509  
510 510  Content:
511 -
512 512  Header, QuerySubscriptionResponse, ftr:Footer?
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.
511 +(% style="width:973.835px" %)
512 +|(% style="width:233px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:443px" %)**Documentation**
513 +|(% style="width:233px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:443px" %)
514 +|(% style="width:233px" %)QuerySubscriptionResponse|(% style="width:295px" %)ref: QuerySubscriptionResponseType|(% style="width:443px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
515 +|(% style="width:233px" %)ftr:Footer|(% style="width:295px" %)ftr:FooterType|(% style="width:443px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
520 520  
521 -**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
517 +**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document.
522 522  
523 523  Derivation:
524 524  
525 -//MessageType// (restriction)
526 - RegistryInterfaceType (restriction)
527 - NotifyRegistryEventType
521 +* //MessageType// (restriction)
522 +** RegistryInterfaceType (restriction)
523 +*** NotifyRegistryEventType
528 528  
529 529  Content:
530 -
531 531  Header, NotifyRegistryEvent
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.
530 +(% style="width:836.294px" %)
531 +|**Name**|**Type**|(% style="width:473px" %)**Documentation**
532 +|Header|BasicHeaderType|(% style="width:473px" %)
533 +|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>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] 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
539 +* //MessageType// (restriction)
540 +** DataQueryType
545 545  
546 546  Content:
547 -
548 548  Header, Query
549 549  
550 550  Element Documentation:
551 551  
552 -|**Name**|**Type**|**Documentation**
553 -|Header|BasicHeaderType|
554 -|Query|qry:DataQueryType|
547 +(% style="width:839.294px" %)
548 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation**
549 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %)
550 +|(% 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
556 +* //MessageType// (restriction)
557 +** DataQueryType (restriction)
558 +*** GenericDataQueryType
563 563  
564 564  Content:
565 -
566 566  Header, Query
567 567  
568 568  Element Documentation:
569 569  
570 -|**Name**|**Type**|**Documentation**
571 -|Header|BasicHeaderType|
572 -|Query|qry: GenericDataQueryType|
565 +(% style="width:833.294px" %)
566 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation**
567 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %)
568 +|(% 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
574 +* //MessageType// (restriction)
575 +** DataQueryType (restriction)
576 +*** GenericDataQueryType (restriction)
577 +**** GenericTimeSeriesDataQueryType
582 582  
583 583  Content:
584 -
585 585  Header, Query
586 586  
587 587  Element Documentation:
588 588  
589 -|**Name**|**Type**|**Documentation**
590 -|Header|BasicHeaderType|
591 -|Query|qry: GenericTimeSeriesDat aQueryType|
584 +(% style="width:909.294px" %)
585 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation**
586 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %)
587 +|(% 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
593 +* //MessageType// (restriction)
594 +** DataQueryType (restriction)
595 +*** StructureSpecificTimeSeriesDataQueryType
600 600  
601 601  Content:
602 -
603 603  Header, Query
604 604  
605 605  Element Documentation:
606 606  
607 -|**Name**|**Type**|**Documentation**
608 -|Header|BasicHeaderType|
609 -|Query|qry: TimeSeriesDataQueryT ype|
602 +(% style="width:903.294px" %)
603 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation**
604 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
605 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
610 610  
611 -**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
607 +**MetadataQueryType: **MetadataQueryType defines the structure of a [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] query message.
612 612  
613 613  Derivation:
614 614  
615 -//MessageType// (restriction)
616 - MetadataQueryType
611 +* //MessageType// (restriction)
612 +** MetadataQueryType
617 617  
618 618  Content:
619 -
620 620  Header, Query
621 621  
622 622  Element Documentation:
623 623  
624 -|**Name**|**Type**|**Documentation**
625 -|Header|BasicHeaderType|
626 -|Query|qry: MetadataQueryType|
619 +(% style="width:858.294px" %)
620 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation**
621 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %)
622 +|(% 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
628 +* //MessageType// (restriction)
629 +** DataSchemaQueryType
634 634  
635 635  Content:
636 -
637 637  Header, Query
638 638  
639 639  Element Documentation:
640 640  
641 -|**Name**|**Type**|**Documentation**
642 -|Header|BasicHeaderType|
643 -|Query|qry: DataSchemaQueryType|
636 +(% style="width:895.294px" %)
637 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation**
638 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %)
639 +|(% 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
645 +* //MessageType// (restriction)
646 +** MetadataSchemaQueryType
651 651  
652 652  Content:
653 -
654 654  Header, Query
655 655  
656 656  Element Documentation:
657 657  
658 -|**Name**|**Type**|**Documentation**
659 -|Header|BasicHeaderType|
660 -|Query|qry: MetadataSchemaQueryT ype|
653 +(% style="width:897.294px" %)
654 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation**
655 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %)
656 +|(% 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
662 +* //MessageType// (restriction)
663 +** StructuresQueryType
668 668  
669 669  Content:
670 -
671 671  Header, Query
672 672  
673 673  Element Documentation:
674 674  
675 -|**Name**|**Type**|**Documentation**
676 -|Header|BasicHeaderType|
677 -|Query|qry: StructuresQueryType|
670 +(% style="width:886.294px" %)
671 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation**
672 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
673 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
678 678  
679 -**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
675 +**DataflowQueryType: **DataflowQueryType defines the structure of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] query message.
680 680  
681 681  Derivation:
682 682  
683 -//MessageType// (restriction)
684 - DataflowQueryType
679 +* //MessageType// (restriction)
680 +** DataflowQueryType
685 685  
686 686  Content:
687 -
688 688  Header, Query
689 689  
690 690  Element Documentation:
691 691  
692 -|**Name**|**Type**|**Documentation**
693 -|Header|BasicHeaderType|
694 -|Query|qry: DataflowQueryType|
687 +(% style="width:888.294px" %)
688 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation**
689 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
690 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
695 695  
696 -**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
692 +**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] query message.
697 697  
698 698  Derivation:
699 699  
700 -//MessageType// (restriction)
701 - MetadataflowQueryType
696 +* //MessageType// (restriction)
697 +** MetadataflowQueryType
702 702  
703 703  Content:
704 -
705 705  Header, Query
706 706  
707 707  Element Documentation:
708 708  
709 -|**Name**|**Type**|**Documentation**
710 -|Header|BasicHeaderType|
711 -|Query|qry: MetadataflowQueryTyp e|
704 +(% style="width:886.294px" %)
705 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation**
706 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %)
707 +|(% 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
713 +* //MessageType// (restriction)
714 +** DataStructureQueryType
719 719  
720 720  Content:
721 -
722 722  Header, Query
723 723  
724 724  Element Documentation:
725 725  
726 -|**Name**|**Type**|**Documentation**
727 -|Header|BasicHeaderType|
728 -|Query|qry: DataStructureQueryTy pe|
721 +(% style="width:901.294px" %)
722 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation**
723 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %)
724 +|(% 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
730 +* //MessageType// (restriction)
731 +** MetadataStructureQueryType
736 736  
737 737  Content:
738 -
739 739  Header, Query
740 740  
741 741  Element Documentation:
742 742  
743 -|**Name**|**Type**|**Documentation**
744 -|Header|BasicHeaderType|
745 -|Query|qry: MetadataStructureQue ryType|
738 +(% style="width:904.294px" %)
739 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation**
740 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
741 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
746 746  
747 -**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
743 +**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] query message.
748 748  
749 749  Derivation:
750 750  
751 -//MessageType// (restriction)
752 - CategorySchemeQueryType
747 +* //MessageType// (restriction)
748 +** CategorySchemeQueryType
753 753  
754 754  Content:
755 -
756 756  Header, Query
757 757  
758 758  Element Documentation:
759 759  
760 -|**Name**|**Type**|**Documentation**
761 -|Header|BasicHeaderType|
762 -|Query|qry: CategorySchemeQueryT ype|
755 +(% style="width:915.294px" %)
756 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation**
757 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
758 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
763 763  
764 -**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
760 +**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] query message.
765 765  
766 766  Derivation:
767 767  
768 -//MessageType// (restriction)
769 - ConceptSchemeQueryType
764 +* //MessageType// (restriction)
765 +** ConceptSchemeQueryType
770 770  
771 771  Content:
772 -
773 773  Header, Query
774 774  
775 775  Element Documentation:
776 776  
777 -|**Name**|**Type**|**Documentation**
778 -|Header|BasicHeaderType|
779 -|Query|qry: ConceptSchemeQueryTy pe|
772 +(% style="width:895.294px" %)
773 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation**
774 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
775 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
780 780  
781 -**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
777 +**CodelistQueryType: **CodelistQueryType defines the structure of a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
782 782  
783 783  Derivation:
784 784  
785 -//MessageType// (restriction)
786 - CodelistQueryType
781 +* //MessageType// (restriction)
782 +** CodelistQueryType
787 787  
788 788  Content:
789 -
790 790  Header, Query
791 791  
792 792  Element Documentation:
793 793  
794 -|**Name**|**Type**|**Documentation**
795 -|Header|BasicHeaderType|
796 -|Query|qry: CodelistQueryType|
789 +(% style="width:911.294px" %)
790 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
791 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
792 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
797 797  
798 -**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
794 +**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
799 799  
800 800  Derivation:
801 801  
802 -//MessageType// (restriction)
803 - HierarchicalCodelistQueryType
798 +* //MessageType// (restriction)
799 +** HierarchicalCodelistQueryType
804 804  
805 805  Content:
806 -
807 807  Header, Query
808 808  
809 809  Element Documentation:
810 810  
811 -|**Name**|**Type**|**Documentation**
812 -|Header|BasicHeaderType|
813 -|Query|qry: HierarchicalCodelist QueryType|
806 +(% style="width:906.294px" %)
807 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
808 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %)
809 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %)
814 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
815 +* //MessageType// (restriction)
816 +** OrganisationSchemeQueryType
821 821  
822 822  Content:
823 -
824 824  Header, Query
825 825  
826 826  Element Documentation:
827 827  
828 -|**Name**|**Type**|**Documentation**
829 -|Header|BasicHeaderType|
830 -|Query|qry: OrganisationSchemeQu eryType|
823 +(% style="width:891.294px" %)
824 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
825 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %)
826 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %)
831 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
832 +* //MessageType// (restriction)
833 +** ReportingTaxonomyQueryType
838 838  
839 839  Content:
840 -
841 841  Header, Query
842 842  
843 843  Element Documentation:
844 844  
845 -|**Name**|**Type**|**Documentation**
846 -|Header|BasicHeaderType|
847 -|Query|qry: ReportingTaxonomyQue ryType|
840 +(% style="width:916.294px" %)
841 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
842 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
843 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
848 848  
849 -**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
845 +**StructureSetQueryType: **StructureSetQueryType defines the structure of a [[structure set>>doc:sdmx:Glossary.Structure set.WebHome]] query message.
850 850  
851 851  Derivation:
852 852  
853 -//MessageType// (restriction)
854 - StructureSetQueryType
849 +* //MessageType// (restriction)
850 +** StructureSetQueryType
855 855  
856 856  Content:
857 -
858 858  Header, Query
859 859  
860 860  Element Documentation:
861 861  
862 -|**Name**|**Type**|**Documentation**
863 -|Header|BasicHeaderType|
864 -|Query|qry: StructureSetQueryTyp e|
857 +(% style="width:896.294px" %)
858 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
859 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %)
860 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %)
865 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
866 +* //MessageType// (restriction)
867 +** ProcessQueryType
872 872  
873 873  Content:
874 -
875 875  Header, Query
876 876  
877 877  Element Documentation:
878 878  
879 -|**Name**|**Type**|**Documentation**
880 -|Header|BasicHeaderType|
881 -|Query|qry:ProcessQueryType|
874 +(% style="width:907.294px" %)
875 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
876 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %)
877 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %)
882 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
883 +* //MessageType// (restriction)
884 +** CategorisationQueryType
889 889  
890 890  Content:
891 -
892 892  Header, Query
893 893  
894 894  Element Documentation:
895 895  
896 -|**Name**|**Type**|**Documentation**
897 -|Header|BasicHeaderType|
898 -|Query|qry: CategorisationQueryT ype|
891 +(% style="width:897.294px" %)
892 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
893 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
894 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
899 899  
900 -**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
896 +**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] query message.
901 901  
902 902  Derivation:
903 903  
904 -//MessageType// (restriction)
905 - ProvisionAgreementQueryType
900 +* //MessageType// (restriction)
901 +** ProvisionAgreementQueryType
906 906  
907 907  Content:
908 -
909 909  Header, Query
910 910  
911 911  Element Documentation:
912 912  
913 -|**Name**|**Type**|**Documentation**
914 -|Header|BasicHeaderType|
915 -|Query|qry: ProvisionAgreementQu eryType|
908 +(% style="width:902.294px" %)
909 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
910 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
911 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
916 916  
917 -**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
913 +**ConstraintQueryType: **ConstraintQueryType defines the structure of a (% style="color:#e74c3c" %)constraint(%%) query message.
918 918  
919 919  Derivation:
920 920  
921 -//MessageType// (restriction)
922 - ConstraintQueryType
917 +* //MessageType// (restriction)
918 +** ConstraintQueryType
923 923  
924 924  Content:
925 -
926 926  Header, Query
927 927  
928 928  Element Documentation:
929 929  
930 -|**Name**|**Type**|**Documentation**
931 -|Header|BasicHeaderType|
932 -|Query|qry: ConstraintQueryType|
925 +(% style="width:902.294px" %)
926 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
927 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %)
928 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %)
933 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
934 +* //MessageType// (restriction)
935 +** TransformationSchemeQueryType
940 940  
941 941  Content:
942 -
943 943  Header, Query
944 944  
945 945  Element Documentation:
946 946  
947 -|**Name**|**Type**|**Documentation**
948 -|Header|BasicHeaderType|
949 -|Query|qry: TransformationScheme QueryType|
942 +(% style="width:833.294px" %)
943 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
944 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
945 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
950 950  
951 -**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
947 +**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mappings scheme query message.
952 952  
953 953  Derivation:
954 954  
955 -//MessageType// (restriction)
956 - VtlMappingSchemeQueryType
951 +* //MessageType// (restriction)
952 +** VtlMappingSchemeQueryType
957 957  
958 958  Content:
959 -
960 960  Header, Query
961 961  
962 962  Element Documentation:
963 963  
964 -|**Name**|**Type**|**Documentation**
965 -|Header|BasicHeaderType|
966 -|Query|qry: VtlMappingSchemeQuer yType|
959 +(% style="width:843.294px" %)
960 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
961 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %)
962 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %)
967 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
968 +* //MessageType// (restriction)
969 +** NamePersonalisationSchemeQueryType
974 974  
975 975  Content:
976 -
977 977  Header, Query
978 978  
979 979  Element Documentation:
980 980  
981 -|**Name**|**Type**|**Documentation**
982 -|Header|BasicHeaderType|
983 -|Query|qry: NamePersonalisationS chemeQueryType|
976 +(% style="width:895.294px" %)
977 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
978 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %)
979 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %)
984 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
985 +* //MessageType// (restriction)
986 +** RulesetSchemeQueryType
991 991  
992 992  Content:
993 -
994 994  Header, Query
995 995  
996 996  Element Documentation:
997 997  
998 -|**Name**|**Type**|**Documentation**
999 -|Header|BasicHeaderType|
1000 -|Query|qry: RulesetSchemeQueryTy pe|
993 +(% style="width:886.294px" %)
994 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
995 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %)
996 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %)
1001 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
1002 +* //MessageType// (restriction)
1003 +** UserDefinedOperatorSchemeQueryType
1008 1008  
1009 1009  Content:
1010 -
1011 1011  Header, Query
1012 1012  
1013 1013  Element Documentation:
1014 1014  
1015 -|**Name**|**Type**|**Documentation**
1016 -|Header|BasicHeaderType|
1017 -|Query|qry: UserDefinedOperatorS chemeQueryType|
1010 +(% style="width:866.294px" %)
1011 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
1012 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %)
1013 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %)
1018 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
1019 +* //MessageType// (restriction)
1020 +** CustomTypeSchemeQueryType
1025 1025  
1026 1026  Content:
1027 -
1028 1028  Header, Query
1029 1029  
1030 1030  Element Documentation:
1031 1031  
1032 -|**Name**|**Type**|**Documentation**
1033 -|Header|BasicHeaderType|
1034 -|Query|qry: CustomTypeSchemeQuer yType|
1027 +(% style="width:828.294px" %)
1028 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
1029 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %)
1030 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %)
1035 1035  
1036 1036  **ErrorType: **ErrorType describes the structure of an error response.
1037 1037  
1038 1038  Content:
1039 -
1040 1040  ErrorMessage+
1041 1041  
1042 1042  Element Documentation:
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.
1039 +(% style="width:899.294px" %)
1040 +|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1041 +|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>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors.
1046 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:
1050 -
1051 1051  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure*, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
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.
1050 +(% style="width:891.294px" %)
1051 +|**Name**|**Type**|(% style="width:552px" %)**Documentation**
1052 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender.
1053 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not.
1054 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared.
1055 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1056 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1057 +|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1058 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1059 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1060 +|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1061 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1062 +|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1063 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1064 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1065 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1066 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1071 1071  
1072 -**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1068 +**StructureHeaderType: **StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages.
1073 1073  
1074 1074  Derivation:
1075 1075  
1076 -//BaseHeaderType// (restriction)
1077 - StructureHeaderType
1072 +* //BaseHeaderType// (restriction)
1073 +** StructureHeaderType
1078 1078  
1079 1079  Content:
1080 -
1081 1081  ID, Test, Prepared, Sender, Receiver*, com:Name*, Source*
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.
1080 +(% style="width:1099.29px" %)
1081 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1082 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1083 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1084 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1085 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1086 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1087 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1088 +|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
1094 +* //BaseHeaderType// (restriction)
1095 +** GenericDataHeaderType
1100 1100  
1101 1101  Content:
1102 -
1103 1103  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
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.
1102 +(% style="width:895.294px" %)
1103 +|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1104 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1105 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1106 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1107 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1108 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1109 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1110 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1111 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1112 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1113 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1114 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1115 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1116 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1117 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1118 +|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
1124 +* //BaseHeaderType// (restriction)
1125 +** GenericDataHeaderType (restriction)
1126 +*** GenericTimeSeriesDataHeaderType
1131 1131  
1132 1132  Content:
1133 -
1134 1134  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
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.
1133 +(% style="width:926.294px" %)
1134 +|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1135 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1136 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1137 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1138 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1139 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1140 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1141 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1142 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1143 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1144 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1145 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1146 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1147 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1148 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1149 +|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
1155 +* //BaseHeaderType// (restriction)
1156 +** StructureSpecificDataHeaderType
1161 1161  
1162 1162  Content:
1163 -
1164 1164  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
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.
1163 +(% style="width:930.294px" %)
1164 +|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1165 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1166 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1167 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1168 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1169 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1170 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1171 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1172 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1173 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1174 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1175 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1176 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1177 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1178 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1179 +|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
1185 +* //BaseHeaderType// (restriction)
1186 +** StructureSpecificDataHeaderType (restriction)
1187 +*** StructureSpecificTimeSeriesDataHeaderType
1192 1192  
1193 1193  Content:
1194 -
1195 1195  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
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.
1194 +(% style="width:943.294px" %)
1195 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1196 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1197 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1198 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1199 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1200 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1201 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1202 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1203 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1204 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1205 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1206 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1207 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1208 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1209 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1210 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1215 1215  
1216 -**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1212 +**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
1217 1217  
1218 1218  Derivation:
1219 1219  
1220 -//BaseHeaderType// (restriction)
1221 - GenericMetadataHeaderType
1216 +* //BaseHeaderType// (restriction)
1217 +** GenericMetadataHeaderType
1222 1222  
1223 1223  Content:
1224 -
1225 1225  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
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.
1224 +(% style="width:928.294px" %)
1225 +|**Name**|**Type**|(% style="width:554px" %)**Documentation**
1226 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender.
1227 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not.
1228 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared.
1229 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1230 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1231 +|com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1232 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1233 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1234 +|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1235 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1236 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1237 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1242 1242  
1243 -**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1239 +**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] 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
1243 +* //BaseHeaderType// (restriction)
1244 +** StructureSpecificMetadataHeaderType
1249 1249  
1250 1250  Content:
1251 -
1252 1252  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
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.
1251 +(% style="width:996.294px" %)
1252 +|**Name**|**Type**|(% style="width:557px" %)**Documentation**
1253 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender.
1254 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not.
1255 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared.
1256 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1257 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1258 +|com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1259 +|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>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 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>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)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>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1260 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1261 +|DataSetAction|com:ActionType|(% style="width:557px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1262 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1263 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1264 +|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
1270 +* //BaseHeaderType// (restriction)
1271 +** BasicHeaderType
1276 1276  
1277 1277  Content:
1278 -
1279 1279  ID, Test, Prepared, Sender, Receiver
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.
1278 +(% style="width:903.294px" %)
1279 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1280 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1281 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1282 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1283 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1284 +|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  
... ... @@ -1294,83 +1294,78 @@
1294 1294  id
1295 1295  
1296 1296  Content:
1293 +com:Name*, (% style="color:#e74c3c" %)Contact(%%)*
1297 1297  
1298 -com:Name*, Contact*
1295 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1299 1299  
1300 -Attribute Documentation:
1297 +(% style="width:888.294px" %)
1298 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:569px" %)**Documentation**
1299 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:569px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
1301 1301  
1302 -|**Name**|**Type**|**Documentation**
1303 -|id|com:IDType|The id attribute holds the identification of the party.
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.
1303 +(% style="width:889.294px" %)
1304 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:568px" %)**Documentation**
1305 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:568px" %)Name is a human-readable name of the party.
1306 +|(% style="width:134px" %)(% style="color:#e74c3c" %)Contact|(% style="width:183px" %)ContactType|(% style="width:568px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)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
1312 +* PartyType (extension)
1313 +** SenderType
1317 1317  
1318 1318  Attributes:
1319 -
1320 1320  id
1321 1321  
1322 1322  Content:
1319 +com:Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone?
1323 1323  
1324 -com:Name*, Contact*, Timezone?
1321 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1325 1325  
1326 -Attribute Documentation:
1323 +(% style="width:824.294px" %)
1324 +|(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
1325 +|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
1327 1327  
1328 -|**Name**|**Type**|**Documentation**
1329 -|id|com:IDType|The id attribute holds the identification of the party.
1330 -
1331 1331  Element Documentation:
1332 1332  
1333 -|**Name**|**Type**|**Documentation**
1334 -|com:Name|com:TextType|Name is a human-readable name of the party.
1335 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1336 -|Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1329 +(% style="width:1016.29px" %)
1330 +|**Name**|**Type**|(% style="width:738px" %)**Documentation**
1331 +|com:Name|com:TextType|(% style="width:738px" %)Name is a human-readable name of the party.
1332 +|(%%)(% style="color:#e74c3c" %)Contact|ContactType|(% style="width:738px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.
1333 +|Timezone|com:TimezoneType|(% style="width:738px" %)Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1337 1337  
1338 -**ContactType: **ContactType provides defines the contact information about a party.
1335 +**ContactType: **ContactType provides defines the (% style="color:#e74c3c" %)contact(%%) information about a party.
1339 1339  
1340 1340  Content:
1341 -
1342 1342  com:Name*, Department*, Role*, (Telephone | Fax | X400 | URI | Email)*
1343 1343  
1344 1344  Element Documentation:
1345 1345  
1346 -|**Name**|**Type**|**Documentation**
1347 -|com:Name|com:TextType|Name contains a human-readable name for the contact.
1348 -|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
1349 -|Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
1350 -|Telephone|xs:string|Telephone holds the telephone number for the contact person.
1351 -|Fax|xs:string|Fax holds the fax number for the contact person.
1352 -|X400|xs:string|X400 holds the X.400 address for the contact person.
1353 -|URI|xs:anyURI|URI holds an information URL for the contact person.
1354 -|Email|xs:string|Email holds the email address for the contact person.
1342 +(% style="width:1035.29px" %)
1343 +|**Name**|**Type**|(% style="width:623px" %)**Documentation**
1344 +|com:Name|com:TextType|(% style="width:623px" %)Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%).
1345 +|Department|com:TextType|(% style="width:623px" %)Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%) person works.
1346 +|Role|com:TextType|(% style="width:623px" %)Role is the responsibility of the (% style="color:#e74c3c" %)contact(%%) person with respect to the object for which this person is the (% style="color:#e74c3c" %)contact(%%).
1347 +|Telephone|xs:string|(% style="width:623px" %)Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the (% style="color:#e74c3c" %)contact(%%) person.
1348 +|Fax|xs:string|(% style="width:623px" %)Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%) person.
1349 +|X400|xs:string|(% style="width:623px" %)X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%) person.
1350 +|URI|xs:anyURI|(% style="width:623px" %)URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%) person.
1351 +|Email|xs:string|(% style="width:623px" %)Email holds the email address for the (% style="color:#e74c3c" %)contact(%%) person.
1355 1355  
1356 -1.
1357 -11.
1358 -111. Simple Types
1353 +=== 2.1.4 Simple Types ===
1359 1359  
1360 1360  **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
1361 1361  
1362 1362  Union of:
1363 -
1364 1364  xs:dateTime, xs:date.
1365 1365  
1366 -1.
1367 -11. Message Footer Namespace
1360 +== 2.2 Message Footer Namespace ==
1368 1368  
1369 1369  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1370 1370  
1371 -1.
1372 -11.
1373 -111. Summary
1364 +=== 2.2.1 Summary ===
1374 1374  
1375 1375  Referenced Namespaces:
1376 1376  
... ... @@ -1379,52 +1379,45 @@
1379 1379  |http:~/~/www.w3.org/2001/XMLSchema|xs
1380 1380  
1381 1381  Contents:
1382 -
1383 1383  1 Global Element
1384 1384  2 Complex Types
1385 1385  1 Simple Type
1386 1386  
1387 -1.
1388 -11.
1389 -111. Global Elements
1377 +=== 2.2.2 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.
1395 -111. Complex Types
1381 +=== 2.2.3 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.
1398 1398  
1399 1399  Content:
1400 -
1401 1401  Message+
1402 1402  
1403 1403  Element Documentation:
1404 1404  
1405 -|**Name**|**Type**|**Documentation**
1406 -|Message|FooterMessageType|Message contains a single error, information, or warning message. A code is provided along with an optional severity. The text of the message can be expressed in multiple languages.
1390 +(% style="width:1112.29px" %)
1391 +|**Name**|**Type**|(% style="width:782px" %)**Documentation**
1392 +|Message|FooterMessageType|(% style="width:782px" %)Message contains a single error, information, or warning message. A [[code>>doc:sdmx:Glossary.Code.WebHome]] is provided along with an optional severity. The text of the message can be expressed in multiple languages.
1407 1407  
1408 -**FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity code of Error, Information, or Warning added to it.
1394 +**FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity [[code>>doc:sdmx:Glossary.Code.WebHome]] of Error, Information, or Warning added to it.
1409 1409  
1410 1410  Derivation:
1411 1411  
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
1398 +* com:StatusMessageType (restriction)
1399 +** com:CodedStatusMessageType (extension)
1400 +*** FooterMessageType
1415 1415  
1416 1416  Attributes:
1403 +[[code>>doc:sdmx:Glossary.Code.WebHome]], severity?
1417 1417  
1418 -code, severity?
1419 -
1420 1420  Content:
1421 -
1422 1422  com:Text+
1423 1423  
1424 -Attribute Documentation:
1408 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1425 1425  
1426 1426  |**Name**|**Type**|**Documentation**
1427 -|code|xs:string|The code attribute holds an optional code identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
1411 +|[[code>>doc:sdmx:Glossary.Code.WebHome]]|xs:string|The [[code>>doc:sdmx:Glossary.Code.WebHome]] [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds an optional [[code>>doc:sdmx:Glossary.Code.WebHome]] identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
1428 1428  |severity|SeverityCodeType|
1429 1429  
1430 1430  Element Documentation:
... ... @@ -1432,9 +1432,7 @@
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.
1437 -111. Simple Types
1419 +=== 2.2.4 Simple Types ===
1438 1438  
1439 1439  **SeverityCodeType:**
1440 1440  
... ... @@ -1445,19 +1445,4 @@
1445 1445  |**Value**|**Documentation**
1446 1446  |Error|Error indicates the status message coresponds to an error.
1447 1447  |Warning|Warning indicates that the status message corresponds to a warning.
1448 -|Information|Information indicates that the status message corresponds to an informational message.
1449 -
1450 -
1451 -
1452 -
1453 -
1454 -
1455 -
1456 -
1457 -
1458 -
1459 -
1460 -
1461 -
1462 -
1463 -
1430 +|Information|Information indicates that the status message corresponds to an informational message.