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