Skip to Content

Wiki source code of Part I. Message

Version 3.5 by Helena on 2025/06/23 17:05
Show last authors
1 {{box title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
4
5 **Corrigendum**
6
7 The following problems with the specification dated April 2011 have been rectified as described below.
8
9 **~1. Problem**
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.
12
13 **Rectification**
14
15 The documentation of the Structure element (line 40) has been updated to remove this reference.
16
17 = 1. Introduction =
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.
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.
22
23 In general, every message in SDMX follows common format of:
24
25 * Header
26 * Payload (0..n)
27 * Footer (0..1)
28
29 The header and payload elements exist in the message namespace, but the content of the payload is defined in the namespaces that are specific the functionality of the messages. Note that the header follows a common construct, which is then restricted according to the requirements of the message which is using it.
30
31 = 2. Schema Documentation =
32
33 == 2.1 Message Namespace ==
34
35 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message**
36
37 === 2.1.1 Summary ===
38
39 Referenced Namespaces:
40
41 (% style="width:788.294px" %)
42 |(% style="width:612px" %)**Namespace**|(% style="width:173px" %)**Prefix**
43 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:173px" %)com
44 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|(% style="width:173px" %)dat
45 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)dsd
46 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|(% style="width:173px" %)ftr
47 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|(% style="width:173px" %)rep
48 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|(% style="width:173px" %)msd
49 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|(% style="width:173px" %)qry
50 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|(% style="width:173px" %)ref
51 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|(% style="width:173px" %)str
52 |(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs
53
54 Contents:
55
56 50 Global Elements
57 62 Complex Types
58 1 Simple Type
59
60 === 2.1.2 Global Elements ===
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.
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).
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.
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.
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.
71
72 **GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
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.
75
76 **RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
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.
79
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
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.
83
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
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.
87
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
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
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.
93
94 **QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
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.
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.
99
100 **StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data.
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.
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.
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.
107
108 **GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata.
109
110 **StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata.
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.
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.
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).
117
118 **DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows.
119
120 **MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows.
121
122 **DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions.
123
124 **MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions.
125
126 **CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes.
127
128 **ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes.
129
130 **CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists.
131
132 **HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists.
133
134 **OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes.
135
136 **ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies.
137
138 **StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets.
139
140 **ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes.
141
142 **CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations.
143
144 **ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements.
145
146 **ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints.
147
148 **TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes.
149
150 **VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes.
151
152 **NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes.
153
154 **RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes.
155
156 **UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes.
157
158 **CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes.
159
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
162 === 2.1.3 Complex Types ===
163
164 **//MessageType//: **MessageType is an abstract type which is used by all of the messages, to allow inheritance of common features. Every message consists of a mandatory header, followed by optional payload (which may occur multiple times), and finally an optional footer section for conveying error, warning, and informational messages.
165
166 Content:
167
168 Header, {any element with namespace of http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message}*, ftr:Footer?
169
170 Element Documentation:
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.
175
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
178 Derivation:
179
180 //MessageType// (restriction)
181 StructureType
182
183 Content:
184
185 Header, Structures?, ftr:Footer?
186
187 Element Documentation:
188
189 (% style="width:856.294px" %)
190 |**Name**|(% style="width:210px" %)**Type**|(% style="width:455px" %)**Documentation**
191 |Header|(% style="width:210px" %)StructureHeaderType|(% style="width:455px" %)
192 |Structures|(% style="width:210px" %)str:StructuresType|(% style="width:455px" %)
193 |ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:455px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
194
195 **GenericDataType: **GenericDataType defines the contents of a generic data message.
196
197 Derivation:
198
199 //MessageType// (restriction)
200 GenericDataType
201
202 Content:
203
204 Header, DataSet*, ftr:Footer?
205
206 Element Documentation:
207
208 (% style="width:847.294px" %)
209 |**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation**
210 |Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %)
211 |DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
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
214 **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
215
216 Derivation:
217
218 * //MessageType// (restriction)
219 ** GenericDataType (restriction)
220 *** GenericTimeSeriesDataType
221
222 Content:
223
224 Header, DataSet*, ftr:Footer?
225
226 Element Documentation:
227
228 (% style="width:856.294px" %)
229 |**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation**
230 |Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %)
231 |DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
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
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.
235
236 Derivation:
237
238 * //MessageType// (restriction)
239 ** StructureSpecificDataType
240
241 Content:
242
243 Header, DataSet*, ftr:Footer?
244
245 Element Documentation:
246
247 (% style="width:828.294px" %)
248 |**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation**
249 |Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %)
250 |DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
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
253 **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
254
255 Derivation:
256
257 * //MessageType// (restriction)
258 ** StructureSpecificDataType (restriction)
259 *** StructureSpecificTimeSeriesDataType
260
261 Content:
262
263 Header, DataSet*, ftr:Footer?
264
265 Element Documentation:
266
267 (% style="width:839.294px" %)
268 |**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
269 |Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
270 |DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
271 |ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
272
273 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
274
275 Derivation:
276
277 //MessageType// (restriction)
278 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
279
280 Content:
281
282 Header, MetadataSet*, ftr:Footer?
283
284 Element Documentation:
285
286 |**Name**|**Type**|**Documentation**
287 |Header|GenericMetadataHeade rType|
288 |MetadataSet|rep:MetadataSetType|
289 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
290
291 **StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
292
293 Derivation:
294
295 //MessageType// (restriction)
296 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
297
298 Content:
299
300 Header, MetadataSet*, ftr:Footer?
301
302 Element Documentation:
303
304 |**Name**|**Type**|**Documentation**
305 |Header|StructureSpecificMet adataHeaderType|
306 |MetadataSet|//msd:MetadataSetType//|
307 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
308
309 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
310
311 Derivation:
312
313 //MessageType// (restriction)
314 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
315
316 Content:
317
318 Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, ftr:Footer?
319
320 Element Documentation:
321
322 |**Name**|**Type**|**Documentation**
323 |Header|BasicHeaderType|
324 |SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
325 |SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
326 |QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
327 |QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
328 |SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
329 |SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
330 |SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
331 |SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
332 |QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
333 |QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
334 |NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
335 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
336
337 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
338
339 Derivation:
340
341 //MessageType// (restriction)
342 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
343 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
344
345 Content:
346
347 Header, SubmitRegistrationsRequest
348
349 Element Documentation:
350
351 |**Name**|**Type**|**Documentation**
352 |Header|BasicHeaderType|
353 |SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
354
355 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
356
357 Derivation:
358
359 //MessageType// (restriction)
360 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
361 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
362
363 Content:
364
365 Header, SubmitRegistrationsResponse, ftr:Footer?
366
367 Element Documentation:
368
369 |**Name**|**Type**|**Documentation**
370 |Header|BasicHeaderType|
371 |SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
372 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
373
374 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
375
376 Derivation:
377
378 //MessageType// (restriction)
379 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
380 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
381
382 Content:
383
384 Header, QueryRegistrationRequest
385
386 Element Documentation:
387
388 |**Name**|**Type**|**Documentation**
389 |Header|BasicHeaderType|
390 |QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
391
392 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
393
394 Derivation:
395
396 //MessageType// (restriction)
397 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
398 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
399
400 Content:
401
402 Header, QueryRegistrationResponse, ftr:Footer?
403
404 Element Documentation:
405
406 |**Name**|**Type**|**Documentation**
407 |Header|BasicHeaderType|
408 |QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
409 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
410
411 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
412
413 Derivation:
414
415 //MessageType// (restriction)
416 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
417 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
418
419 Content:
420
421 Header, SubmitStructureRequest
422
423 Element Documentation:
424
425 |**Name**|**Type**|**Documentation**
426 |Header|BasicHeaderType|
427 |SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
428
429 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
430
431 Derivation:
432
433 //MessageType// (restriction)
434 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
435 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
436
437 Content:
438
439 Header, SubmitStructureResponse, ftr:Footer?
440
441 Element Documentation:
442
443 |**Name**|**Type**|**Documentation**
444 |Header|BasicHeaderType|
445 |SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
446 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
447
448 **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
449
450 Derivation:
451
452 //MessageType// (restriction)
453 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
454 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
455
456 Content:
457
458 Header, SubmitSubscriptionsRequest
459
460 Element Documentation:
461
462 |**Name**|**Type**|**Documentation**
463 |Header|BasicHeaderType|
464 |SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
465
466 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
467
468 Derivation:
469
470 //MessageType// (restriction)
471 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
472 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
473
474 Content:
475
476 Header, SubmitSubscriptionsResponse, ftr:Footer?
477
478 Element Documentation:
479
480 |**Name**|**Type**|**Documentation**
481 |Header|BasicHeaderType|
482 |SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
483 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
484
485 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
486
487 Derivation:
488
489 //MessageType// (restriction)
490 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
491 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
492
493 Content:
494
495 Header, QuerySubscriptionRequest
496
497 Element Documentation:
498
499 |**Name**|**Type**|**Documentation**
500 |Header|BasicHeaderType|
501 |QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
502
503 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
504
505 Derivation:
506
507 //MessageType// (restriction)
508 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
509 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
510
511 Content:
512
513 Header, QuerySubscriptionResponse, ftr:Footer?
514
515 Element Documentation:
516
517 |**Name**|**Type**|**Documentation**
518 |Header|BasicHeaderType|
519 |QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
520 |ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
521
522 **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
523
524 Derivation:
525
526 //MessageType// (restriction)
527 RegistryInterfaceType (restriction)
528 NotifyRegistryEventType
529
530 Content:
531
532 Header, NotifyRegistryEvent
533
534 Element Documentation:
535
536 |**Name**|**Type**|**Documentation**
537 |Header|BasicHeaderType|
538 |NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
539
540 **DataQueryType: **DataQueryType defines the structure of a data query message.
541
542 Derivation:
543
544 //MessageType// (restriction)
545 DataQueryType
546
547 Content:
548
549 Header, Query
550
551 Element Documentation:
552
553 |**Name**|**Type**|**Documentation**
554 |Header|BasicHeaderType|
555 |Query|qry:DataQueryType|
556
557 **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message.
558
559 Derivation:
560
561 //MessageType// (restriction)
562 DataQueryType (restriction)
563 GenericDataQueryType
564
565 Content:
566
567 Header, Query
568
569 Element Documentation:
570
571 |**Name**|**Type**|**Documentation**
572 |Header|BasicHeaderType|
573 |Query|qry: GenericDataQueryType|
574
575 **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message.
576
577 Derivation:
578
579 //MessageType// (restriction)
580 DataQueryType (restriction)
581 GenericDataQueryType (restriction)
582 GenericTimeSeriesDataQueryType
583
584 Content:
585
586 Header, Query
587
588 Element Documentation:
589
590 |**Name**|**Type**|**Documentation**
591 |Header|BasicHeaderType|
592 |Query|qry: GenericTimeSeriesDat aQueryType|
593
594 **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message.
595
596 Derivation:
597
598 //MessageType// (restriction)
599 DataQueryType (restriction)
600 StructureSpecificTimeSeriesDataQueryType
601
602 Content:
603
604 Header, Query
605
606 Element Documentation:
607
608 |**Name**|**Type**|**Documentation**
609 |Header|BasicHeaderType|
610 |Query|qry: TimeSeriesDataQueryT ype|
611
612 **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
613
614 Derivation:
615
616 //MessageType// (restriction)
617 MetadataQueryType
618
619 Content:
620
621 Header, Query
622
623 Element Documentation:
624
625 |**Name**|**Type**|**Documentation**
626 |Header|BasicHeaderType|
627 |Query|qry: MetadataQueryType|
628
629 **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message.
630
631 Derivation:
632
633 //MessageType// (restriction)
634 DataSchemaQueryType
635
636 Content:
637
638 Header, Query
639
640 Element Documentation:
641
642 |**Name**|**Type**|**Documentation**
643 |Header|BasicHeaderType|
644 |Query|qry: DataSchemaQueryType|
645
646 **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message.
647
648 Derivation:
649
650 //MessageType// (restriction)
651 MetadataSchemaQueryType
652
653 Content:
654
655 Header, Query
656
657 Element Documentation:
658
659 |**Name**|**Type**|**Documentation**
660 |Header|BasicHeaderType|
661 |Query|qry: MetadataSchemaQueryT ype|
662
663 **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message.
664
665 Derivation:
666
667 //MessageType// (restriction)
668 StructuresQueryType
669
670 Content:
671
672 Header, Query
673
674 Element Documentation:
675
676 |**Name**|**Type**|**Documentation**
677 |Header|BasicHeaderType|
678 |Query|qry: StructuresQueryType|
679
680 **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
681
682 Derivation:
683
684 //MessageType// (restriction)
685 DataflowQueryType
686
687 Content:
688
689 Header, Query
690
691 Element Documentation:
692
693 |**Name**|**Type**|**Documentation**
694 |Header|BasicHeaderType|
695 |Query|qry: DataflowQueryType|
696
697 **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
698
699 Derivation:
700
701 //MessageType// (restriction)
702 MetadataflowQueryType
703
704 Content:
705
706 Header, Query
707
708 Element Documentation:
709
710 |**Name**|**Type**|**Documentation**
711 |Header|BasicHeaderType|
712 |Query|qry: MetadataflowQueryTyp e|
713
714 **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message.
715
716 Derivation:
717
718 //MessageType// (restriction)
719 DataStructureQueryType
720
721 Content:
722
723 Header, Query
724
725 Element Documentation:
726
727 |**Name**|**Type**|**Documentation**
728 |Header|BasicHeaderType|
729 |Query|qry: DataStructureQueryTy pe|
730
731 **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message.
732
733 Derivation:
734
735 //MessageType// (restriction)
736 MetadataStructureQueryType
737
738 Content:
739
740 Header, Query
741
742 Element Documentation:
743
744 |**Name**|**Type**|**Documentation**
745 |Header|BasicHeaderType|
746 |Query|qry: MetadataStructureQue ryType|
747
748 **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
749
750 Derivation:
751
752 //MessageType// (restriction)
753 CategorySchemeQueryType
754
755 Content:
756
757 Header, Query
758
759 Element Documentation:
760
761 |**Name**|**Type**|**Documentation**
762 |Header|BasicHeaderType|
763 |Query|qry: CategorySchemeQueryT ype|
764
765 **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
766
767 Derivation:
768
769 //MessageType// (restriction)
770 ConceptSchemeQueryType
771
772 Content:
773
774 Header, Query
775
776 Element Documentation:
777
778 |**Name**|**Type**|**Documentation**
779 |Header|BasicHeaderType|
780 |Query|qry: ConceptSchemeQueryTy pe|
781
782 **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
783
784 Derivation:
785
786 //MessageType// (restriction)
787 CodelistQueryType
788
789 Content:
790
791 Header, Query
792
793 Element Documentation:
794
795 |**Name**|**Type**|**Documentation**
796 |Header|BasicHeaderType|
797 |Query|qry: CodelistQueryType|
798
799 **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
800
801 Derivation:
802
803 //MessageType// (restriction)
804 HierarchicalCodelistQueryType
805
806 Content:
807
808 Header, Query
809
810 Element Documentation:
811
812 |**Name**|**Type**|**Documentation**
813 |Header|BasicHeaderType|
814 |Query|qry: HierarchicalCodelist QueryType|
815
816 **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message.
817
818 Derivation:
819
820 //MessageType// (restriction)
821 OrganisationSchemeQueryType
822
823 Content:
824
825 Header, Query
826
827 Element Documentation:
828
829 |**Name**|**Type**|**Documentation**
830 |Header|BasicHeaderType|
831 |Query|qry: OrganisationSchemeQu eryType|
832
833 **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message.
834
835 Derivation:
836
837 //MessageType// (restriction)
838 ReportingTaxonomyQueryType
839
840 Content:
841
842 Header, Query
843
844 Element Documentation:
845
846 |**Name**|**Type**|**Documentation**
847 |Header|BasicHeaderType|
848 |Query|qry: ReportingTaxonomyQue ryType|
849
850 **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
851
852 Derivation:
853
854 //MessageType// (restriction)
855 StructureSetQueryType
856
857 Content:
858
859 Header, Query
860
861 Element Documentation:
862
863 |**Name**|**Type**|**Documentation**
864 |Header|BasicHeaderType|
865 |Query|qry: StructureSetQueryTyp e|
866
867 **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message.
868
869 Derivation:
870
871 //MessageType// (restriction)
872 ProcessQueryType
873
874 Content:
875
876 Header, Query
877
878 Element Documentation:
879
880 |**Name**|**Type**|**Documentation**
881 |Header|BasicHeaderType|
882 |Query|qry:ProcessQueryType|
883
884 **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message.
885
886 Derivation:
887
888 //MessageType// (restriction)
889 CategorisationQueryType
890
891 Content:
892
893 Header, Query
894
895 Element Documentation:
896
897 |**Name**|**Type**|**Documentation**
898 |Header|BasicHeaderType|
899 |Query|qry: CategorisationQueryT ype|
900
901 **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
902
903 Derivation:
904
905 //MessageType// (restriction)
906 ProvisionAgreementQueryType
907
908 Content:
909
910 Header, Query
911
912 Element Documentation:
913
914 |**Name**|**Type**|**Documentation**
915 |Header|BasicHeaderType|
916 |Query|qry: ProvisionAgreementQu eryType|
917
918 **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
919
920 Derivation:
921
922 //MessageType// (restriction)
923 ConstraintQueryType
924
925 Content:
926
927 Header, Query
928
929 Element Documentation:
930
931 |**Name**|**Type**|**Documentation**
932 |Header|BasicHeaderType|
933 |Query|qry: ConstraintQueryType|
934
935 **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message.
936
937 Derivation:
938
939 //MessageType// (restriction)
940 TransformationSchemeQueryType
941
942 Content:
943
944 Header, Query
945
946 Element Documentation:
947
948 |**Name**|**Type**|**Documentation**
949 |Header|BasicHeaderType|
950 |Query|qry: TransformationScheme QueryType|
951
952 **VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
953
954 Derivation:
955
956 //MessageType// (restriction)
957 VtlMappingSchemeQueryType
958
959 Content:
960
961 Header, Query
962
963 Element Documentation:
964
965 |**Name**|**Type**|**Documentation**
966 |Header|BasicHeaderType|
967 |Query|qry: VtlMappingSchemeQuer yType|
968
969 **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message.
970
971 Derivation:
972
973 //MessageType// (restriction)
974 NamePersonalisationSchemeQueryType
975
976 Content:
977
978 Header, Query
979
980 Element Documentation:
981
982 |**Name**|**Type**|**Documentation**
983 |Header|BasicHeaderType|
984 |Query|qry: NamePersonalisationS chemeQueryType|
985
986 **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message.
987
988 Derivation:
989
990 //MessageType// (restriction)
991 RulesetSchemeQueryType
992
993 Content:
994
995 Header, Query
996
997 Element Documentation:
998
999 |**Name**|**Type**|**Documentation**
1000 |Header|BasicHeaderType|
1001 |Query|qry: RulesetSchemeQueryTy pe|
1002
1003 **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message.
1004
1005 Derivation:
1006
1007 //MessageType// (restriction)
1008 UserDefinedOperatorSchemeQueryType
1009
1010 Content:
1011
1012 Header, Query
1013
1014 Element Documentation:
1015
1016 |**Name**|**Type**|**Documentation**
1017 |Header|BasicHeaderType|
1018 |Query|qry: UserDefinedOperatorS chemeQueryType|
1019
1020 **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message.
1021
1022 Derivation:
1023
1024 //MessageType// (restriction)
1025 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1026
1027 Content:
1028
1029 Header, Query
1030
1031 Element Documentation:
1032
1033 |**Name**|**Type**|**Documentation**
1034 |Header|BasicHeaderType|
1035 |Query|qry: CustomTypeSchemeQuer yType|
1036
1037 **ErrorType: **ErrorType describes the structure of an error response.
1038
1039 Content:
1040
1041 ErrorMessage+
1042
1043 Element Documentation:
1044
1045 |**Name**|**Type**|**Documentation**
1046 |ErrorMessage|com: CodedStatusMessageTy pe|ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1047
1048 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1049
1050 Content:
1051
1052 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure*, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1053
1054 Element Documentation:
1055
1056 |**Name**|**Type**|**Documentation**
1057 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1058 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1059 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1060 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1061 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1062 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1063 |Structure|//com: PayloadStructureType//|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1064 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1065 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1066 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1067 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1068 |ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1069 |ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1070 |EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1071 |Source|com:TextType|Source provides human-readable information about the source of the data.
1072
1073 **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1074
1075 Derivation:
1076
1077 //BaseHeaderType// (restriction)
1078 StructureHeaderType
1079
1080 Content:
1081
1082 ID, Test, Prepared, Sender, Receiver*, com:Name*, Source*
1083
1084 Element Documentation:
1085
1086 |**Name**|**Type**|**Documentation**
1087 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1088 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1089 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1090 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1091 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1092 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1093 |Source|com:TextType|Source provides human-readable information about the source of the data.
1094
1095 **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1096
1097 Derivation:
1098
1099 //BaseHeaderType// (restriction)
1100 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1101
1102 Content:
1103
1104 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1105
1106 Element Documentation:
1107
1108 |**Name**|**Type**|**Documentation**
1109 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1110 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1111 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1112 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1113 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1114 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1115 |Structure|com: GenericDataStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1116 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1117 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1118 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1119 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1120 |ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1121 |ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1122 |EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1123 |Source|com:TextType|Source provides human-readable information about the source of the data.
1124
1125 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1126
1127 Derivation:
1128
1129 //BaseHeaderType// (restriction)
1130 GenericDataHeaderType (restriction)
1131 GenericTimeSeriesDataHeaderType
1132
1133 Content:
1134
1135 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1136
1137 Element Documentation:
1138
1139 |**Name**|**Type**|**Documentation**
1140 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1141 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1142 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1143 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1144 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1145 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1146 |Structure|com: GenericTimeSeriesDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1147 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1148 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1149 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1150 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1151 |ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1152 |ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1153 |EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1154 |Source|com:TextType|Source provides human-readable information about the source of the data.
1155
1156 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1157
1158 Derivation:
1159
1160 //BaseHeaderType// (restriction)
1161 StructureSpecificDataHeaderType
1162
1163 Content:
1164
1165 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1166
1167 Element Documentation:
1168
1169 |**Name**|**Type**|**Documentation**
1170 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1171 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1172 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1173 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1174 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1175 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1176 |Structure|com: StructureSpecificDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1177 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1178 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1179 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1180 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1181 |ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1182 |ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1183 |EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1184 |Source|com:TextType|Source provides human-readable information about the source of the data.
1185
1186 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1187
1188 Derivation:
1189
1190 //BaseHeaderType// (restriction)
1191 StructureSpecificDataHeaderType (restriction)
1192 StructureSpecificTimeSeriesDataHeaderType
1193
1194 Content:
1195
1196 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1197
1198 Element Documentation:
1199
1200 |**Name**|**Type**|**Documentation**
1201 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1202 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1203 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1204 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1205 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1206 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1207 |Structure|com: StructureSpecificDat aTimeSeriesStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1208 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1209 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1210 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1211 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1212 |ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).
1213 |ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).
1214 |EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.
1215 |Source|com:TextType|Source provides human-readable information about the source of the data.
1216
1217 **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1218
1219 Derivation:
1220
1221 //BaseHeaderType// (restriction)
1222 GenericMetadataHeaderType
1223
1224 Content:
1225
1226 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1227
1228 Element Documentation:
1229
1230 |**Name**|**Type**|**Documentation**
1231 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1232 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1233 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1234 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1235 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1236 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1237 |Structure|com: GenericMetadataStruc tureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1238 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1239 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1240 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1241 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1242 |Source|com:TextType|Source provides human-readable information about the source of the data.
1243
1244 **StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1245
1246 Derivation:
1247
1248 //BaseHeaderType// (restriction)
1249 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1250
1251 Content:
1252
1253 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1254
1255 Element Documentation:
1256
1257 |**Name**|**Type**|**Documentation**
1258 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1259 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1260 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1261 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1262 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1263 |com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.
1264 |Structure|com: StructureSpecificMet adataStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly.
1265 |DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message.
1266 |DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1267 |DataSetID|com:IDType|DataSetID provides an identifier for a contained data set.
1268 |Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.
1269 |Source|com:TextType|Source provides human-readable information about the source of the data.
1270
1271 **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges.
1272
1273 Derivation:
1274
1275 //BaseHeaderType// (restriction)
1276 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1277
1278 Content:
1279
1280 ID, Test, Prepared, Sender, Receiver
1281
1282 Element Documentation:
1283
1284 |**Name**|**Type**|**Documentation**
1285 |ID|com:IDType|ID identifies an identification for the message, assigned by the sender.
1286 |Test|xs:boolean|Test indicates whether the message is for test purposes or not.
1287 |Prepared|HeaderTimeType|Prepared is the date the message was prepared.
1288 |Sender|SenderType|Sender is information about the party that is transmitting the message.
1289 |Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
1290
1291 **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1292
1293 Attributes:
1294
1295 id
1296
1297 Content:
1298
1299 com:Name*, Contact*
1300
1301 Attribute Documentation:
1302
1303 |**Name**|**Type**|**Documentation**
1304 |id|com:IDType|The id attribute holds the identification of the party.
1305
1306 Element Documentation:
1307
1308 |**Name**|**Type**|**Documentation**
1309 |com:Name|com:TextType|Name is a human-readable name of the party.
1310 |Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1311
1312 **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1313
1314 Derivation:
1315
1316 PartyType (extension)
1317 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1318
1319 Attributes:
1320
1321 id
1322
1323 Content:
1324
1325 com:Name*, Contact*, Timezone?
1326
1327 Attribute Documentation:
1328
1329 |**Name**|**Type**|**Documentation**
1330 |id|com:IDType|The id attribute holds the identification of the party.
1331
1332 Element Documentation:
1333
1334 |**Name**|**Type**|**Documentation**
1335 |com:Name|com:TextType|Name is a human-readable name of the party.
1336 |Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1337 |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".
1338
1339 **ContactType: **ContactType provides defines the contact information about a party.
1340
1341 Content:
1342
1343 com:Name*, Department*, Role*, (Telephone | Fax | X400 | URI | Email)*
1344
1345 Element Documentation:
1346
1347 |**Name**|**Type**|**Documentation**
1348 |com:Name|com:TextType|Name contains a human-readable name for the contact.
1349 |Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
1350 |Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
1351 |Telephone|xs:string|Telephone holds the telephone number for the contact person.
1352 |Fax|xs:string|Fax holds the fax number for the contact person.
1353 |X400|xs:string|X400 holds the X.400 address for the contact person.
1354 |URI|xs:anyURI|URI holds an information URL for the contact person.
1355 |Email|xs:string|Email holds the email address for the contact person.
1356
1357 1.
1358 11.
1359 111. Simple Types
1360
1361 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
1362
1363 Union of:
1364
1365 xs:dateTime, xs:date.
1366
1367 1.
1368 11. Message Footer Namespace
1369
1370 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1371
1372 1.
1373 11.
1374 111. Summary
1375
1376 Referenced Namespaces:
1377
1378 |**Namespace**|**Prefix**
1379 |http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com
1380 |http:~/~/www.w3.org/2001/XMLSchema|xs
1381
1382 Contents:
1383
1384 1 Global Element
1385 2 Complex Types
1386 1 Simple Type
1387
1388 1.
1389 11.
1390 111. Global Elements
1391
1392 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1393
1394 1.
1395 11.
1396 111. Complex Types
1397
1398 **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.
1399
1400 Content:
1401
1402 Message+
1403
1404 Element Documentation:
1405
1406 |**Name**|**Type**|**Documentation**
1407 |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.
1408
1409 **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.
1410
1411 Derivation:
1412
1413 com:StatusMessageType (restriction)
1414 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1415 [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1416
1417 Attributes:
1418
1419 code, severity?
1420
1421 Content:
1422
1423 com:Text+
1424
1425 Attribute Documentation:
1426
1427 |**Name**|**Type**|**Documentation**
1428 |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.
1429 |severity|SeverityCodeType|
1430
1431 Element Documentation:
1432
1433 |**Name**|**Type**|**Documentation**
1434 |com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1435
1436 1.
1437 11.
1438 111. Simple Types
1439
1440 **SeverityCodeType:**
1441
1442 Derived by restriction of xs:string .
1443
1444 Enumerations:
1445
1446 |**Value**|**Documentation**
1447 |Error|Error indicates the status message coresponds to an error.
1448 |Warning|Warning indicates that the status message corresponds to a warning.
1449 |Information|Information indicates that the status message corresponds to an informational message.
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464