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