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
-
... ... @@ -38,17 +38,18 @@ 38 38 39 39 Referenced Namespaces: 40 40 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 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 52 52 53 53 Contents: 54 54 ... ... @@ -56,9 +56,7 @@ 56 56 62 Complex Types 57 57 1 Simple Type 58 58 59 -1. 60 -11. 61 -111. Global Elements 60 +=== 2.1.2 Global Elements === 62 62 63 63 **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. 64 64 ... ... @@ -160,9 +160,7 @@ 160 160 161 161 **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. 162 162 163 -1. 164 -11. 165 -111. Complex Types 162 +=== 2.1.3 Complex Types === 166 166 167 167 **//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. 168 168 ... ... @@ -181,7 +181,7 @@ 181 181 Derivation: 182 182 183 183 //MessageType// (restriction) 184 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureType181 + StructureType 185 185 186 186 Content: 187 187 ... ... @@ -189,10 +189,11 @@ 189 189 190 190 Element Documentation: 191 191 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. 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. 196 196 197 197 **GenericDataType: **GenericDataType defines the contents of a generic data message. 198 198 ... ... @@ -199,7 +199,7 @@ 199 199 Derivation: 200 200 201 201 //MessageType// (restriction) 202 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType200 + GenericDataType 203 203 204 204 Content: 205 205 ... ... @@ -207,18 +207,19 @@ 207 207 208 208 Element Documentation: 209 209 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. 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. 214 214 215 215 **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message. 216 216 217 217 Derivation: 218 218 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="-"]]GenericTimeSeriesDataType218 +* //MessageType// (restriction) 219 +** GenericDataType (restriction) 220 +*** GenericTimeSeriesDataType 222 222 223 223 Content: 224 224 ... ... @@ -226,17 +226,18 @@ 226 226 227 227 Element Documentation: 228 228 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. 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 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 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType238 +* //MessageType// (restriction) 239 +** StructureSpecificDataType 240 240 241 241 Content: 242 242 ... ... @@ -244,18 +244,19 @@ 244 244 245 245 Element Documentation: 246 246 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. 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. 251 251 252 252 **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message. 253 253 254 254 Derivation: 255 255 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="-"]]StructureSpecificTimeSeriesDataType257 +* //MessageType// (restriction) 258 +** StructureSpecificDataType (restriction) 259 +*** StructureSpecificTimeSeriesDataType 259 259 260 260 Content: 261 261 ... ... @@ -263,17 +263,18 @@ 263 263 264 264 Element Documentation: 265 265 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. 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. 270 270 271 271 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message. 272 272 273 273 Derivation: 274 274 275 -//MessageType// (restriction) 276 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericMetadataType277 +* //MessageType// (restriction) 278 +** GenericMetadataType 277 277 278 278 Content: 279 279 ... ... @@ -281,17 +281,18 @@ 281 281 282 282 Element Documentation: 283 283 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. 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. 288 288 289 289 **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. 290 290 291 291 Derivation: 292 292 293 -//MessageType// (restriction) 294 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataType296 +* //MessageType// (restriction) 297 +** StructureSpecificMetadataType 295 295 296 296 Content: 297 297 ... ... @@ -299,17 +299,18 @@ 299 299 300 300 Element Documentation: 301 301 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. 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. 306 306 307 307 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. 308 308 309 309 Derivation: 310 310 311 -//MessageType// (restriction) 312 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType315 +* //MessageType// (restriction) 316 +** RegistryInterfaceType 313 313 314 314 Content: 315 315 ... ... @@ -317,46 +317,47 @@ 317 317 318 318 Element Documentation: 319 319 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. 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. 334 334 335 335 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 336 336 337 337 Derivation: 338 338 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="-"]]SubmitRegistrationsRequestType344 +* //MessageType// (restriction) 345 +** RegistryInterfaceType (restriction) 346 +*** SubmitRegistrationsRequestType 342 342 343 343 Content: 344 344 345 -Header, SubmitRegistrationsRequest 350 +* Header, SubmitRegistrationsRequest 351 +* Element Documentation: 346 346 347 -Element Documentation: 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. 348 348 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 - 353 353 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 354 354 355 355 Derivation: 356 356 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="-"]]SubmitRegistrationsResponseType362 +* //MessageType// (restriction) 363 +** RegistryInterfaceType (restriction) 364 +*** SubmitRegistrationsResponseType 360 360 361 361 Content: 362 362 ... ... @@ -374,8 +374,8 @@ 374 374 Derivation: 375 375 376 376 //MessageType// (restriction) 377 - 378 - 382 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 383 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType 379 379 380 380 Content: 381 381 ... ... @@ -392,8 +392,8 @@ 392 392 Derivation: 393 393 394 394 //MessageType// (restriction) 395 - 396 - 400 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 401 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType 397 397 398 398 Content: 399 399 ... ... @@ -411,8 +411,8 @@ 411 411 Derivation: 412 412 413 413 //MessageType// (restriction) 414 - 415 - 419 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 420 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType 416 416 417 417 Content: 418 418 ... ... @@ -429,8 +429,8 @@ 429 429 Derivation: 430 430 431 431 //MessageType// (restriction) 432 - 433 - 437 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 438 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType 434 434 435 435 Content: 436 436 ... ... @@ -448,8 +448,8 @@ 448 448 Derivation: 449 449 450 450 //MessageType// (restriction) 451 - 452 - 456 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 457 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType 453 453 454 454 Content: 455 455 ... ... @@ -466,8 +466,8 @@ 466 466 Derivation: 467 467 468 468 //MessageType// (restriction) 469 - 470 - 474 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 475 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType 471 471 472 472 Content: 473 473 ... ... @@ -485,8 +485,8 @@ 485 485 Derivation: 486 486 487 487 //MessageType// (restriction) 488 - 489 - 493 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 494 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType 490 490 491 491 Content: 492 492 ... ... @@ -503,8 +503,8 @@ 503 503 Derivation: 504 504 505 505 //MessageType// (restriction) 506 - 507 - 511 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 512 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType 508 508 509 509 Content: 510 510 ... ... @@ -1020,7 +1020,7 @@ 1020 1020 Derivation: 1021 1021 1022 1022 //MessageType// (restriction) 1023 - 1028 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType 1024 1024 1025 1025 Content: 1026 1026 ... ... @@ -1095,7 +1095,7 @@ 1095 1095 Derivation: 1096 1096 1097 1097 //BaseHeaderType// (restriction) 1098 - 1103 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType 1099 1099 1100 1100 Content: 1101 1101 ... ... @@ -1244,7 +1244,7 @@ 1244 1244 Derivation: 1245 1245 1246 1246 //BaseHeaderType// (restriction) 1247 - 1252 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType 1248 1248 1249 1249 Content: 1250 1250 ... ... @@ -1271,7 +1271,7 @@ 1271 1271 Derivation: 1272 1272 1273 1273 //BaseHeaderType// (restriction) 1274 - 1279 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType 1275 1275 1276 1276 Content: 1277 1277 ... ... @@ -1312,7 +1312,7 @@ 1312 1312 Derivation: 1313 1313 1314 1314 PartyType (extension) 1315 - 1320 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1316 1316 1317 1317 Attributes: 1318 1318 ... ... @@ -1352,8 +1352,8 @@ 1352 1352 |URI|xs:anyURI|URI holds an information URL for the contact person. 1353 1353 |Email|xs:string|Email holds the email address for the contact person. 1354 1354 1355 -1. 1356 -11. 1360 +1. 1361 +11. 1357 1357 111. Simple Types 1358 1358 1359 1359 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. ... ... @@ -1362,13 +1362,13 @@ 1362 1362 1363 1363 xs:dateTime, xs:date. 1364 1364 1365 -1. 1370 +1. 1366 1366 11. Message Footer Namespace 1367 1367 1368 1368 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1369 1369 1370 -1. 1371 -11. 1375 +1. 1376 +11. 1372 1372 111. Summary 1373 1373 1374 1374 Referenced Namespaces: ... ... @@ -1383,14 +1383,14 @@ 1383 1383 2 Complex Types 1384 1384 1 Simple Type 1385 1385 1386 -1. 1387 -11. 1391 +1. 1392 +11. 1388 1388 111. Global Elements 1389 1389 1390 1390 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1391 1391 1392 -1. 1393 -11. 1397 +1. 1398 +11. 1394 1394 111. Complex Types 1395 1395 1396 1396 **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. ... ... @@ -1409,8 +1409,8 @@ 1409 1409 Derivation: 1410 1410 1411 1411 com:StatusMessageType (restriction) 1412 - 1413 - 1417 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1418 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1414 1414 1415 1415 Attributes: 1416 1416 ... ... @@ -1431,8 +1431,8 @@ 1431 1431 |**Name**|**Type**|**Documentation** 1432 1432 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1433 1433 1434 -1. 1435 -11. 1439 +1. 1440 +11. 1436 1436 111. Simple Types 1437 1437 1438 1438 **SeverityCodeType:**