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