Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Tags
-
... ... @@ -1,0 +1,1 @@ 1 +Attribute|Category scheme|Code|Code list|Concept scheme|Contact phone number|Data set|Data source|Data structure definition|Dataflow|Dimension|Hierarchical code list|Metadata set|Metadata structure definition|Metadataflow|Notification|Provision agreement|Reference metadata|Reference period|Reporting taxonomy|SDMX Registry|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Structure set|Subscription|Time period|Validation and transformation language - Content
-
... ... @@ -6,21 +6,21 @@ 6 6 7 7 The following problems with the specification dated April 2011 have been rectified as described below. 8 8 9 -1. **Problem**9 +**~1. Problem** 10 10 11 -Various parts of the the documentation refer to stand-alone concepts, which were part of earlier draft releases but ultimately excluded from the final release of the standard. 11 +Various parts of the the documentation refer to stand-alone (% style="color:#e74c3c" %)concepts(%%), which were part of earlier draft releases but ultimately excluded from the final release of the standard. 12 12 13 13 **Rectification** 14 14 15 15 The documentation of the Structure element (line 40) has been updated to remove this reference. 16 16 17 -1. Introduction 17 += 1. Introduction = 18 18 19 -At the core of the SDMX XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in SDMX. 19 +At the core of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]]. 20 20 21 -There are two namespaces associated with the messages. The main namespace schema which defines every message in SDMX is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted. 21 +There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message. Associated with this is another sub-namespace, http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer. This namespace defines footer (% style="color:#e74c3c" %)level(%%) information that is available in messages which might require non-standard payload information to be transmitted. 22 22 23 -In general, every message in SDMX follows common format of: 23 +In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of: 24 24 25 25 * Header 26 26 * Payload (0..n) ... ... @@ -28,28 +28,28 @@ 28 28 29 29 The header and payload elements exist in the message namespace, but the content of the payload is defined in the namespaces that are specific the functionality of the messages. Note that the header follows a common construct, which is then restricted according to the requirements of the message which is using it. 30 30 31 -1. Schema Documentation 32 -11. Message Namespace 31 += 2. Schema Documentation = 33 33 33 +== 2.1 Message Namespace == 34 + 34 34 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message** 35 35 36 -1. 37 -11. 38 -111. Summary 37 +=== 2.1.1 Summary === 39 39 40 40 Referenced Namespaces: 41 41 42 -|**Namespace**|**Prefix** 43 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com 44 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|dat 45 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|dsd 46 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|ftr 47 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|rep 48 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|msd 49 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|qry 50 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|ref 51 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|str 52 -|http:~/~/www.w3.org/2001/XMLSchema|xs 41 +(% style="width:788.294px" %) 42 +|(% style="width:612px" %)**Namespace**|(% style="width:173px" %)**Prefix** 43 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:173px" %)com 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]] 46 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|(% style="width:173px" %)ftr 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]] 49 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|(% style="width:173px" %)qry 50 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|(% style="width:173px" %)ref 51 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|(% style="width:173px" %)str 52 +|(% style="width:612px" %)http:~/~/www.w3.org/2001/XMLSchema|(% style="width:173px" %)xs 53 53 54 54 Contents: 55 55 ... ... @@ -57,113 +57,109 @@ 57 57 62 Complex Types 58 58 1 Simple Type 59 59 60 -1. 61 -11. 62 -111. Global Elements 60 +=== 2.1.2 Global Elements === 63 63 64 -**Structure (StructureType): **Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), constraints (attachment and content) data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, and structure sets. 62 +**Structure (StructureType): **Structure is a message that contains [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. It may contain any of the following; categorisations, [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) ([[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]), (% style="color:#e74c3c" %)constraints(%%) (attachment and content) [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], organisation schemes, processes, [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]], and structure sets. 65 65 66 -**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. Data sets in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation dimension). 64 +**GenericData (GenericDataType): **GenericData is used to convey data in a non data structure specific form. [[Data sets>>doc:sdmx:Glossary.Data set.WebHome]] in this message will be each have a related structure specification in the header, which states the data structure the data conforms to and how the data is organised (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]). 67 67 68 -**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 66 +**GenericTimeSeriesData (GenericTimeSeriesDataType): **GenericTimeSeriesData is a special derivation of the generic data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a generic data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 69 69 70 -**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to data structure definition. The payload of this message (i.e. the data sets) will be based on XML schemas which are specific to the data structure definition and the orientation (i.e. the observation dimension) of the data. 68 +**StructureSpecificData (StructureSpecificDataType): **StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The payload of this message (i.e. the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]) will be based on XML schemas which are specific to the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and the orientation (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data. 71 71 72 -**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation dimension must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation dimension; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 70 +**StructureSpecificTimeSeriesData (StructureSpecificTimeSeriesDataType): **StructureSpecificTimeSeriesData is a special derivation of the structure specific data message which only allows for time series oriented date (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] must be time). Although this is a different message, the content of this message will be exactly the same as a structure specific data message that specifies time as the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]; therefore no additional processing requirements are necessary. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 73 73 74 -**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any metadata structure definition. 72 +**GenericMetadata (GenericMetadataType): **GenericMetadata contains reported metadata in a format which supports any [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]. 75 75 76 -**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the metadata structure definitions which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each metadata set provided will be based on a metadata structure specific schema. 74 +**StructureSpecificMetadata (StructureSpecificMetadataType): **StructureSpecificMetadata contains reported metadata in a format which is specific to the [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] which define the structure of the metadata being reported. This format allows for validation of the metadata against the intended structure. Note that the each [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] provided will be based on a metadata structure specific schema. 77 77 78 -**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the SDMX Registry Services. 76 +**RegistryInterface (RegistryInterfaceType): **RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services. 79 79 80 -**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 78 +**SubmitRegistrationsRequest (SubmitRegistrationsRequestType): **SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request on or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 81 81 82 82 **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. 83 83 84 -**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 82 +**QueryRegistrationRequest (QueryRegistrationRequestType): **QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys. 85 85 86 86 **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. 87 87 88 -**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 86 +**SubmitStructureRequest (SubmitStructureRequestType): **SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information. 89 89 90 90 **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. 91 91 92 92 **SubmitSubscriptionsRequest (SubmitSubscriptionsRequestType): **SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 93 93 94 -**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 92 +**SubmitSubscriptionsResponse (SubmitSubscriptionsResponseType): **SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID. 95 95 96 -**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 94 +**QuerySubscriptionRequest (QuerySubscriptionRequestType): **QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation. 97 97 98 -**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 96 +**QuerySubscriptionResponse (QuerySubscriptionResponseType): **QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent. 99 99 100 -**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 98 +**NotifyRegistryEvent (NotifyRegistryEventType): **NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] that triggered the [[notification>>doc:sdmx:Glossary.Notification.WebHome]] are always sent. Optionally, the details of the changed object may also be provided. 101 101 102 -**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query SDMX compliant databases or web services for structure specific data. 100 +**StructureSpecificDataQuery (DataQueryType): **StructureSpecificDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure specific data. 103 103 104 -**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query SDMX compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner. 102 +**GenericDataQuery (GenericDataQueryType): **GenericDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic data. This is actually a specialization of the structured data query, and therefore can be processed in the same manner. 105 105 106 -**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 104 +**GenericTimeSeriesDataQuery (GenericTimeSeriesDataQueryType): **GenericTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only generic data. This is actually a specialization of the generic data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 107 107 108 -**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query SDMX compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 106 +**StructureSpecificTimeSeriesDataQuery (StructureSpecificTimeSeriesDataQueryType): **StructureSpecificTimeSeriesDataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for time series only structure specific data. This is actually a specialization of the structure specific data query, and therefore can be processed in the same manner. This message is intended to only be used when it is necessary to restrict an exchange to being only time series based data. 109 109 110 -**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query SDMX compliant databases or web services for generic format reference metadata. 108 +**GenericMetadataQuery (MetadataQueryType): **GenericMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for generic format [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 111 111 112 -**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query SDMX compliant databases or web services for metadata structure specific reference metadata. 110 +**StructureSpecificMetadataQuery (MetadataQueryType): **StructureSpecificMetadataQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 113 113 114 -**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query SDMX compliant databases or web services for data structure specific schemas for the purpose of validating structured data. 112 +**DataSchemaQuery (DataSchemaQueryType): **DataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structure specific schemas for the purpose of validating structured data. 115 115 116 -**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query SDMX compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata. 114 +**MetadataSchemaQuery (MetadataSchemaQueryType): **MetadataSchemaQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for metadata structure specific schemas for the purpose of validating structured metadata. 117 117 118 -**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query SDMX compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency). 116 +**StructuresQuery (StructuresQueryType): **StructuresQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for any structures based on simple maintainable object properties (e.g. all objects maintained by a maintenance agency). 119 119 120 -**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query SDMX compliant databases or web services for dataflows. 118 +**DataflowQuery (DataflowQueryType): **DataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for dataflows. 121 121 122 -**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query SDMX compliant databases or web services for metadata flows. 120 +**MetadataflowQuery (MetadataflowQueryType): **MetadataflowQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]]. 123 123 124 -**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query SDMX compliant databases or web services for data structures definitions. 122 +**DataStructureQuery (DataStructureQueryType): **DataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for data structures definitions. 125 125 126 -**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query SDMX compliant databases or web services for metadata structure definitions. 124 +**MetadataStructureQuery (MetadataStructureQueryType): **MetadataStructureQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]. 127 127 128 -**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query SDMX compliant databases or web services for category schemes. 126 +**CategorySchemeQuery (CategorySchemeQueryType): **CategorySchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]]. 129 129 130 -**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query SDMX compliant databases or web services for concept schemes. 128 +**ConceptSchemeQuery (ConceptSchemeQueryType): **ConceptSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]. 131 131 132 -**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query SDMX compliant databases or web services for codelists. 130 +**CodelistQuery (CodelistQueryType): **CodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for codelists. 133 133 134 -**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query SDMX compliant databases or web services for hierarchical codelists. 132 +**HierarchicalCodelistQuery (HierarchicalCodelistQueryType): **HierarchicalCodelistQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for hierarchical codelists. 135 135 136 -**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query SDMX compliant databases or web services for organisation schemes. 134 +**OrganisationSchemeQuery (OrganisationSchemeQueryType): **OrganisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for organisation schemes. 137 137 138 -**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query SDMX compliant databases or web services for reporting taxonomies. 136 +**ReportingTaxonomyQuery (ReportingTaxonomyQueryType): **ReportingTaxonomyQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]]. 139 139 140 -**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query SDMX compliant databases or web services for structure sets. 138 +**StructureSetQuery (StructureSetQueryType): **StructureSetQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for structure sets. 141 141 142 -**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query SDMX compliant databases or web services for processes. 140 +**ProcessQuery (ProcessQueryType): **ProcessQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for processes. 143 143 144 -**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query SDMX compliant databases or web services for categorisations. 142 +**CategorisationQuery (CategorisationQueryType): **CategorisationQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for categorisations. 145 145 146 -**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query SDMX compliant databases or web services for provision agreements. 144 +**ProvisionAgreementQuery (ProvisionAgreementQueryType): **ProvisionAgreementQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for provision agreements. 147 147 148 -**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query SDMX compliant databases or web services for constraints. 146 +**ConstraintQuery (ConstraintQueryType): **ConstraintQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for (% style="color:#e74c3c" %)constraints(%%). 149 149 150 -**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query SDMX compliant databases or web services for transformation schemes. 148 +**TransformationSchemeQuery (TransformationSchemeQueryType): **TransformationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for transformation schemes. 151 151 152 -**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query SDMX compliant databases or web services for VTL mapping schemes. 150 +**VtlMappingSchemeQuery (VtlMappingSchemeQueryType): **VtlMappingSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mapping schemes. 153 153 154 -**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query SDMX compliant databases or web services for name personalisation schemes. 152 +**NamePersonalisationSchemeQuery (NamePersonalisationSchemeQueryType): **NamePersonalisationSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for name personalisation schemes. 155 155 156 -**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query SDMX compliant databases or web services for ruleset schemes. 154 +**RulesetSchemeQuery (RulesetSchemeQueryType): **RulesetSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for ruleset schemes. 157 157 158 -**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query SDMX compliant databases or web services for user defined schemes. 156 +**UserDefinedOperatorSchemeQuery (UserDefinedOperatorSchemeQueryType): **UserDefinedOperatorSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for user defined schemes. 159 159 160 -**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query SDMX compliant databases or web services for custom type schemes. 158 +**CustomTypeSchemeQuery (CustomTypeSchemeQueryType): **CustomTypeSchemeQuery is used to query [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] compliant databases or web services for custom type schemes. 161 161 162 162 **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. 163 163 164 -1. 165 -11. 166 -111. Complex Types 162 +=== 2.1.3 Complex Types === 167 167 168 168 **//MessageType//: **MessageType is an abstract type which is used by all of the messages, to allow inheritance of common features. Every message consists of a mandatory header, followed by optional payload (which may occur multiple times), and finally an optional footer section for conveying error, warning, and informational messages. 169 169 ... ... @@ -181,8 +181,8 @@ 181 181 182 182 Derivation: 183 183 184 -//MessageType// (restriction) 185 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureType180 +* //MessageType// (restriction) 181 +** StructureType 186 186 187 187 Content: 188 188 ... ... @@ -190,91 +190,96 @@ 190 190 191 191 Element Documentation: 192 192 193 -|**Name**|**Type**|**Documentation** 194 -|Header|StructureHeaderType| 195 -|Structures|str:StructuresType| 196 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 189 +(% style="width:856.294px" %) 190 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:455px" %)**Documentation** 191 +|Header|(% style="width:210px" %)StructureHeaderType|(% style="width:455px" %) 192 +|Structures|(% style="width:210px" %)str:StructuresType|(% style="width:455px" %) 193 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:455px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 197 197 198 198 **GenericDataType: **GenericDataType defines the contents of a generic data message. 199 199 200 200 Derivation: 201 201 202 -//MessageType// (restriction) 203 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType199 +* //MessageType// (restriction) 200 +** GenericDataType 204 204 205 205 Content: 206 206 207 -Header, DataSet*, ftr:Footer? 204 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 208 208 209 209 Element Documentation: 210 210 211 -|**Name**|**Type**|**Documentation** 212 -|Header|GenericDataHeaderTyp e| 213 -|DataSet|dat:DataSetType| 214 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 208 +(% style="width:847.294px" %) 209 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation** 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" %) 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. 215 215 216 216 **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message. 217 217 218 218 Derivation: 219 219 220 -//MessageType// (restriction) 221 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType (restriction)222 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericTimeSeriesDataType218 +* //MessageType// (restriction) 219 +** GenericDataType (restriction) 220 +*** GenericTimeSeriesDataType 223 223 224 224 Content: 225 225 226 -Header, DataSet*, ftr:Footer? 224 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 227 227 228 228 Element Documentation: 229 229 230 -|**Name**|**Type**|**Documentation** 231 -|Header|GenericTimeSeriesDat aHeaderType| 232 -|DataSet|dat: TimeSeriesDataSetTyp e| 233 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 228 +(% style="width:856.294px" %) 229 +|**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation** 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" %) 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. 234 234 235 -**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. 234 +**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 236 236 237 237 Derivation: 238 238 239 -//MessageType// (restriction) 240 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType238 +* //MessageType// (restriction) 239 +** StructureSpecificDataType 241 241 242 242 Content: 243 243 244 -Header, DataSet*, ftr:Footer? 243 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 245 245 246 246 Element Documentation: 247 247 248 -|**Name**|**Type**|**Documentation** 249 -|Header|StructureSpecificDat aHeaderType| 250 -|DataSet|//dsd:DataSetType//| 251 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 247 +(% style="width:828.294px" %) 248 +|**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation** 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.Data structure definition.WebHome]]:DataSetType//|(% style="width:420px" %) 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. 254 254 255 255 Derivation: 256 256 257 -//MessageType// (restriction) 258 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType (restriction)259 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificTimeSeriesDataType257 +* //MessageType// (restriction) 258 +** StructureSpecificDataType (restriction) 259 +*** StructureSpecificTimeSeriesDataType 260 260 261 261 Content: 262 262 263 -Header, DataSet*, ftr:Footer? 263 +Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, ftr:Footer? 264 264 265 265 Element Documentation: 266 266 267 -|**Name**|**Type**|**Documentation** 268 -|Header|StructureSpecificTim eSeriesDataHeaderTyp e| 269 -|DataSet|//dsd: TimeSeriesDataSetTyp e//| 270 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 267 +(% style="width:839.294px" %) 268 +|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation** 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.Data structure definition.WebHome]]: TimeSeriesDataSetTyp e//|(% style="width:434px" %) 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. 271 271 272 272 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message. 273 273 274 274 Derivation: 275 275 276 -//MessageType// (restriction) 277 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericMetadataType277 +* //MessageType// (restriction) 278 +** GenericMetadataType 278 278 279 279 Content: 280 280 ... ... @@ -282,17 +282,18 @@ 282 282 283 283 Element Documentation: 284 284 285 -|**Name**|**Type**|**Documentation** 286 -|Header|GenericMetadataHeade rType| 287 -|MetadataSet|rep:MetadataSetType| 288 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 286 +(% style="width:836.294px" %) 287 +|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation** 288 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %) 289 +|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %) 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. 289 289 290 -**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. 292 +**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]] payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 291 291 292 292 Derivation: 293 293 294 -//MessageType// (restriction) 295 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataType296 +* //MessageType// (restriction) 297 +** StructureSpecificMetadataType 296 296 297 297 Content: 298 298 ... ... @@ -300,17 +300,18 @@ 300 300 301 301 Element Documentation: 302 302 303 -|**Name**|**Type**|**Documentation** 304 -|Header|StructureSpecificMet adataHeaderType| 305 -|MetadataSet|//msd:MetadataSetType//| 306 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 305 +(% style="width:841.294px" %) 306 +|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation** 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.Metadata structure definition.WebHome]]:MetadataSetType//|(% style="width:428px" %) 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. 307 307 308 308 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. 309 309 310 310 Derivation: 311 311 312 -//MessageType// (restriction) 313 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType315 +* //MessageType// (restriction) 316 +** RegistryInterfaceType 314 314 315 315 Content: 316 316 ... ... @@ -318,28 +318,29 @@ 318 318 319 319 Element Documentation: 320 320 321 -|**Name**|**Type**|**Documentation** 322 -|Header|BasicHeaderType| 323 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 324 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 325 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 326 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 327 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 328 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 329 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 330 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 331 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 332 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 333 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 334 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 324 +(% style="width:903.294px" %) 325 +|**Name**|**Type**|(% style="width:441px" %)**Documentation** 326 +|Header|BasicHeaderType|(% style="width:441px" %) 327 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 328 +|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.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys. 330 +|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. 332 +|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 333 +|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 334 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>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. 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. 335 335 336 336 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 337 337 338 338 Derivation: 339 339 340 -//MessageType// (restriction) 341 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)342 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsRequestType344 +* //MessageType// (restriction) 345 +** RegistryInterfaceType (restriction) 346 +*** SubmitRegistrationsRequestType 343 343 344 344 Content: 345 345 ... ... @@ -347,17 +347,18 @@ 347 347 348 348 Element Documentation: 349 349 350 -|**Name**|**Type**|**Documentation** 351 -|Header|BasicHeaderType| 352 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 354 +(% style="width:844.294px" %) 355 +|**Name**|**Type**|(% style="width:377px" %)**Documentation** 356 +|Header|BasicHeaderType|(% style="width:377px" %) 357 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or [[metadata set>>doc:sdmx:Glossary.Metadata set.WebHome]]. The [[data source>>doc:sdmx:Glossary.Data source.WebHome]] to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 353 353 354 354 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 355 355 356 356 Derivation: 357 357 358 -//MessageType// (restriction) 359 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)360 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsResponseType363 +* //MessageType// (restriction) 364 +** RegistryInterfaceType (restriction) 365 +*** SubmitRegistrationsResponseType 361 361 362 362 Content: 363 363 ... ... @@ -365,18 +365,19 @@ 365 365 366 366 Element Documentation: 367 367 368 -|**Name**|**Type**|**Documentation** 369 -|Header|BasicHeaderType| 370 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 371 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 373 +(% style="width:847.294px" %) 374 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 375 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) 376 +|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 377 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 372 372 373 373 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 374 374 375 375 Derivation: 376 376 377 -//MessageType// (restriction) 378 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)379 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationRequestType383 +* //MessageType// (restriction) 384 +** RegistryInterfaceType (restriction) 385 +*** QueryRegistrationRequestType 380 380 381 381 Content: 382 382 ... ... @@ -384,17 +384,18 @@ 384 384 385 385 Element Documentation: 386 386 387 -|**Name**|**Type**|**Documentation** 388 -|Header|BasicHeaderType| 389 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 393 +(% style="width:847.294px" %) 394 +|**Name**|**Type**|(% style="width:397px" %)**Documentation** 395 +|Header|BasicHeaderType|(% style="width:397px" %) 396 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for [[data sets>>doc:sdmx:Glossary.Data set.WebHome]] and [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]]. It specifies whether the result set should include [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]], [[data sets>>doc:sdmx:Glossary.Data set.WebHome]], or both. The search can be characterized by providing (% style="color:#e74c3c" %)constraints(%%) including [[reference periods>>doc:sdmx:Glossary.Reference period.WebHome]], data regions, and data keys. 390 390 391 391 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 392 392 393 393 Derivation: 394 394 395 -//MessageType// (restriction) 396 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)397 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationResponseType402 +* //MessageType// (restriction) 403 +** RegistryInterfaceType (restriction) 404 +*** QueryRegistrationResponseType 398 398 399 399 Content: 400 400 ... ... @@ -402,18 +402,19 @@ 402 402 403 403 Element Documentation: 404 404 405 -|**Name**|**Type**|**Documentation** 406 -|Header|BasicHeaderType| 407 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 408 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 412 +(% style="width:856.294px" %) 413 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation** 414 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %) 415 +|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 416 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 409 409 410 410 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 411 411 412 412 Derivation: 413 413 414 -//MessageType// (restriction) 415 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureRequestType422 +* //MessageType// (restriction) 423 +** RegistryInterfaceType (restriction) 424 +*** SubmitStructureRequestType 417 417 418 418 Content: 419 419 ... ... @@ -421,17 +421,18 @@ 421 421 422 422 Element Documentation: 423 423 424 -|**Name**|**Type**|**Documentation** 425 -|Header|BasicHeaderType| 426 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 432 +(% style="width:870.294px" %) 433 +|**Name**|**Type**|(% style="width:453px" %)**Documentation** 434 +|Header|BasicHeaderType|(% style="width:453px" %) 435 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% 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. 427 427 428 428 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document. 429 429 430 430 Derivation: 431 431 432 -//MessageType// (restriction) 433 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)434 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureResponseType441 +* //MessageType// (restriction) 442 +** RegistryInterfaceType (restriction) 443 +*** SubmitStructureResponseType 435 435 436 436 Content: 437 437 ... ... @@ -439,18 +439,19 @@ 439 439 440 440 Element Documentation: 441 441 442 -|**Name**|**Type**|**Documentation** 443 -|Header|BasicHeaderType| 444 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 445 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 451 +(% style="width:835.294px" %) 452 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 453 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) 454 +|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 455 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 446 446 447 -**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document. 457 +**SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document. 448 448 449 449 Derivation: 450 450 451 -//MessageType// (restriction) 452 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)453 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsRequestType461 +* //MessageType// (restriction) 462 +** RegistryInterfaceType (restriction) 463 +*** SubmitSubscriptionsRequestType 454 454 455 455 Content: 456 456 ... ... @@ -458,17 +458,18 @@ 458 458 459 459 Element Documentation: 460 460 461 -|**Name**|**Type**|**Documentation** 462 -|Header|BasicHeaderType| 463 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 471 +(% style="width:832.294px" %) 472 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 473 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %) 474 +|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 464 464 465 -**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document. 476 +**SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document. 466 466 467 467 Derivation: 468 468 469 -//MessageType// (restriction) 470 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)471 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsResponseType480 +* //MessageType// (restriction) 481 +** RegistryInterfaceType (restriction) 482 +*** SubmitSubscriptionsResponseType 472 472 473 473 Content: 474 474 ... ... @@ -476,18 +476,19 @@ 476 476 477 477 Element Documentation: 478 478 479 -|**Name**|**Type**|**Documentation** 480 -|Header|BasicHeaderType| 481 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 482 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 490 +(% style="width:843.294px" %) 491 +|**Name**|**Type**|(% style="width:362px" %)**Documentation** 492 +|Header|BasicHeaderType|(% style="width:362px" %) 493 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] request. It contains information which describes the success or failure of each [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request, providing any error messages in the event of failure. If successful, it returns the registry URN of the [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]], and the subscriber-assigned ID. 494 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 483 483 484 -**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document. 496 +**QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] request document. 485 485 486 486 Derivation: 487 487 488 -//MessageType// (restriction) 489 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)490 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionRequestType500 +* //MessageType// (restriction) 501 +** RegistryInterfaceType (restriction) 502 +*** QuerySubscriptionRequestType 491 491 492 492 Content: 493 493 ... ... @@ -495,17 +495,18 @@ 495 495 496 496 Element Documentation: 497 497 498 -|**Name**|**Type**|**Documentation** 499 -|Header|BasicHeaderType| 500 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 510 +(% style="width:839.294px" %) 511 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation** 512 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %) 513 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation. 501 501 502 -**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document. 515 +**QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] response document. 503 503 504 504 Derivation: 505 505 506 -//MessageType// (restriction) 507 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)508 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionResponseType519 +* //MessageType// (restriction) 520 +** RegistryInterfaceType (restriction) 521 +*** QuerySubscriptionResponseType 509 509 510 510 Content: 511 511 ... ... @@ -513,18 +513,19 @@ 513 513 514 514 Element Documentation: 515 515 516 -|**Name**|**Type**|**Documentation** 517 -|Header|BasicHeaderType| 518 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 519 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 529 +(% style="width:912.294px" %) 530 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation** 531 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %) 532 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a [[subscription>>doc:sdmx:Glossary.Subscription.WebHome]] query. If the query is successful, the details of all [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] for the requested organisation are sent. 533 +|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. 520 520 521 -**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document. 535 +**NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry [[notification>>doc:sdmx:Glossary.Notification.WebHome]] document. 522 522 523 523 Derivation: 524 524 525 -//MessageType// (restriction) 526 - 527 - 539 +* //MessageType// (restriction) 540 +** RegistryInterfaceType (restriction) 541 +*** NotifyRegistryEventType 528 528 529 529 Content: 530 530 ... ... @@ -532,16 +532,17 @@ 532 532 533 533 Element Documentation: 534 534 535 -|**Name**|**Type**|**Documentation** 536 -|Header|BasicHeaderType| 537 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 549 +(% style="width:836.294px" %) 550 +|**Name**|**Type**|(% style="width:473px" %)**Documentation** 551 +|Header|BasicHeaderType|(% style="width:473px" %) 552 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the [[subscription>>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. 538 538 539 539 **DataQueryType: **DataQueryType defines the structure of a data query message. 540 540 541 541 Derivation: 542 542 543 -//MessageType// (restriction) 544 - 558 +* //MessageType// (restriction) 559 +** DataQueryType 545 545 546 546 Content: 547 547 ... ... @@ -549,17 +549,18 @@ 549 549 550 550 Element Documentation: 551 551 552 -|**Name**|**Type**|**Documentation** 553 -|Header|BasicHeaderType| 554 -|Query|qry:DataQueryType| 567 +(% style="width:839.294px" %) 568 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation** 569 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %) 570 +|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %) 555 555 556 556 **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message. 557 557 558 558 Derivation: 559 559 560 -//MessageType// (restriction) 561 - 562 - 576 +* //MessageType// (restriction) 577 +** DataQueryType (restriction) 578 +*** GenericDataQueryType 563 563 564 564 Content: 565 565 ... ... @@ -567,18 +567,19 @@ 567 567 568 568 Element Documentation: 569 569 570 -|**Name**|**Type**|**Documentation** 571 -|Header|BasicHeaderType| 572 -|Query|qry: GenericDataQueryType| 586 +(% style="width:833.294px" %) 587 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 588 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) 589 +|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %) 573 573 574 574 **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message. 575 575 576 576 Derivation: 577 577 578 -//MessageType// (restriction) 579 - 580 - 581 - 595 +* //MessageType// (restriction) 596 +** DataQueryType (restriction) 597 +*** GenericDataQueryType (restriction) 598 +**** GenericTimeSeriesDataQueryType 582 582 583 583 Content: 584 584 ... ... @@ -586,17 +586,18 @@ 586 586 587 587 Element Documentation: 588 588 589 -|**Name**|**Type**|**Documentation** 590 -|Header|BasicHeaderType| 591 -|Query|qry: GenericTimeSeriesDat aQueryType| 606 +(% style="width:909.294px" %) 607 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 608 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) 609 +|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %) 592 592 593 593 **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message. 594 594 595 595 Derivation: 596 596 597 -//MessageType// (restriction) 598 - 599 - 615 +* //MessageType// (restriction) 616 +** DataQueryType (restriction) 617 +*** StructureSpecificTimeSeriesDataQueryType 600 600 601 601 Content: 602 602 ... ... @@ -604,16 +604,17 @@ 604 604 605 605 Element Documentation: 606 606 607 -|**Name**|**Type**|**Documentation** 608 -|Header|BasicHeaderType| 609 -|Query|qry: TimeSeriesDataQueryT ype| 625 +(% style="width:903.294px" %) 626 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 627 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %) 628 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %) 610 610 611 -**MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message. 630 +**MetadataQueryType: **MetadataQueryType defines the structure of a [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] query message. 612 612 613 613 Derivation: 614 614 615 -//MessageType// (restriction) 616 - 634 +* //MessageType// (restriction) 635 +** MetadataQueryType 617 617 618 618 Content: 619 619 ... ... @@ -621,16 +621,17 @@ 621 621 622 622 Element Documentation: 623 623 624 -|**Name**|**Type**|**Documentation** 625 -|Header|BasicHeaderType| 626 -|Query|qry: MetadataQueryType| 643 +(% style="width:858.294px" %) 644 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 645 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) 646 +|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %) 627 627 628 628 **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message. 629 629 630 630 Derivation: 631 631 632 -//MessageType// (restriction) 633 - 652 +* //MessageType// (restriction) 653 +** DataSchemaQueryType 634 634 635 635 Content: 636 636 ... ... @@ -638,16 +638,17 @@ 638 638 639 639 Element Documentation: 640 640 641 -|**Name**|**Type**|**Documentation** 642 -|Header|BasicHeaderType| 643 -|Query|qry: DataSchemaQueryType| 661 +(% style="width:895.294px" %) 662 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 663 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) 664 +|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %) 644 644 645 645 **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message. 646 646 647 647 Derivation: 648 648 649 -//MessageType// (restriction) 650 - 670 +* //MessageType// (restriction) 671 +** MetadataSchemaQueryType 651 651 652 652 Content: 653 653 ... ... @@ -655,16 +655,17 @@ 655 655 656 656 Element Documentation: 657 657 658 -|**Name**|**Type**|**Documentation** 659 -|Header|BasicHeaderType| 660 -|Query|qry: MetadataSchemaQueryT ype| 679 +(% style="width:897.294px" %) 680 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 681 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) 682 +|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %) 661 661 662 662 **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message. 663 663 664 664 Derivation: 665 665 666 -//MessageType// (restriction) 667 - 688 +* //MessageType// (restriction) 689 +** StructuresQueryType 668 668 669 669 Content: 670 670 ... ... @@ -672,16 +672,17 @@ 672 672 673 673 Element Documentation: 674 674 675 -|**Name**|**Type**|**Documentation** 676 -|Header|BasicHeaderType| 677 -|Query|qry: StructuresQueryType| 697 +(% style="width:886.294px" %) 698 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 699 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %) 700 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %) 678 678 679 -**DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message. 702 +**DataflowQueryType: **DataflowQueryType defines the structure of a [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]] query message. 680 680 681 681 Derivation: 682 682 683 -//MessageType// (restriction) 684 - 706 +* //MessageType// (restriction) 707 +** DataflowQueryType 685 685 686 686 Content: 687 687 ... ... @@ -689,16 +689,17 @@ 689 689 690 690 Element Documentation: 691 691 692 -|**Name**|**Type**|**Documentation** 693 -|Header|BasicHeaderType| 694 -|Query|qry: DataflowQueryType| 715 +(% style="width:888.294px" %) 716 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 717 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %) 718 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %) 695 695 696 -**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message. 720 +**MetadataflowQueryType: **MetadataflowQueryType defines the structure of a [[metadata flow>>doc:sdmx:Glossary.Metadataflow.WebHome]] query message. 697 697 698 698 Derivation: 699 699 700 -//MessageType// (restriction) 701 - 724 +* //MessageType// (restriction) 725 +** MetadataflowQueryType 702 702 703 703 Content: 704 704 ... ... @@ -706,16 +706,17 @@ 706 706 707 707 Element Documentation: 708 708 709 -|**Name**|**Type**|**Documentation** 710 -|Header|BasicHeaderType| 711 -|Query|qry: MetadataflowQueryTyp e| 733 +(% style="width:886.294px" %) 734 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 735 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) 736 +|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %) 712 712 713 713 **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message. 714 714 715 715 Derivation: 716 716 717 -//MessageType// (restriction) 718 - 742 +* //MessageType// (restriction) 743 +** DataStructureQueryType 719 719 720 720 Content: 721 721 ... ... @@ -723,16 +723,17 @@ 723 723 724 724 Element Documentation: 725 725 726 -|**Name**|**Type**|**Documentation** 727 -|Header|BasicHeaderType| 728 -|Query|qry: DataStructureQueryTy pe| 751 +(% style="width:901.294px" %) 752 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 753 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) 754 +|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %) 729 729 730 730 **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message. 731 731 732 732 Derivation: 733 733 734 -//MessageType// (restriction) 735 - 760 +* //MessageType// (restriction) 761 +** MetadataStructureQueryType 736 736 737 737 Content: 738 738 ... ... @@ -740,16 +740,17 @@ 740 740 741 741 Element Documentation: 742 742 743 -|**Name**|**Type**|**Documentation** 744 -|Header|BasicHeaderType| 745 -|Query|qry: MetadataStructureQue ryType| 769 +(% style="width:904.294px" %) 770 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 771 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %) 772 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %) 746 746 747 -**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message. 774 +**CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a [[category scheme>>doc:sdmx:Glossary.Category scheme.WebHome]] query message. 748 748 749 749 Derivation: 750 750 751 -//MessageType// (restriction) 752 - 778 +* //MessageType// (restriction) 779 +** CategorySchemeQueryType 753 753 754 754 Content: 755 755 ... ... @@ -757,16 +757,17 @@ 757 757 758 758 Element Documentation: 759 759 760 -|**Name**|**Type**|**Documentation** 761 -|Header|BasicHeaderType| 762 -|Query|qry: CategorySchemeQueryT ype| 787 +(% style="width:915.294px" %) 788 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 789 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %) 790 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %) 763 763 764 -**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message. 792 +**ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a [[concept scheme>>doc:sdmx:Glossary.Concept scheme.WebHome]] query message. 765 765 766 766 Derivation: 767 767 768 -//MessageType// (restriction) 769 - 796 +* //MessageType// (restriction) 797 +** ConceptSchemeQueryType 770 770 771 771 Content: 772 772 ... ... @@ -774,16 +774,17 @@ 774 774 775 775 Element Documentation: 776 776 777 -|**Name**|**Type**|**Documentation** 778 -|Header|BasicHeaderType| 779 -|Query|qry: ConceptSchemeQueryTy pe| 805 +(% style="width:895.294px" %) 806 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 807 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %) 808 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %) 780 780 781 -**CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message. 810 +**CodelistQueryType: **CodelistQueryType defines the structure of a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message. 782 782 783 783 Derivation: 784 784 785 -//MessageType// (restriction) 786 - 814 +* //MessageType// (restriction) 815 +** CodelistQueryType 787 787 788 788 Content: 789 789 ... ... @@ -791,16 +791,17 @@ 791 791 792 792 Element Documentation: 793 793 794 -|**Name**|**Type**|**Documentation** 795 -|Header|BasicHeaderType| 796 -|Query|qry: CodelistQueryType| 823 +(% style="width:911.294px" %) 824 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation** 825 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %) 826 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %) 797 797 798 -**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message. 828 +**HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query message. 799 799 800 800 Derivation: 801 801 802 -//MessageType// (restriction) 803 - 832 +* //MessageType// (restriction) 833 +** HierarchicalCodelistQueryType 804 804 805 805 Content: 806 806 ... ... @@ -808,16 +808,17 @@ 808 808 809 809 Element Documentation: 810 810 811 -|**Name**|**Type**|**Documentation** 812 -|Header|BasicHeaderType| 813 -|Query|qry: HierarchicalCodelist QueryType| 841 +(% style="width:906.294px" %) 842 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation** 843 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %) 844 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %) 814 814 815 815 **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message. 816 816 817 817 Derivation: 818 818 819 -//MessageType// (restriction) 820 - 850 +* //MessageType// (restriction) 851 +** OrganisationSchemeQueryType 821 821 822 822 Content: 823 823 ... ... @@ -825,16 +825,17 @@ 825 825 826 826 Element Documentation: 827 827 828 -|**Name**|**Type**|**Documentation** 829 -|Header|BasicHeaderType| 830 -|Query|qry: OrganisationSchemeQu eryType| 859 +(% style="width:891.294px" %) 860 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation** 861 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %) 862 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %) 831 831 832 832 **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message. 833 833 834 834 Derivation: 835 835 836 -//MessageType// (restriction) 837 - 868 +* //MessageType// (restriction) 869 +** ReportingTaxonomyQueryType 838 838 839 839 Content: 840 840 ... ... @@ -842,16 +842,17 @@ 842 842 843 843 Element Documentation: 844 844 845 -|**Name**|**Type**|**Documentation** 846 -|Header|BasicHeaderType| 847 -|Query|qry: ReportingTaxonomyQue ryType| 877 +(% style="width:916.294px" %) 878 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation** 879 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %) 880 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %) 848 848 849 -**StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message. 882 +**StructureSetQueryType: **StructureSetQueryType defines the structure of a [[structure set>>doc:sdmx:Glossary.Structure set.WebHome]] query message. 850 850 851 851 Derivation: 852 852 853 -//MessageType// (restriction) 854 - 886 +* //MessageType// (restriction) 887 +** StructureSetQueryType 855 855 856 856 Content: 857 857 ... ... @@ -859,16 +859,17 @@ 859 859 860 860 Element Documentation: 861 861 862 -|**Name**|**Type**|**Documentation** 863 -|Header|BasicHeaderType| 864 -|Query|qry: StructureSetQueryTyp e| 895 +(% style="width:896.294px" %) 896 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation** 897 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %) 898 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %) 865 865 866 866 **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message. 867 867 868 868 Derivation: 869 869 870 -//MessageType// (restriction) 871 - 904 +* //MessageType// (restriction) 905 +** ProcessQueryType 872 872 873 873 Content: 874 874 ... ... @@ -876,16 +876,17 @@ 876 876 877 877 Element Documentation: 878 878 879 -|**Name**|**Type**|**Documentation** 880 -|Header|BasicHeaderType| 881 -|Query|qry:ProcessQueryType| 913 +(% style="width:907.294px" %) 914 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation** 915 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %) 916 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %) 882 882 883 883 **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message. 884 884 885 885 Derivation: 886 886 887 -//MessageType// (restriction) 888 - 922 +* //MessageType// (restriction) 923 +** CategorisationQueryType 889 889 890 890 Content: 891 891 ... ... @@ -893,16 +893,17 @@ 893 893 894 894 Element Documentation: 895 895 896 -|**Name**|**Type**|**Documentation** 897 -|Header|BasicHeaderType| 898 -|Query|qry: CategorisationQueryT ype| 931 +(% style="width:897.294px" %) 932 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation** 933 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %) 934 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %) 899 899 900 -**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message. 936 +**ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]] query message. 901 901 902 902 Derivation: 903 903 904 -//MessageType// (restriction) 905 - 940 +* //MessageType// (restriction) 941 +** ProvisionAgreementQueryType 906 906 907 907 Content: 908 908 ... ... @@ -910,16 +910,17 @@ 910 910 911 911 Element Documentation: 912 912 913 -|**Name**|**Type**|**Documentation** 914 -|Header|BasicHeaderType| 915 -|Query|qry: ProvisionAgreementQu eryType| 949 +(% style="width:902.294px" %) 950 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation** 951 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %) 952 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %) 916 916 917 -**ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message. 954 +**ConstraintQueryType: **ConstraintQueryType defines the structure of a (% style="color:#e74c3c" %)constraint(%%) query message. 918 918 919 919 Derivation: 920 920 921 -//MessageType// (restriction) 922 - 958 +* //MessageType// (restriction) 959 +** ConstraintQueryType 923 923 924 924 Content: 925 925 ... ... @@ -927,16 +927,17 @@ 927 927 928 928 Element Documentation: 929 929 930 -|**Name**|**Type**|**Documentation** 931 -|Header|BasicHeaderType| 932 -|Query|qry: ConstraintQueryType| 967 +(% style="width:902.294px" %) 968 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation** 969 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %) 970 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %) 933 933 934 934 **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message. 935 935 936 936 Derivation: 937 937 938 -//MessageType// (restriction) 939 - 976 +* //MessageType// (restriction) 977 +** TransformationSchemeQueryType 940 940 941 941 Content: 942 942 ... ... @@ -944,16 +944,17 @@ 944 944 945 945 Element Documentation: 946 946 947 -|**Name**|**Type**|**Documentation** 948 -|Header|BasicHeaderType| 949 -|Query|qry: TransformationScheme QueryType| 985 +(% style="width:833.294px" %) 986 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation** 987 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %) 988 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %) 950 950 951 -**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message. 990 +**VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a [[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] mappings scheme query message. 952 952 953 953 Derivation: 954 954 955 -//MessageType// (restriction) 956 - 994 +* //MessageType// (restriction) 995 +** VtlMappingSchemeQueryType 957 957 958 958 Content: 959 959 ... ... @@ -961,16 +961,17 @@ 961 961 962 962 Element Documentation: 963 963 964 -|**Name**|**Type**|**Documentation** 965 -|Header|BasicHeaderType| 966 -|Query|qry: VtlMappingSchemeQuer yType| 1003 +(% style="width:843.294px" %) 1004 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation** 1005 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %) 1006 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %) 967 967 968 968 **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message. 969 969 970 970 Derivation: 971 971 972 -//MessageType// (restriction) 973 - 1012 +* //MessageType// (restriction) 1013 +** NamePersonalisationSchemeQueryType 974 974 975 975 Content: 976 976 ... ... @@ -978,16 +978,17 @@ 978 978 979 979 Element Documentation: 980 980 981 -|**Name**|**Type**|**Documentation** 982 -|Header|BasicHeaderType| 983 -|Query|qry: NamePersonalisationS chemeQueryType| 1021 +(% style="width:895.294px" %) 1022 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation** 1023 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %) 1024 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %) 984 984 985 985 **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message. 986 986 987 987 Derivation: 988 988 989 -//MessageType// (restriction) 990 - 1030 +* //MessageType// (restriction) 1031 +** RulesetSchemeQueryType 991 991 992 992 Content: 993 993 ... ... @@ -995,16 +995,17 @@ 995 995 996 996 Element Documentation: 997 997 998 -|**Name**|**Type**|**Documentation** 999 -|Header|BasicHeaderType| 1000 -|Query|qry: RulesetSchemeQueryTy pe| 1039 +(% style="width:886.294px" %) 1040 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation** 1041 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %) 1042 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %) 1001 1001 1002 1002 **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message. 1003 1003 1004 1004 Derivation: 1005 1005 1006 -//MessageType// (restriction) 1007 - 1048 +* //MessageType// (restriction) 1049 +** UserDefinedOperatorSchemeQueryType 1008 1008 1009 1009 Content: 1010 1010 ... ... @@ -1012,16 +1012,17 @@ 1012 1012 1013 1013 Element Documentation: 1014 1014 1015 -|**Name**|**Type**|**Documentation** 1016 -|Header|BasicHeaderType| 1017 -|Query|qry: UserDefinedOperatorS chemeQueryType| 1057 +(% style="width:866.294px" %) 1058 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation** 1059 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %) 1060 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %) 1018 1018 1019 1019 **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message. 1020 1020 1021 1021 Derivation: 1022 1022 1023 -//MessageType// (restriction) 1024 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]CustomTypeSchemeQueryType1066 +* //MessageType// (restriction) 1067 +** CustomTypeSchemeQueryType 1025 1025 1026 1026 Content: 1027 1027 ... ... @@ -1029,9 +1029,10 @@ 1029 1029 1030 1030 Element Documentation: 1031 1031 1032 -|**Name**|**Type**|**Documentation** 1033 -|Header|BasicHeaderType| 1034 -|Query|qry: CustomTypeSchemeQuer yType| 1075 +(% style="width:828.294px" %) 1076 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation** 1077 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %) 1078 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %) 1035 1035 1036 1036 **ErrorType: **ErrorType describes the structure of an error response. 1037 1037 ... ... @@ -1041,8 +1041,9 @@ 1041 1041 1042 1042 Element Documentation: 1043 1043 1044 -|**Name**|**Type**|**Documentation** 1045 -|ErrorMessage|com: CodedStatusMessageTy pe|ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors. 1088 +(% style="width:899.294px" %) 1089 +|**Name**|**Type**|(% style="width:546px" %)**Documentation** 1090 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a [[code>>doc:sdmx:Glossary.Code.WebHome]] in order to distinguish message for unique errors. 1046 1046 1047 1047 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this 1048 1048 ... ... @@ -1052,29 +1052,30 @@ 1052 1052 1053 1053 Element Documentation: 1054 1054 1055 -|**Name**|**Type**|**Documentation** 1056 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1057 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1058 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1059 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1060 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1061 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1062 -|Structure|//com: PayloadStructureType//|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1063 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1064 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1065 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1066 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1067 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1068 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1069 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1070 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1100 +(% style="width:891.294px" %) 1101 +|**Name**|**Type**|(% style="width:552px" %)**Documentation** 1102 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender. 1103 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not. 1104 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared. 1105 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message. 1106 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message. 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.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1109 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 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]]. 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.Time period.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.Time period.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.Time period.WebHome]] before which the data included in this message is not available. 1116 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data. 1071 1071 1072 -**StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages. 1118 +**StructureHeaderType: **StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages. 1073 1073 1074 1074 Derivation: 1075 1075 1076 -//BaseHeaderType// (restriction) 1077 - 1122 +* //BaseHeaderType// (restriction) 1123 +** StructureHeaderType 1078 1078 1079 1079 Content: 1080 1080 ... ... @@ -1082,21 +1082,22 @@ 1082 1082 1083 1083 Element Documentation: 1084 1084 1085 -|**Name**|**Type**|**Documentation** 1086 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1087 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1088 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1089 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1090 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1091 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1092 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1131 +(% style="width:1099.29px" %) 1132 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation** 1133 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender. 1134 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not. 1135 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared. 1136 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message. 1137 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message. 1138 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1139 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data. 1093 1093 1094 1094 **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message. 1095 1095 1096 1096 Derivation: 1097 1097 1098 -//BaseHeaderType// (restriction) 1099 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataHeaderType1145 +* //BaseHeaderType// (restriction) 1146 +** GenericDataHeaderType 1100 1100 1101 1101 Content: 1102 1102 ... ... @@ -1104,30 +1104,31 @@ 1104 1104 1105 1105 Element Documentation: 1106 1106 1107 -|**Name**|**Type**|**Documentation** 1108 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1109 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1110 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1111 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1112 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1113 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1114 -|Structure|com: GenericDataStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1115 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1116 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1117 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1118 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1119 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1120 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1121 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1122 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1154 +(% style="width:895.294px" %) 1155 +|**Name**|**Type**|(% style="width:556px" %)**Documentation** 1156 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender. 1157 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not. 1158 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared. 1159 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1160 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1161 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1162 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1163 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 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]]. 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.Time period.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.Time period.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.Time period.WebHome]] before which the data included in this message is not available. 1170 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1123 1123 1124 1124 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. 1125 1125 1126 1126 Derivation: 1127 1127 1128 -//BaseHeaderType// (restriction) 1129 - 1130 - 1176 +* //BaseHeaderType// (restriction) 1177 +** GenericDataHeaderType (restriction) 1178 +*** GenericTimeSeriesDataHeaderType 1131 1131 1132 1132 Content: 1133 1133 ... ... @@ -1135,29 +1135,30 @@ 1135 1135 1136 1136 Element Documentation: 1137 1137 1138 -|**Name**|**Type**|**Documentation** 1139 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1140 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1141 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1142 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1143 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1144 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1145 -|Structure|com: GenericTimeSeriesDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1146 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1147 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1148 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1149 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1150 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1151 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1152 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1153 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1186 +(% style="width:926.294px" %) 1187 +|**Name**|**Type**|(% style="width:497px" %)**Documentation** 1188 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender. 1189 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not. 1190 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared. 1191 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1192 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1193 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1194 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1195 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 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]]. 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.Time period.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.Time period.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.Time period.WebHome]] before which the data included in this message is not available. 1202 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1154 1154 1155 1155 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message. 1156 1156 1157 1157 Derivation: 1158 1158 1159 -//BaseHeaderType// (restriction) 1160 - 1208 +* //BaseHeaderType// (restriction) 1209 +** StructureSpecificDataHeaderType 1161 1161 1162 1162 Content: 1163 1163 ... ... @@ -1165,30 +1165,31 @@ 1165 1165 1166 1166 Element Documentation: 1167 1167 1168 -|**Name**|**Type**|**Documentation** 1169 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1170 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1171 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1172 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1173 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1174 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1175 -|Structure|com: StructureSpecificDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1176 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1177 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1178 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1179 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1180 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1181 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1182 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1183 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1217 +(% style="width:930.294px" %) 1218 +|**Name**|**Type**|(% style="width:578px" %)**Documentation** 1219 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender. 1220 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not. 1221 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared. 1222 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1223 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1224 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1225 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1226 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 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]]. 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.Time period.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.Time period.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.Time period.WebHome]] before which the data included in this message is not available. 1233 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1184 1184 1185 1185 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. 1186 1186 1187 1187 Derivation: 1188 1188 1189 -//BaseHeaderType// (restriction) 1190 - 1191 - 1239 +* //BaseHeaderType// (restriction) 1240 +** StructureSpecificDataHeaderType (restriction) 1241 +*** StructureSpecificTimeSeriesDataHeaderType 1192 1192 1193 1193 Content: 1194 1194 ... ... @@ -1196,29 +1196,30 @@ 1196 1196 1197 1197 Element Documentation: 1198 1198 1199 -|**Name**|**Type**|**Documentation** 1200 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1201 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1202 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1203 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1204 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1205 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1206 -|Structure|com: StructureSpecificDat aTimeSeriesStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1207 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1208 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1209 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1210 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1211 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1212 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1213 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1214 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1249 +(% style="width:943.294px" %) 1250 +|**Name**|(% style="width:352px" %)**Type**|(% style="width:461px" %)**Documentation** 1251 +|ID|(% style="width:352px" %)com:IDType|(% style="width:461px" %)ID identifies an identification for the message, assigned by the sender. 1252 +|Test|(% style="width:352px" %)xs:boolean|(% style="width:461px" %)Test indicates whether the message is for test purposes or not. 1253 +|Prepared|(% style="width:352px" %)HeaderTimeType|(% style="width:461px" %)Prepared is the date the message was prepared. 1254 +|Sender|(% style="width:352px" %)SenderType|(% style="width:461px" %)Sender is information about the party that is transmitting the message. 1255 +|Receiver|(% style="width:352px" %)PartyType|(% style="width:461px" %)Receiver is information about the party that is the intended recipient of the message. 1256 +|com:Name|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1257 +|Structure|(% style="width:352px" %)com: StructureSpecificDataTimeSeriesStructureType|(% style="width:461px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 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.Reference metadata.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]]. 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.Time period.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.Time period.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.Time period.WebHome]] before which the data included in this message is not available. 1265 +|Source|(% style="width:352px" %)com:TextType|(% style="width:461px" %)Source provides human-readable information about the source of the data. 1215 1215 1216 -**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic reference metadata. 1267 +**GenericMetadataHeaderType: **GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]]. 1217 1217 1218 1218 Derivation: 1219 1219 1220 -//BaseHeaderType// (restriction) 1221 - 1271 +* //BaseHeaderType// (restriction) 1272 +** GenericMetadataHeaderType 1222 1222 1223 1223 Content: 1224 1224 ... ... @@ -1226,26 +1226,27 @@ 1226 1226 1227 1227 Element Documentation: 1228 1228 1229 -|**Name**|**Type**|**Documentation** 1230 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1231 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1232 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1233 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1234 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1235 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1236 -|Structure|com: GenericMetadataStruc tureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1237 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1238 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1239 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1240 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1241 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1280 +(% style="width:928.294px" %) 1281 +|**Name**|**Type**|(% style="width:554px" %)**Documentation** 1282 +|ID|com:IDType|(% style="width:554px" %)ID identifies an identification for the message, assigned by the sender. 1283 +|Test|xs:boolean|(% style="width:554px" %)Test indicates whether the message is for test purposes or not. 1284 +|Prepared|HeaderTimeType|(% style="width:554px" %)Prepared is the date the message was prepared. 1285 +|Sender|SenderType|(% style="width:554px" %)Sender is information about the party that is transmitting the message. 1286 +|Receiver|PartyType|(% style="width:554px" %)Receiver is information about the party that is the intended recipient of the message. 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.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1289 +|DataProvider|com: DataProviderReferenceType|(% style="width:554px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 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]]. 1292 +|Extracted|xs:dateTime|(% style="width:554px" %)Extracted is a time-stamp from the system rendering the data. 1293 +|Source|com:TextType|(% style="width:554px" %)Source provides human-readable information about the source of the data. 1242 1242 1243 -**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for metadata structure definition specific reference metadata messages. 1295 +**StructureSpecificMetadataHeaderType: **StructureSpecificMetadataHeaderType defines the header format for [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] specific [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] messages. 1244 1244 1245 1245 Derivation: 1246 1246 1247 -//BaseHeaderType// (restriction) 1248 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataHeaderType1299 +* //BaseHeaderType// (restriction) 1300 +** StructureSpecificMetadataHeaderType 1249 1249 1250 1250 Content: 1251 1251 ... ... @@ -1253,26 +1253,27 @@ 1253 1253 1254 1254 Element Documentation: 1255 1255 1256 -|**Name**|**Type**|**Documentation** 1257 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1258 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1259 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1260 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1261 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1262 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1263 -|Structure|com: StructureSpecificMet adataStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1264 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1265 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1266 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1267 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1268 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1308 +(% style="width:996.294px" %) 1309 +|**Name**|**Type**|(% style="width:557px" %)**Documentation** 1310 +|ID|com:IDType|(% style="width:557px" %)ID identifies an identification for the message, assigned by the sender. 1311 +|Test|xs:boolean|(% style="width:557px" %)Test indicates whether the message is for test purposes or not. 1312 +|Prepared|HeaderTimeType|(% style="width:557px" %)Prepared is the date the message was prepared. 1313 +|Sender|SenderType|(% style="width:557px" %)Sender is information about the party that is transmitting the message. 1314 +|Receiver|PartyType|(% style="width:557px" %)Receiver is information about the party that is the intended recipient of the message. 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.Reference metadata.WebHome]]. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is being used at the observation (% style="color:#e74c3c" %)level(%%). This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/[[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] will require this reference explicitly. 1317 +|DataProvider|com: DataProviderReferenceType|(% style="width:557px" %)DataProvider identifies the provider of the data for a data/[[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] message. 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]]. 1320 +|Extracted|xs:dateTime|(% style="width:557px" %)Extracted is a time-stamp from the system rendering the data. 1321 +|Source|com:TextType|(% style="width:557px" %)Source provides human-readable information about the source of the data. 1269 1269 1270 1270 **BasicHeaderType: **BasicHeaderType defines the most basic header information used in simple message exchanges. 1271 1271 1272 1272 Derivation: 1273 1273 1274 -//BaseHeaderType// (restriction) 1275 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]BasicHeaderType1327 +* //BaseHeaderType// (restriction) 1328 +** BasicHeaderType 1276 1276 1277 1277 Content: 1278 1278 ... ... @@ -1280,12 +1280,13 @@ 1280 1280 1281 1281 Element Documentation: 1282 1282 1283 -|**Name**|**Type**|**Documentation** 1284 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1285 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1286 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1287 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1288 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1336 +(% style="width:903.294px" %) 1337 +|**Name**|(% style="width:236px" %)**Type**|(% style="width:457px" %)**Documentation** 1338 +|ID|(% style="width:236px" %)com:IDType|(% style="width:457px" %)ID identifies an identification for the message, assigned by the sender. 1339 +|Test|(% style="width:236px" %)xs:boolean|(% style="width:457px" %)Test indicates whether the message is for test purposes or not. 1340 +|Prepared|(% style="width:236px" %)HeaderTimeType|(% style="width:457px" %)Prepared is the date the message was prepared. 1341 +|Sender|(% style="width:236px" %)SenderType|(% style="width:457px" %)Sender is information about the party that is transmitting the message. 1342 +|Receiver|(% style="width:236px" %)PartyType|(% style="width:457px" %)Receiver is information about the party that is the intended recipient of the message. 1289 1289 1290 1290 **PartyType: **PartyType defines the information which is sent about various parties such as senders and receivers of messages. 1291 1291 ... ... @@ -1295,25 +1295,27 @@ 1295 1295 1296 1296 Content: 1297 1297 1298 -com:Name*, Contact* 1352 +com:Name*, (% style="color:#e74c3c" %)Contact(%%)* 1299 1299 1300 -Attribute Documentation: 1354 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation: 1301 1301 1302 -|**Name**|**Type**|**Documentation** 1303 -|id|com:IDType|The id attribute holds the identification of the party. 1356 +(% style="width:739.294px" %) 1357 +|(% style="width:125px" %)**Name**|(% style="width:190px" %)**Type**|(% style="width:421px" %)**Documentation** 1358 +|(% style="width:125px" %)id|(% style="width:190px" %)com:IDType|(% style="width:421px" %)The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party. 1304 1304 1305 1305 Element Documentation: 1306 1306 1307 -|**Name**|**Type**|**Documentation** 1308 -|com:Name|com:TextType|Name is a human-readable name of the party. 1309 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message. 1362 +(% style="width:751.294px" %) 1363 +|(% style="width:134px" %)**Name**|(% style="width:183px" %)**Type**|(% style="width:431px" %)**Documentation** 1364 +|(% style="width:134px" %)com:Name|(% style="width:183px" %)com:TextType|(% style="width:431px" %)Name is a human-readable name of the party. 1365 +|(% style="width:134px" %)(% 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. 1310 1310 1311 1311 **SenderType: **SenderType extends the basic party structure to add an optional time zone declaration. 1312 1312 1313 1313 Derivation: 1314 1314 1315 -PartyType (extension) 1316 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SenderType1371 +* PartyType (extension) 1372 +** SenderType 1317 1317 1318 1318 Attributes: 1319 1319 ... ... @@ -1321,21 +1321,22 @@ 1321 1321 1322 1322 Content: 1323 1323 1324 -com:Name*, Contact*, Timezone? 1380 +com:Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone? 1325 1325 1326 -Attribute Documentation: 1382 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation: 1327 1327 1328 -|**Name**|**Type**|**Documentation** 1329 -|id|com:IDType|The id attribute holds the identification of the party. 1384 +(% style="width:824.294px" %) 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. 1330 1330 1331 1331 Element Documentation: 1332 1332 1333 1333 |**Name**|**Type**|**Documentation** 1334 1334 |com:Name|com:TextType|Name is a human-readable name of the party. 1335 -|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message. 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. 1336 1336 |Timezone|com:TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time". 1337 1337 1338 -**ContactType: **ContactType provides defines the contact information about a party. 1395 +**ContactType: **ContactType provides defines the (% style="color:#e74c3c" %)contact(%%) information about a party. 1339 1339 1340 1340 Content: 1341 1341 ... ... @@ -1344,18 +1344,16 @@ 1344 1344 Element Documentation: 1345 1345 1346 1346 |**Name**|**Type**|**Documentation** 1347 -|com:Name|com:TextType|Name contains a human-readable name for the contact. 1348 -|Department|com:TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works. 1349 -|Role|com:TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact. 1350 -|Telephone|xs:string|Telephone holds the telephone number for the contact person. 1351 -|Fax|xs:string|Fax holds the fax number for the contact person. 1352 -|X400|xs:string|X400 holds the X.400 address for the contact person. 1353 -|URI|xs:anyURI|URI holds an information URL for the contact person. 1354 -|Email|xs:string|Email holds the email address for the contact person. 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.Contact phone 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. 1355 1355 1356 -1. 1357 -11. 1358 -111. Simple Types 1413 +=== 2.1.4 Simple Types === 1359 1359 1360 1360 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. 1361 1361 ... ... @@ -1363,14 +1363,11 @@ 1363 1363 1364 1364 xs:dateTime, xs:date. 1365 1365 1366 -1. 1367 -11. Message Footer Namespace 1421 +== 2.2 Message Footer Namespace == 1368 1368 1369 1369 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1370 1370 1371 -1. 1372 -11. 1373 -111. Summary 1425 +=== 2.2.1 Summary === 1374 1374 1375 1375 Referenced Namespaces: 1376 1376 ... ... @@ -1384,15 +1384,11 @@ 1384 1384 2 Complex Types 1385 1385 1 Simple Type 1386 1386 1387 -1. 1388 -11. 1389 -111. Global Elements 1439 +=== 2.2.2 Global Elements === 1390 1390 1391 1391 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1392 1392 1393 -1. 1394 -11. 1395 -111. Complex Types 1443 +=== 2.2.3 Complex Types === 1396 1396 1397 1397 **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. 1398 1398 ... ... @@ -1403,28 +1403,28 @@ 1403 1403 Element Documentation: 1404 1404 1405 1405 |**Name**|**Type**|**Documentation** 1406 -|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. 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. 1407 1407 1408 -**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. 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. 1409 1409 1410 1410 Derivation: 1411 1411 1412 -com:StatusMessageType (restriction) 1413 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)1414 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]FooterMessageType1460 +* com:StatusMessageType (restriction) 1461 +** com:CodedStatusMessageType (extension) 1462 +*** FooterMessageType 1415 1415 1416 1416 Attributes: 1417 1417 1418 -code, severity? 1466 +[[code>>doc:sdmx:Glossary.Code.WebHome]], severity? 1419 1419 1420 1420 Content: 1421 1421 1422 1422 com:Text+ 1423 1423 1424 -Attribute Documentation: 1472 +[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation: 1425 1425 1426 1426 |**Name**|**Type**|**Documentation** 1427 -|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. 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. 1428 1428 |severity|SeverityCodeType| 1429 1429 1430 1430 Element Documentation: ... ... @@ -1432,9 +1432,7 @@ 1432 1432 |**Name**|**Type**|**Documentation** 1433 1433 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1434 1434 1435 -1. 1436 -11. 1437 -111. Simple Types 1483 +=== 2.2.4 Simple Types === 1438 1438 1439 1439 **SeverityCodeType:** 1440 1440 ... ... @@ -1445,19 +1445,4 @@ 1445 1445 |**Value**|**Documentation** 1446 1446 |Error|Error indicates the status message coresponds to an error. 1447 1447 |Warning|Warning indicates that the status message corresponds to a warning. 1448 -|Information|Information indicates that the status message corresponds to an informational message. 1449 - 1450 - 1451 - 1452 - 1453 - 1454 - 1455 - 1456 - 1457 - 1458 - 1459 - 1460 - 1461 - 1462 - 1463 - 1494 +|Information|Information indicates that the status message corresponds to an informational message.