Changes for page Part I. Message Namespace

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

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