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
-
... ... @@ -42,10 +42,10 @@ 42 42 |(% style="width:612px" %)**Namespace**|(% style="width:173px" %)**Prefix** 43 43 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:173px" %)com 44 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 45 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)[[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]] 46 46 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|(% style="width:173px" %)ftr 47 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 48 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|(% style="width:173px" %)[[msd>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] 49 49 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|(% style="width:173px" %)qry 50 50 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|(% style="width:173px" %)ref 51 51 |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|(% style="width:173px" %)str ... ... @@ -52,6 +52,7 @@ 52 52 |(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs 53 53 54 54 Contents: 55 + 55 55 50 Global Elements 56 56 62 Complex Types 57 57 1 Simple Type ... ... @@ -168,10 +168,9 @@ 168 168 169 169 Element Documentation: 170 170 171 -(% style="width:1004.83px" %) 172 -|**Name**|**Type**|(% style="width:631px" %)**Documentation** 173 -|Header|//BaseHeaderType//|(% style="width:631px" %) 174 -|ftr:Footer|ftr:FooterType|(% style="width:631px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 172 +|**Name**|**Type**|**Documentation** 173 +|Header|//BaseHeaderType//| 174 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 175 175 176 176 **StructureType: **StructureType defines the contents of a structure message. The payload is optional since this message may be returned from a web service with only information in the footer. 177 177 ... ... @@ -181,6 +181,7 @@ 181 181 ** StructureType 182 182 183 183 Content: 184 + 184 184 Header, Structures?, ftr:Footer? 185 185 186 186 Element Documentation: ... ... @@ -199,6 +199,7 @@ 199 199 ** GenericDataType 200 200 201 201 Content: 203 + 202 202 Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 203 203 204 204 Element Documentation: ... ... @@ -218,6 +218,7 @@ 218 218 *** GenericTimeSeriesDataType 219 219 220 220 Content: 223 + 221 221 Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 222 222 223 223 Element Documentation: ... ... @@ -236,6 +236,7 @@ 236 236 ** StructureSpecificDataType 237 237 238 238 Content: 242 + 239 239 Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 240 240 241 241 Element Documentation: ... ... @@ -243,7 +243,7 @@ 243 243 (% style="width:828.294px" %) 244 244 |**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation** 245 245 |Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %) 246 -|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %) 250 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//[[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]]:DataSetType//|(% style="width:420px" %) 247 247 |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. 248 248 249 249 **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message. ... ... @@ -255,6 +255,7 @@ 255 255 *** StructureSpecificTimeSeriesDataType 256 256 257 257 Content: 262 + 258 258 Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 259 259 260 260 Element Documentation: ... ... @@ -262,7 +262,7 @@ 262 262 (% style="width:839.294px" %) 263 263 |**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation** 264 264 |Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %) 265 -|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %) 270 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//[[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]]: TimeSeriesDataSetTyp e//|(% style="width:434px" %) 266 266 |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. 267 267 268 268 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message. ... ... @@ -273,6 +273,7 @@ 273 273 ** GenericMetadataType 274 274 275 275 Content: 281 + 276 276 Header, MetadataSet*, ftr:Footer? 277 277 278 278 Element Documentation: ... ... @@ -279,7 +279,7 @@ 279 279 280 280 (% style="width:836.294px" %) 281 281 |(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation** 282 -|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeaderType|(% style="width:427px" %) 288 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %) 283 283 |(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %) 284 284 |(% 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. 285 285 ... ... @@ -291,6 +291,7 @@ 291 291 ** StructureSpecificMetadataType 292 292 293 293 Content: 300 + 294 294 Header, MetadataSet*, ftr:Footer? 295 295 296 296 Element Documentation: ... ... @@ -297,8 +297,8 @@ 297 297 298 298 (% style="width:841.294px" %) 299 299 |(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation** 300 -|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMetadataHeaderType|(% style="width:428px" %) 301 -|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %) 307 +|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %) 308 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//[[msd>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]:MetadataSetType//|(% style="width:428px" %) 302 302 |(% 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. 303 303 304 304 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. ... ... @@ -309,25 +309,26 @@ 309 309 ** RegistryInterfaceType 310 310 311 311 Content: 319 + 312 312 Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, ftr:Footer? 313 313 314 314 Element Documentation: 315 315 316 -(% style="width: 1000.83px" %)317 -|**Name**| (% style="width:317px" %)**Type**|(% style="width:491px" %)**Documentation**318 -|Header| (% style="width:317px" %)BasicHeaderType|(% style="width:491px" %)319 -|SubmitRegistrationsRequest| (% style="width:317px" %)ref: SubmitRegistrationsRequestType|(% style="width:491px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.320 -|SubmitRegistrationsResponse| (% style="width:317px" %)ref: SubmitRegistrationsResponseType|(% style="width:491px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.321 -|QueryRegistrationRequest| (% style="width:317px" %)ref: QueryRegistrationRequestType|(% style="width:491px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.322 -|QueryRegistrationResponse| (% style="width:317px" %)ref: QueryRegistrationResponseType|(% style="width:491px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.323 -|SubmitStructureReque st|(%style="width:317px" %)ref: SubmitStructureRequestType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.324 -|SubmitStructureResponse| (% style="width:317px" %)ref: SubmitStructureResponseType|(% style="width:491px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.325 -|SubmitSubscriptionsRequest| (% style="width:317px" %)ref: SubmitSubscriptionsRequestType|(% style="width:491px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.326 -|SubmitSubscriptionsResponse| (% style="width:317px" %)ref: SubmitSubscriptionsResponseType|(% style="width:491px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.327 -|QuerySubscriptionRequest| (% style="width:317px" %)ref: QuerySubscriptionRequestType|(% style="width:491px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.328 -|QuerySubscriptionResponse| (% style="width:317px" %)ref: QuerySubscriptionResponseType|(% style="width:491px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.329 -|NotifyRegistryEvent| (% style="width:317px" %)ref: NotifyRegistryEventType|(% style="width:491px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.330 -|ftr:Footer| (% style="width:317px" %)ftr:FooterType|(% style="width:491px" %)Footer is used to communicate information such as error and warnings after the payload of a message.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>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 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>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys. 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, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information. 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>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID. 335 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation. 336 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent. 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>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided. 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. 331 331 332 332 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 333 333 ... ... @@ -338,14 +338,15 @@ 338 338 *** SubmitRegistrationsRequestType 339 339 340 340 Content: 349 + 341 341 Header, SubmitRegistrationsRequest 342 342 343 343 Element Documentation: 344 344 345 -(% style="width: 966.835px" %)346 -|**Name**|**Type**|(% style="width: 490px" %)**Documentation**347 -|Header|BasicHeaderType|(% style="width: 490px" %)348 -|SubmitRegistrationsRequest|ref: SubmitRegistrationsRequestType|(% style="width: 490px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.354 +(% style="width:844.294px" %) 355 +|**Name**|**Type**|(% style="width:377px" %)**Documentation** 356 +|Header|BasicHeaderType|(% style="width:377px" %) 357 +|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>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 349 349 350 350 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 351 351 ... ... @@ -356,15 +356,16 @@ 356 356 *** SubmitRegistrationsResponseType 357 357 358 358 Content: 368 + 359 359 Header, SubmitRegistrationsResponse, ftr:Footer? 360 360 361 361 Element Documentation: 362 362 363 -(% style="width: 974.835px" %)364 -|**Name**|(% style="width:210px" %)**Type**|(% style="width:4 73px" %)**Documentation**365 -|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:4 73px" %)366 -|SubmitRegistrationsResponse|(% style="width:210px" %)ref: SubmitRegistrationsResponseType|(% style="width:4 73px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.367 -|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:4 73px" %)Footer is used to communicate information such as error and warnings after the payload of a message.373 +(% style="width:847.294px" %) 374 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 375 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) 376 +|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. 377 +|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. 368 368 369 369 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 370 370 ... ... @@ -375,14 +375,15 @@ 375 375 *** QueryRegistrationRequestType 376 376 377 377 Content: 388 + 378 378 Header, QueryRegistrationRequest 379 379 380 380 Element Documentation: 381 381 382 -(% style="width: 971.835px" %)383 -|**Name**| (% style="width:288px" %)**Type**|(% style="width:476px" %)**Documentation**384 -|Header| (% style="width:288px" %)BasicHeaderType|(% style="width:476px" %)385 -|QueryRegistrationRequest| (% style="width:288px" %)ref: QueryRegistrationRequestType|(% style="width:476px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.393 +(% style="width:847.294px" %) 394 +|**Name**|**Type**|(% style="width:397px" %)**Documentation** 395 +|Header|BasicHeaderType|(% style="width:397px" %) 396 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys. 386 386 387 387 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 388 388 ... ... @@ -393,15 +393,16 @@ 393 393 *** QueryRegistrationResponseType 394 394 395 395 Content: 407 + 396 396 Header, QueryRegistrationResponse, ftr:Footer? 397 397 398 398 Element Documentation: 399 399 400 -(% style="width: 969.835px" %)401 -|**Name**|(% style="width:235px" %)**Type**|(% style="width:4 96px" %)**Documentation**402 -|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:4 96px" %)403 -|QueryRegistrationResponse|(% style="width:235px" %)ref: QueryRegistrationResponseType|(% style="width:4 96px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.404 -|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:4 96px" %)Footer is used to communicate information such as error and warnings after the payload of a message.412 +(% style="width:856.294px" %) 413 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation** 414 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %) 415 +|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. 416 +|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. 405 405 406 406 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 407 407 ... ... @@ -412,14 +412,15 @@ 412 412 *** SubmitStructureRequestType 413 413 414 414 Content: 427 + 415 415 Header, SubmitStructureRequest 416 416 417 417 Element Documentation: 418 418 419 -(% style="width: 970.835px" %)420 -|**Name**| (% style="width:286px" %)**Type**|(% style="width:491px" %)**Documentation**421 -|Header| (% style="width:286px" %)BasicHeaderType|(% style="width:491px" %)422 -|SubmitStructureReque st|(%style="width:286px" %)ref: SubmitStructureRequestType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.432 +(% style="width:870.294px" %) 433 +|**Name**|**Type**|(% style="width:453px" %)**Documentation** 434 +|Header|BasicHeaderType|(% style="width:453px" %) 435 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information. 423 423 424 424 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document. 425 425 ... ... @@ -430,15 +430,16 @@ 430 430 *** SubmitStructureResponseType 431 431 432 432 Content: 446 + 433 433 Header, SubmitStructureResponse, ftr:Footer? 434 434 435 435 Element Documentation: 436 436 437 -(% style="width: 969.835px" %)438 -|**Name**|(% style="width:246px" %)**Type**|(% style="width: 498px" %)**Documentation**439 -|Header|(% style="width:246px" %)BasicHeaderType|(% style="width: 498px" %)440 -|SubmitStructureResponse|(% style="width:246px" %)ref: SubmitStructureResponseType|(% style="width: 498px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.441 -|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width: 498px" %)Footer is used to communicate information such as error and warnings after the payload of a message.451 +(% style="width:835.294px" %) 452 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 453 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) 454 +|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 455 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 442 442 443 443 **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document. 444 444 ... ... @@ -449,14 +449,15 @@ 449 449 *** SubmitSubscriptionsRequestType 450 450 451 451 Content: 466 + 452 452 Header, SubmitSubscriptionsRequest 453 453 454 454 Element Documentation: 455 455 456 -(% style="width: 960.835px" %)457 -|**Name**|(% style="width:227px" %)**Type**|(% style="width: 445px" %)**Documentation**458 -|Header|(% style="width:227px" %)BasicHeaderType|(% style="width: 445px" %)459 -|SubmitSubscriptionsRequest|(% style="width:227px" %)ref: SubmitSubscriptionsRequestType|(% style="width: 445px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.471 +(% style="width:832.294px" %) 472 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 473 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %) 474 +|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 460 460 461 461 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document. 462 462 ... ... @@ -467,15 +467,16 @@ 467 467 *** SubmitSubscriptionsResponseType 468 468 469 469 Content: 485 + 470 470 Header, SubmitSubscriptionsResponse, ftr:Footer? 471 471 472 472 Element Documentation: 473 473 474 -(% style="width: 965.835px" %)475 -|**Name**|**Type**|(% style="width: 482px" %)**Documentation**476 -|Header|BasicHeaderType|(% style="width: 482px" %)477 -|SubmitSubscriptionsResponse|ref: SubmitSubscriptionsResponseType|(% style="width: 482px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.478 -|ftr:Footer|ftr:FooterType|(% style="width: 482px" %)Footer is used to communicate information such as error and warnings after the payload of a message.490 +(% style="width:843.294px" %) 491 +|**Name**|**Type**|(% style="width:362px" %)**Documentation** 492 +|Header|BasicHeaderType|(% style="width:362px" %) 493 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID. 494 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 479 479 480 480 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document. 481 481 ... ... @@ -486,14 +486,15 @@ 486 486 *** QuerySubscriptionRequestType 487 487 488 488 Content: 505 + 489 489 Header, QuerySubscriptionRequest 490 490 491 491 Element Documentation: 492 492 493 -(% style="width: 970.835px" %)494 -|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width: 483px" %)**Documentation**495 -|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width: 483px" %)496 -|(% style="width:230px" %)QuerySubscriptionRequest|(% style="width:254px" %)ref: QuerySubscriptionRequestType|(% style="width: 483px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.510 +(% style="width:839.294px" %) 511 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation** 512 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %) 513 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation. 497 497 498 498 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document. 499 499 ... ... @@ -504,15 +504,16 @@ 504 504 *** QuerySubscriptionResponseType 505 505 506 506 Content: 524 + 507 507 Header, QuerySubscriptionResponse, ftr:Footer? 508 508 509 509 Element Documentation: 510 510 511 -(% style="width:9 73.835px" %)512 -| (% style="width:233px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:443px" %)**Documentation**513 -| (% style="width:233px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:443px" %)514 -| (% style="width:233px" %)QuerySubscriptionResponse|(% style="width:295px" %)ref: QuerySubscriptionResponseType|(% style="width:443px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.515 -| (% style="width:233px" %)ftr:Footer|(% style="width:295px" %)ftr:FooterType|(% style="width:443px" %)Footer is used to communicate information such as error and warnings after the payload of a message.529 +(% style="width:912.294px" %) 530 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation** 531 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %) 532 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent. 533 +|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 516 516 517 517 **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document. 518 518 ... ... @@ -523,14 +523,15 @@ 523 523 *** NotifyRegistryEventType 524 524 525 525 Content: 544 + 526 526 Header, NotifyRegistryEvent 527 527 528 528 Element Documentation: 529 529 530 -(% style="width: 963.835px" %)531 -|**Name**| (% style="width:228px" %)**Type**|(% style="width:576px" %)**Documentation**532 -|Header| (% style="width:228px" %)BasicHeaderType|(% style="width:576px" %)533 -|NotifyRegistryEvent| (% style="width:228px" %)ref: NotifyRegistryEventType|(% style="width:576px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.549 +(% style="width:836.294px" %) 550 +|**Name**|**Type**|(% style="width:473px" %)**Documentation** 551 +|Header|BasicHeaderType|(% style="width:473px" %) 552 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided. 534 534 535 535 **DataQueryType: **DataQueryType defines the structure of a data query message. 536 536 ... ... @@ -540,6 +540,7 @@ 540 540 ** DataQueryType 541 541 542 542 Content: 562 + 543 543 Header, Query 544 544 545 545 Element Documentation: ... ... @@ -558,6 +558,7 @@ 558 558 *** GenericDataQueryType 559 559 560 560 Content: 581 + 561 561 Header, Query 562 562 563 563 Element Documentation: ... ... @@ -577,6 +577,7 @@ 577 577 **** GenericTimeSeriesDataQueryType 578 578 579 579 Content: 601 + 580 580 Header, Query 581 581 582 582 Element Documentation: ... ... @@ -595,6 +595,7 @@ 595 595 *** StructureSpecificTimeSeriesDataQueryType 596 596 597 597 Content: 620 + 598 598 Header, Query 599 599 600 600 Element Documentation: ... ... @@ -612,6 +612,7 @@ 612 612 ** MetadataQueryType 613 613 614 614 Content: 638 + 615 615 Header, Query 616 616 617 617 Element Documentation: ... ... @@ -629,6 +629,7 @@ 629 629 ** DataSchemaQueryType 630 630 631 631 Content: 656 + 632 632 Header, Query 633 633 634 634 Element Documentation: ... ... @@ -646,6 +646,7 @@ 646 646 ** MetadataSchemaQueryType 647 647 648 648 Content: 674 + 649 649 Header, Query 650 650 651 651 Element Documentation: ... ... @@ -663,6 +663,7 @@ 663 663 ** StructuresQueryType 664 664 665 665 Content: 692 + 666 666 Header, Query 667 667 668 668 Element Documentation: ... ... @@ -680,6 +680,7 @@ 680 680 ** DataflowQueryType 681 681 682 682 Content: 710 + 683 683 Header, Query 684 684 685 685 Element Documentation: ... ... @@ -697,6 +697,7 @@ 697 697 ** MetadataflowQueryType 698 698 699 699 Content: 728 + 700 700 Header, Query 701 701 702 702 Element Documentation: ... ... @@ -714,6 +714,7 @@ 714 714 ** DataStructureQueryType 715 715 716 716 Content: 746 + 717 717 Header, Query 718 718 719 719 Element Documentation: ... ... @@ -731,6 +731,7 @@ 731 731 ** MetadataStructureQueryType 732 732 733 733 Content: 764 + 734 734 Header, Query 735 735 736 736 Element Documentation: ... ... @@ -748,6 +748,7 @@ 748 748 ** CategorySchemeQueryType 749 749 750 750 Content: 782 + 751 751 Header, Query 752 752 753 753 Element Documentation: ... ... @@ -765,6 +765,7 @@ 765 765 ** ConceptSchemeQueryType 766 766 767 767 Content: 800 + 768 768 Header, Query 769 769 770 770 Element Documentation: ... ... @@ -782,6 +782,7 @@ 782 782 ** CodelistQueryType 783 783 784 784 Content: 818 + 785 785 Header, Query 786 786 787 787 Element Documentation: ... ... @@ -799,6 +799,7 @@ 799 799 ** HierarchicalCodelistQueryType 800 800 801 801 Content: 836 + 802 802 Header, Query 803 803 804 804 Element Documentation: ... ... @@ -816,6 +816,7 @@ 816 816 ** OrganisationSchemeQueryType 817 817 818 818 Content: 854 + 819 819 Header, Query 820 820 821 821 Element Documentation: ... ... @@ -833,6 +833,7 @@ 833 833 ** ReportingTaxonomyQueryType 834 834 835 835 Content: 872 + 836 836 Header, Query 837 837 838 838 Element Documentation: ... ... @@ -850,6 +850,7 @@ 850 850 ** StructureSetQueryType 851 851 852 852 Content: 890 + 853 853 Header, Query 854 854 855 855 Element Documentation: ... ... @@ -867,6 +867,7 @@ 867 867 ** ProcessQueryType 868 868 869 869 Content: 908 + 870 870 Header, Query 871 871 872 872 Element Documentation: ... ... @@ -884,6 +884,7 @@ 884 884 ** CategorisationQueryType 885 885 886 886 Content: 926 + 887 887 Header, Query 888 888 889 889 Element Documentation: ... ... @@ -901,6 +901,7 @@ 901 901 ** ProvisionAgreementQueryType 902 902 903 903 Content: 944 + 904 904 Header, Query 905 905 906 906 Element Documentation: ... ... @@ -918,6 +918,7 @@ 918 918 ** ConstraintQueryType 919 919 920 920 Content: 962 + 921 921 Header, Query 922 922 923 923 Element Documentation: ... ... @@ -935,6 +935,7 @@ 935 935 ** TransformationSchemeQueryType 936 936 937 937 Content: 980 + 938 938 Header, Query 939 939 940 940 Element Documentation: ... ... @@ -952,6 +952,7 @@ 952 952 ** VtlMappingSchemeQueryType 953 953 954 954 Content: 998 + 955 955 Header, Query 956 956 957 957 Element Documentation: ... ... @@ -969,6 +969,7 @@ 969 969 ** NamePersonalisationSchemeQueryType 970 970 971 971 Content: 1016 + 972 972 Header, Query 973 973 974 974 Element Documentation: ... ... @@ -986,6 +986,7 @@ 986 986 ** RulesetSchemeQueryType 987 987 988 988 Content: 1034 + 989 989 Header, Query 990 990 991 991 Element Documentation: ... ... @@ -1003,6 +1003,7 @@ 1003 1003 ** UserDefinedOperatorSchemeQueryType 1004 1004 1005 1005 Content: 1052 + 1006 1006 Header, Query 1007 1007 1008 1008 Element Documentation: ... ... @@ -1020,6 +1020,7 @@ 1020 1020 ** CustomTypeSchemeQueryType 1021 1021 1022 1022 Content: 1070 + 1023 1023 Header, Query 1024 1024 1025 1025 Element Documentation: ... ... @@ -1032,17 +1032,19 @@ 1032 1032 **ErrorType: **ErrorType describes the structure of an error response. 1033 1033 1034 1034 Content: 1083 + 1035 1035 ErrorMessage+ 1036 1036 1037 1037 Element Documentation: 1038 1038 1039 -(% style="width:9 74.835px" %)1040 -|**Name**| (% style="width:271px" %)**Type**|(% style="width:584px" %)**Documentation**1041 -|ErrorMessage| (% style="width:271px" %)com: CodedStatusMessageType|(% style="width:584px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors.1088 +(% style="width:899.294px" %) 1089 +|**Name**|**Type**|(% style="width:546px" %)**Documentation** 1090 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors. 1042 1042 1043 1043 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this 1044 1044 1045 1045 Content: 1095 + 1046 1046 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure*, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source* 1047 1047 1048 1048 Element Documentation: ... ... @@ -1073,19 +1073,20 @@ 1073 1073 ** StructureHeaderType 1074 1074 1075 1075 Content: 1126 + 1076 1076 ID, Test, Prepared, Sender, Receiver*, com:Name*, Source* 1077 1077 1078 1078 Element Documentation: 1079 1079 1080 -(% style="width:9 86.835px" %)1081 -| (% style="width:162px" %)**Name**|(% style="width:193px" %)**Type**|(% style="width:630px" %)**Documentation**1082 -| (% style="width:162px" %)ID|(% style="width:193px" %)com:IDType|(% style="width:630px" %)ID identifies an identification for the message, assigned by the sender.1083 -| (% style="width:162px" %)Test|(% style="width:193px" %)xs:boolean|(% style="width:630px" %)Test indicates whether the message is for test purposes or not.1084 -| (% style="width:162px" %)Prepared|(% style="width:193px" %)HeaderTimeType|(% style="width:630px" %)Prepared is the date the message was prepared.1085 -| (% style="width:162px" %)Sender|(% style="width:193px" %)SenderType|(% style="width:630px" %)Sender is information about the party that is transmitting the message.1086 -| (% style="width:162px" %)Receiver|(% style="width:193px" %)PartyType|(% style="width:630px" %)Receiver is information about the party that is the intended recipient of the message.1087 -| (% style="width:162px" %)com:Name|(% style="width:193px" %)com:TextType|(% style="width:630px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.1088 -| (% style="width:162px" %)Source|(% style="width:193px" %)com:TextType|(% style="width:630px" %)Source provides human-readable information about the source of the data.1131 +(% style="width:1099.29px" %) 1132 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation** 1133 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender. 1134 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not. 1135 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared. 1136 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message. 1137 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message. 1138 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1139 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data. 1089 1089 1090 1090 **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message. 1091 1091 ... ... @@ -1095,27 +1095,28 @@ 1095 1095 ** GenericDataHeaderType 1096 1096 1097 1097 Content: 1149 + 1098 1098 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source* 1099 1099 1100 1100 Element Documentation: 1101 1101 1102 -(% style="width: 970.835px" %)1103 -|**Name**| (% style="width:250px" %)**Type**|(% style="width:589px" %)**Documentation**1104 -|ID| (% style="width:250px" %)com:IDType|(% style="width:589px" %)ID identifies an identification for the message, assigned by the sender.1105 -|Test| (% style="width:250px" %)xs:boolean|(% style="width:589px" %)Test indicates whether the message is for test purposes or not.1106 -|Prepared| (% style="width:250px" %)HeaderTimeType|(% style="width:589px" %)Prepared is the date the message was prepared.1107 -|Sender| (% style="width:250px" %)SenderType|(% style="width:589px" %)Sender is information about the party that is transmitting the message.1108 -|Receiver| (% style="width:250px" %)PartyType|(% style="width:589px" %)Receiver is information about the party that is the intended recipient of the message.1109 -|com:Name| (% style="width:250px" %)com:TextType|(% style="width:589px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.1110 -|Structure| (% style="width:250px" %)com: GenericDataStructureType|(% style="width:589px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.1111 -|DataProvider| (% style="width:250px" %)com: DataProviderReferenceType|(% style="width:589px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.1112 -|DataSetAction| (% style="width:250px" %)com:ActionType|(% style="width:589px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).1113 -|DataSetID| (% style="width:250px" %)com:IDType|(% style="width:589px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1114 -|Extracted| (% style="width:250px" %)xs:dateTime|(% style="width:589px" %)Extracted is a time-stamp from the system rendering the data.1115 -|ReportingBegin| (% style="width:250px" %)com: ObservationalTimePeriodType|(% style="width:589px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1116 -|ReportingEnd| (% style="width:250px" %)com: ObservationalTimePeriodType|(% style="width:589px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1117 -|EmbargoDate| (% style="width:250px" %)xs:dateTime|(% style="width:589px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.1118 -|Source| (% style="width:250px" %)com:TextType|(% style="width:589px" %)Source provides human-readable information about the source of the data.1154 +(% style="width:895.294px" %) 1155 +|**Name**|**Type**|(% style="width:556px" %)**Documentation** 1156 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender. 1157 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not. 1158 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared. 1159 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1160 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1161 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1162 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1163 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 1164 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1165 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. 1166 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data. 1167 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1168 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1169 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available. 1170 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1119 1119 1120 1120 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. 1121 1121 ... ... @@ -1126,27 +1126,28 @@ 1126 1126 *** GenericTimeSeriesDataHeaderType 1127 1127 1128 1128 Content: 1181 + 1129 1129 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source* 1130 1130 1131 1131 Element Documentation: 1132 1132 1133 -(% style="width:9 73.835px" %)1134 -|**Name**|**Type**|(% style="width: 542px" %)**Documentation**1135 -|ID|com:IDType|(% style="width: 542px" %)ID identifies an identification for the message, assigned by the sender.1136 -|Test|xs:boolean|(% style="width: 542px" %)Test indicates whether the message is for test purposes or not.1137 -|Prepared|HeaderTimeType|(% style="width: 542px" %)Prepared is the date the message was prepared.1138 -|Sender|SenderType|(% style="width: 542px" %)Sender is information about the party that is transmitting the message.1139 -|Receiver|PartyType|(% style="width: 542px" %)Receiver is information about the party that is the intended recipient of the message.1140 -|com:Name|com:TextType|(% style="width: 542px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.1141 -|Structure|com: GenericTimeSeriesDataStructureType|(% style="width: 542px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.1142 -|DataProvider|com: DataProviderReferenceType|(% style="width: 542px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.1143 -|DataSetAction|com:ActionType|(% style="width: 542px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).1144 -|DataSetID|com:IDType|(% style="width: 542px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1145 -|Extracted|xs:dateTime|(% style="width: 542px" %)Extracted is a time-stamp from the system rendering the data.1146 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width: 542px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1147 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width: 542px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1148 -|EmbargoDate|xs:dateTime|(% style="width: 542px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.1149 -|Source|com:TextType|(% style="width: 542px" %)Source provides human-readable information about the source of the data.1186 +(% style="width:926.294px" %) 1187 +|**Name**|**Type**|(% style="width:497px" %)**Documentation** 1188 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender. 1189 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not. 1190 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared. 1191 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1192 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1193 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1194 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1195 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 1196 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1197 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. 1198 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data. 1199 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1200 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1201 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available. 1202 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1150 1150 1151 1151 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message. 1152 1152 ... ... @@ -1156,27 +1156,28 @@ 1156 1156 ** StructureSpecificDataHeaderType 1157 1157 1158 1158 Content: 1212 + 1159 1159 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source* 1160 1160 1161 1161 Element Documentation: 1162 1162 1163 1163 (% style="width:930.294px" %) 1164 -|**Name**| (% style="width:190px" %)**Type**|(% style="width:611px" %)**Documentation**1165 -|ID| (% style="width:190px" %)com:IDType|(% style="width:611px" %)ID identifies an identification for the message, assigned by the sender.1166 -|Test| (% style="width:190px" %)xs:boolean|(% style="width:611px" %)Test indicates whether the message is for test purposes or not.1167 -|Prepared| (% style="width:190px" %)HeaderTimeType|(% style="width:611px" %)Prepared is the date the message was prepared.1168 -|Sender| (% style="width:190px" %)SenderType|(% style="width:611px" %)Sender is information about the party that is transmitting the message.1169 -|Receiver| (% style="width:190px" %)PartyType|(% style="width:611px" %)Receiver is information about the party that is the intended recipient of the message.1170 -|com:Name| (% style="width:190px" %)com:TextType|(% style="width:611px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.1171 -|Structure| (% style="width:190px" %)com: StructureSpecificDataStructureType|(% style="width:611px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.1172 -|DataProvider| (% style="width:190px" %)com: DataProviderReferenceType|(% style="width:611px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.1173 -|DataSetAction| (% style="width:190px" %)com:ActionType|(% style="width:611px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).1174 -|DataSetID| (% style="width:190px" %)com:IDType|(% style="width:611px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1175 -|Extracted| (% style="width:190px" %)xs:dateTime|(% style="width:611px" %)Extracted is a time-stamp from the system rendering the data.1176 -|ReportingBegin| (% style="width:190px" %)com: ObservationalTimePeriodType|(% style="width:611px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1177 -|ReportingEnd| (% style="width:190px" %)com: ObservationalTimePeriodType|(% style="width:611px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1178 -|EmbargoDate| (% style="width:190px" %)xs:dateTime|(% style="width:611px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.1179 -|Source| (% style="width:190px" %)com:TextType|(% style="width:611px" %)Source provides human-readable information about the source of the data.1218 +|**Name**|**Type**|(% style="width:578px" %)**Documentation** 1219 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender. 1220 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not. 1221 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared. 1222 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1223 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1224 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1225 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1226 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 1227 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1228 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. 1229 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data. 1230 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1231 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1232 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available. 1233 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1180 1180 1181 1181 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. 1182 1182 ... ... @@ -1187,27 +1187,28 @@ 1187 1187 *** StructureSpecificTimeSeriesDataHeaderType 1188 1188 1189 1189 Content: 1244 + 1190 1190 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source* 1191 1191 1192 1192 Element Documentation: 1193 1193 1194 -(% style="width:9 67.835px" %)1195 -|**Name**|(% style="width: 238px" %)**Type**|(% style="width:486px" %)**Documentation**1196 -|ID|(% style="width: 238px" %)com:IDType|(% style="width:486px" %)ID identifies an identification for the message, assigned by the sender.1197 -|Test|(% style="width: 238px" %)xs:boolean|(% style="width:486px" %)Test indicates whether the message is for test purposes or not.1198 -|Prepared|(% style="width: 238px" %)HeaderTimeType|(% style="width:486px" %)Prepared is the date the message was prepared.1199 -|Sender|(% style="width: 238px" %)SenderType|(% style="width:486px" %)Sender is information about the party that is transmitting the message.1200 -|Receiver|(% style="width: 238px" %)PartyType|(% style="width:486px" %)Receiver is information about the party that is the intended recipient of the message.1201 -|com:Name|(% style="width: 238px" %)com:TextType|(% style="width:486px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.1202 -|Structure|(% style="width: 238px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:486px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.1203 -|DataProvider|(% style="width: 238px" %)com: DataProviderReferenceType|(% style="width:486px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.1204 -|DataSetAction|(% style="width: 238px" %)com:ActionType|(% style="width:486px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).1205 -|DataSetID|(% style="width: 238px" %)com:IDType|(% style="width:486px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1206 -|Extracted|(% style="width: 238px" %)xs:dateTime|(% style="width:486px" %)Extracted is a time-stamp from the system rendering the data.1207 -|ReportingBegin|(% style="width: 238px" %)com: ObservationalTimePeriodType|(% style="width:486px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1208 -|ReportingEnd|(% style="width: 238px" %)com: ObservationalTimePeriodType|(% style="width:486px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).1209 -|EmbargoDate|(% style="width: 238px" %)xs:dateTime|(% style="width:486px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.1210 -|Source|(% style="width: 238px" %)com:TextType|(% style="width:486px" %)Source provides human-readable information about the source of the data.1249 +(% style="width:943.294px" %) 1250 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation** 1251 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender. 1252 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not. 1253 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared. 1254 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message. 1255 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message. 1256 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1257 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1258 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 1259 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1260 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]]. 1261 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data. 1262 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1263 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data). 1264 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available. 1265 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data. 1211 1211 1212 1212 **GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 1213 1213 ... ... @@ -1217,6 +1217,7 @@ 1217 1217 ** GenericMetadataHeaderType 1218 1218 1219 1219 Content: 1275 + 1220 1220 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source* 1221 1221 1222 1222 Element Documentation: ... ... @@ -1244,6 +1244,7 @@ 1244 1244 ** StructureSpecificMetadataHeaderType 1245 1245 1246 1246 Content: 1303 + 1247 1247 ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source* 1248 1248 1249 1249 Element Documentation: ... ... @@ -1271,17 +1271,18 @@ 1271 1271 ** BasicHeaderType 1272 1272 1273 1273 Content: 1331 + 1274 1274 ID, Test, Prepared, Sender, Receiver 1275 1275 1276 1276 Element Documentation: 1277 1277 1278 -(% style="width:9 64.835px" %)1279 -|**Name**|(% style="width:2 16px" %)**Type**|(% style="width:535px" %)**Documentation**1280 -|ID|(% style="width:2 16px" %)com:IDType|(% style="width:535px" %)ID identifies an identification for the message, assigned by the sender.1281 -|Test|(% style="width:2 16px" %)xs:boolean|(% style="width:535px" %)Test indicates whether the message is for test purposes or not.1282 -|Prepared|(% style="width:2 16px" %)HeaderTimeType|(% style="width:535px" %)Prepared is the date the message was prepared.1283 -|Sender|(% style="width:2 16px" %)SenderType|(% style="width:535px" %)Sender is information about the party that is transmitting the message.1284 -|Receiver|(% style="width:2 16px" %)PartyType|(% style="width:535px" %)Receiver is information about the party that is the intended recipient of the message.1336 +(% style="width:903.294px" %) 1337 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation** 1338 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender. 1339 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not. 1340 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared. 1341 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message. 1342 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message. 1285 1285 1286 1286 **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages. 1287 1287 ... ... @@ -1290,20 +1290,21 @@ 1290 1290 id 1291 1291 1292 1292 Content: 1351 + 1293 1293 com:Name*, (% style="color:#e74c3c" %)Contact(%%)* 1294 1294 1295 1295 [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation: 1296 1296 1297 -(% style="width: 888.294px" %)1298 -|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width: 569px" %)**Documentation**1299 -|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width: 569px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.1356 +(% style="width:739.294px" %) 1357 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation** 1358 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party. 1300 1300 1301 1301 Element Documentation: 1302 1302 1303 -(% style="width: 889.294px" %)1304 -|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width: 568px" %)**Documentation**1305 -|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width: 568px" %)Name is a human-readable name of the party.1306 -|(% style="width:134px" %)(% style="color:#e74c3c" %)Contact|(% style="width:183px" %)ContactType|(% style="width: 568px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.1362 +(% style="width:751.294px" %) 1363 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation** 1364 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party. 1365 +|(% style="width:134px" %)(% style="color:#e74c3c" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message. 1307 1307 1308 1308 **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration. 1309 1309 ... ... @@ -1313,9 +1313,11 @@ 1313 1313 ** SenderType 1314 1314 1315 1315 Attributes: 1375 + 1316 1316 id 1317 1317 1318 1318 Content: 1379 + 1319 1319 com:Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone? 1320 1320 1321 1321 [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation: ... ... @@ -1326,29 +1326,28 @@ 1326 1326 1327 1327 Element Documentation: 1328 1328 1329 -(% style="width:966.835px" %) 1330 -|**Name**|**Type**|(% style="width:686px" %)**Documentation** 1331 -|com:Name|com:TextType|(% style="width:686px" %)Name is a human-readable name of the party. 1332 -|(%%)(% style="color:#e74c3c" %)Contact|ContactType|(% style="width:686px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message. 1333 -|Timezone|com:TimezoneType|(% style="width:686px" %)Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time". 1390 +|**Name**|**Type**|**Documentation** 1391 +|com:Name|com:TextType|Name is a human-readable name of the party. 1392 +|(%%)(% style="color:#e74c3c" %)Contact|ContactType|(%%)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message. 1393 +|Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time". 1334 1334 1335 1335 **ContactType: **ContactType provides defines the (% style="color:#e74c3c" %)contact(%%) information about a party. 1336 1336 1337 1337 Content: 1398 + 1338 1338 com:Name*, Department*, Role*, (Telephone | Fax | X400 | URI | Email)* 1339 1339 1340 1340 Element Documentation: 1341 1341 1342 -(% style="width:969.835px" %) 1343 -|**Name**|(% style="width:161px" %)**Type**|(% style="width:613px" %)**Documentation** 1344 -|com:Name|(% style="width:161px" %)com:TextType|(% style="width:613px" %)Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%). 1345 -|Department|(% style="width:161px" %)com:TextType|(% style="width:613px" %)Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%) person works. 1346 -|Role|(% style="width:161px" %)com:TextType|(% style="width:613px" %)Role is the responsibility of the (% style="color:#e74c3c" %)contact(%%) person with respect to the object for which this person is the (% style="color:#e74c3c" %)contact(%%). 1347 -|Telephone|(% style="width:161px" %)xs:string|(% style="width:613px" %)Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the (% style="color:#e74c3c" %)contact(%%) person. 1348 -|Fax|(% style="width:161px" %)xs:string|(% style="width:613px" %)Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%) person. 1349 -|X400|(% style="width:161px" %)xs:string|(% style="width:613px" %)X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%) person. 1350 -|URI|(% style="width:161px" %)xs:anyURI|(% style="width:613px" %)URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%) person. 1351 -|Email|(% style="width:161px" %)xs:string|(% style="width:613px" %)Email holds the email address for the (% style="color:#e74c3c" %)contact(%%) person. 1403 +|**Name**|**Type**|**Documentation** 1404 +|com:Name|com:TextType|Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%). 1405 +|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%) person works. 1406 +|Role|com:TextType|Role is the responsibility of the (% style="color:#e74c3c" %)contact(%%) person with respect to the object for which this person is the (% style="color:#e74c3c" %)contact(%%). 1407 +|Telephone|xs:string|Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the (% style="color:#e74c3c" %)contact(%%) person. 1408 +|Fax|xs:string|Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%) person. 1409 +|X400|xs:string|X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%) person. 1410 +|URI|xs:anyURI|URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%) person. 1411 +|Email|xs:string|Email holds the email address for the (% style="color:#e74c3c" %)contact(%%) person. 1352 1352 1353 1353 === 2.1.4 Simple Types === 1354 1354 ... ... @@ -1355,6 +1355,7 @@ 1355 1355 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. 1356 1356 1357 1357 Union of: 1418 + 1358 1358 xs:dateTime, xs:date. 1359 1359 1360 1360 == 2.2 Message Footer Namespace == ... ... @@ -1365,12 +1365,12 @@ 1365 1365 1366 1366 Referenced Namespaces: 1367 1367 1368 -(% style="width:821.835px" %) 1369 -|(% style="width:525px" %)**Namespace**|(% style="width:294px" %)**Prefix** 1370 -|(% style="width:525px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:294px" %)com 1371 -|(% style="width:525px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:294px" %)xs 1429 +|**Namespace**|**Prefix** 1430 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com 1431 +|http:~/~/www.w3.org/2001/XMLSchema|xs 1372 1372 1373 1373 Contents: 1434 + 1374 1374 1 Global Element 1375 1375 2 Complex Types 1376 1376 1 Simple Type ... ... @@ -1384,13 +1384,13 @@ 1384 1384 **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. 1385 1385 1386 1386 Content: 1448 + 1387 1387 Message+ 1388 1388 1389 1389 Element Documentation: 1390 1390 1391 -(% style="width:989.835px" %) 1392 -|**Name**|(% style="width:181px" %)**Type**|(% style="width:695px" %)**Documentation** 1393 -|Message|(% style="width:181px" %)FooterMessageType|(% style="width:695px" %)Message contains a single error, information, or warning message. A [[code>>doc:sdmx:Glossary.Code.WebHome]] is provided along with an optional severity. The text of the message can be expressed in multiple languages. 1453 +|**Name**|**Type**|**Documentation** 1454 +|Message|FooterMessageType|Message contains a single error, information, or warning message. A [[code>>doc:sdmx:Glossary.Code.WebHome]] is provided along with an optional severity. The text of the message can be expressed in multiple languages. 1394 1394 1395 1395 **FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity [[code>>doc:sdmx:Glossary.Code.WebHome]] of Error, Information, or Warning added to it. 1396 1396 ... ... @@ -1401,23 +1401,23 @@ 1401 1401 *** FooterMessageType 1402 1402 1403 1403 Attributes: 1465 + 1404 1404 [[code>>doc:sdmx:Glossary.Code.WebHome]], severity? 1405 1405 1406 1406 Content: 1469 + 1407 1407 com:Text+ 1408 1408 1409 1409 [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation: 1410 1410 1411 -(% style="width:981.835px" %) 1412 -|**Name**|(% style="width:152px" %)**Type**|(% style="width:754px" %)**Documentation** 1413 -|[[code>>doc:sdmx:Glossary.Code.WebHome]]|(% style="width:152px" %)xs:string|(% style="width:754px" %)The [[code>>doc:sdmx:Glossary.Code.WebHome]] [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds an optional [[code>>doc:sdmx:Glossary.Code.WebHome]] identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error. 1414 -|severity|(% style="width:152px" %)SeverityCodeType|(% style="width:754px" %) 1474 +|**Name**|**Type**|**Documentation** 1475 +|[[code>>doc:sdmx:Glossary.Code.WebHome]]|xs:string|The [[code>>doc:sdmx:Glossary.Code.WebHome]] [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds an optional [[code>>doc:sdmx:Glossary.Code.WebHome]] identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error. 1476 +|severity|SeverityCodeType| 1415 1415 1416 1416 Element Documentation: 1417 1417 1418 -(% style="width:985.835px" %) 1419 -|**Name**|(% style="width:155px" %)**Type**|(% style="width:635px" %)**Documentation** 1420 -|com:Text|(% style="width:155px" %)com:TextType|(% style="width:635px" %)Text contains the text of the message, in parallel language values. 1480 +|**Name**|**Type**|**Documentation** 1481 +|com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1421 1421 1422 1422 === 2.2.4 Simple Types === 1423 1423 ... ... @@ -1427,8 +1427,7 @@ 1427 1427 1428 1428 Enumerations: 1429 1429 1430 -(% style="width:996.835px" %) 1431 -|**Value**|(% style="width:783px" %)**Documentation** 1432 -|Error|(% style="width:783px" %)Error indicates the status message coresponds to an error. 1433 -|Warning|(% style="width:783px" %)Warning indicates that the status message corresponds to a warning. 1434 -|Information|(% style="width:783px" %)Information indicates that the status message corresponds to an informational message. 1491 +|**Value**|**Documentation** 1492 +|Error|Error indicates the status message coresponds to an error. 1493 +|Warning|Warning indicates that the status message corresponds to a warning. 1494 +|Information|Information indicates that the status message corresponds to an informational message.