Changes for page Part I. Message Namespace

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

From version 3.10
edited by Helena
on 2025/06/23 17:07
Change comment: There is no comment for this version
To version 2.3
edited by Helena
on 2025/06/23 16:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,18 +38,17 @@
38 38  
39 39  Referenced Namespaces:
40 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
41 +|**Namespace**|**Prefix**
42 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com
43 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|dat
44 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|dsd
45 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|ftr
46 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|rep
47 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|msd
48 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|qry
49 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|ref
50 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|str
51 +|http:~/~/www.w3.org/2001/XMLSchema|xs
53 53  
54 54  Contents:
55 55  
... ... @@ -57,7 +57,9 @@
57 57  62 Complex Types
58 58  1 Simple Type
59 59  
60 -=== 2.1.2 Global Elements ===
59 +1.
60 +11.
61 +111. Global Elements
61 61  
62 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 63  
... ... @@ -159,7 +159,9 @@
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  
162 -=== 2.1.3 Complex Types ===
163 +1.
164 +11.
165 +111. Complex Types
163 163  
164 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 165  
... ... @@ -178,7 +178,7 @@
178 178  Derivation:
179 179  
180 180  //MessageType// (restriction)
181 - StructureType
184 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureType
182 182  
183 183  Content:
184 184  
... ... @@ -186,11 +186,10 @@
186 186  
187 187  Element Documentation:
188 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.
192 +|**Name**|**Type**|**Documentation**
193 +|Header|StructureHeaderType|
194 +|Structures|str:StructuresType|
195 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
194 194  
195 195  **GenericDataType: **GenericDataType defines the contents of a generic data message.
196 196  
... ... @@ -197,7 +197,7 @@
197 197  Derivation:
198 198  
199 199  //MessageType// (restriction)
200 - GenericDataType
202 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType
201 201  
202 202  Content:
203 203  
... ... @@ -205,19 +205,18 @@
205 205  
206 206  Element Documentation:
207 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.
210 +|**Name**|**Type**|**Documentation**
211 +|Header|GenericDataHeaderTyp e|
212 +|DataSet|dat:DataSetType|
213 +|ftr:Footer|ftr:FooterType|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.
215 215  
216 216  Derivation:
217 217  
218 -* //MessageType// (restriction)
219 -** GenericDataType (restriction)
220 -*** GenericTimeSeriesDataType
219 +//MessageType// (restriction)
220 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType (restriction)
221 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericTimeSeriesDataType
221 221  
222 222  Content:
223 223  
... ... @@ -225,18 +225,17 @@
225 225  
226 226  Element Documentation:
227 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.
229 +|**Name**|**Type**|**Documentation**
230 +|Header|GenericTimeSeriesDat aHeaderType|
231 +|DataSet|dat: TimeSeriesDataSetTyp e|
232 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
233 233  
234 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 235  
236 236  Derivation:
237 237  
238 -* //MessageType// (restriction)
239 -** StructureSpecificDataType
238 +//MessageType// (restriction)
239 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType
240 240  
241 241  Content:
242 242  
... ... @@ -244,19 +244,18 @@
244 244  
245 245  Element Documentation:
246 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.
247 +|**Name**|**Type**|**Documentation**
248 +|Header|StructureSpecificDat aHeaderType|
249 +|DataSet|//dsd:DataSetType//|
250 +|ftr:Footer|ftr:FooterType|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.
254 254  
255 255  Derivation:
256 256  
257 -* //MessageType// (restriction)
258 -** StructureSpecificDataType (restriction)
259 -*** StructureSpecificTimeSeriesDataType
256 +//MessageType// (restriction)
257 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType (restriction)
258 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificTimeSeriesDataType
260 260  
261 261  Content:
262 262  
... ... @@ -264,18 +264,17 @@
264 264  
265 265  Element Documentation:
266 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.
266 +|**Name**|**Type**|**Documentation**
267 +|Header|StructureSpecificTim eSeriesDataHeaderTyp e|
268 +|DataSet|//dsd: TimeSeriesDataSetTyp e//|
269 +|ftr:Footer|ftr:FooterType|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.
274 274  
275 275  Derivation:
276 276  
277 -* //MessageType// (restriction)
278 -** GenericMetadataType
275 +//MessageType// (restriction)
276 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
279 279  
280 280  Content:
281 281  
... ... @@ -283,18 +283,17 @@
283 283  
284 284  Element Documentation:
285 285  
286 -(% style="width:836.294px" %)
287 -|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
288 -|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %)
289 -|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
290 -|(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
284 +|**Name**|**Type**|**Documentation**
285 +|Header|GenericMetadataHeade rType|
286 +|MetadataSet|rep:MetadataSetType|
287 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
291 291  
292 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.
293 293  
294 294  Derivation:
295 295  
296 -* //MessageType// (restriction)
297 -** StructureSpecificMetadataType
293 +//MessageType// (restriction)
294 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
298 298  
299 299  Content:
300 300  
... ... @@ -302,18 +302,17 @@
302 302  
303 303  Element Documentation:
304 304  
305 -(% style="width:841.294px" %)
306 -|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
307 -|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
308 -|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
309 -|(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
302 +|**Name**|**Type**|**Documentation**
303 +|Header|StructureSpecificMet adataHeaderType|
304 +|MetadataSet|//msd:MetadataSetType//|
305 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
310 310  
311 311  **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
312 312  
313 313  Derivation:
314 314  
315 -* //MessageType// (restriction)
316 -** RegistryInterfaceType
311 +//MessageType// (restriction)
312 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
317 317  
318 318  Content:
319 319  
... ... @@ -321,53 +321,53 @@
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.
320 +|**Name**|**Type**|**Documentation**
321 +|Header|BasicHeaderType|
322 +|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.
323 +|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.
324 +|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.
325 +|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.
326 +|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.
327 +|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.
328 +|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.
329 +|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.
330 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
331 +|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.
332 +|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.
333 +|ftr:Footer|ftr:FooterType|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  
342 342  Derivation:
343 343  
344 -* //MessageType// (restriction)
345 -** RegistryInterfaceType (restriction)
346 -*** SubmitRegistrationsRequestType
339 +//MessageType// (restriction)
340 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
341 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsRequestType
347 347  
348 348  Content:
349 349  
350 -* Header, SubmitRegistrationsRequest
351 -* Element Documentation:
345 +Header, SubmitRegistrationsRequest
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.
347 +Element Documentation:
357 357  
349 +|**Name**|**Type**|**Documentation**
350 +|Header|BasicHeaderType|
351 +|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.
352 +
358 358  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
359 359  
360 360  Derivation:
361 361  
362 -* //MessageType// (restriction)
363 -** RegistryInterfaceType (restriction)
364 -*** SubmitRegistrationsResponseType
357 +//MessageType// (restriction)
358 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
359 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
365 365  
366 366  Content:
367 367  
368 -* Header, SubmitRegistrationsResponse, ftr:Footer?
369 -* Element Documentation:
363 +Header, SubmitRegistrationsResponse, ftr:Footer?
370 370  
365 +Element Documentation:
366 +
371 371  |**Name**|**Type**|**Documentation**
372 372  |Header|BasicHeaderType|
373 373  |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.
... ... @@ -378,8 +378,8 @@
378 378  Derivation:
379 379  
380 380  //MessageType// (restriction)
381 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
382 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
377 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
378 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
383 383  
384 384  Content:
385 385  
... ... @@ -396,8 +396,8 @@
396 396  Derivation:
397 397  
398 398  //MessageType// (restriction)
399 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
400 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
395 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
396 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
401 401  
402 402  Content:
403 403  
... ... @@ -415,8 +415,8 @@
415 415  Derivation:
416 416  
417 417  //MessageType// (restriction)
418 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
419 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
414 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
415 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
420 420  
421 421  Content:
422 422  
... ... @@ -433,8 +433,8 @@
433 433  Derivation:
434 434  
435 435  //MessageType// (restriction)
436 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
437 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
432 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
433 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
438 438  
439 439  Content:
440 440  
... ... @@ -452,8 +452,8 @@
452 452  Derivation:
453 453  
454 454  //MessageType// (restriction)
455 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
456 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
451 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
452 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
457 457  
458 458  Content:
459 459  
... ... @@ -470,8 +470,8 @@
470 470  Derivation:
471 471  
472 472  //MessageType// (restriction)
473 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
474 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
469 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
470 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
475 475  
476 476  Content:
477 477  
... ... @@ -489,8 +489,8 @@
489 489  Derivation:
490 490  
491 491  //MessageType// (restriction)
492 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
493 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
488 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
489 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
494 494  
495 495  Content:
496 496  
... ... @@ -507,8 +507,8 @@
507 507  Derivation:
508 508  
509 509  //MessageType// (restriction)
510 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
511 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
506 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
507 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
512 512  
513 513  Content:
514 514  
... ... @@ -1024,7 +1024,7 @@
1024 1024  Derivation:
1025 1025  
1026 1026  //MessageType// (restriction)
1027 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1023 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1028 1028  
1029 1029  Content:
1030 1030  
... ... @@ -1099,7 +1099,7 @@
1099 1099  Derivation:
1100 1100  
1101 1101  //BaseHeaderType// (restriction)
1102 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1098 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1103 1103  
1104 1104  Content:
1105 1105  
... ... @@ -1248,7 +1248,7 @@
1248 1248  Derivation:
1249 1249  
1250 1250  //BaseHeaderType// (restriction)
1251 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1247 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1252 1252  
1253 1253  Content:
1254 1254  
... ... @@ -1275,7 +1275,7 @@
1275 1275  Derivation:
1276 1276  
1277 1277  //BaseHeaderType// (restriction)
1278 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1274 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1279 1279  
1280 1280  Content:
1281 1281  
... ... @@ -1316,7 +1316,7 @@
1316 1316  Derivation:
1317 1317  
1318 1318  PartyType (extension)
1319 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1315 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1320 1320  
1321 1321  Attributes:
1322 1322  
... ... @@ -1356,8 +1356,8 @@
1356 1356  |URI|xs:anyURI|URI holds an information URL for the contact person.
1357 1357  |Email|xs:string|Email holds the email address for the contact person.
1358 1358  
1359 -1.
1360 -11.
1355 +1.
1356 +11.
1361 1361  111. Simple Types
1362 1362  
1363 1363  **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
... ... @@ -1366,13 +1366,13 @@
1366 1366  
1367 1367  xs:dateTime, xs:date.
1368 1368  
1369 -1.
1365 +1.
1370 1370  11. Message Footer Namespace
1371 1371  
1372 1372  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1373 1373  
1374 -1.
1375 -11.
1370 +1.
1371 +11.
1376 1376  111. Summary
1377 1377  
1378 1378  Referenced Namespaces:
... ... @@ -1387,14 +1387,14 @@
1387 1387  2 Complex Types
1388 1388  1 Simple Type
1389 1389  
1390 -1.
1391 -11.
1386 +1.
1387 +11.
1392 1392  111. Global Elements
1393 1393  
1394 1394  **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1395 1395  
1396 -1.
1397 -11.
1392 +1.
1393 +11.
1398 1398  111. Complex Types
1399 1399  
1400 1400  **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.
... ... @@ -1413,8 +1413,8 @@
1413 1413  Derivation:
1414 1414  
1415 1415  com:StatusMessageType (restriction)
1416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1417 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1412 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1413 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1418 1418  
1419 1419  Attributes:
1420 1420  
... ... @@ -1435,8 +1435,8 @@
1435 1435  |**Name**|**Type**|**Documentation**
1436 1436  |com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1437 1437  
1438 -1.
1439 -11.
1434 +1.
1435 +11.
1440 1440  111. Simple Types
1441 1441  
1442 1442  **SeverityCodeType:**