Changes for page Part I. Message Namespace

Last modified by Artur on 2025/09/10 11:19

From version 9.1
edited by Helena
on 2025/07/03 14:54
Change comment: There is no comment for this version
To version 5.3
edited by Helena
on 2025/06/24 10:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,1 +1,0 @@
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
... ... @@ -16,11 +16,11 @@
16 16  
17 17  = 1. Introduction =
18 18  
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]].
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.
20 20  
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 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 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.
22 22  
23 -In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of:
23 +In general, every message in SDMX follows common format of:
24 24  
25 25  * Header
26 26  * Payload (0..n)
... ... @@ -52,6 +52,7 @@
52 52  |(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs
53 53  
54 54  Contents:
55 +
55 55  50 Global Elements
56 56  62 Complex Types
57 57  1 Simple Type
... ... @@ -58,103 +58,103 @@
58 58  
59 59  === 2.1.2 Global Elements ===
60 60  
61 -**Structure (StructureType): **Structure is a message that contains [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. It may contain any of the following; categorisations, [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) ([[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]), (% style="color:#e74c3c" %)[[constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) (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>>doc:sdmx:Glossary.Structure set.WebHome]].
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 62  
63 -**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. [[Data sets>>doc:sdmx:Glossary.Data set.WebHome]] in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]).
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 64  
65 -**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
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 66  
67 -**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The payload of this message (i.e. the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]) will be based on XML schemas which are specific to the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and the orientation (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data.
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 68  
69 -**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
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 70  
71 -**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
72 +**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
72 72  
73 -**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] provided will be based on a metadata structure specific schema.
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 74  
75 -**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services.
76 +**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
76 76  
77 -**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
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 78  
79 79  **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.
80 80  
81 -**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
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 82  
83 83  **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.
84 84  
85 -**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) 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.
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 86  
87 87  **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.
88 88  
89 89  **SubmitSubscriptionsRequest (SubmitSubscriptionsRequestType): **SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
90 90  
91 -**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
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 92  
93 -**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
94 +**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
94 94  
95 -**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
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 96  
97 -**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
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 98  
99 -**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure specific data.
100 +**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data.
100 100  
101 -**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
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 102  
103 -**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
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 104  
105 -**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
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 106  
107 -**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic format [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
108 +**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata.
108 108  
109 -**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
110 +**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata.
110 110  
111 -**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
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 112  
113 -**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
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 114  
115 -**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
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 116  
117 -**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for dataflows.
118 +**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows.
118 118  
119 -**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]].
120 +**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows.
120 120  
121 -**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structures definitions.
122 +**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions.
122 122  
123 -**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
124 +**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions.
124 124  
125 -**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]].
126 +**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes.
126 126  
127 -**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]].
128 +**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes.
128 128  
129 -**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for codelists.
130 +**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists.
130 130  
131 -**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for hierarchical codelists.
132 +**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists.
132 132  
133 -**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for organisation schemes.
134 +**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes.
134 134  
135 -**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]].
136 +**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies.
136 136  
137 -**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure sets.
138 +**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets.
138 138  
139 -**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for processes.
140 +**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes.
140 140  
141 -**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for categorisations.
142 +**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations.
142 142  
143 -**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for provision agreements.
144 +**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements.
144 144  
145 -**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for (% style="color:#e74c3c" %)constraints(%%).
146 +**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints.
146 146  
147 -**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for transformation schemes.
148 +**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes.
148 148  
149 -**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes.
150 +**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes.
150 150  
151 -**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for name personalisation schemes.
152 +**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes.
152 152  
153 -**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for ruleset schemes.
154 +**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes.
154 154  
155 -**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for user defined schemes.
156 +**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes.
156 156  
157 -**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for custom type schemes.
158 +**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes.
158 158  
159 159  **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.
160 160  
... ... @@ -168,10 +168,9 @@
168 168  
169 169  Element Documentation:
170 170  
171 -(% style="width:1004.83px" %)
172 -|**Name**|**Type**|(% style="width:631px" %)**Documentation**
173 -|Header|//BaseHeaderType//|(% style="width:631px" %)
174 -|ftr:Footer|ftr:FooterType|(% style="width:631px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
172 +|**Name**|**Type**|**Documentation**
173 +|Header|//BaseHeaderType//|
174 +|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.
175 175  
176 176  **StructureType: **StructureType defines the contents of a structure message. The payload is optional since this message may be returned from a web service with only information in the footer.
177 177  
... ... @@ -181,6 +181,7 @@
181 181  ** StructureType
182 182  
183 183  Content:
184 +
184 184  Header, Structures?, ftr:Footer?
185 185  
186 186  Element Documentation:
... ... @@ -199,14 +199,15 @@
199 199  ** GenericDataType
200 200  
201 201  Content:
202 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
203 203  
204 +Header, DataSet*, ftr:Footer?
205 +
204 204  Element Documentation:
205 205  
206 206  (% style="width:847.294px" %)
207 207  |**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation**
208 208  |Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %)
209 -|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
211 +|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
210 210  |ftr:Footer|(% style="width:227px" %)ftr:FooterType|(% style="width:450px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
211 211  
212 212  **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
... ... @@ -218,17 +218,18 @@
218 218  *** GenericTimeSeriesDataType
219 219  
220 220  Content:
221 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
222 222  
224 +Header, DataSet*, ftr:Footer?
225 +
223 223  Element Documentation:
224 224  
225 225  (% style="width:856.294px" %)
226 226  |**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation**
227 227  |Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %)
228 -|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
231 +|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
229 229  |ftr:Footer|(% style="width:239px" %)ftr:FooterType|(% style="width:458px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
230 230  
231 -**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
234 +**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.
232 232  
233 233  Derivation:
234 234  
... ... @@ -236,14 +236,15 @@
236 236  ** StructureSpecificDataType
237 237  
238 238  Content:
239 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
240 240  
243 +Header, DataSet*, ftr:Footer?
244 +
241 241  Element Documentation:
242 242  
243 243  (% style="width:828.294px" %)
244 244  |**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation**
245 245  |Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %)
246 -|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
250 +|DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
247 247  |ftr:Footer|(% style="width:247px" %)ftr:FooterType|(% style="width:420px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
248 248  
249 249  **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
... ... @@ -255,14 +255,15 @@
255 255  *** StructureSpecificTimeSeriesDataType
256 256  
257 257  Content:
258 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
259 259  
263 +Header, DataSet*, ftr:Footer?
264 +
260 260  Element Documentation:
261 261  
262 262  (% style="width:839.294px" %)
263 263  |**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
264 264  |Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
265 -|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
270 +|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
266 266  |ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
267 267  
268 268  **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
... ... @@ -273,6 +273,7 @@
273 273  ** GenericMetadataType
274 274  
275 275  Content:
281 +
276 276  Header, MetadataSet*, ftr:Footer?
277 277  
278 278  Element Documentation:
... ... @@ -279,11 +279,11 @@
279 279  
280 280  (% style="width:836.294px" %)
281 281  |(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation**
282 -|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeaderType|(% style="width:427px" %)
288 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %)
283 283  |(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
284 284  |(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
285 285  
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.
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.
287 287  
288 288  Derivation:
289 289  
... ... @@ -291,6 +291,7 @@
291 291  ** StructureSpecificMetadataType
292 292  
293 293  Content:
300 +
294 294  Header, MetadataSet*, ftr:Footer?
295 295  
296 296  Element Documentation:
... ... @@ -297,7 +297,7 @@
297 297  
298 298  (% style="width:841.294px" %)
299 299  |(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
300 -|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMetadataHeaderType|(% style="width:428px" %)
307 +|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
301 301  |(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
302 302  |(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
303 303  
... ... @@ -309,25 +309,26 @@
309 309  ** RegistryInterfaceType
310 310  
311 311  Content:
319 +
312 312  Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, ftr:Footer?
313 313  
314 314  Element Documentation:
315 315  
316 -(% style="width:1000.83px" %)
317 -|**Name**|(% style="width:317px" %)**Type**|(% style="width:491px" %)**Documentation**
318 -|Header|(% style="width:317px" %)BasicHeaderType|(% style="width:491px" %)
319 -|SubmitRegistrationsRequest|(% style="width:317px" %)ref: SubmitRegistrationsRequestType|(% style="width:491px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
320 -|SubmitRegistrationsResponse|(% style="width:317px" %)ref: SubmitRegistrationsResponseType|(% style="width:491px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
321 -|QueryRegistrationRequest|(% style="width:317px" %)ref: QueryRegistrationRequestType|(% style="width:491px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)[[constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
322 -|QueryRegistrationResponse|(% style="width:317px" %)ref: QueryRegistrationResponseType|(% style="width:491px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
323 -|SubmitStructureRequest|(% style="width:317px" %)ref: SubmitStructureRequestType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
324 -|SubmitStructureResponse|(% style="width:317px" %)ref: SubmitStructureResponseType|(% style="width:491px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
325 -|SubmitSubscriptionsRequest|(% style="width:317px" %)ref: SubmitSubscriptionsRequestType|(% style="width:491px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
326 -|SubmitSubscriptionsResponse|(% style="width:317px" %)ref: SubmitSubscriptionsResponseType|(% style="width:491px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
327 -|QuerySubscriptionRequest|(% style="width:317px" %)ref: QuerySubscriptionRequestType|(% style="width:491px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
328 -|QuerySubscriptionResponse|(% style="width:317px" %)ref: QuerySubscriptionResponseType|(% style="width:491px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
329 -|NotifyRegistryEvent|(% style="width:317px" %)ref: NotifyRegistryEventType|(% style="width:491px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
330 -|ftr:Footer|(% style="width:317px" %)ftr:FooterType|(% style="width:491px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
324 +(% style="width:903.294px" %)
325 +|**Name**|**Type**|(% style="width:441px" %)**Documentation**
326 +|Header|BasicHeaderType|(% style="width:441px" %)
327 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
328 +|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
329 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
330 +|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
331 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
332 +|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
333 +|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
334 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
335 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
336 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
337 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
338 +|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
331 331  
332 332  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
333 333  
... ... @@ -338,14 +338,15 @@
338 338  *** SubmitRegistrationsRequestType
339 339  
340 340  Content:
349 +
341 341  Header, SubmitRegistrationsRequest
342 342  
343 343  Element Documentation:
344 344  
345 -(% style="width:966.835px" %)
346 -|**Name**|**Type**|(% style="width:490px" %)**Documentation**
347 -|Header|BasicHeaderType|(% style="width:490px" %)
348 -|SubmitRegistrationsRequest|ref: SubmitRegistrationsRequestType|(% style="width:490px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
354 +(% style="width:844.294px" %)
355 +|**Name**|**Type**|(% style="width:377px" %)**Documentation**
356 +|Header|BasicHeaderType|(% style="width:377px" %)
357 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set 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.
349 349  
350 350  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
351 351  
... ... @@ -356,15 +356,16 @@
356 356  *** SubmitRegistrationsResponseType
357 357  
358 358  Content:
368 +
359 359  Header, SubmitRegistrationsResponse, ftr:Footer?
360 360  
361 361  Element Documentation:
362 362  
363 -(% style="width:974.835px" %)
364 -|**Name**|(% style="width:210px" %)**Type**|(% style="width:473px" %)**Documentation**
365 -|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:473px" %)
366 -|SubmitRegistrationsResponse|(% style="width:210px" %)ref: SubmitRegistrationsResponseType|(% style="width:473px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
367 -|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:473px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
373 +(% style="width:847.294px" %)
374 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation**
375 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %)
376 +|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
377 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
368 368  
369 369  **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document.
370 370  
... ... @@ -375,14 +375,15 @@
375 375  *** QueryRegistrationRequestType
376 376  
377 377  Content:
388 +
378 378  Header, QueryRegistrationRequest
379 379  
380 380  Element Documentation:
381 381  
382 -(% style="width:971.835px" %)
383 -|**Name**|(% style="width:288px" %)**Type**|(% style="width:476px" %)**Documentation**
384 -|Header|(% style="width:288px" %)BasicHeaderType|(% style="width:476px" %)
385 -|QueryRegistrationRequest|(% style="width:288px" %)ref: QueryRegistrationRequestType|(% style="width:476px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)[[constraints>>doc:sdmx:Glossary.Constraint.WebHome]](%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
393 +(% style="width:847.294px" %)
394 +|**Name**|**Type**|(% style="width:397px" %)**Documentation**
395 +|Header|BasicHeaderType|(% style="width:397px" %)
396 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets 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.
386 386  
387 387  **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
388 388  
... ... @@ -393,15 +393,16 @@
393 393  *** QueryRegistrationResponseType
394 394  
395 395  Content:
407 +
396 396  Header, QueryRegistrationResponse, ftr:Footer?
397 397  
398 398  Element Documentation:
399 399  
400 -(% style="width:969.835px" %)
401 -|**Name**|(% style="width:235px" %)**Type**|(% style="width:496px" %)**Documentation**
402 -|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:496px" %)
403 -|QueryRegistrationResponse|(% style="width:235px" %)ref: QueryRegistrationResponseType|(% style="width:496px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
404 -|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:496px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
412 +(% style="width:856.294px" %)
413 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation**
414 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %)
415 +|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
416 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
405 405  
406 406  **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document.
407 407  
... ... @@ -412,14 +412,15 @@
412 412  *** SubmitStructureRequestType
413 413  
414 414  Content:
427 +
415 415  Header, SubmitStructureRequest
416 416  
417 417  Element Documentation:
418 418  
419 -(% style="width:970.835px" %)
420 -|**Name**|(% style="width:286px" %)**Type**|(% style="width:491px" %)**Documentation**
421 -|Header|(% style="width:286px" %)BasicHeaderType|(% style="width:491px" %)
422 -|SubmitStructureRequest|(% style="width:286px" %)ref: SubmitStructureRequestType|(% style="width:491px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
432 +(% style="width:870.294px" %)
433 +|**Name**|**Type**|(% style="width:453px" %)**Documentation**
434 +|Header|BasicHeaderType|(% style="width:453px" %)
435 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, 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.
423 423  
424 424  **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
425 425  
... ... @@ -430,17 +430,18 @@
430 430  *** SubmitStructureResponseType
431 431  
432 432  Content:
446 +
433 433  Header, SubmitStructureResponse, ftr:Footer?
434 434  
435 435  Element Documentation:
436 436  
437 -(% style="width:969.835px" %)
438 -|**Name**|(% style="width:246px" %)**Type**|(% style="width:498px" %)**Documentation**
439 -|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:498px" %)
440 -|SubmitStructureResponse|(% style="width:246px" %)ref: SubmitStructureResponseType|(% style="width:498px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
441 -|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:498px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
451 +(% style="width:835.294px" %)
452 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation**
453 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %)
454 +|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
455 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
442 442  
443 -**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document.
457 +**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
444 444  
445 445  Derivation:
446 446  
... ... @@ -449,16 +449,17 @@
449 449  *** SubmitSubscriptionsRequestType
450 450  
451 451  Content:
466 +
452 452  Header, SubmitSubscriptionsRequest
453 453  
454 454  Element Documentation:
455 455  
456 -(% style="width:960.835px" %)
457 -|**Name**|(% style="width:227px" %)**Type**|(% style="width:445px" %)**Documentation**
458 -|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:445px" %)
459 -|SubmitSubscriptionsRequest|(% style="width:227px" %)ref: SubmitSubscriptionsRequestType|(% style="width:445px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
471 +(% style="width:832.294px" %)
472 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation**
473 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
474 +|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
460 460  
461 -**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document.
476 +**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
462 462  
463 463  Derivation:
464 464  
... ... @@ -467,17 +467,18 @@
467 467  *** SubmitSubscriptionsResponseType
468 468  
469 469  Content:
485 +
470 470  Header, SubmitSubscriptionsResponse, ftr:Footer?
471 471  
472 472  Element Documentation:
473 473  
474 -(% style="width:965.835px" %)
475 -|**Name**|**Type**|(% style="width:482px" %)**Documentation**
476 -|Header|BasicHeaderType|(% style="width:482px" %)
477 -|SubmitSubscriptionsResponse|ref: SubmitSubscriptionsResponseType|(% style="width:482px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
478 -|ftr:Footer|ftr:FooterType|(% style="width:482px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
490 +(% style="width:843.294px" %)
491 +|**Name**|**Type**|(% style="width:362px" %)**Documentation**
492 +|Header|BasicHeaderType|(% style="width:362px" %)
493 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions 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.
494 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
479 479  
480 -**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document.
496 +**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
481 481  
482 482  Derivation:
483 483  
... ... @@ -486,16 +486,17 @@
486 486  *** QuerySubscriptionRequestType
487 487  
488 488  Content:
505 +
489 489  Header, QuerySubscriptionRequest
490 490  
491 491  Element Documentation:
492 492  
493 -(% style="width:970.835px" %)
494 -|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:483px" %)**Documentation**
495 -|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:483px" %)
496 -|(% style="width:230px" %)QuerySubscriptionRequest|(% style="width:254px" %)ref: QuerySubscriptionRequestType|(% style="width:483px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
510 +(% style="width:839.294px" %)
511 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
512 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %)
513 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
497 497  
498 -**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document.
515 +**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
499 499  
500 500  Derivation:
501 501  
... ... @@ -504,17 +504,18 @@
504 504  *** QuerySubscriptionResponseType
505 505  
506 506  Content:
524 +
507 507  Header, QuerySubscriptionResponse, ftr:Footer?
508 508  
509 509  Element Documentation:
510 510  
511 -(% style="width:973.835px" %)
512 -|(% style="width:233px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:443px" %)**Documentation**
513 -|(% style="width:233px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:443px" %)
514 -|(% style="width:233px" %)QuerySubscriptionResponse|(% style="width:295px" %)ref: QuerySubscriptionResponseType|(% style="width:443px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
515 -|(% style="width:233px" %)ftr:Footer|(% style="width:295px" %)ftr:FooterType|(% style="width:443px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
529 +(% style="width:912.294px" %)
530 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
531 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %)
532 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
533 +|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
516 516  
517 -**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document.
535 +**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
518 518  
519 519  Derivation:
520 520  
... ... @@ -523,14 +523,15 @@
523 523  *** NotifyRegistryEventType
524 524  
525 525  Content:
544 +
526 526  Header, NotifyRegistryEvent
527 527  
528 528  Element Documentation:
529 529  
530 -(% style="width:963.835px" %)
531 -|**Name**|(% style="width:228px" %)**Type**|(% style="width:576px" %)**Documentation**
532 -|Header|(% style="width:228px" %)BasicHeaderType|(% style="width:576px" %)
533 -|NotifyRegistryEvent|(% style="width:228px" %)ref: NotifyRegistryEventType|(% style="width:576px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
549 +(% style="width:836.294px" %)
550 +|**Name**|**Type**|(% style="width:473px" %)**Documentation**
551 +|Header|BasicHeaderType|(% style="width:473px" %)
552 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
534 534  
535 535  **DataQueryType: **DataQueryType defines the structure of a data query message.
536 536  
... ... @@ -540,6 +540,7 @@
540 540  ** DataQueryType
541 541  
542 542  Content:
562 +
543 543  Header, Query
544 544  
545 545  Element Documentation:
... ... @@ -558,6 +558,7 @@
558 558  *** GenericDataQueryType
559 559  
560 560  Content:
581 +
561 561  Header, Query
562 562  
563 563  Element Documentation:
... ... @@ -577,6 +577,7 @@
577 577  **** GenericTimeSeriesDataQueryType
578 578  
579 579  Content:
601 +
580 580  Header, Query
581 581  
582 582  Element Documentation:
... ... @@ -595,6 +595,7 @@
595 595  *** StructureSpecificTimeSeriesDataQueryType
596 596  
597 597  Content:
620 +
598 598  Header, Query
599 599  
600 600  Element Documentation:
... ... @@ -604,7 +604,7 @@
604 604  |(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
605 605  |(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
606 606  
607 -**MetadataQueryType: **MetadataQueryType defines the structure of a [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] query message.
630 +**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
608 608  
609 609  Derivation:
610 610  
... ... @@ -612,6 +612,7 @@
612 612  ** MetadataQueryType
613 613  
614 614  Content:
638 +
615 615  Header, Query
616 616  
617 617  Element Documentation:
... ... @@ -629,6 +629,7 @@
629 629  ** DataSchemaQueryType
630 630  
631 631  Content:
656 +
632 632  Header, Query
633 633  
634 634  Element Documentation:
... ... @@ -646,6 +646,7 @@
646 646  ** MetadataSchemaQueryType
647 647  
648 648  Content:
674 +
649 649  Header, Query
650 650  
651 651  Element Documentation:
... ... @@ -663,6 +663,7 @@
663 663  ** StructuresQueryType
664 664  
665 665  Content:
692 +
666 666  Header, Query
667 667  
668 668  Element Documentation:
... ... @@ -672,7 +672,7 @@
672 672  |(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
673 673  |(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
674 674  
675 -**DataflowQueryType: **DataflowQueryType defines the structure of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] query message.
702 +**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
676 676  
677 677  Derivation:
678 678  
... ... @@ -680,6 +680,7 @@
680 680  ** DataflowQueryType
681 681  
682 682  Content:
710 +
683 683  Header, Query
684 684  
685 685  Element Documentation:
... ... @@ -689,7 +689,7 @@
689 689  |(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
690 690  |(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
691 691  
692 -**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] query message.
720 +**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
693 693  
694 694  Derivation:
695 695  
... ... @@ -697,6 +697,7 @@
697 697  ** MetadataflowQueryType
698 698  
699 699  Content:
728 +
700 700  Header, Query
701 701  
702 702  Element Documentation:
... ... @@ -714,6 +714,7 @@
714 714  ** DataStructureQueryType
715 715  
716 716  Content:
746 +
717 717  Header, Query
718 718  
719 719  Element Documentation:
... ... @@ -731,6 +731,7 @@
731 731  ** MetadataStructureQueryType
732 732  
733 733  Content:
764 +
734 734  Header, Query
735 735  
736 736  Element Documentation:
... ... @@ -740,7 +740,7 @@
740 740  |(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
741 741  |(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
742 742  
743 -**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] query message.
774 +**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
744 744  
745 745  Derivation:
746 746  
... ... @@ -748,6 +748,7 @@
748 748  ** CategorySchemeQueryType
749 749  
750 750  Content:
782 +
751 751  Header, Query
752 752  
753 753  Element Documentation:
... ... @@ -757,7 +757,7 @@
757 757  |(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
758 758  |(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
759 759  
760 -**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] query message.
792 +**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
761 761  
762 762  Derivation:
763 763  
... ... @@ -765,6 +765,7 @@
765 765  ** ConceptSchemeQueryType
766 766  
767 767  Content:
800 +
768 768  Header, Query
769 769  
770 770  Element Documentation:
... ... @@ -774,7 +774,7 @@
774 774  |(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
775 775  |(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
776 776  
777 -**CodelistQueryType: **CodelistQueryType defines the structure of a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
810 +**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
778 778  
779 779  Derivation:
780 780  
... ... @@ -782,6 +782,7 @@
782 782  ** CodelistQueryType
783 783  
784 784  Content:
818 +
785 785  Header, Query
786 786  
787 787  Element Documentation:
... ... @@ -791,7 +791,7 @@
791 791  |(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
792 792  |(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
793 793  
794 -**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
828 +**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
795 795  
796 796  Derivation:
797 797  
... ... @@ -799,6 +799,7 @@
799 799  ** HierarchicalCodelistQueryType
800 800  
801 801  Content:
836 +
802 802  Header, Query
803 803  
804 804  Element Documentation:
... ... @@ -816,6 +816,7 @@
816 816  ** OrganisationSchemeQueryType
817 817  
818 818  Content:
854 +
819 819  Header, Query
820 820  
821 821  Element Documentation:
... ... @@ -833,6 +833,7 @@
833 833  ** ReportingTaxonomyQueryType
834 834  
835 835  Content:
872 +
836 836  Header, Query
837 837  
838 838  Element Documentation:
... ... @@ -842,7 +842,7 @@
842 842  |(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
843 843  |(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
844 844  
845 -**StructureSetQueryType: **StructureSetQueryType defines the structure of a [[structure set>>doc:sdmx:Glossary.Structure set.WebHome]] query message.
882 +**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
846 846  
847 847  Derivation:
848 848  
... ... @@ -850,6 +850,7 @@
850 850  ** StructureSetQueryType
851 851  
852 852  Content:
890 +
853 853  Header, Query
854 854  
855 855  Element Documentation:
... ... @@ -867,6 +867,7 @@
867 867  ** ProcessQueryType
868 868  
869 869  Content:
908 +
870 870  Header, Query
871 871  
872 872  Element Documentation:
... ... @@ -884,6 +884,7 @@
884 884  ** CategorisationQueryType
885 885  
886 886  Content:
926 +
887 887  Header, Query
888 888  
889 889  Element Documentation:
... ... @@ -893,7 +893,7 @@
893 893  |(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
894 894  |(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
895 895  
896 -**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] query message.
936 +**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
897 897  
898 898  Derivation:
899 899  
... ... @@ -901,6 +901,7 @@
901 901  ** ProvisionAgreementQueryType
902 902  
903 903  Content:
944 +
904 904  Header, Query
905 905  
906 906  Element Documentation:
... ... @@ -918,6 +918,7 @@
918 918  ** ConstraintQueryType
919 919  
920 920  Content:
962 +
921 921  Header, Query
922 922  
923 923  Element Documentation:
... ... @@ -935,6 +935,7 @@
935 935  ** TransformationSchemeQueryType
936 936  
937 937  Content:
980 +
938 938  Header, Query
939 939  
940 940  Element Documentation:
... ... @@ -944,7 +944,7 @@
944 944  |(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
945 945  |(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
946 946  
947 -**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mappings scheme query message.
990 +**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
948 948  
949 949  Derivation:
950 950  
... ... @@ -952,6 +952,7 @@
952 952  ** VtlMappingSchemeQueryType
953 953  
954 954  Content:
998 +
955 955  Header, Query
956 956  
957 957  Element Documentation:
... ... @@ -969,6 +969,7 @@
969 969  ** NamePersonalisationSchemeQueryType
970 970  
971 971  Content:
1016 +
972 972  Header, Query
973 973  
974 974  Element Documentation:
... ... @@ -986,6 +986,7 @@
986 986  ** RulesetSchemeQueryType
987 987  
988 988  Content:
1034 +
989 989  Header, Query
990 990  
991 991  Element Documentation:
... ... @@ -1003,6 +1003,7 @@
1003 1003  ** UserDefinedOperatorSchemeQueryType
1004 1004  
1005 1005  Content:
1052 +
1006 1006  Header, Query
1007 1007  
1008 1008  Element Documentation:
... ... @@ -1020,6 +1020,7 @@
1020 1020  ** CustomTypeSchemeQueryType
1021 1021  
1022 1022  Content:
1070 +
1023 1023  Header, Query
1024 1024  
1025 1025  Element Documentation:
... ... @@ -1032,17 +1032,19 @@
1032 1032  **ErrorType: **ErrorType describes the structure of an error response.
1033 1033  
1034 1034  Content:
1083 +
1035 1035  ErrorMessage+
1036 1036  
1037 1037  Element Documentation:
1038 1038  
1039 -(% style="width:974.835px" %)
1040 -|**Name**|(% style="width:271px" %)**Type**|(% style="width:584px" %)**Documentation**
1041 -|ErrorMessage|(% style="width:271px" %)com: CodedStatusMessageType|(% style="width:584px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors.
1088 +(% style="width:899.294px" %)
1089 +|**Name**|**Type**|(% style="width:546px" %)**Documentation**
1090 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
1042 1042  
1043 1043  **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1044 1044  
1045 1045  Content:
1095 +
1046 1046  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure*, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1047 1047  
1048 1048  Element Documentation:
... ... @@ -1055,17 +1055,17 @@
1055 1055  |Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1056 1056  |Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1057 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 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]].
1108 +|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. 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.
1109 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1110 +|DataSetAction|com:ActionType|(% style="width:552px" %)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).
1111 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1062 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.
1113 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1114 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1115 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1066 1066  |Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1067 1067  
1068 -**StructureHeaderType: **StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages.
1118 +**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1069 1069  
1070 1070  Derivation:
1071 1071  
... ... @@ -1073,19 +1073,20 @@
1073 1073  ** StructureHeaderType
1074 1074  
1075 1075  Content:
1126 +
1076 1076  ID, Test, Prepared, Sender, Receiver*, com:Name*, Source*
1077 1077  
1078 1078  Element Documentation:
1079 1079  
1080 -(% style="width:986.835px" %)
1081 -|(% style="width:162px" %)**Name**|(% style="width:193px" %)**Type**|(% style="width:630px" %)**Documentation**
1082 -|(% style="width:162px" %)ID|(% style="width:193px" %)com:IDType|(% style="width:630px" %)ID identifies an identification for the message, assigned by the sender.
1083 -|(% style="width:162px" %)Test|(% style="width:193px" %)xs:boolean|(% style="width:630px" %)Test indicates whether the message is for test purposes or not.
1084 -|(% style="width:162px" %)Prepared|(% style="width:193px" %)HeaderTimeType|(% style="width:630px" %)Prepared is the date the message was prepared.
1085 -|(% style="width:162px" %)Sender|(% style="width:193px" %)SenderType|(% style="width:630px" %)Sender is information about the party that is transmitting the message.
1086 -|(% style="width:162px" %)Receiver|(% style="width:193px" %)PartyType|(% style="width:630px" %)Receiver is information about the party that is the intended recipient of the message.
1087 -|(% style="width:162px" %)com:Name|(% style="width:193px" %)com:TextType|(% style="width:630px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1088 -|(% style="width:162px" %)Source|(% style="width:193px" %)com:TextType|(% style="width:630px" %)Source provides human-readable information about the source of the data.
1131 +(% style="width:1099.29px" %)
1132 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation**
1133 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender.
1134 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not.
1135 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared.
1136 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message.
1137 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message.
1138 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1139 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data.
1089 1089  
1090 1090  **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message.
1091 1091  
... ... @@ -1095,27 +1095,28 @@
1095 1095  ** GenericDataHeaderType
1096 1096  
1097 1097  Content:
1149 +
1098 1098  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1099 1099  
1100 1100  Element Documentation:
1101 1101  
1102 -(% style="width:970.835px" %)
1103 -|**Name**|(% style="width:250px" %)**Type**|(% style="width:589px" %)**Documentation**
1104 -|ID|(% style="width:250px" %)com:IDType|(% style="width:589px" %)ID identifies an identification for the message, assigned by the sender.
1105 -|Test|(% style="width:250px" %)xs:boolean|(% style="width:589px" %)Test indicates whether the message is for test purposes or not.
1106 -|Prepared|(% style="width:250px" %)HeaderTimeType|(% style="width:589px" %)Prepared is the date the message was prepared.
1107 -|Sender|(% style="width:250px" %)SenderType|(% style="width:589px" %)Sender is information about the party that is transmitting the message.
1108 -|Receiver|(% style="width:250px" %)PartyType|(% style="width:589px" %)Receiver is information about the party that is the intended recipient of the message.
1109 -|com:Name|(% style="width:250px" %)com:TextType|(% style="width:589px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1110 -|Structure|(% style="width:250px" %)com: GenericDataStructureType|(% style="width:589px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1111 -|DataProvider|(% style="width:250px" %)com: DataProviderReferenceType|(% style="width:589px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1112 -|DataSetAction|(% style="width:250px" %)com:ActionType|(% style="width:589px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1113 -|DataSetID|(% style="width:250px" %)com:IDType|(% style="width:589px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1114 -|Extracted|(% style="width:250px" %)xs:dateTime|(% style="width:589px" %)Extracted is a time-stamp from the system rendering the data.
1115 -|ReportingBegin|(% style="width:250px" %)com: ObservationalTimePeriodType|(% style="width:589px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1116 -|ReportingEnd|(% style="width:250px" %)com: ObservationalTimePeriodType|(% style="width:589px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1117 -|EmbargoDate|(% style="width:250px" %)xs:dateTime|(% style="width:589px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1118 -|Source|(% style="width:250px" %)com:TextType|(% style="width:589px" %)Source provides human-readable information about the source of the data.
1154 +(% style="width:895.294px" %)
1155 +|**Name**|**Type**|(% style="width:556px" %)**Documentation**
1156 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender.
1157 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not.
1158 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared.
1159 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1160 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1161 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1162 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
1163 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1164 +|DataSetAction|com:ActionType|(% style="width:556px" %)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).
1165 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1166 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1167 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1168 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1169 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1170 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1119 1119  
1120 1120  **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
1121 1121  
... ... @@ -1126,27 +1126,28 @@
1126 1126  *** GenericTimeSeriesDataHeaderType
1127 1127  
1128 1128  Content:
1181 +
1129 1129  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1130 1130  
1131 1131  Element Documentation:
1132 1132  
1133 -(% style="width:973.835px" %)
1134 -|**Name**|**Type**|(% style="width:542px" %)**Documentation**
1135 -|ID|com:IDType|(% style="width:542px" %)ID identifies an identification for the message, assigned by the sender.
1136 -|Test|xs:boolean|(% style="width:542px" %)Test indicates whether the message is for test purposes or not.
1137 -|Prepared|HeaderTimeType|(% style="width:542px" %)Prepared is the date the message was prepared.
1138 -|Sender|SenderType|(% style="width:542px" %)Sender is information about the party that is transmitting the message.
1139 -|Receiver|PartyType|(% style="width:542px" %)Receiver is information about the party that is the intended recipient of the message.
1140 -|com:Name|com:TextType|(% style="width:542px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1141 -|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:542px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1142 -|DataProvider|com: DataProviderReferenceType|(% style="width:542px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1143 -|DataSetAction|com:ActionType|(% style="width:542px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1144 -|DataSetID|com:IDType|(% style="width:542px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1145 -|Extracted|xs:dateTime|(% style="width:542px" %)Extracted is a time-stamp from the system rendering the data.
1146 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:542px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1147 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:542px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1148 -|EmbargoDate|xs:dateTime|(% style="width:542px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1149 -|Source|com:TextType|(% style="width:542px" %)Source provides human-readable information about the source of the data.
1186 +(% style="width:926.294px" %)
1187 +|**Name**|**Type**|(% style="width:497px" %)**Documentation**
1188 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender.
1189 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not.
1190 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared.
1191 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1192 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1193 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1194 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
1195 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1196 +|DataSetAction|com:ActionType|(% style="width:497px" %)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).
1197 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1198 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1199 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1200 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1201 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1202 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1150 1150  
1151 1151  **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
1152 1152  
... ... @@ -1156,27 +1156,28 @@
1156 1156  ** StructureSpecificDataHeaderType
1157 1157  
1158 1158  Content:
1212 +
1159 1159  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1160 1160  
1161 1161  Element Documentation:
1162 1162  
1163 1163  (% style="width:930.294px" %)
1164 -|**Name**|(% style="width:190px" %)**Type**|(% style="width:611px" %)**Documentation**
1165 -|ID|(% style="width:190px" %)com:IDType|(% style="width:611px" %)ID identifies an identification for the message, assigned by the sender.
1166 -|Test|(% style="width:190px" %)xs:boolean|(% style="width:611px" %)Test indicates whether the message is for test purposes or not.
1167 -|Prepared|(% style="width:190px" %)HeaderTimeType|(% style="width:611px" %)Prepared is the date the message was prepared.
1168 -|Sender|(% style="width:190px" %)SenderType|(% style="width:611px" %)Sender is information about the party that is transmitting the message.
1169 -|Receiver|(% style="width:190px" %)PartyType|(% style="width:611px" %)Receiver is information about the party that is the intended recipient of the message.
1170 -|com:Name|(% style="width:190px" %)com:TextType|(% style="width:611px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1171 -|Structure|(% style="width:190px" %)com: StructureSpecificDataStructureType|(% style="width:611px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1172 -|DataProvider|(% style="width:190px" %)com: DataProviderReferenceType|(% style="width:611px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1173 -|DataSetAction|(% style="width:190px" %)com:ActionType|(% style="width:611px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1174 -|DataSetID|(% style="width:190px" %)com:IDType|(% style="width:611px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1175 -|Extracted|(% style="width:190px" %)xs:dateTime|(% style="width:611px" %)Extracted is a time-stamp from the system rendering the data.
1176 -|ReportingBegin|(% style="width:190px" %)com: ObservationalTimePeriodType|(% style="width:611px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1177 -|ReportingEnd|(% style="width:190px" %)com: ObservationalTimePeriodType|(% style="width:611px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1178 -|EmbargoDate|(% style="width:190px" %)xs:dateTime|(% style="width:611px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1179 -|Source|(% style="width:190px" %)com:TextType|(% style="width:611px" %)Source provides human-readable information about the source of the data.
1218 +|**Name**|**Type**|(% style="width:578px" %)**Documentation**
1219 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender.
1220 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not.
1221 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared.
1222 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1223 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1224 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1225 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
1226 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1227 +|DataSetAction|com:ActionType|(% style="width:578px" %)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).
1228 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1229 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1230 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1231 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1232 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1233 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1180 1180  
1181 1181  **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
1182 1182  
... ... @@ -1187,29 +1187,30 @@
1187 1187  *** StructureSpecificTimeSeriesDataHeaderType
1188 1188  
1189 1189  Content:
1244 +
1190 1190  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1191 1191  
1192 1192  Element Documentation:
1193 1193  
1194 -(% style="width:967.835px" %)
1195 -|**Name**|(% style="width:238px" %)**Type**|(% style="width:486px" %)**Documentation**
1196 -|ID|(% style="width:238px" %)com:IDType|(% style="width:486px" %)ID identifies an identification for the message, assigned by the sender.
1197 -|Test|(% style="width:238px" %)xs:boolean|(% style="width:486px" %)Test indicates whether the message is for test purposes or not.
1198 -|Prepared|(% style="width:238px" %)HeaderTimeType|(% style="width:486px" %)Prepared is the date the message was prepared.
1199 -|Sender|(% style="width:238px" %)SenderType|(% style="width:486px" %)Sender is information about the party that is transmitting the message.
1200 -|Receiver|(% style="width:238px" %)PartyType|(% style="width:486px" %)Receiver is information about the party that is the intended recipient of the message.
1201 -|com:Name|(% style="width:238px" %)com:TextType|(% style="width:486px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1202 -|Structure|(% style="width:238px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:486px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1203 -|DataProvider|(% style="width:238px" %)com: DataProviderReferenceType|(% style="width:486px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1204 -|DataSetAction|(% style="width:238px" %)com:ActionType|(% style="width:486px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1205 -|DataSetID|(% style="width:238px" %)com:IDType|(% style="width:486px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1206 -|Extracted|(% style="width:238px" %)xs:dateTime|(% style="width:486px" %)Extracted is a time-stamp from the system rendering the data.
1207 -|ReportingBegin|(% style="width:238px" %)com: ObservationalTimePeriodType|(% style="width:486px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1208 -|ReportingEnd|(% style="width:238px" %)com: ObservationalTimePeriodType|(% style="width:486px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1209 -|EmbargoDate|(% style="width:238px" %)xs:dateTime|(% style="width:486px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1210 -|Source|(% style="width:238px" %)com:TextType|(% style="width:486px" %)Source provides human-readable information about the source of the data.
1249 +(% style="width:943.294px" %)
1250 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation**
1251 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender.
1252 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not.
1253 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared.
1254 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1255 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1256 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1257 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
1258 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1259 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)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).
1260 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1261 +|Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1262 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1263 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1264 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1265 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1211 1211  
1212 -**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
1267 +**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1213 1213  
1214 1214  Derivation:
1215 1215  
... ... @@ -1217,6 +1217,7 @@
1217 1217  ** GenericMetadataHeaderType
1218 1218  
1219 1219  Content:
1275 +
1220 1220  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1221 1221  
1222 1222  Element Documentation:
... ... @@ -1229,14 +1229,14 @@
1229 1229  |Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1230 1230  |Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1231 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 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]].
1288 +|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. 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.
1289 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1290 +|DataSetAction|com:ActionType|(% style="width:554px" %)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).
1291 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1236 1236  |Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1237 1237  |Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1238 1238  
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.
1295 +**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1240 1240  
1241 1241  Derivation:
1242 1242  
... ... @@ -1244,6 +1244,7 @@
1244 1244  ** StructureSpecificMetadataHeaderType
1245 1245  
1246 1246  Content:
1303 +
1247 1247  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1248 1248  
1249 1249  Element Documentation:
... ... @@ -1256,10 +1256,10 @@
1256 1256  |Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1257 1257  |Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1258 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]].
1316 +|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. 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.
1317 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1318 +|DataSetAction|com:ActionType|(% style="width:557px" %)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).
1319 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
1263 1263  |Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1264 1264  |Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1265 1265  
... ... @@ -1271,17 +1271,18 @@
1271 1271  ** BasicHeaderType
1272 1272  
1273 1273  Content:
1331 +
1274 1274  ID, Test, Prepared, Sender, Receiver
1275 1275  
1276 1276  Element Documentation:
1277 1277  
1278 -(% style="width:964.835px" %)
1279 -|**Name**|(% style="width:216px" %)**Type**|(% style="width:535px" %)**Documentation**
1280 -|ID|(% style="width:216px" %)com:IDType|(% style="width:535px" %)ID identifies an identification for the message, assigned by the sender.
1281 -|Test|(% style="width:216px" %)xs:boolean|(% style="width:535px" %)Test indicates whether the message is for test purposes or not.
1282 -|Prepared|(% style="width:216px" %)HeaderTimeType|(% style="width:535px" %)Prepared is the date the message was prepared.
1283 -|Sender|(% style="width:216px" %)SenderType|(% style="width:535px" %)Sender is information about the party that is transmitting the message.
1284 -|Receiver|(% style="width:216px" %)PartyType|(% style="width:535px" %)Receiver is information about the party that is the intended recipient of the message.
1336 +(% style="width:903.294px" %)
1337 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation**
1338 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender.
1339 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not.
1340 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared.
1341 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message.
1342 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message.
1285 1285  
1286 1286  **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages.
1287 1287  
... ... @@ -1290,20 +1290,21 @@
1290 1290  id
1291 1291  
1292 1292  Content:
1293 -com:Name*, (% style="color:#e74c3c" %)[[Contact>>doc:sdmx:Glossary.Contact.WebHome]](%%)*
1294 1294  
1295 -[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1352 +com:Name*, Contact*
1296 1296  
1297 -(% style="width:888.294px" %)
1298 -|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:569px" %)**Documentation**
1299 -|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:569px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
1354 +Attribute Documentation:
1300 1300  
1356 +(% style="width:739.294px" %)
1357 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
1358 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
1359 +
1301 1301  Element Documentation:
1302 1302  
1303 -(% style="width:889.294px" %)
1304 -|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:568px" %)**Documentation**
1305 -|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:568px" %)Name is a human-readable name of the party.
1306 -|(% style="width:134px" %)(% style="color:#e74c3c" %)[[Contact>>doc:sdmx:Glossary.Contact.WebHome]]|(% style="width:183px" %)ContactType|(% style="width:568px" %)(% style="color:#e74c3c" %)[[Contact>>doc:sdmx:Glossary.Contact.WebHome]](%%) provides contact information for the party in regard to the transmission of the message.
1362 +(% style="width:751.294px" %)
1363 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
1364 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
1365 +|(% style="width:134px" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)Contact provides contact information for the party in regard to the transmission of the message.
1307 1307  
1308 1308  **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1309 1309  
... ... @@ -1313,45 +1313,43 @@
1313 1313  ** SenderType
1314 1314  
1315 1315  Attributes:
1375 +
1316 1316  id
1317 1317  
1318 1318  Content:
1319 -com:Name*, (% style="color:#e74c3c" %)[[Contact>>doc:sdmx:Glossary.Contact.WebHome]](%%)*, Timezone?
1320 1320  
1321 -[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1380 +com:Name*, Contact*, Timezone?
1322 1322  
1382 +Attribute Documentation:
1383 +
1323 1323  (% style="width:824.294px" %)
1324 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.
1386 +|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
1326 1326  
1327 1327  Element Documentation:
1328 1328  
1329 -(% style="width:966.835px" %)
1330 -|**Name**|**Type**|(% style="width:686px" %)**Documentation**
1331 -|com:Name|com:TextType|(% style="width:686px" %)Name is a human-readable name of the party.
1332 -|(%%)(% style="color:#e74c3c" %)[[Contact>>doc:sdmx:Glossary.Contact.WebHome]]|ContactType|(% style="width:686px" %)(((
1333 -(% style="width:966.835px" %)
1334 -|(% style="width:686px" %)[[Contact>>doc:sdmx:Glossary.Contact.WebHome]] provides contact information for the party in regard to the transmission of the message.
1335 -)))
1336 -|Timezone|com:TimezoneType|(% style="width:686px" %)Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1390 +|**Name**|**Type**|**Documentation**
1391 +|com:Name|com:TextType|Name is a human-readable name of the party.
1392 +|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1393 +|Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1337 1337  
1338 1338  **ContactType: **ContactType provides defines the contact information about a party.
1339 1339  
1340 1340  Content:
1398 +
1341 1341  com:Name*, Department*, Role*, (Telephone | Fax | X400 | URI | Email)*
1342 1342  
1343 1343  Element Documentation:
1344 1344  
1345 -(% style="width:969.835px" %)
1346 -|**Name**|(% style="width:161px" %)**Type**|(% style="width:613px" %)**Documentation**
1347 -|com:Name|(% style="width:161px" %)com:TextType|(% style="width:613px" %)Name contains a human-readable name for the [[contact>>doc:sdmx:Glossary.Contact.WebHome]].
1348 -|Department|(% style="width:161px" %)com:TextType|(% style="width:613px" %)Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
1349 -|Role|(% style="width:161px" %)com:TextType|(% style="width:613px" %)Role is the responsibility of the contact person with respect to the object for which this person is the [[contact>>doc:sdmx:Glossary.Contact.WebHome]].
1350 -|Telephone|(% style="width:161px" %)xs:string|(% style="width:613px" %)Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the contact person.
1351 -|Fax|(% style="width:161px" %)xs:string|(% style="width:613px" %)Fax holds the fax number for the contact person.
1352 -|X400|(% style="width:161px" %)xs:string|(% style="width:613px" %)X400 holds the X.400 address for the contact person.
1353 -|URI|(% style="width:161px" %)xs:anyURI|(% style="width:613px" %)URI holds an information URL for the contact person.
1354 -|Email|(% style="width:161px" %)xs:string|(% style="width:613px" %)Email holds the email address for the contact person.
1403 +|**Name**|**Type**|**Documentation**
1404 +|com:Name|com:TextType|Name contains a human-readable name for the contact.
1405 +|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
1406 +|Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
1407 +|Telephone|xs:string|Telephone holds the telephone number for the contact person.
1408 +|Fax|xs:string|Fax holds the fax number for the contact person.
1409 +|X400|xs:string|X400 holds the X.400 address for the contact person.
1410 +|URI|xs:anyURI|URI holds an information URL for the contact person.
1411 +|Email|xs:string|Email holds the email address for the contact person.
1355 1355  
1356 1356  === 2.1.4 Simple Types ===
1357 1357  
... ... @@ -1358,6 +1358,7 @@
1358 1358  **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
1359 1359  
1360 1360  Union of:
1418 +
1361 1361  xs:dateTime, xs:date.
1362 1362  
1363 1363  == 2.2 Message Footer Namespace ==
... ... @@ -1368,61 +1368,67 @@
1368 1368  
1369 1369  Referenced Namespaces:
1370 1370  
1371 -(% style="width:821.835px" %)
1372 -|(% style="width:525px" %)**Namespace**|(% style="width:294px" %)**Prefix**
1373 -|(% style="width:525px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:294px" %)com
1374 -|(% style="width:525px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:294px" %)xs
1429 +|**Namespace**|**Prefix**
1430 +|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com
1431 +|http:~/~/www.w3.org/2001/XMLSchema|xs
1375 1375  
1376 1376  Contents:
1434 +
1377 1377  1 Global Element
1378 1378  2 Complex Types
1379 1379  1 Simple Type
1380 1380  
1381 -=== 2.2.2 Global Elements ===
1439 +1.
1440 +11.
1441 +111. Global Elements
1382 1382  
1383 1383  **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1384 1384  
1385 -=== 2.2.3 Complex Types ===
1445 +1.
1446 +11.
1447 +111. Complex Types
1386 1386  
1387 1387  **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.
1388 1388  
1389 1389  Content:
1452 +
1390 1390  Message+
1391 1391  
1392 1392  Element Documentation:
1393 1393  
1394 -(% style="width:989.835px" %)
1395 -|**Name**|(% style="width:181px" %)**Type**|(% style="width:695px" %)**Documentation**
1396 -|Message|(% style="width:181px" %)FooterMessageType|(% style="width:695px" %)Message contains a single error, information, or warning message. A [[code>>doc:sdmx:Glossary.Code.WebHome]] is provided along with an optional severity. The text of the message can be expressed in multiple languages.
1457 +|**Name**|**Type**|**Documentation**
1458 +|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.
1397 1397  
1398 -**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.
1460 +**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.
1399 1399  
1400 1400  Derivation:
1401 1401  
1402 -* com:StatusMessageType (restriction)
1403 -** com:CodedStatusMessageType (extension)
1404 -*** FooterMessageType
1464 +com:StatusMessageType (restriction)
1465 +[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1466 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1405 1405  
1406 1406  Attributes:
1407 -[[code>>doc:sdmx:Glossary.Code.WebHome]], severity?
1408 1408  
1470 +code, severity?
1471 +
1409 1409  Content:
1473 +
1410 1410  com:Text+
1411 1411  
1412 -[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1476 +Attribute Documentation:
1413 1413  
1414 -(% style="width:981.835px" %)
1415 -|**Name**|(% style="width:152px" %)**Type**|(% style="width:754px" %)**Documentation**
1416 -|[[code>>doc:sdmx:Glossary.Code.WebHome]]|(% style="width:152px" %)xs:string|(% style="width:754px" %)The [[code>>doc:sdmx:Glossary.Code.WebHome]] [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds an optional [[code>>doc:sdmx:Glossary.Code.WebHome]] identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
1417 -|severity|(% style="width:152px" %)SeverityCodeType|(% style="width:754px" %)
1478 +|**Name**|**Type**|**Documentation**
1479 +|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.
1480 +|severity|SeverityCodeType|
1418 1418  
1419 1419  Element Documentation:
1420 1420  
1421 -(% style="width:985.835px" %)
1422 -|**Name**|(% style="width:155px" %)**Type**|(% style="width:635px" %)**Documentation**
1423 -|com:Text|(% style="width:155px" %)com:TextType|(% style="width:635px" %)Text contains the text of the message, in parallel language values.
1484 +|**Name**|**Type**|**Documentation**
1485 +|com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1424 1424  
1425 -=== 2.2.4 Simple Types ===
1487 +1.
1488 +11.
1489 +111. Simple Types
1426 1426  
1427 1427  **SeverityCodeType:**
1428 1428  
... ... @@ -1430,8 +1430,22 @@
1430 1430  
1431 1431  Enumerations:
1432 1432  
1433 -(% style="width:996.835px" %)
1434 -|**Value**|(% style="width:783px" %)**Documentation**
1435 -|Error|(% style="width:783px" %)Error indicates the status message coresponds to an error.
1436 -|Warning|(% style="width:783px" %)Warning indicates that the status message corresponds to a warning.
1437 -|Information|(% style="width:783px" %)Information indicates that the status message corresponds to an informational message.
1497 +|**Value**|**Documentation**
1498 +|Error|Error indicates the status message coresponds to an error.
1499 +|Warning|Warning indicates that the status message corresponds to a warning.
1500 +|Information|Information indicates that the status message corresponds to an informational message.
1501 +
1502 +
1503 +
1504 +
1505 +
1506 +
1507 +
1508 +
1509 +
1510 +
1511 +
1512 +
1513 +
1514 +
1515 +
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +1