Changes for page Part I. Message Namespace

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

From version 4.2
edited by Helena
on 2025/06/24 10:20
Change comment: There is no comment for this version
To version 7.1
edited by Helena
on 2025/06/29 16:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Tags
... ... @@ -1,0 +1,1 @@
1 +Attribute|Category scheme|Code|Code list|Concept scheme|Contact phone number|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchical code list|Metadata set|Metadata structure definition|Metadataflow|Notification|Provision agreement|Reference metadata|Reference period|Reporting taxonomy|SDMX Registry|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Structure set|Subscription|Time period|Validation and transformation language
Content
... ... @@ -8,7 +8,7 @@
8 8  
9 9  **~1. Problem**
10 10  
11 -Various parts of the the documentation refer to stand-alone concepts, which were part of earlier draft releases but ultimately excluded from the final release of the standard.
11 +Various parts of the the documentation refer to stand-alone (% style="color:#e74c3c" %)concepts(%%), which were part of earlier draft releases but ultimately excluded from the final release of the standard.
12 12  
13 13  **Rectification**
14 14  
... ... @@ -16,11 +16,11 @@
16 16  
17 17  = 1. Introduction =
18 18  
19 -At the core of the SDMX XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in SDMX.
19 +At the core of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
20 20  
21 -There are two namespaces associated with the messages. The main namespace schema which defines every message in SDMX is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted.
21 +There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer (% style="color:#e74c3c" %)level(%%) information that is available in messages which might require non-standard payload information to be transmitted.
22 22  
23 -In general, every message in SDMX follows common format of:
23 +In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of:
24 24  
25 25  * Header
26 26  * Payload (0..n)
... ... @@ -42,10 +42,10 @@
42 42  |(% style="width:612px" %)**Namespace**|(% style="width:173px" %)**Prefix**
43 43  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:173px" %)com
44 44  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|(% style="width:173px" %)dat
45 -|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)dsd
45 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)[[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]]
46 46  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|(% style="width:173px" %)ftr
47 47  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|(% style="width:173px" %)rep
48 -|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|(% style="width:173px" %)msd
48 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|(% style="width:173px" %)[[msd>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]
49 49  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|(% style="width:173px" %)qry
50 50  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|(% style="width:173px" %)ref
51 51  |(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|(% style="width:173px" %)str
... ... @@ -59,103 +59,103 @@
59 59  
60 60  === 2.1.2 Global Elements ===
61 61  
62 -**Structure (StructureType): **Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), constraints (attachment and content) data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, and structure sets.
62 +**Structure (StructureType): **Structure is a message that contains [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. It may contain any of the following; categorisations, [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) ([[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]), (% style="color:#e74c3c" %)constraints(%%) (attachment and content) [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], organisation schemes, processes, [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]], and structure sets.
63 63  
64 -**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. Data sets in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation dimension).
64 +**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. [[Data sets>>doc:sdmx:Glossary.Data set.WebHome]] in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]).
65 65  
66 -**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
66 +**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
67 67  
68 -**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to data structure definition. The payload of this message (i.e. the data sets) will be based on XML schemas which are specific to the data structure definition and the orientation (i.e. the observation dimension) of the data.
68 +**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The payload of this message (i.e. the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]) will be based on XML schemas which are specific to the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and the orientation (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data.
69 69  
70 -**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
70 +**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
71 71  
72 -**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
72 +**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
73 73  
74 -**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the metadata structure definitions which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each metadata set provided will be based on a metadata structure specific schema.
74 +**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] provided will be based on a metadata structure specific schema.
75 75  
76 -**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
76 +**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services.
77 77  
78 -**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
78 +**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
79 79  
80 80  **SubmitRegistrationsResponse (SubmitRegistrationsResponseType): **SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a registration requests. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
81 81  
82 -**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
82 +**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
83 83  
84 84  **QueryRegistrationResponse (QueryRegistrationResponseType): **QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
85 85  
86 -**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
86 +**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
87 87  
88 88  **SubmitStructureResponse (SubmitStructureResponseType): **SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
89 89  
90 90  **SubmitSubscriptionsRequest (SubmitSubscriptionsRequestType): **SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
91 91  
92 -**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
92 +**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
93 93  
94 -**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
94 +**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
95 95  
96 -**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
96 +**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
97 97  
98 -**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
98 +**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
99 99  
100 -**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data.
100 +**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure specific data.
101 101  
102 -**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query SDMX compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
102 +**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.
103 103  
104 -**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
104 +**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
105 105  
106 -**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
106 +**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.
107 107  
108 -**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata.
108 +**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic format [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
109 109  
110 -**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata.
110 +**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
111 111  
112 -**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query SDMX compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
112 +**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structure specific schemas for the purpose of validating structured data.
113 113  
114 -**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query SDMX compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
114 +**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.
115 115  
116 -**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query SDMX compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
116 +**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).
117 117  
118 -**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows.
118 +**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for dataflows.
119 119  
120 -**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows.
120 +**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]].
121 121  
122 -**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions.
122 +**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structures definitions.
123 123  
124 -**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions.
124 +**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].
125 125  
126 -**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes.
126 +**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]].
127 127  
128 -**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes.
128 +**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]].
129 129  
130 -**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists.
130 +**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for codelists.
131 131  
132 -**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists.
132 +**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for hierarchical codelists.
133 133  
134 -**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes.
134 +**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for organisation schemes.
135 135  
136 -**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies.
136 +**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]].
137 137  
138 -**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets.
138 +**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure sets.
139 139  
140 -**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes.
140 +**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for processes.
141 141  
142 -**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations.
142 +**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for categorisations.
143 143  
144 -**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements.
144 +**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for provision agreements.
145 145  
146 -**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints.
146 +**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for (% style="color:#e74c3c" %)constraints(%%).
147 147  
148 -**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes.
148 +**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for transformation schemes.
149 149  
150 -**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes.
150 +**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes.
151 151  
152 -**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes.
152 +**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for name personalisation schemes.
153 153  
154 -**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes.
154 +**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for ruleset schemes.
155 155  
156 -**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes.
156 +**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for user defined schemes.
157 157  
158 -**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes.
158 +**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for custom type schemes.
159 159  
160 160  **Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages.
161 161  
... ... @@ -181,7 +181,6 @@
181 181  ** StructureType
182 182  
183 183  Content:
184 -
185 185  Header, Structures?, ftr:Footer?
186 186  
187 187  Element Documentation:
... ... @@ -200,15 +200,14 @@
200 200  ** GenericDataType
201 201  
202 202  Content:
202 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
203 203  
204 -Header, DataSet*, ftr:Footer?
205 -
206 206  Element Documentation:
207 207  
208 208  (% style="width:847.294px" %)
209 209  |**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation**
210 210  |Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %)
211 -|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
209 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)
212 212  |ftr:Footer|(% style="width:227px" %)ftr:FooterType|(% style="width:450px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
213 213  
214 214  **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
... ... @@ -220,18 +220,17 @@
220 220  *** GenericTimeSeriesDataType
221 221  
222 222  Content:
221 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
223 223  
224 -Header, DataSet*, ftr:Footer?
225 -
226 226  Element Documentation:
227 227  
228 228  (% style="width:856.294px" %)
229 229  |**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation**
230 230  |Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %)
231 -|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
228 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)
232 232  |ftr:Footer|(% style="width:239px" %)ftr:FooterType|(% style="width:458px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
233 233  
234 -**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
231 +**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
235 235  
236 236  Derivation:
237 237  
... ... @@ -239,15 +239,14 @@
239 239  ** StructureSpecificDataType
240 240  
241 241  Content:
239 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
242 242  
243 -Header, DataSet*, ftr:Footer?
244 -
245 245  Element Documentation:
246 246  
247 247  (% style="width:828.294px" %)
248 248  |**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation**
249 249  |Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %)
250 -|DataSet|(% style="width:247px" %)//dsd:DataSetType//|(% style="width:420px" %)
246 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//[[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]]:DataSetType//|(% style="width:420px" %)
251 251  |ftr:Footer|(% style="width:247px" %)ftr:FooterType|(% style="width:420px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
252 252  
253 253  **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message.
... ... @@ -259,15 +259,14 @@
259 259  *** StructureSpecificTimeSeriesDataType
260 260  
261 261  Content:
258 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?
262 262  
263 -Header, DataSet*, ftr:Footer?
264 -
265 265  Element Documentation:
266 266  
267 267  (% style="width:839.294px" %)
268 268  |**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation**
269 269  |Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %)
270 -|DataSet|(% style="width:256px" %)//dsd: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
265 +|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//[[dsd>>doc:sdmx:Glossary.Data structure definition.WebHome]]: TimeSeriesDataSetTyp e//|(% style="width:434px" %)
271 271  |ftr:Footer|(% style="width:256px" %)ftr:FooterType|(% style="width:434px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
272 272  
273 273  **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
... ... @@ -278,7 +278,6 @@
278 278  ** GenericMetadataType
279 279  
280 280  Content:
281 -
282 282  Header, MetadataSet*, ftr:Footer?
283 283  
284 284  Element Documentation:
... ... @@ -289,7 +289,7 @@
289 289  |(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %)
290 290  |(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
291 291  
292 -**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
286 +**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
293 293  
294 294  Derivation:
295 295  
... ... @@ -297,7 +297,6 @@
297 297  ** StructureSpecificMetadataType
298 298  
299 299  Content:
300 -
301 301  Header, MetadataSet*, ftr:Footer?
302 302  
303 303  Element Documentation:
... ... @@ -305,7 +305,7 @@
305 305  (% style="width:841.294px" %)
306 306  |(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation**
307 307  |(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %)
308 -|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %)
301 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//[[msd>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]:MetadataSetType//|(% style="width:428px" %)
309 309  |(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
310 310  
311 311  **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
... ... @@ -316,7 +316,6 @@
316 316  ** RegistryInterfaceType
317 317  
318 318  Content:
319 -
320 320  Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, ftr:Footer?
321 321  
322 322  Element Documentation:
... ... @@ -324,17 +324,17 @@
324 324  (% style="width:903.294px" %)
325 325  |**Name**|**Type**|(% style="width:441px" %)**Documentation**
326 326  |Header|BasicHeaderType|(% style="width:441px" %)
327 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
319 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
328 328  |SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
329 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
321 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
330 330  |QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
331 -|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
323 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
332 332  |SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
333 333  |SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
334 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
335 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
336 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
337 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
326 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
327 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
328 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
329 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
338 338  |ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
339 339  
340 340  **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
... ... @@ -346,7 +346,6 @@
346 346  *** SubmitRegistrationsRequestType
347 347  
348 348  Content:
349 -
350 350  Header, SubmitRegistrationsRequest
351 351  
352 352  Element Documentation:
... ... @@ -354,7 +354,7 @@
354 354  (% style="width:844.294px" %)
355 355  |**Name**|**Type**|(% style="width:377px" %)**Documentation**
356 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.
348 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
358 358  
359 359  **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document.
360 360  
... ... @@ -365,7 +365,6 @@
365 365  *** SubmitRegistrationsResponseType
366 366  
367 367  Content:
368 -
369 369  Header, SubmitRegistrationsResponse, ftr:Footer?
370 370  
371 371  Element Documentation:
... ... @@ -385,7 +385,6 @@
385 385  *** QueryRegistrationRequestType
386 386  
387 387  Content:
388 -
389 389  Header, QueryRegistrationRequest
390 390  
391 391  Element Documentation:
... ... @@ -393,7 +393,7 @@
393 393  (% style="width:847.294px" %)
394 394  |**Name**|**Type**|(% style="width:397px" %)**Documentation**
395 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.
385 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.
397 397  
398 398  **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document.
399 399  
... ... @@ -404,7 +404,6 @@
404 404  *** QueryRegistrationResponseType
405 405  
406 406  Content:
407 -
408 408  Header, QueryRegistrationResponse, ftr:Footer?
409 409  
410 410  Element Documentation:
... ... @@ -424,7 +424,6 @@
424 424  *** SubmitStructureRequestType
425 425  
426 426  Content:
427 -
428 428  Header, SubmitStructureRequest
429 429  
430 430  Element Documentation:
... ... @@ -432,7 +432,7 @@
432 432  (% style="width:870.294px" %)
433 433  |**Name**|**Type**|(% style="width:453px" %)**Documentation**
434 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.
422 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
436 436  
437 437  **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document.
438 438  
... ... @@ -443,7 +443,6 @@
443 443  *** SubmitStructureResponseType
444 444  
445 445  Content:
446 -
447 447  Header, SubmitStructureResponse, ftr:Footer?
448 448  
449 449  Element Documentation:
... ... @@ -454,7 +454,7 @@
454 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 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.
456 456  
457 -**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document.
443 +**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document.
458 458  
459 459  Derivation:
460 460  
... ... @@ -463,7 +463,6 @@
463 463  *** SubmitSubscriptionsRequestType
464 464  
465 465  Content:
466 -
467 467  Header, SubmitSubscriptionsRequest
468 468  
469 469  Element Documentation:
... ... @@ -473,7 +473,7 @@
473 473  |Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %)
474 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.
475 475  
476 -**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document.
461 +**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document.
477 477  
478 478  Derivation:
479 479  
... ... @@ -482,7 +482,6 @@
482 482  *** SubmitSubscriptionsResponseType
483 483  
484 484  Content:
485 -
486 486  Header, SubmitSubscriptionsResponse, ftr:Footer?
487 487  
488 488  Element Documentation:
... ... @@ -490,10 +490,10 @@
490 490  (% style="width:843.294px" %)
491 491  |**Name**|**Type**|(% style="width:362px" %)**Documentation**
492 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.
477 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.
494 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.
495 495  
496 -**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document.
480 +**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document.
497 497  
498 498  Derivation:
499 499  
... ... @@ -502,7 +502,6 @@
502 502  *** QuerySubscriptionRequestType
503 503  
504 504  Content:
505 -
506 506  Header, QuerySubscriptionRequest
507 507  
508 508  Element Documentation:
... ... @@ -510,9 +510,9 @@
510 510  (% style="width:839.294px" %)
511 511  |(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation**
512 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.
496 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
514 514  
515 -**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document.
498 +**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document.
516 516  
517 517  Derivation:
518 518  
... ... @@ -521,7 +521,6 @@
521 521  *** QuerySubscriptionResponseType
522 522  
523 523  Content:
524 -
525 525  Header, QuerySubscriptionResponse, ftr:Footer?
526 526  
527 527  Element Documentation:
... ... @@ -529,10 +529,10 @@
529 529  (% style="width:912.294px" %)
530 530  |**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation**
531 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.
514 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent.
533 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.
534 534  
535 -**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document.
517 +**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document.
536 536  
537 537  Derivation:
538 538  
... ... @@ -541,7 +541,6 @@
541 541  *** NotifyRegistryEventType
542 542  
543 543  Content:
544 -
545 545  Header, NotifyRegistryEvent
546 546  
547 547  Element Documentation:
... ... @@ -549,7 +549,7 @@
549 549  (% style="width:836.294px" %)
550 550  |**Name**|**Type**|(% style="width:473px" %)**Documentation**
551 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.
533 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided.
553 553  
554 554  **DataQueryType: **DataQueryType defines the structure of a data query message.
555 555  
... ... @@ -559,7 +559,6 @@
559 559  ** DataQueryType
560 560  
561 561  Content:
562 -
563 563  Header, Query
564 564  
565 565  Element Documentation:
... ... @@ -578,7 +578,6 @@
578 578  *** GenericDataQueryType
579 579  
580 580  Content:
581 -
582 582  Header, Query
583 583  
584 584  Element Documentation:
... ... @@ -598,7 +598,6 @@
598 598  **** GenericTimeSeriesDataQueryType
599 599  
600 600  Content:
601 -
602 602  Header, Query
603 603  
604 604  Element Documentation:
... ... @@ -617,7 +617,6 @@
617 617  *** StructureSpecificTimeSeriesDataQueryType
618 618  
619 619  Content:
620 -
621 621  Header, Query
622 622  
623 623  Element Documentation:
... ... @@ -627,7 +627,7 @@
627 627  |(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %)
628 628  |(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %)
629 629  
630 -**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message.
607 +**MetadataQueryType: **MetadataQueryType defines the structure of a [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] query message.
631 631  
632 632  Derivation:
633 633  
... ... @@ -635,7 +635,6 @@
635 635  ** MetadataQueryType
636 636  
637 637  Content:
638 -
639 639  Header, Query
640 640  
641 641  Element Documentation:
... ... @@ -653,7 +653,6 @@
653 653  ** DataSchemaQueryType
654 654  
655 655  Content:
656 -
657 657  Header, Query
658 658  
659 659  Element Documentation:
... ... @@ -671,7 +671,6 @@
671 671  ** MetadataSchemaQueryType
672 672  
673 673  Content:
674 -
675 675  Header, Query
676 676  
677 677  Element Documentation:
... ... @@ -689,7 +689,6 @@
689 689  ** StructuresQueryType
690 690  
691 691  Content:
692 -
693 693  Header, Query
694 694  
695 695  Element Documentation:
... ... @@ -699,7 +699,7 @@
699 699  |(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %)
700 700  |(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %)
701 701  
702 -**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message.
675 +**DataflowQueryType: **DataflowQueryType defines the structure of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] query message.
703 703  
704 704  Derivation:
705 705  
... ... @@ -707,7 +707,6 @@
707 707  ** DataflowQueryType
708 708  
709 709  Content:
710 -
711 711  Header, Query
712 712  
713 713  Element Documentation:
... ... @@ -717,7 +717,7 @@
717 717  |(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %)
718 718  |(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %)
719 719  
720 -**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message.
692 +**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] query message.
721 721  
722 722  Derivation:
723 723  
... ... @@ -725,7 +725,6 @@
725 725  ** MetadataflowQueryType
726 726  
727 727  Content:
728 -
729 729  Header, Query
730 730  
731 731  Element Documentation:
... ... @@ -743,7 +743,6 @@
743 743  ** DataStructureQueryType
744 744  
745 745  Content:
746 -
747 747  Header, Query
748 748  
749 749  Element Documentation:
... ... @@ -761,7 +761,6 @@
761 761  ** MetadataStructureQueryType
762 762  
763 763  Content:
764 -
765 765  Header, Query
766 766  
767 767  Element Documentation:
... ... @@ -771,7 +771,7 @@
771 771  |(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %)
772 772  |(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %)
773 773  
774 -**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message.
743 +**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] query message.
775 775  
776 776  Derivation:
777 777  
... ... @@ -779,7 +779,6 @@
779 779  ** CategorySchemeQueryType
780 780  
781 781  Content:
782 -
783 783  Header, Query
784 784  
785 785  Element Documentation:
... ... @@ -789,7 +789,7 @@
789 789  |(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %)
790 790  |(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %)
791 791  
792 -**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message.
760 +**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] query message.
793 793  
794 794  Derivation:
795 795  
... ... @@ -797,7 +797,6 @@
797 797  ** ConceptSchemeQueryType
798 798  
799 799  Content:
800 -
801 801  Header, Query
802 802  
803 803  Element Documentation:
... ... @@ -807,7 +807,7 @@
807 807  |(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %)
808 808  |(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %)
809 809  
810 -**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message.
777 +**CodelistQueryType: **CodelistQueryType defines the structure of a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
811 811  
812 812  Derivation:
813 813  
... ... @@ -815,9 +815,9 @@
815 815  ** CodelistQueryType
816 816  
817 817  Content:
785 +Header, Query
818 818  
819 -* Header, Query
820 -* Element Documentation:
787 +Element Documentation:
821 821  
822 822  (% style="width:911.294px" %)
823 823  |(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation**
... ... @@ -824,7 +824,7 @@
824 824  |(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %)
825 825  |(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %)
826 826  
827 -**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message.
794 +**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message.
828 828  
829 829  Derivation:
830 830  
... ... @@ -832,9 +832,9 @@
832 832  ** HierarchicalCodelistQueryType
833 833  
834 834  Content:
802 +Header, Query
835 835  
836 -* Header, Query
837 -* Element Documentation:
804 +Element Documentation:
838 838  
839 839  (% style="width:906.294px" %)
840 840  |(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation**
... ... @@ -849,9 +849,9 @@
849 849  ** OrganisationSchemeQueryType
850 850  
851 851  Content:
819 +Header, Query
852 852  
853 -* Header, Query
854 -* Element Documentation:
821 +Element Documentation:
855 855  
856 856  (% style="width:891.294px" %)
857 857  |(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation**
... ... @@ -866,9 +866,9 @@
866 866  ** ReportingTaxonomyQueryType
867 867  
868 868  Content:
836 +Header, Query
869 869  
870 -* Header, Query
871 -* Element Documentation:
838 +Element Documentation:
872 872  
873 873  (% style="width:916.294px" %)
874 874  |(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation**
... ... @@ -875,7 +875,7 @@
875 875  |(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %)
876 876  |(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %)
877 877  
878 -**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message.
845 +**StructureSetQueryType: **StructureSetQueryType defines the structure of a [[structure set>>doc:sdmx:Glossary.Structure set.WebHome]] query message.
879 879  
880 880  Derivation:
881 881  
... ... @@ -883,9 +883,9 @@
883 883  ** StructureSetQueryType
884 884  
885 885  Content:
853 +Header, Query
886 886  
887 -* Header, Query
888 -* Element Documentation:
855 +Element Documentation:
889 889  
890 890  (% style="width:896.294px" %)
891 891  |(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation**
... ... @@ -900,9 +900,9 @@
900 900  ** ProcessQueryType
901 901  
902 902  Content:
870 +Header, Query
903 903  
904 -* Header, Query
905 -* Element Documentation:
872 +Element Documentation:
906 906  
907 907  (% style="width:907.294px" %)
908 908  |(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation**
... ... @@ -917,9 +917,9 @@
917 917  ** CategorisationQueryType
918 918  
919 919  Content:
887 +Header, Query
920 920  
921 -* Header, Query
922 -* Element Documentation:
889 +Element Documentation:
923 923  
924 924  (% style="width:897.294px" %)
925 925  |(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation**
... ... @@ -926,7 +926,7 @@
926 926  |(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %)
927 927  |(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %)
928 928  
929 -**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message.
896 +**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] query message.
930 930  
931 931  Derivation:
932 932  
... ... @@ -934,9 +934,9 @@
934 934  ** ProvisionAgreementQueryType
935 935  
936 936  Content:
904 +Header, Query
937 937  
938 -* Header, Query
939 -* Element Documentation:
906 +Element Documentation:
940 940  
941 941  (% style="width:902.294px" %)
942 942  |(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation**
... ... @@ -943,7 +943,7 @@
943 943  |(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %)
944 944  |(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %)
945 945  
946 -**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message.
913 +**ConstraintQueryType: **ConstraintQueryType defines the structure of a (% style="color:#e74c3c" %)constraint(%%) query message.
947 947  
948 948  Derivation:
949 949  
... ... @@ -951,9 +951,9 @@
951 951  ** ConstraintQueryType
952 952  
953 953  Content:
921 +Header, Query
954 954  
955 -* Header, Query
956 -* Element Documentation:
923 +Element Documentation:
957 957  
958 958  (% style="width:902.294px" %)
959 959  |(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation**
... ... @@ -968,9 +968,9 @@
968 968  ** TransformationSchemeQueryType
969 969  
970 970  Content:
938 +Header, Query
971 971  
972 -* Header, Query
973 -* Element Documentation:
940 +Element Documentation:
974 974  
975 975  (% style="width:833.294px" %)
976 976  |(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation**
... ... @@ -977,7 +977,7 @@
977 977  |(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %)
978 978  |(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %)
979 979  
980 -**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message.
947 +**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mappings scheme query message.
981 981  
982 982  Derivation:
983 983  
... ... @@ -985,9 +985,9 @@
985 985  ** VtlMappingSchemeQueryType
986 986  
987 987  Content:
955 +Header, Query
988 988  
989 -* Header, Query
990 -* Element Documentation:
957 +Element Documentation:
991 991  
992 992  (% style="width:843.294px" %)
993 993  |(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation**
... ... @@ -1002,9 +1002,9 @@
1002 1002  ** NamePersonalisationSchemeQueryType
1003 1003  
1004 1004  Content:
972 +Header, Query
1005 1005  
1006 -* Header, Query
1007 -* Element Documentation:
974 +Element Documentation:
1008 1008  
1009 1009  (% style="width:895.294px" %)
1010 1010  |(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation**
... ... @@ -1019,9 +1019,9 @@
1019 1019  ** RulesetSchemeQueryType
1020 1020  
1021 1021  Content:
989 +Header, Query
1022 1022  
1023 -* Header, Query
1024 -* Element Documentation:
991 +Element Documentation:
1025 1025  
1026 1026  (% style="width:886.294px" %)
1027 1027  |(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation**
... ... @@ -1036,9 +1036,9 @@
1036 1036  ** UserDefinedOperatorSchemeQueryType
1037 1037  
1038 1038  Content:
1006 +Header, Query
1039 1039  
1040 -* Header, Query
1041 -* Element Documentation:
1008 +Element Documentation:
1042 1042  
1043 1043  (% style="width:866.294px" %)
1044 1044  |(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation**
... ... @@ -1053,9 +1053,9 @@
1053 1053  ** CustomTypeSchemeQueryType
1054 1054  
1055 1055  Content:
1023 +Header, Query
1056 1056  
1057 -* Header, Query
1058 -* Element Documentation:
1025 +Element Documentation:
1059 1059  
1060 1060  (% style="width:828.294px" %)
1061 1061  |(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation**
... ... @@ -1065,18 +1065,17 @@
1065 1065  **ErrorType: **ErrorType describes the structure of an error response.
1066 1066  
1067 1067  Content:
1035 +ErrorMessage+
1068 1068  
1069 -* ErrorMessage+
1070 -* Element Documentation:
1037 +Element Documentation:
1071 1071  
1072 1072  (% style="width:899.294px" %)
1073 1073  |**Name**|**Type**|(% style="width:546px" %)**Documentation**
1074 -|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.
1041 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors.
1075 1075  
1076 1076  **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
1077 1077  
1078 1078  Content:
1079 -
1080 1080  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure*, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1081 1081  
1082 1082  Element Documentation:
... ... @@ -1089,17 +1089,17 @@
1089 1089  |Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message.
1090 1090  |Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message.
1091 1091  |com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1092 -|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.
1093 -|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1094 -|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).
1095 -|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set.
1058 +|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1059 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1060 +|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1061 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1096 1096  |Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data.
1097 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1098 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1099 -|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available.
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.
1100 1100  |Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data.
1101 1101  
1102 -**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages.
1068 +**StructureHeaderType: **StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages.
1103 1103  
1104 1104  Derivation:
1105 1105  
... ... @@ -1107,7 +1107,6 @@
1107 1107  ** StructureHeaderType
1108 1108  
1109 1109  Content:
1110 -
1111 1111  ID, Test, Prepared, Sender, Receiver*, com:Name*, Source*
1112 1112  
1113 1113  Element Documentation:
... ... @@ -1130,7 +1130,6 @@
1130 1130  ** GenericDataHeaderType
1131 1131  
1132 1132  Content:
1133 -
1134 1134  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1135 1135  
1136 1136  Element Documentation:
... ... @@ -1143,14 +1143,14 @@
1143 1143  |Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message.
1144 1144  |Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message.
1145 1145  |com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1146 -|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.
1147 -|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1148 -|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).
1149 -|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set.
1110 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1111 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1112 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1113 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1150 1150  |Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data.
1151 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1152 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1153 -|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1115 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1116 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1117 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1154 1154  |Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data.
1155 1155  
1156 1156  **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message.
... ... @@ -1162,7 +1162,6 @@
1162 1162  *** GenericTimeSeriesDataHeaderType
1163 1163  
1164 1164  Content:
1165 -
1166 1166  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1167 1167  
1168 1168  Element Documentation:
... ... @@ -1175,14 +1175,14 @@
1175 1175  |Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message.
1176 1176  |Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message.
1177 1177  |com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1178 -|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.
1179 -|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1180 -|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).
1181 -|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set.
1141 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1142 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1143 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1144 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1182 1182  |Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data.
1183 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1184 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1185 -|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1146 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1147 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1148 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1186 1186  |Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data.
1187 1187  
1188 1188  **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
... ... @@ -1193,7 +1193,6 @@
1193 1193  ** StructureSpecificDataHeaderType
1194 1194  
1195 1195  Content:
1196 -
1197 1197  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1198 1198  
1199 1199  Element Documentation:
... ... @@ -1206,14 +1206,14 @@
1206 1206  |Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message.
1207 1207  |Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message.
1208 1208  |com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1209 -|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.
1210 -|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1211 -|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).
1212 -|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set.
1171 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1172 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1173 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1174 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1213 1213  |Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data.
1214 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data).
1215 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data).
1216 -|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available.
1176 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1177 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1178 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1217 1217  |Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data.
1218 1218  
1219 1219  **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message.
... ... @@ -1225,7 +1225,6 @@
1225 1225  *** StructureSpecificTimeSeriesDataHeaderType
1226 1226  
1227 1227  Content:
1228 -
1229 1229  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source*
1230 1230  
1231 1231  Element Documentation:
... ... @@ -1238,17 +1238,17 @@
1238 1238  |Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message.
1239 1239  |Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message.
1240 1240  |com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1241 -|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.
1242 -|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1243 -|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).
1244 -|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set.
1202 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1203 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1204 +|DataSetAction|(% style="width:352px" %)com:ActionType|(% style="width:461px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1205 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1245 1245  |Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data.
1246 -|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).
1247 -|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).
1248 -|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.
1207 +|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1208 +|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
1209 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
1249 1249  |Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data.
1250 1250  
1251 -**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata.
1212 +**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
1252 1252  
1253 1253  Derivation:
1254 1254  
... ... @@ -1256,7 +1256,6 @@
1256 1256  ** GenericMetadataHeaderType
1257 1257  
1258 1258  Content:
1259 -
1260 1260  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1261 1261  
1262 1262  Element Documentation:
... ... @@ -1269,14 +1269,14 @@
1269 1269  |Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message.
1270 1270  |Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message.
1271 1271  |com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1272 -|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.
1273 -|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1274 -|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).
1275 -|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set.
1232 +|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly.
1233 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message.
1234 +|DataSetAction|com:ActionType|(% style="width:554px" %)DataSetAction [[code>>doc:sdmx:Glossary.Code.WebHome]] provides a [[code>>doc:sdmx:Glossary.Code.WebHome]] for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message).
1235 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
1276 1276  |Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data.
1277 1277  |Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data.
1278 1278  
1279 -**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages.
1239 +**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages.
1280 1280  
1281 1281  Derivation:
1282 1282  
... ... @@ -1284,7 +1284,6 @@
1284 1284  ** StructureSpecificMetadataHeaderType
1285 1285  
1286 1286  Content:
1287 -
1288 1288  ID, Test, Prepared, Sender, Receiver*, com:Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, Source*
1289 1289  
1290 1290  Element Documentation:
... ... @@ -1297,10 +1297,10 @@
1297 1297  |Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message.
1298 1298  |Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message.
1299 1299  |com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
1300 -|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.
1301 -|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message.
1302 -|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).
1303 -|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set.
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]].
1304 1304  |Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data.
1305 1305  |Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data.
1306 1306  
... ... @@ -1312,7 +1312,6 @@
1312 1312  ** BasicHeaderType
1313 1313  
1314 1314  Content:
1315 -
1316 1316  ID, Test, Prepared, Sender, Receiver
1317 1317  
1318 1318  Element Documentation:
... ... @@ -1332,21 +1332,20 @@
1332 1332  id
1333 1333  
1334 1334  Content:
1293 +com:Name*, (% style="color:#e74c3c" %)Contact(%%)*
1335 1335  
1336 -com:Name*, Contact*
1295 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1337 1337  
1338 -Attribute Documentation:
1297 +(% style="width:888.294px" %)
1298 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:569px" %)**Documentation**
1299 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:569px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
1339 1339  
1340 -(% style="width:739.294px" %)
1341 -|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation**
1342 -|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party.
1343 -
1344 1344  Element Documentation:
1345 1345  
1346 -(% style="width:751.294px" %)
1347 -|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation**
1348 -|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party.
1349 -|(% 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.
1303 +(% style="width:889.294px" %)
1304 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:568px" %)**Documentation**
1305 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:568px" %)Name is a human-readable name of the party.
1306 +|(% style="width:134px" %)(% style="color:#e74c3c" %)Contact|(% style="width:183px" %)ContactType|(% style="width:568px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.
1350 1350  
1351 1351  **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration.
1352 1352  
... ... @@ -1356,62 +1356,55 @@
1356 1356  ** SenderType
1357 1357  
1358 1358  Attributes:
1359 -
1360 1360  id
1361 1361  
1362 1362  Content:
1319 +com:Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone?
1363 1363  
1364 -com:Name*, Contact*, Timezone?
1321 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1365 1365  
1366 -Attribute Documentation:
1367 -
1368 1368  (% style="width:824.294px" %)
1369 1369  |(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation**
1370 -|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party.
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.
1371 1371  
1372 1372  Element Documentation:
1373 1373  
1374 -|**Name**|**Type**|**Documentation**
1375 -|com:Name|com:TextType|Name is a human-readable name of the party.
1376 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
1377 -|Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1329 +(% style="width:1016.29px" %)
1330 +|**Name**|**Type**|(% style="width:738px" %)**Documentation**
1331 +|com:Name|com:TextType|(% style="width:738px" %)Name is a human-readable name of the party.
1332 +|(%%)(% style="color:#e74c3c" %)Contact|ContactType|(% style="width:738px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.
1333 +|Timezone|com:TimezoneType|(% style="width:738px" %)Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
1378 1378  
1379 -**ContactType: **ContactType provides defines the contact information about a party.
1335 +**ContactType: **ContactType provides defines the (% style="color:#e74c3c" %)contact(%%) information about a party.
1380 1380  
1381 1381  Content:
1382 -
1383 1383  com:Name*, Department*, Role*, (Telephone | Fax | X400 | URI | Email)*
1384 1384  
1385 1385  Element Documentation:
1386 1386  
1387 -|**Name**|**Type**|**Documentation**
1388 -|com:Name|com:TextType|Name contains a human-readable name for the contact.
1389 -|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
1390 -|Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
1391 -|Telephone|xs:string|Telephone holds the telephone number for the contact person.
1392 -|Fax|xs:string|Fax holds the fax number for the contact person.
1393 -|X400|xs:string|X400 holds the X.400 address for the contact person.
1394 -|URI|xs:anyURI|URI holds an information URL for the contact person.
1395 -|Email|xs:string|Email holds the email address for the contact person.
1342 +(% style="width:1035.29px" %)
1343 +|**Name**|**Type**|(% style="width:623px" %)**Documentation**
1344 +|com:Name|com:TextType|(% style="width:623px" %)Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%).
1345 +|Department|com:TextType|(% style="width:623px" %)Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%) person works.
1346 +|Role|com:TextType|(% style="width:623px" %)Role is the responsibility of the (% style="color:#e74c3c" %)contact(%%) person with respect to the object for which this person is the (% style="color:#e74c3c" %)contact(%%).
1347 +|Telephone|xs:string|(% style="width:623px" %)Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the (% style="color:#e74c3c" %)contact(%%) person.
1348 +|Fax|xs:string|(% style="width:623px" %)Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%) person.
1349 +|X400|xs:string|(% style="width:623px" %)X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%) person.
1350 +|URI|xs:anyURI|(% style="width:623px" %)URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%) person.
1351 +|Email|xs:string|(% style="width:623px" %)Email holds the email address for the (% style="color:#e74c3c" %)contact(%%) person.
1396 1396  
1397 -1.
1398 -11.
1399 -111. Simple Types
1353 +=== 2.1.4 Simple Types ===
1400 1400  
1401 1401  **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message.
1402 1402  
1403 1403  Union of:
1404 -
1405 1405  xs:dateTime, xs:date.
1406 1406  
1407 -1.
1408 -11. Message Footer Namespace
1360 +== 2.2 Message Footer Namespace ==
1409 1409  
1410 1410  **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer**
1411 1411  
1412 -1.
1413 -11.
1414 -111. Summary
1364 +=== 2.2.1 Summary ===
1415 1415  
1416 1416  Referenced Namespaces:
1417 1417  
... ... @@ -1420,52 +1420,45 @@
1420 1420  |http:~/~/www.w3.org/2001/XMLSchema|xs
1421 1421  
1422 1422  Contents:
1423 -
1424 1424  1 Global Element
1425 1425  2 Complex Types
1426 1426  1 Simple Type
1427 1427  
1428 -1.
1429 -11.
1430 -111. Global Elements
1377 +=== 2.2.2 Global Elements ===
1431 1431  
1432 1432  **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message.
1433 1433  
1434 -1.
1435 -11.
1436 -111. Complex Types
1381 +=== 2.2.3 Complex Types ===
1437 1437  
1438 1438  **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.
1439 1439  
1440 1440  Content:
1441 -
1442 1442  Message+
1443 1443  
1444 1444  Element Documentation:
1445 1445  
1446 -|**Name**|**Type**|**Documentation**
1447 -|Message|FooterMessageType|Message contains a single error, information, or warning message. A code is provided along with an optional severity. The text of the message can be expressed in multiple languages.
1390 +(% style="width:1112.29px" %)
1391 +|**Name**|**Type**|(% style="width:782px" %)**Documentation**
1392 +|Message|FooterMessageType|(% style="width:782px" %)Message contains a single error, information, or warning message. A [[code>>doc:sdmx:Glossary.Code.WebHome]] is provided along with an optional severity. The text of the message can be expressed in multiple languages.
1448 1448  
1449 -**FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity code of Error, Information, or Warning added to it.
1394 +**FooterMessageType: **FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity [[code>>doc:sdmx:Glossary.Code.WebHome]] of Error, Information, or Warning added to it.
1450 1450  
1451 1451  Derivation:
1452 1452  
1453 -com:StatusMessageType (restriction)
1454 -[[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1455 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
1398 +* com:StatusMessageType (restriction)
1399 +** com:CodedStatusMessageType (extension)
1400 +*** FooterMessageType
1456 1456  
1457 1457  Attributes:
1403 +[[code>>doc:sdmx:Glossary.Code.WebHome]], severity?
1458 1458  
1459 -code, severity?
1460 -
1461 1461  Content:
1462 -
1463 1463  com:Text+
1464 1464  
1465 -Attribute Documentation:
1408 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
1466 1466  
1467 1467  |**Name**|**Type**|**Documentation**
1468 -|code|xs:string|The code attribute holds an optional code identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
1411 +|[[code>>doc:sdmx:Glossary.Code.WebHome]]|xs:string|The [[code>>doc:sdmx:Glossary.Code.WebHome]] [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds an optional [[code>>doc:sdmx:Glossary.Code.WebHome]] identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
1469 1469  |severity|SeverityCodeType|
1470 1470  
1471 1471  Element Documentation:
... ... @@ -1473,9 +1473,7 @@
1473 1473  |**Name**|**Type**|**Documentation**
1474 1474  |com:Text|com:TextType|Text contains the text of the message, in parallel language values.
1475 1475  
1476 -1.
1477 -11.
1478 -111. Simple Types
1419 +=== 2.2.4 Simple Types ===
1479 1479  
1480 1480  **SeverityCodeType:**
1481 1481  
... ... @@ -1486,19 +1486,4 @@
1486 1486  |**Value**|**Documentation**
1487 1487  |Error|Error indicates the status message coresponds to an error.
1488 1488  |Warning|Warning indicates that the status message corresponds to a warning.
1489 -|Information|Information indicates that the status message corresponds to an informational message.
1490 -
1491 -
1492 -
1493 -
1494 -
1495 -
1496 -
1497 -
1498 -
1499 -
1500 -
1501 -
1502 -
1503 -
1504 -
1430 +|Information|Information indicates that the status message corresponds to an informational message.