Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Tags
-
... ... @@ -1,1 +1,0 @@ 1 -Attribute|Category scheme|Code|Code list|Concept scheme|Contact phone number|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchical code list|Metadata set|Metadata structure definition|Metadataflow|Notification|Provision agreement|Reference metadata|Reference period|Reporting taxonomy|SDMX Registry|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Structure set|Subscription|Time period|Validation and transformation language - Content
-
... ... @@ -8,7 +8,7 @@ 8 8 9 9 **~1. Problem** 10 10 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.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. 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>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in[[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].19 +At the core of the SDMX XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in SDMX. 20 20 21 -There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary.Statisticaldata 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.21 +There are two namespaces associated with the messages. The main namespace schema which defines every message in SDMX is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted. 22 22 23 -In general, every message in [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]]follows common format of:23 +In general, every message in SDMX follows common format of: 24 24 25 25 * Header 26 26 * Payload (0..n) ... ... @@ -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>>doc:sdmx:Glossary.Data structure definition.WebHome]]45 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)dsd 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>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]48 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|(% style="width:173px" %)msd 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>>doc:sdmx:Glossary.Structuralmetadata.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.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. 63 63 64 -**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. [[Data sets>>doc:sdmx:Glossary.Dataset.WebHome]]in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation[[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]).64 +**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. Data sets in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation dimension). 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>>doc:sdmx:Glossary.Dimension.WebHome]]must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation[[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.66 +**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 67 67 68 -**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Datastructure 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.Datastructure definition.WebHome]]and the orientation (i.e. the observation[[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data.68 +**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to data structure definition. The payload of this message (i.e. the data sets) will be based on XML schemas which are specific to the data structure definition and the orientation (i.e. the observation dimension) of the data. 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>>doc:sdmx:Glossary.Dimension.WebHome]]must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation[[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.70 +**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 71 71 72 -**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].72 +**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition. 73 73 74 -**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the [[metadata structure definitions>>doc:sdmx:Glossary.Metadatastructure 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.Metadataset.WebHome]]provided will be based on a metadata structure specific schema.74 +**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the metadata structure definitions which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each metadata set provided will be based on a metadata structure specific schema. 75 75 76 -**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMXRegistry.WebHome]]Services.76 +**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry 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>>doc:sdmx:Glossary.Dataset.WebHome]] or[[metadata set>>doc:sdmx:Glossary.Metadataset.WebHome]].The[[data source>>doc:sdmx:Glossary.Datasource.WebHome]]to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.78 +**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 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>>doc:sdmx:Glossary.Dataset.WebHome]]and[[metadata sets>>doc:sdmx:Glossary.Metadataset.WebHome]].It specifies whether the result set should include[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]],[[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing(% style="color:#e74c3c" %)constraints(%%)including[[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys.82 +**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 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, (% 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.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. 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>>doc:sdmx:Glossary.Subscription.WebHome]]request. It contains information which describes the success or failure of each[[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]request, providing any error messages in the event of failure. If successful, it returns the registry URN of the[[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID.92 +**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 93 93 94 -**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]]of a given organisation.94 +**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 95 95 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.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. 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>>doc:sdmx:Glossary.Subscription.WebHome]]that triggered the[[notification>>doc:sdmx:Glossary.Notification.WebHome]]are always sent. Optionally, the details of the changed object may also be provided.98 +**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 99 99 100 -**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for structure specific data.100 +**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data. 101 101 102 -**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner.102 +**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query SDMX compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner. 103 103 104 -**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.104 +**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 105 105 106 -**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data.106 +**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 107 107 108 -**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for generic format[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].108 +**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata. 109 109 110 -**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].110 +**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata. 111 111 112 -**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for data structure specific schemas for the purpose of validating structured data.112 +**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query SDMX compliant databases or web services for data structure specific schemas for the purpose of validating structured data. 113 113 114 -**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata.114 +**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query SDMX compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata. 115 115 116 -**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency).116 +**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query SDMX compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency). 117 117 118 -**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for dataflows.118 +**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows. 119 119 120 -**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for[[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]].120 +**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows. 121 121 122 -**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for data structures definitions.122 +**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions. 123 123 124 -**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for[[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]].124 +**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions. 125 125 126 -**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for[[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]].126 +**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes. 127 127 128 -**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for[[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]].128 +**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes. 129 129 130 -**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for codelists.130 +**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists. 131 131 132 -**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for hierarchical codelists.132 +**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists. 133 133 134 -**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for organisation schemes.134 +**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes. 135 135 136 -**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for[[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]].136 +**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies. 137 137 138 -**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for structure sets.138 +**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets. 139 139 140 -**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for processes.140 +**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes. 141 141 142 -**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for categorisations.142 +**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations. 143 143 144 -**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for provision agreements.144 +**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements. 145 145 146 -**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for(% style="color:#e74c3c" %)constraints(%%).146 +**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints. 147 147 148 -**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for transformation schemes.148 +**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes. 149 149 150 -**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for[[VTL>>doc:sdmx:Glossary.Validationand transformation language.WebHome]] mapping schemes.150 +**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes. 151 151 152 -**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for name personalisation schemes.152 +**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes. 153 153 154 -**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for ruleset schemes.154 +**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes. 155 155 156 -**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for user defined schemes.156 +**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes. 157 157 158 -**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statisticaldata and metadata exchange.WebHome]] compliant databases or web services for custom type schemes.158 +**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes. 159 159 160 160 **Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages. 161 161 ... ... @@ -177,8 +177,8 @@ 177 177 178 178 Derivation: 179 179 180 - *//MessageType// (restriction)181 - **StructureType180 +//MessageType// (restriction) 181 + StructureType 182 182 183 183 Content: 184 184 ... ... @@ -196,12 +196,12 @@ 196 196 197 197 Derivation: 198 198 199 - *//MessageType// (restriction)200 - **GenericDataType199 +//MessageType// (restriction) 200 + GenericDataType 201 201 202 202 Content: 203 203 204 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?204 +Header, DataSet*, ftr:Footer? 205 205 206 206 Element Documentation: 207 207 ... ... @@ -208,7 +208,7 @@ 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>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %)211 +|DataSet|(% 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. ... ... @@ -221,7 +221,7 @@ 221 221 222 222 Content: 223 223 224 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?224 +Header, DataSet*, ftr:Footer? 225 225 226 226 Element Documentation: 227 227 ... ... @@ -228,10 +228,10 @@ 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>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %)231 +|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %) 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>>doc:sdmx:Glossary.Dataset.WebHome]]payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.234 +**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 235 235 236 236 Derivation: 237 237 ... ... @@ -240,7 +240,7 @@ 240 240 241 241 Content: 242 242 243 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?243 +Header, DataSet*, ftr:Footer? 244 244 245 245 Element Documentation: 246 246 ... ... @@ -247,7 +247,7 @@ 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>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:247px" %)//[[dsd>>doc:sdmx:Glossary.Datastructure definition.WebHome]]:DataSetType//|(% style="width:420px" %)250 +|DataSet|(% style="width:247px" %)//dsd: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. ... ... @@ -260,7 +260,7 @@ 260 260 261 261 Content: 262 262 263 -Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer?263 +Header, DataSet*, ftr:Footer? 264 264 265 265 Element Documentation: 266 266 ... ... @@ -267,7 +267,7 @@ 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>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:256px" %)//[[dsd>>doc:sdmx:Glossary.Datastructure definition.WebHome]]:TimeSeriesDataSetTyp e//|(% style="width:434px" %)270 +|DataSet|(% style="width:256px" %)//dsd: 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. ... ... @@ -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>>doc:sdmx:Glossary.Metadataset.WebHome]]payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.292 +**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 293 293 294 294 Derivation: 295 295 ... ... @@ -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>>doc:sdmx:Glossary.Metadatastructure definition.WebHome]]:MetadataSetType//|(% style="width:428px" %)308 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd: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. ... ... @@ -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>>doc:sdmx:Glossary.Dataset.WebHome]] or[[metadata set>>doc:sdmx:Glossary.Metadataset.WebHome]].The[[data source>>doc:sdmx:Glossary.Datasource.WebHome]]to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.327 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 328 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>>doc:sdmx:Glossary.Dataset.WebHome]]and[[metadata sets>>doc:sdmx:Glossary.Metadataset.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.329 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 330 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, (% 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.331 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 332 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>>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.335 -|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.336 -|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.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>>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.334 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 335 +|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 336 +|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 337 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 338 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. ... ... @@ -347,14 +347,13 @@ 347 347 348 348 Content: 349 349 350 -Header, SubmitRegistrationsRequest 350 +* Header, SubmitRegistrationsRequest 351 +* Element Documentation: 351 351 352 -Element Documentation: 353 - 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>>doc:sdmx:Glossary.Dataset.WebHome]] or[[metadata set>>doc:sdmx:Glossary.Metadataset.WebHome]].The[[data source>>doc:sdmx:Glossary.Datasource.WebHome]]to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.356 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 358 358 359 359 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 360 360 ... ... @@ -366,10 +366,9 @@ 366 366 367 367 Content: 368 368 369 -Header, SubmitRegistrationsResponse, ftr:Footer? 368 +* Header, SubmitRegistrationsResponse, ftr:Footer? 369 +* Element Documentation: 370 370 371 -Element Documentation: 372 - 373 373 (% style="width:847.294px" %) 374 374 |**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 375 375 |Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) ... ... @@ -386,14 +386,13 @@ 386 386 387 387 Content: 388 388 389 -Header, QueryRegistrationRequest 387 +* Header, QueryRegistrationRequest 388 +* Element Documentation: 390 390 391 -Element Documentation: 392 - 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>>doc:sdmx:Glossary.Dataset.WebHome]]and[[metadata sets>>doc:sdmx:Glossary.Metadataset.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.393 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 397 397 398 398 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 399 399 ... ... @@ -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, (% 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.432 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 436 436 437 437 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document. 438 438 ... ... @@ -444,10 +444,9 @@ 444 444 445 445 Content: 446 446 447 -Header, SubmitStructureResponse, ftr:Footer? 444 +* Header, SubmitStructureResponse, ftr:Footer? 445 +* Element Documentation: 448 448 449 -Element Documentation: 450 - 451 451 (% style="width:835.294px" %) 452 452 |**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 453 453 |Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) ... ... @@ -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>>doc:sdmx:Glossary.Subscription.WebHome]]request document.453 +**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document. 458 458 459 459 Derivation: 460 460 ... ... @@ -464,16 +464,15 @@ 464 464 465 465 Content: 466 466 467 -Header, SubmitSubscriptionsRequest 463 +* Header, SubmitSubscriptionsRequest 464 +* Element Documentation: 468 468 469 -Element Documentation: 470 - 471 471 (% style="width:832.294px" %) 472 472 |**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 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>>doc:sdmx:Glossary.Subscription.WebHome]]response document.471 +**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document. 477 477 478 478 Derivation: 479 479 ... ... @@ -483,17 +483,16 @@ 483 483 484 484 Content: 485 485 486 -Header, SubmitSubscriptionsResponse, ftr:Footer? 481 +* Header, SubmitSubscriptionsResponse, ftr:Footer? 482 +* Element Documentation: 487 487 488 -Element Documentation: 489 - 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>>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.487 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 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>>doc:sdmx:Glossary.Subscription.WebHome]]request document.490 +**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document. 497 497 498 498 Derivation: 499 499 ... ... @@ -503,16 +503,15 @@ 503 503 504 504 Content: 505 505 506 -Header, QuerySubscriptionRequest 500 +* Header, QuerySubscriptionRequest 501 +* Element Documentation: 507 507 508 -Element Documentation: 509 - 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>>doc:sdmx:Glossary.Subscription.WebHome]]of a given organisation.506 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 514 514 515 -**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]]response document.508 +**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document. 516 516 517 517 Derivation: 518 518 ... ... @@ -522,17 +522,16 @@ 522 522 523 523 Content: 524 524 525 -Header, QuerySubscriptionResponse, ftr:Footer? 518 +* Header, QuerySubscriptionResponse, ftr:Footer? 519 +* Element Documentation: 526 526 527 -Element Documentation: 528 - 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>>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.524 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 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>>doc:sdmx:Glossary.Notification.WebHome]]document.527 +**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document. 536 536 537 537 Derivation: 538 538 ... ... @@ -542,14 +542,13 @@ 542 542 543 543 Content: 544 544 545 -Header, NotifyRegistryEvent 537 +* Header, NotifyRegistryEvent 538 +* Element Documentation: 546 546 547 -Element Documentation: 548 - 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>>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.543 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 553 553 554 554 **DataQueryType: **DataQueryType defines the structure of a data query message. 555 555 ... ... @@ -560,10 +560,9 @@ 560 560 561 561 Content: 562 562 563 -Header, Query 554 +* Header, Query 555 +* Element Documentation: 564 564 565 -Element Documentation: 566 - 567 567 (% style="width:839.294px" %) 568 568 |(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation** 569 569 |(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %) ... ... @@ -579,10 +579,9 @@ 579 579 580 580 Content: 581 581 582 -Header, Query 572 +* Header, Query 573 +* Element Documentation: 583 583 584 -Element Documentation: 585 - 586 586 (% style="width:833.294px" %) 587 587 |(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 588 588 |(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) ... ... @@ -599,10 +599,9 @@ 599 599 600 600 Content: 601 601 602 -Header, Query 591 +* Header, Query 592 +* Element Documentation: 603 603 604 -Element Documentation: 605 - 606 606 (% style="width:909.294px" %) 607 607 |(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 608 608 |(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) ... ... @@ -618,16 +618,15 @@ 618 618 619 619 Content: 620 620 621 -Header, Query 609 +* Header, Query 610 +* Element Documentation: 622 622 623 -Element Documentation: 624 - 625 625 (% style="width:903.294px" %) 626 626 |(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 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>>doc:sdmx:Glossary.Referencemetadata.WebHome]]query message.617 +**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message. 631 631 632 632 Derivation: 633 633 ... ... @@ -636,10 +636,9 @@ 636 636 637 637 Content: 638 638 639 -Header, Query 626 +* Header, Query 627 +* Element Documentation: 640 640 641 -Element Documentation: 642 - 643 643 (% style="width:858.294px" %) 644 644 |(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 645 645 |(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) ... ... @@ -654,10 +654,9 @@ 654 654 655 655 Content: 656 656 657 -Header, Query 643 +* Header, Query 644 +* Element Documentation: 658 658 659 -Element Documentation: 660 - 661 661 (% style="width:895.294px" %) 662 662 |(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 663 663 |(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) ... ... @@ -672,10 +672,9 @@ 672 672 673 673 Content: 674 674 675 -Header, Query 660 +* Header, Query 661 +* Element Documentation: 676 676 677 -Element Documentation: 678 - 679 679 (% style="width:897.294px" %) 680 680 |(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 681 681 |(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) ... ... @@ -690,16 +690,15 @@ 690 690 691 691 Content: 692 692 693 -Header, Query 677 +* Header, Query 678 +* Element Documentation: 694 694 695 -Element Documentation: 696 - 697 697 (% style="width:886.294px" %) 698 698 |(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 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>>doc:sdmx:Glossary.Dataflow.WebHome]]query message.685 +**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message. 703 703 704 704 Derivation: 705 705 ... ... @@ -708,16 +708,15 @@ 708 708 709 709 Content: 710 710 711 -Header, Query 694 +* Header, Query 695 +* Element Documentation: 712 712 713 -Element Documentation: 714 - 715 715 (% style="width:888.294px" %) 716 716 |(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 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>>doc:sdmx:Glossary.Metadataflow.WebHome]]query message.702 +**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message. 721 721 722 722 Derivation: 723 723 ... ... @@ -726,10 +726,9 @@ 726 726 727 727 Content: 728 728 729 -Header, Query 711 +* Header, Query 712 +* Element Documentation: 730 730 731 -Element Documentation: 732 - 733 733 (% style="width:886.294px" %) 734 734 |(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 735 735 |(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) ... ... @@ -744,10 +744,9 @@ 744 744 745 745 Content: 746 746 747 -Header, Query 728 +* Header, Query 729 +* Element Documentation: 748 748 749 -Element Documentation: 750 - 751 751 (% style="width:901.294px" %) 752 752 |(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 753 753 |(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) ... ... @@ -762,16 +762,15 @@ 762 762 763 763 Content: 764 764 765 -Header, Query 745 +* Header, Query 746 +* Element Documentation: 766 766 767 -Element Documentation: 768 - 769 769 (% style="width:904.294px" %) 770 770 |(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 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>>doc:sdmx:Glossary.Categoryscheme.WebHome]]query message.753 +**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message. 775 775 776 776 Derivation: 777 777 ... ... @@ -780,16 +780,15 @@ 780 780 781 781 Content: 782 782 783 -Header, Query 762 +* Header, Query 763 +* Element Documentation: 784 784 785 -Element Documentation: 786 - 787 787 (% style="width:915.294px" %) 788 788 |(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 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>>doc:sdmx:Glossary.Conceptscheme.WebHome]]query message.770 +**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message. 793 793 794 794 Derivation: 795 795 ... ... @@ -798,16 +798,15 @@ 798 798 799 799 Content: 800 800 801 -Header, Query 779 +* Header, Query 780 +* Element Documentation: 802 802 803 -Element Documentation: 804 - 805 805 (% style="width:895.294px" %) 806 806 |(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 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>>doc:sdmx:Glossary.Codelist.WebHome]]query message.787 +**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message. 811 811 812 812 Derivation: 813 813 ... ... @@ -816,16 +816,15 @@ 816 816 817 817 Content: 818 818 819 -Header, Query 796 +* Header, Query 797 +* Element Documentation: 820 820 821 -Element Documentation: 822 - 823 823 (% style="width:911.294px" %) 824 824 |(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation** 825 825 |(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %) 826 826 |(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %) 827 827 828 -**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical [[codelist>>doc:sdmx:Glossary.Codelist.WebHome]]query message.804 +**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message. 829 829 830 830 Derivation: 831 831 ... ... @@ -834,10 +834,9 @@ 834 834 835 835 Content: 836 836 837 -Header, Query 813 +* Header, Query 814 +* Element Documentation: 838 838 839 -Element Documentation: 840 - 841 841 (% style="width:906.294px" %) 842 842 |(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation** 843 843 |(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %) ... ... @@ -852,10 +852,9 @@ 852 852 853 853 Content: 854 854 855 -Header, Query 830 +* Header, Query 831 +* Element Documentation: 856 856 857 -Element Documentation: 858 - 859 859 (% style="width:891.294px" %) 860 860 |(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation** 861 861 |(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %) ... ... @@ -870,16 +870,15 @@ 870 870 871 871 Content: 872 872 873 -Header, Query 847 +* Header, Query 848 +* Element Documentation: 874 874 875 -Element Documentation: 876 - 877 877 (% style="width:916.294px" %) 878 878 |(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation** 879 879 |(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %) 880 880 |(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %) 881 881 882 -**StructureSetQueryType: **StructureSetQueryType defines the structure of a [[structure set>>doc:sdmx:Glossary.Structureset.WebHome]]query message.855 +**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message. 883 883 884 884 Derivation: 885 885 ... ... @@ -888,10 +888,9 @@ 888 888 889 889 Content: 890 890 891 -Header, Query 864 +* Header, Query 865 +* Element Documentation: 892 892 893 -Element Documentation: 894 - 895 895 (% style="width:896.294px" %) 896 896 |(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation** 897 897 |(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %) ... ... @@ -906,10 +906,9 @@ 906 906 907 907 Content: 908 908 909 -Header, Query 881 +* Header, Query 882 +* Element Documentation: 910 910 911 -Element Documentation: 912 - 913 913 (% style="width:907.294px" %) 914 914 |(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation** 915 915 |(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %) ... ... @@ -924,16 +924,15 @@ 924 924 925 925 Content: 926 926 927 -Header, Query 898 +* Header, Query 899 +* Element Documentation: 928 928 929 -Element Documentation: 930 - 931 931 (% style="width:897.294px" %) 932 932 |(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation** 933 933 |(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %) 934 934 |(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %) 935 935 936 -**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a [[provision agreement>>doc:sdmx:Glossary.Provisionagreement.WebHome]]query message.906 +**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message. 937 937 938 938 Derivation: 939 939 ... ... @@ -942,16 +942,15 @@ 942 942 943 943 Content: 944 944 945 -Header, Query 915 +* Header, Query 916 +* Element Documentation: 946 946 947 -Element Documentation: 948 - 949 949 (% style="width:902.294px" %) 950 950 |(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation** 951 951 |(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %) 952 952 |(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %) 953 953 954 -**ConstraintQueryType: **ConstraintQueryType defines the structure of a (% style="color:#e74c3c" %)constraint(%%)query message.923 +**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message. 955 955 956 956 Derivation: 957 957 ... ... @@ -960,10 +960,9 @@ 960 960 961 961 Content: 962 962 963 -Header, Query 932 +* Header, Query 933 +* Element Documentation: 964 964 965 -Element Documentation: 966 - 967 967 (% style="width:902.294px" %) 968 968 |(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation** 969 969 |(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %) ... ... @@ -978,16 +978,15 @@ 978 978 979 979 Content: 980 980 981 -Header, Query 949 +* Header, Query 950 +* Element Documentation: 982 982 983 -Element Documentation: 984 - 985 985 (% style="width:833.294px" %) 986 986 |(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation** 987 987 |(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %) 988 988 |(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %) 989 989 990 -**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a [[VTL>>doc:sdmx:Glossary.Validationand transformation language.WebHome]] mappings scheme query message.957 +**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message. 991 991 992 992 Derivation: 993 993 ... ... @@ -996,10 +996,9 @@ 996 996 997 997 Content: 998 998 999 -Header, Query 966 +* Header, Query 967 +* Element Documentation: 1000 1000 1001 -Element Documentation: 1002 - 1003 1003 (% style="width:843.294px" %) 1004 1004 |(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation** 1005 1005 |(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %) ... ... @@ -1014,10 +1014,9 @@ 1014 1014 1015 1015 Content: 1016 1016 1017 -Header, Query 983 +* Header, Query 984 +* Element Documentation: 1018 1018 1019 -Element Documentation: 1020 - 1021 1021 (% style="width:895.294px" %) 1022 1022 |(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation** 1023 1023 |(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %) ... ... @@ -1032,10 +1032,9 @@ 1032 1032 1033 1033 Content: 1034 1034 1035 -Header, Query 1000 +* Header, Query 1001 +* Element Documentation: 1036 1036 1037 -Element Documentation: 1038 - 1039 1039 (% style="width:886.294px" %) 1040 1040 |(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation** 1041 1041 |(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %) ... ... @@ -1050,10 +1050,9 @@ 1050 1050 1051 1051 Content: 1052 1052 1053 -Header, Query 1017 +* Header, Query 1018 +* Element Documentation: 1054 1054 1055 -Element Documentation: 1056 - 1057 1057 (% style="width:866.294px" %) 1058 1058 |(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation** 1059 1059 |(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %) ... ... @@ -1068,10 +1068,9 @@ 1068 1068 1069 1069 Content: 1070 1070 1071 -Header, Query 1034 +* Header, Query 1035 +* Element Documentation: 1072 1072 1073 -Element Documentation: 1074 - 1075 1075 (% style="width:828.294px" %) 1076 1076 |(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation** 1077 1077 |(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %) ... ... @@ -1081,13 +1081,12 @@ 1081 1081 1082 1082 Content: 1083 1083 1084 -ErrorMessage+ 1046 +* ErrorMessage+ 1047 +* Element Documentation: 1085 1085 1086 -Element Documentation: 1087 - 1088 1088 (% style="width:899.294px" %) 1089 1089 |**Name**|**Type**|(% style="width:546px" %)**Documentation** 1090 -|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]]in order to distinguish message for unique errors.1051 +|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. 1091 1091 1092 1092 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this 1093 1093 ... ... @@ -1105,17 +1105,17 @@ 1105 1105 |Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message. 1106 1106 |Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message. 1107 1107 |com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1108 -|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1109 -|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1110 -|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).1111 -|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1069 +|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. 1070 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1071 +|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). 1072 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set. 1112 1112 |Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data. 1113 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1114 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1115 -|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]] before which the data included in this message is not available.1074 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1075 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1076 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1116 1116 |Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data. 1117 1117 1118 -**StructureHeaderType: **StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structuralmetadata.WebHome]] messages.1079 +**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages. 1119 1119 1120 1120 Derivation: 1121 1121 ... ... @@ -1159,14 +1159,14 @@ 1159 1159 |Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1160 1160 |Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1161 1161 |com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1162 -|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1163 -|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1164 -|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).1165 -|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1123 +|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. 1124 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1125 +|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). 1126 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set. 1166 1166 |Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data. 1167 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1168 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1169 -|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]] before which the data included in this message is not available.1128 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1129 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1130 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1170 1170 |Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1171 1171 1172 1172 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. ... ... @@ -1191,14 +1191,14 @@ 1191 1191 |Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1192 1192 |Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1193 1193 |com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1194 -|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1195 -|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1196 -|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).1197 -|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1155 +|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. 1156 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1157 +|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). 1158 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set. 1198 1198 |Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data. 1199 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1200 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1201 -|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]] before which the data included in this message is not available.1160 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1161 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1162 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1202 1202 |Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1203 1203 1204 1204 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message. ... ... @@ -1222,14 +1222,14 @@ 1222 1222 |Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1223 1223 |Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1224 1224 |com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1225 -|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1226 -|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1227 -|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).1228 -|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1186 +|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. 1187 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1188 +|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). 1189 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set. 1229 1229 |Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data. 1230 -|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1231 -|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1232 -|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]] before which the data included in this message is not available.1191 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1192 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1193 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1233 1233 |Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1234 1234 1235 1235 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. ... ... @@ -1254,17 +1254,17 @@ 1254 1254 |Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message. 1255 1255 |Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message. 1256 1256 |com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1257 -|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1258 -|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1259 -|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).1260 -|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1218 +|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. 1219 +|DataProvider|(% style="width:352px" %)com: DataProviderReferenceType|(% style="width:461px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1220 +|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). 1221 +|DataSetID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)DataSetID provides an identifier for a contained data set. 1261 1261 |Extracted|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)Extracted is a time-stamp from the system rendering the data. 1262 -|ReportingBegin|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1263 -|ReportingEnd|(% style="width:352px" %)com: ObservationalTimePeriodType|(% style="width:461px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]]covered by the message (in the case of data).1264 -|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Timeperiod.WebHome]] before which the data included in this message is not available.1223 +|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). 1224 +|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). 1225 +|EmbargoDate|(% style="width:352px" %)xs:dateTime|(% style="width:461px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1265 1265 |Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data. 1266 1266 1267 -**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].1228 +**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata. 1268 1268 1269 1269 Derivation: 1270 1270 ... ... @@ -1285,14 +1285,14 @@ 1285 1285 |Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message. 1286 1286 |Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message. 1287 1287 |com:Name|com:TextType|(% style="width:554px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1288 -|Structure|com: GenericMetadataStructureType|(% style="width:554px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1289 -|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1290 -|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).1291 -|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1249 +|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. 1250 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1251 +|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). 1252 +|DataSetID|com:IDType|(% style="width:554px" %)DataSetID provides an identifier for a contained data set. 1292 1292 |Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data. 1293 1293 |Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data. 1294 1294 1295 -**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for [[metadata structure definition>>doc:sdmx:Glossary.Metadatastructure definition.WebHome]] specific[[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] messages.1256 +**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages. 1296 1296 1297 1297 Derivation: 1298 1298 ... ... @@ -1313,10 +1313,10 @@ 1313 1313 |Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message. 1314 1314 |Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message. 1315 1315 |com:Name|com:TextType|(% style="width:557px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1316 -|Structure|com: StructureSpecificMetadataStructureType|(% style="width:557px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.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.Metadataset.WebHome]]will require this reference explicitly.1317 -|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/ [[reference metadata>>doc:sdmx:Glossary.Referencemetadata.WebHome]] message.1318 -|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).1319 -|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].1277 +|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. 1278 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1279 +|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). 1280 +|DataSetID|com:IDType|(% style="width:557px" %)DataSetID provides an identifier for a contained data set. 1320 1320 |Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data. 1321 1321 |Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data. 1322 1322 ... ... @@ -1349,13 +1349,13 @@ 1349 1349 1350 1350 Content: 1351 1351 1352 -com:Name*, (% style="color:#e74c3c" %)Contact(%%)*1313 +com:Name*, Contact* 1353 1353 1354 - [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]Documentation:1315 +Attribute Documentation: 1355 1355 1356 1356 (% style="width:739.294px" %) 1357 1357 |(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation** 1358 -|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]]holds the identification of the party.1319 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id attribute holds the identification of the party. 1359 1359 1360 1360 Element Documentation: 1361 1361 ... ... @@ -1362,7 +1362,7 @@ 1362 1362 (% style="width:751.294px" %) 1363 1363 |(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation** 1364 1364 |(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party. 1365 -|(% style="width:134px" %) (% style="color:#e74c3c" %)Contact|(% style="width:183px" %)ContactType|(% style="width:431px" %)(% style="color:#e74c3c" %)Contact(%%)provides(% style="color:#e74c3c" %)contact(%%)information for the party in regard to the transmission of the message.1326 +|(% 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. 1366 1366 1367 1367 **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration. 1368 1368 ... ... @@ -1377,22 +1377,22 @@ 1377 1377 1378 1378 Content: 1379 1379 1380 -com:Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone?1341 +com:Name*, Contact*, Timezone? 1381 1381 1382 - [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]Documentation:1343 +Attribute Documentation: 1383 1383 1384 1384 (% style="width:824.294px" %) 1385 1385 |(% style="width:177px" %)**Name**|(% style="width:241px" %)**Type**|(% style="width:403px" %)**Documentation** 1386 -|(% 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.1347 +|(% style="width:177px" %)id|(% style="width:241px" %)com:IDType|(% style="width:403px" %)The id attribute holds the identification of the party. 1387 1387 1388 1388 Element Documentation: 1389 1389 1390 1390 |**Name**|**Type**|**Documentation** 1391 1391 |com:Name|com:TextType|Name is a human-readable name of the party. 1392 -| (%%)(% style="color:#e74c3c" %)Contact|ContactType|(%%)(% style="color:#e74c3c" %)Contact(%%)provides(% style="color:#e74c3c" %)contact(%%)information for the party in regard to the transmission of the message.1353 +|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message. 1393 1393 |Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time". 1394 1394 1395 -**ContactType: **ContactType provides defines the (% style="color:#e74c3c" %)contact(%%)information about a party.1356 +**ContactType: **ContactType provides defines the contact information about a party. 1396 1396 1397 1397 Content: 1398 1398 ... ... @@ -1401,16 +1401,18 @@ 1401 1401 Element Documentation: 1402 1402 1403 1403 |**Name**|**Type**|**Documentation** 1404 -|com:Name|com:TextType|Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%).1405 -|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%)person works.1406 -|Role|com:TextType|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(%%).1407 -|Telephone|xs:string|Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contactphone number.WebHome]]for the(% style="color:#e74c3c" %)contact(%%)person.1408 -|Fax|xs:string|Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%)person.1409 -|X400|xs:string|X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%)person.1410 -|URI|xs:anyURI|URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%)person.1411 -|Email|xs:string|Email holds the email address for the (% style="color:#e74c3c" %)contact(%%)person.1365 +|com:Name|com:TextType|Name contains a human-readable name for the contact. 1366 +|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works. 1367 +|Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact. 1368 +|Telephone|xs:string|Telephone holds the telephone number for the contact person. 1369 +|Fax|xs:string|Fax holds the fax number for the contact person. 1370 +|X400|xs:string|X400 holds the X.400 address for the contact person. 1371 +|URI|xs:anyURI|URI holds an information URL for the contact person. 1372 +|Email|xs:string|Email holds the email address for the contact person. 1412 1412 1413 -=== 2.1.4 Simple Types === 1374 +1. 1375 +11. 1376 +111. Simple Types 1414 1414 1415 1415 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. 1416 1416 ... ... @@ -1418,11 +1418,14 @@ 1418 1418 1419 1419 xs:dateTime, xs:date. 1420 1420 1421 -== 2.2 Message Footer Namespace == 1384 +1. 1385 +11. Message Footer Namespace 1422 1422 1423 1423 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1424 1424 1425 -=== 2.2.1 Summary === 1389 +1. 1390 +11. 1391 +111. Summary 1426 1426 1427 1427 Referenced Namespaces: 1428 1428 ... ... @@ -1436,11 +1436,15 @@ 1436 1436 2 Complex Types 1437 1437 1 Simple Type 1438 1438 1439 -=== 2.2.2 Global Elements === 1405 +1. 1406 +11. 1407 +111. Global Elements 1440 1440 1441 1441 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1442 1442 1443 -=== 2.2.3 Complex Types === 1411 +1. 1412 +11. 1413 +111. Complex Types 1444 1444 1445 1445 **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. 1446 1446 ... ... @@ -1451,28 +1451,28 @@ 1451 1451 Element Documentation: 1452 1452 1453 1453 |**Name**|**Type**|**Documentation** 1454 -|Message|FooterMessageType|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.1424 +|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. 1455 1455 1456 -**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.1426 +**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. 1457 1457 1458 1458 Derivation: 1459 1459 1460 - *com:StatusMessageType (restriction)1461 - **com:CodedStatusMessageType (extension)1462 - ***FooterMessageType1430 +com:StatusMessageType (restriction) 1431 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1432 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1463 1463 1464 1464 Attributes: 1465 1465 1466 - [[code>>doc:sdmx:Glossary.Code.WebHome]], severity?1436 +code, severity? 1467 1467 1468 1468 Content: 1469 1469 1470 1470 com:Text+ 1471 1471 1472 - [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]]Documentation:1442 +Attribute Documentation: 1473 1473 1474 1474 |**Name**|**Type**|**Documentation** 1475 -| [[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.1445 +|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. 1476 1476 |severity|SeverityCodeType| 1477 1477 1478 1478 Element Documentation: ... ... @@ -1480,7 +1480,9 @@ 1480 1480 |**Name**|**Type**|**Documentation** 1481 1481 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1482 1482 1483 -=== 2.2.4 Simple Types === 1453 +1. 1454 +11. 1455 +111. Simple Types 1484 1484 1485 1485 **SeverityCodeType:** 1486 1486 ... ... @@ -1491,4 +1491,19 @@ 1491 1491 |**Value**|**Documentation** 1492 1492 |Error|Error indicates the status message coresponds to an error. 1493 1493 |Warning|Warning indicates that the status message corresponds to a warning. 1494 -|Information|Information indicates that the status message corresponds to an informational message. 1466 +|Information|Information indicates that the status message corresponds to an informational message. 1467 + 1468 + 1469 + 1470 + 1471 + 1472 + 1473 + 1474 + 1475 + 1476 + 1477 + 1478 + 1479 + 1480 + 1481 +