Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -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 === 162 +1. 163 +11. 164 +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 183 + [[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. 191 +|**Name**|**Type**|**Documentation** 192 +|Header|StructureHeaderType| 193 +|Structures|str:StructuresType| 194 +|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 201 + [[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. 209 +|**Name**|**Type**|**Documentation** 210 +|Header|GenericDataHeaderTyp e| 211 +|DataSet|dat:DataSetType| 212 +|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 - ***GenericTimeSeriesDataType218 +//MessageType// (restriction) 219 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType (restriction) 220 + [[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. 228 +|**Name**|**Type**|**Documentation** 229 +|Header|GenericTimeSeriesDat aHeaderType| 230 +|DataSet|dat: TimeSeriesDataSetTyp e| 231 +|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 - **StructureSpecificDataType237 +//MessageType// (restriction) 238 + [[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. 246 +|**Name**|**Type**|**Documentation** 247 +|Header|StructureSpecificDat aHeaderType| 248 +|DataSet|//dsd:DataSetType//| 249 +|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 - ***StructureSpecificTimeSeriesDataType255 +//MessageType// (restriction) 256 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType (restriction) 257 + [[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. 265 +|**Name**|**Type**|**Documentation** 266 +|Header|StructureSpecificTim eSeriesDataHeaderTyp e| 267 +|DataSet|//dsd: TimeSeriesDataSetTyp e//| 268 +|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 - **GenericMetadataType274 +//MessageType// (restriction) 275 + [[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. 283 +|**Name**|**Type**|**Documentation** 284 +|Header|GenericMetadataHeade rType| 285 +|MetadataSet|rep:MetadataSetType| 286 +|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 - **StructureSpecificMetadataType292 +//MessageType// (restriction) 293 + [[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. 301 +|**Name**|**Type**|**Documentation** 302 +|Header|StructureSpecificMet adataHeaderType| 303 +|MetadataSet|//msd:MetadataSetType//| 304 +|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 - **RegistryInterfaceType310 +//MessageType// (restriction) 311 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType 317 317 318 318 Content: 319 319 ... ... @@ -321,84 +321,83 @@ 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. 319 +|**Name**|**Type**|**Documentation** 320 +|Header|BasicHeaderType| 321 +|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. 322 +|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. 323 +|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. 324 +|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. 325 +|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. 326 +|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. 327 +|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. 328 +|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. 329 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 330 +|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. 331 +|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. 332 +|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 - ***SubmitRegistrationsRequestType338 +//MessageType// (restriction) 339 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 340 + [[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: 344 +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. 346 +Element Documentation: 357 357 348 +|**Name**|**Type**|**Documentation** 349 +|Header|BasicHeaderType| 350 +|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. 351 + 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 - ***SubmitRegistrationsResponseType356 +//MessageType// (restriction) 357 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 358 + [[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: 362 +Header, SubmitRegistrationsResponse, ftr:Footer? 370 370 371 -(% style="width:847.294px" %) 372 -|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 373 -|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) 374 -|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 375 -|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 364 +Element Documentation: 376 376 366 +|**Name**|**Type**|**Documentation** 367 +|Header|BasicHeaderType| 368 +|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. 369 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 370 + 377 377 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 378 378 379 379 Derivation: 380 380 381 - *//MessageType// (restriction)382 - **RegistryInterfaceType (restriction)383 - ***QueryRegistrationRequestType375 +//MessageType// (restriction) 376 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 377 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType 384 384 385 385 Content: 386 386 387 -* Header, QueryRegistrationRequest 388 -* Element Documentation: 381 +Header, QueryRegistrationRequest 389 389 390 -(% style="width:847.294px" %) 391 -|**Name**|**Type**|(% style="width:397px" %)**Documentation** 392 -|Header|BasicHeaderType|(% style="width:397px" %) 393 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 383 +Element Documentation: 394 394 385 +|**Name**|**Type**|**Documentation** 386 +|Header|BasicHeaderType| 387 +|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. 388 + 395 395 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 396 396 397 397 Derivation: 398 398 399 - *//MessageType// (restriction)400 - **RegistryInterfaceType (restriction)401 - ***QueryRegistrationResponseType393 +//MessageType// (restriction) 394 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 395 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType 402 402 403 403 Content: 404 404 ... ... @@ -406,19 +406,18 @@ 406 406 407 407 Element Documentation: 408 408 409 -(% style="width:856.294px" %) 410 -|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation** 411 -|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %) 412 -|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 413 -|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 403 +|**Name**|**Type**|**Documentation** 404 +|Header|BasicHeaderType| 405 +|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. 406 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 414 414 415 415 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 416 416 417 417 Derivation: 418 418 419 - *//MessageType// (restriction)420 - **RegistryInterfaceType (restriction)421 - ***SubmitStructureRequestType412 +//MessageType// (restriction) 413 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 414 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType 422 422 423 423 Content: 424 424 ... ... @@ -435,8 +435,8 @@ 435 435 Derivation: 436 436 437 437 //MessageType// (restriction) 438 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 439 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType 431 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 432 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType 440 440 441 441 Content: 442 442 ... ... @@ -454,8 +454,8 @@ 454 454 Derivation: 455 455 456 456 //MessageType// (restriction) 457 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 458 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType 450 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 451 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType 459 459 460 460 Content: 461 461 ... ... @@ -472,8 +472,8 @@ 472 472 Derivation: 473 473 474 474 //MessageType// (restriction) 475 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 476 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType 468 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 469 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType 477 477 478 478 Content: 479 479 ... ... @@ -491,8 +491,8 @@ 491 491 Derivation: 492 492 493 493 //MessageType// (restriction) 494 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 495 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType 487 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 488 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType 496 496 497 497 Content: 498 498 ... ... @@ -509,8 +509,8 @@ 509 509 Derivation: 510 510 511 511 //MessageType// (restriction) 512 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 513 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType 505 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 506 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType 514 514 515 515 Content: 516 516 ... ... @@ -1026,7 +1026,7 @@ 1026 1026 Derivation: 1027 1027 1028 1028 //MessageType// (restriction) 1029 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType 1022 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType 1030 1030 1031 1031 Content: 1032 1032 ... ... @@ -1101,7 +1101,7 @@ 1101 1101 Derivation: 1102 1102 1103 1103 //BaseHeaderType// (restriction) 1104 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType 1097 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType 1105 1105 1106 1106 Content: 1107 1107 ... ... @@ -1250,7 +1250,7 @@ 1250 1250 Derivation: 1251 1251 1252 1252 //BaseHeaderType// (restriction) 1253 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType 1246 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType 1254 1254 1255 1255 Content: 1256 1256 ... ... @@ -1277,7 +1277,7 @@ 1277 1277 Derivation: 1278 1278 1279 1279 //BaseHeaderType// (restriction) 1280 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType 1273 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType 1281 1281 1282 1282 Content: 1283 1283 ... ... @@ -1318,7 +1318,7 @@ 1318 1318 Derivation: 1319 1319 1320 1320 PartyType (extension) 1321 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1314 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1322 1322 1323 1323 Attributes: 1324 1324 ... ... @@ -1358,8 +1358,8 @@ 1358 1358 |URI|xs:anyURI|URI holds an information URL for the contact person. 1359 1359 |Email|xs:string|Email holds the email address for the contact person. 1360 1360 1361 -1. 1362 -11. 1354 +1. 1355 +11. 1363 1363 111. Simple Types 1364 1364 1365 1365 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. ... ... @@ -1368,13 +1368,13 @@ 1368 1368 1369 1369 xs:dateTime, xs:date. 1370 1370 1371 -1. 1364 +1. 1372 1372 11. Message Footer Namespace 1373 1373 1374 1374 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1375 1375 1376 -1. 1377 -11. 1369 +1. 1370 +11. 1378 1378 111. Summary 1379 1379 1380 1380 Referenced Namespaces: ... ... @@ -1389,14 +1389,14 @@ 1389 1389 2 Complex Types 1390 1390 1 Simple Type 1391 1391 1392 -1. 1393 -11. 1385 +1. 1386 +11. 1394 1394 111. Global Elements 1395 1395 1396 1396 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1397 1397 1398 -1. 1399 -11. 1391 +1. 1392 +11. 1400 1400 111. Complex Types 1401 1401 1402 1402 **FooterType: **FooterType describes the structure of a message footer. The footer is used to convey any error, information, or warning messages. This is to be used when the message has payload, but also needs to communicate additional information. If an error occurs and no payload is generated, an Error message should be returned. ... ... @@ -1415,8 +1415,8 @@ 1415 1415 Derivation: 1416 1416 1417 1417 com:StatusMessageType (restriction) 1418 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1419 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1411 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1412 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1420 1420 1421 1421 Attributes: 1422 1422 ... ... @@ -1437,8 +1437,8 @@ 1437 1437 |**Name**|**Type**|**Documentation** 1438 1438 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1439 1439 1440 -1. 1441 -11. 1433 +1. 1434 +11. 1442 1442 111. Simple Types 1443 1443 1444 1444 **SeverityCodeType:**