Changes for page Part I. Message Namespace

Summary

• Page properties (3 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • SUZ.Methodology.Code.MethodologyClass[0]

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Part I. Message
	1	+Part I. Message: This contains the description of the message namespaces schemas

Tags

...	...	@@ -1,0 +1,1 @@
	1	+Category scheme|Code list|Concept scheme|Data set|Data structure definition|Dataflow|Dimension|Hierarchical code list|Metadata structure definition|Metadataflow|Reporting taxonomy|Representation|SDMX Registry|SDMX-ML|Statistical data and metadata exchange|Structural metadata

Content

...	...	@@ -4,11 +4,11 @@
4	4
5	5	= 1 Introduction =
6	6
7		-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.
	7	+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]].
8	8
9		-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/v3_1/message. Associated with this is another sub-namespace, http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted.
	9	+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/v3_1/message. Associated with this is another sub-namespace, http://www.sdmx.org/resources/sdmxml/schemas/v3_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.
10	10
11		-In general, every message in SDMX follows common format of:
	11	+In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of:
12	12
13	13	* Header
14	14	* Payload (0..n)
...	...	@@ -26,31 +26,32 @@
26	26
27	27	Referenced Namespaces:
28	28
29		-|**Namespace**|**Prefix**|
30		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
31		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|dsd|
32		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer|footer|
33		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic|metadata|
34		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/registry|registry|
35		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/structure|structure|
36		-|http://www.w3.org/2001/XMLSchema|xs|
	29	+(% style="width:973.294px" %)
	30	+|(% style="width:610px" %)**Namespace**|(% style="width:360px" %)**Prefix**
	31	+|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|(% style="width:360px" %)common
	32	+|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|(% style="width:360px" %)dsd
	33	+|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer|(% style="width:360px" %)footer
	34	+|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic|(% style="width:360px" %)metadata
	35	+|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/registry|(% style="width:360px" %)registry
	36	+|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/structure|(% style="width:360px" %)structure
	37	+|(% style="width:610px" %)http://www.w3.org/2001/XMLSchema|(% style="width:360px" %)xs
37	37
38	38	Contents:
39		-7 Global Elements
40		-16 Complex Types
	40	+7 Global Elements
	41	+16 Complex Types
41	41	1 Simple Type
42	42
43	43	=== 2.1.2 Global Elements ===
44	44
45		-**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), data and metadata constraints, data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, structure maps, representation maps, .
	46	+**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]]), data and metadata (% style="color:#e74c3c" %)constraints(%%), [[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]], structure (% style="color:#e74c3c" %)maps(%%), [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%), .
46	46
47		-**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.
	48	+**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.
48	48
49	49	**GenericMetadata (GenericMetadataType):** GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
50	50
51		-**RegistryInterface (RegistryInterfaceType):** RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
	52	+**RegistryInterface (RegistryInterfaceType):** RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services.
52	52
53		-**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.
	54	+**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.
54	54
55	55	**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.
56	56
...	...	@@ -58,24 +58,25 @@
58	58
59	59	=== 2.1.3 Complex Types ===
60	60
61		-***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.
	62	+//**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.
62	62
63	63	Content:
64	64
65		-Header, {any element with namespace of http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message}*, Footer?
	66	+Header, {any element with namespace of http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/message}, Footer?
66	66
67	67	Element Documentation:
68	68
69		-|**Name**|**Type**|**Documentation**|
70		-|Header|*BaseHeaderType*||
71		-|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
	70	+(% style="width:1007.29px" %)
	71	+|**Name**|(% style="width:192px" %)**Type**|(% style="width:662px" %)**Documentation**
	72	+|Header|(% style="width:192px" %)//BaseHeaderType//|(% style="width:662px" %)
	73	+|Footer|(% style="width:192px" %)FooterType|(% style="width:662px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
72	72
73	73	**StructureType:** StructureType defines the contents of a structure message. The payload is optional since this message may be returned from a web service with only information in the footer.
74	74
75	75	Derivation:
76	76
77		-MessageType (restriction)
78		-   StructureType
	79	+MessageType (restriction)
	80	+ StructureType
79	79
80	80	Content:
81	81	Header, Structures?, Footer?
...	...	@@ -82,34 +82,36 @@
82	82
83	83	Element Documentation:
84	84
85		-|**Name**|**Type**|**Documentation**|
86		-|Header|StructureHeaderType||
87		-|Structures|StructuresType||
88		-|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
	87	+(% style="width:1007.29px" %)
	88	+|**Name**|(% style="width:228px" %)**Type**|(% style="width:589px" %)**Documentation**
	89	+|Header|(% style="width:228px" %)StructureHeaderType|(% style="width:589px" %)
	90	+|Structures|(% style="width:228px" %)StructuresType|(% style="width:589px" %)
	91	+|Footer|(% style="width:228px" %)FooterType|(% style="width:589px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
89	89
90		-**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.
	93	+**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.
91	91
92	92	Derivation:
93	93
94		-MessageType (restriction)
95		-   StructureSpecificDataType
	97	+MessageType (restriction)
	98	+ StructureSpecificDataType
96	96
97	97	Content:
98		-Header, DataSet*, Footer?
	101	+Header, [[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]*, Footer?
99	99
100	100	Element Documentation:
101	101
102		-|**Name**|**Type**|**Documentation**|
103		-|Header|StructureSpecificDat aHeaderType||
104		-|DataSet|*DataSetType*||
105		-|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
	105	+(% style="width:1005.29px" %)
	106	+|**Name**|(% style="width:269px" %)**Type**|(% style="width:585px" %)**Documentation**
	107	+|Header|(% style="width:269px" %)StructureSpecificDat aHeaderType|(% style="width:585px" %)
	108	+|[[DataSet>>doc:sdmx:Glossary.Data set.WebHome]]|(% style="width:269px" %)//DataSetType//|(% style="width:585px" %)
	109	+|Footer|(% style="width:269px" %)FooterType|(% style="width:585px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
106	106
107	107	**GenericMetadataType:** GenericMetadataType defines the contents of a generic metadata message.
108	108
109	109	Derivation:
110	110
111		-MessageType (restriction)
112		-   GenericMetadataType
	115	+MessageType (restriction)
	116	+ GenericMetadataType
113	113
114	114	Content:
115	115	Header, MetadataSet*, Footer?
...	...	@@ -116,17 +116,18 @@
116	116
117	117	Element Documentation:
118	118
119		-|**Name**|**Type**|**Documentation**|
120		-|Header|GenericMetadataHeade rType||
121		-|MetadataSet|MetadataSetType||
122		-|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
	123	+(% style="width:1012.29px" %)
	124	+|**Name**|(% style="width:309px" %)**Type**|(% style="width:593px" %)**Documentation**
	125	+|Header|(% style="width:309px" %)GenericMetadataHeaderType|(% style="width:593px" %)
	126	+|MetadataSet|(% style="width:309px" %)MetadataSetType|(% style="width:593px" %)
	127	+|Footer|(% style="width:309px" %)FooterType|(% style="width:593px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
123	123
124	124	**RegistryInterfaceType:** This is a type which describes a structure for holding all of the various dedicated registry interface message types.
125	125
126	126	Derivation:
127	127
128		-MessageType (restriction)
129		-   RegistryInterfaceType
	133	+MessageType (restriction)
	134	+ RegistryInterfaceType
130	130
131	131	Content:
132	132	Header, (SubmitRegistrationsRequest|SubmitRegistrationsResponse|QueryRegistrationRequest|QueryRegistrationResponse|SubmitStructureRequest|SubmitStructureResponse|SubmitSubscriptionsRequest|SubmitSubscriptionsResponse|QuerySubscriptionRequest|QuerySubscriptionResponse|NotifyRegistryEvent)?, Footer?
...	...	@@ -133,28 +133,29 @@
133	133
134	134	Element Documentation:
135	135
136		-|**Name**|**Type**|**Documentation**|
137		-|Header|BasicHeaderType||
138		-|SubmitRegistrationsR equest|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.|
139		-|SubmitRegistrationsR esponse|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.|
140		-|QueryRegistrationReq uest|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.|
141		-|QueryRegistrationRes ponse|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.|
142		-|SubmitStructureReque st|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.|
143		-|SubmitStructureRespo nse|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.|
144		-|SubmitSubscriptionsR equest|SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.|
145		-|SubmitSubscriptionsR esponse|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.|
146		-|QuerySubscriptionReq uest|QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.|
147		-|QuerySubscriptionRes ponse|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.|
148		-|NotifyRegistryEvent|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.|
149		-|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
	141	+(% style="width:1029.29px" %)
	142	+|**Name**|**Type**|(% style="width:521px" %)**Documentation**
	143	+|Header|BasicHeaderType|(% style="width:521px" %)
	144	+|SubmitRegistrationsRequest|SubmitRegistrationsRequestType|(% style="width:521px" %)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.
	145	+|SubmitRegistrationsResponse|SubmitRegistrationsResponseType|(% style="width:521px" %)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.
	146	+|QueryRegistrationRequest|QueryRegistrationRequestType|(% style="width:521px" %)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.
	147	+|QueryRegistrationResponse|QueryRegistrationResponseType|(% style="width:521px" %)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.
	148	+|SubmitStructureRequest|SubmitStructureRequestType|(% style="width:521px" %)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.
	149	+|SubmitStructureResponse|SubmitStructureResponseType|(% style="width:521px" %)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.
	150	+|SubmitSubscriptionsRequest|SubmitSubscriptionsRequestType|(% style="width:521px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
	151	+|SubmitSubscriptionsResponse|SubmitSubscriptionsResponseType|(% style="width:521px" %)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.
	152	+|QuerySubscriptionRequest|QuerySubscriptionRequestType|(% style="width:521px" %)QuerySubscriptionRequest is used to query the registry for the [[subscriptions>>doc:sdmx:Glossary.Subscription.WebHome]] of a given organisation.
	153	+|QuerySubscriptionResponse|QuerySubscriptionResponseType|(% style="width:521px" %)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.
	154	+|NotifyRegistryEvent|NotifyRegistryEventType|(% style="width:521px" %)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.
	155	+|Footer|FooterType|(% style="width:521px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
150	150
151	151	**SubmitStructureRequestType:** SubmitStructureRequestType defines the structure of a registry submit structure request document.
152	152
153	153	Derivation:
154	154
155		-MessageType (restriction)
156		-   RegistryInterfaceType (restriction)
157		-         SubmitStructureRequestType
	161	+MessageType (restriction)
	162	+ RegistryInterfaceType (restriction)
	163	+ SubmitStructureRequestType
158	158
159	159	Content:
160	160	Header, SubmitStructureRequest
...	...	@@ -161,17 +161,18 @@
161	161
162	162	Element Documentation:
163	163
164		-|**Name**|**Type**|**Documentation**|
165		-|Header|BasicHeaderType||
166		-|SubmitStructureReque st|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.|
	170	+(% style="width:1044.29px" %)
	171	+|**Name**|**Type**|(% style="width:624px" %)**Documentation**
	172	+|Header|BasicHeaderType|(% style="width:624px" %)
	173	+|SubmitStructureRequest|SubmitStructureRequestType|(% style="width:624px" %)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.
167	167
168	168	**SubmitStructureResponseType:** SubmitStructureResponseType defines the structure of a registry submit registration response document.
169	169
170	170	Derivation:
171	171
172		-MessageType (restriction)
173		-   RegistryInterfaceType (restriction)
174		-         SubmitStructureResponseType
	179	+MessageType (restriction)
	180	+ RegistryInterfaceType (restriction)
	181	+ SubmitStructureResponseType
175	175
176	176	Content:
177	177	Header, SubmitStructureResponse, Footer?
...	...	@@ -178,10 +178,11 @@
178	178
179	179	Element Documentation:
180	180
181		-|**Name**|**Type**|**Documentation**|
182		-|Header|BasicHeaderType||
183		-|SubmitStructureRespo nse|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.|
184		-|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
	188	+(% style="width:1027.29px" %)
	189	+|**Name**|**Type**|(% style="width:549px" %)**Documentation**
	190	+|Header|BasicHeaderType|(% style="width:549px" %)
	191	+|SubmitStructureResponse|SubmitStructureResponseType|(% style="width:549px" %)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.
	192	+|Footer|FooterType|(% style="width:549px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
185	185
186	186	**ErrorType:** ErrorType describes the structure of an error response.
187	187
...	...	@@ -190,10 +190,11 @@
190	190
191	191	Element Documentation:
192	192
193		-|**Name**|**Type**|**Documentation**|
194		-|ErrorMessage|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.|
	201	+(% style="width:1039.29px" %)
	202	+|**Name**|**Type**|**Documentation**
	203	+|ErrorMessage|CodedStatusMessageType|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.
195	195
196		-***BaseHeaderType*:** BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
	205	+//**BaseHeaderType:**// BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
197	197
198	198	Content:
199	199	ID, Test, Prepared, Sender, Receiver*, Name*, Structure*, DataProvider?, MetadataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
...	...	@@ -200,30 +200,31 @@
200	200
201	201	Element Documentation:
202	202
203		-|**Name**|**Type**|**Documentation**|
204		-|ID|IDType|ID identifies an identification for the message, assigned by the sender.|
205		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.|
206		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.|
207		-|Sender|SenderType|Sender is information about the party that is transmitting the message.|
208		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.|
209		-|Name|TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.|
210		-|Structure|*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.|
211		-|DataProvider|DataProviderReferenc eType|DataProvider identifies the provider of the data for a data message.|
212		-|MetadataProvider|MetadataProviderRefe renceType|MetadataProvider identifies the provider of the metadata for a metadata message.|
213		-|DataSetAction|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).|
214		-|DataSetID|IDType|DataSetID provides an identifier for a contained data set.|
215		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.|
216		-|ReportingBegin|ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).|
217		-|ReportingEnd|ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).|
218		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.|
219		-|Source|TextType|Source provides human-readable information about the source of the data.|
	212	+(% style="width:1010.29px" %)
	213	+|**Name**|**Type**|(% style="width:612px" %)**Documentation**
	214	+|ID|IDType|(% style="width:612px" %)ID identifies an identification for the message, assigned by the sender.
	215	+|Test|xs:boolean|(% style="width:612px" %)Test indicates whether the message is for test purposes or not.
	216	+|Prepared|HeaderTimeType|(% style="width:612px" %)Prepared is the date the message was prepared.
	217	+|Sender|SenderType|(% style="width:612px" %)Sender is information about the party that is transmitting the message.
	218	+|Receiver|PartyType|(% style="width:612px" %)Receiver is information about the party that is the intended recipient of the message.
	219	+|Name|TextType|(% style="width:612px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	220	+|Structure|//PayloadStructureType//|(% style="width:612px" %)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.
	221	+|DataProvider|DataProviderReferenceType|(% style="width:612px" %)DataProvider identifies the provider of the data for a data message.
	222	+|MetadataProvider|MetadataProviderReferenceType|(% style="width:612px" %)MetadataProvider identifies the provider of the metadata for a metadata message.
	223	+|DataSetAction|ActionType|(% style="width:612px" %)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).
	224	+|DataSetID|IDType|(% style="width:612px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
	225	+|Extracted|xs:dateTime|(% style="width:612px" %)Extracted is a time-stamp from the system rendering the data.
	226	+|ReportingBegin|ObservationalTimePeriodType|(% style="width:612px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
	227	+|ReportingEnd|ObservationalTimePeriodType|(% style="width:612px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
	228	+|EmbargoDate|xs:dateTime|(% style="width:612px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
	229	+|Source|TextType|(% style="width:612px" %)Source provides human-readable information about the source of the data.
220	220
221		-**StructureHeaderType:** StructureHeaderType defines the structure for structural metadata messages.
	231	+**StructureHeaderType:** StructureHeaderType defines the structure for [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] messages.
222	222
223	223	Derivation:
224	224
225	225	BaseHeaderType (restriction)
226		-   StructureHeaderType
	236	+ StructureHeaderType
227	227
228	228	Content:
229	229	ID, Test, Prepared, Sender, Receiver*, Name*, Source
...	...	@@ -230,14 +230,15 @@
230	230
231	231	Element Documentation:
232	232
233		-|**Name**|**Type**|**Documentation**|
234		-|ID|IDType|ID identifies an identification for the message, assigned by the sender.|
235		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.|
236		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.|
237		-|Sender|SenderType|Sender is information about the party that is transmitting the message.|
238		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.|
239		-|Name|TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.|
240		-|Source|TextType|Source provides human-readable information about the source of the data.|
	243	+(% style="width:1018.29px" %)
	244	+|**Name**|(% style="width:200px" %)**Type**|(% style="width:706px" %)**Documentation**
	245	+|ID|(% style="width:200px" %)IDType|(% style="width:706px" %)ID identifies an identification for the message, assigned by the sender.
	246	+|Test|(% style="width:200px" %)xs:boolean|(% style="width:706px" %)Test indicates whether the message is for test purposes or not.
	247	+|Prepared|(% style="width:200px" %)HeaderTimeType|(% style="width:706px" %)Prepared is the date the message was prepared.
	248	+|Sender|(% style="width:200px" %)SenderType|(% style="width:706px" %)Sender is information about the party that is transmitting the message.
	249	+|Receiver|(% style="width:200px" %)PartyType|(% style="width:706px" %)Receiver is information about the party that is the intended recipient of the message.
	250	+|Name|(% style="width:200px" %)TextType|(% style="width:706px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	251	+|Source|(% style="width:200px" %)TextType|(% style="width:706px" %)Source provides human-readable information about the source of the data.
241	241
242	242	**StructureSpecificDataHeaderType:** StructureSpecificDataHeaderType defines the header structure for a structure specific data message.
243	243
...	...	@@ -244,7 +244,7 @@
244	244	Derivation:
245	245
246	246	BaseHeaderType (restriction)
247		-   StructureSpecificDataHeaderType
	258	+ StructureSpecificDataHeaderType
248	248
249	249	Content:
250	250	ID, Test, Prepared, Sender, Receiver*, Name*, Structure+, DataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
...	...	@@ -251,29 +251,30 @@
251	251
252	252	Element Documentation:
253	253
254		-|**Name**|**Type**|**Documentation**|
255		-|ID|IDType|ID identifies an identification for the message, assigned by the sender.|
256		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.|
257		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.|
258		-|Sender|SenderType|Sender is information about the party that is transmitting the message.|
259		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.|
260		-|Name|TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.|
261		-|Structure|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.|
262		-|DataProvider|DataProviderReferenc eType|DataProvider identifies the provider of the data for a data message.|
263		-|DataSetAction|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).|
264		-|DataSetID|IDType|DataSetID provides an identifier for a contained data set.|
265		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.|
266		-|ReportingBegin|ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data).|
267		-|ReportingEnd|ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data).|
268		-|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available.|
269		-|Source|TextType|Source provides human-readable information about the source of the data.|
	265	+(% style="width:1024.29px" %)
	266	+|**Name**|**Type**|(% style="width:622px" %)**Documentation**
	267	+|ID|IDType|(% style="width:622px" %)ID identifies an identification for the message, assigned by the sender.
	268	+|Test|xs:boolean|(% style="width:622px" %)Test indicates whether the message is for test purposes or not.
	269	+|Prepared|HeaderTimeType|(% style="width:622px" %)Prepared is the date the message was prepared.
	270	+|Sender|SenderType|(% style="width:622px" %)Sender is information about the party that is transmitting the message.
	271	+|Receiver|PartyType|(% style="width:622px" %)Receiver is information about the party that is the intended recipient of the message.
	272	+|Name|TextType|(% style="width:622px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	273	+|Structure|StructureSpecificDataStructureType|(% style="width:622px" %)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.
	274	+|DataProvider|DataProviderReferenceType|(% style="width:622px" %)DataProvider identifies the provider of the data for a data message.
	275	+|DataSetAction|ActionType|(% style="width:622px" %)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).
	276	+|DataSetID|IDType|(% style="width:622px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
	277	+|Extracted|xs:dateTime|(% style="width:622px" %)Extracted is a time-stamp from the system rendering the data.
	278	+|ReportingBegin|ObservationalTimePeriodType|(% style="width:622px" %)ReportingBegin provides the start of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
	279	+|ReportingEnd|ObservationalTimePeriodType|(% style="width:622px" %)ReportingEnd provides the end of the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] covered by the message (in the case of data).
	280	+|EmbargoDate|xs:dateTime|(% style="width:622px" %)EmbargoDate holds a [[time period>>doc:sdmx:Glossary.Time period.WebHome]] before which the data included in this message is not available.
	281	+|Source|TextType|(% style="width:622px" %)Source provides human-readable information about the source of the data.
270	270
271		-**GenericMetadataHeaderType:** GenericMetadataHeaderType defines the header format for generic reference metadata.
	283	+**GenericMetadataHeaderType:** GenericMetadataHeaderType defines the header format for generic [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]].
272	272
273	273	Derivation:
274	274
275	275	BaseHeaderType (restriction)
276		-   GenericMetadataHeaderType
	288	+ GenericMetadataHeaderType
277	277
278	278	Content:
279	279	ID, Test, Prepared, Sender, Receiver*, Name*, Structure+, MetadataProvider?, DataSetAction?, DataSetID*, Extracted?, Source
...	...	@@ -280,19 +280,20 @@
280	280
281	281	Element Documentation:
282	282
283		-|**Name**|**Type**|**Documentation**|
284		-|ID|IDType|ID identifies an identification for the message, assigned by the sender.|
285		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.|
286		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.|
287		-|Sender|SenderType|Sender is information about the party that is transmitting the message.|
288		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.|
289		-|Name|TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values.|
290		-|Structure|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.|
291		-|MetadataProvider|MetadataProviderRefe renceType|MetadataProvider identifies the provider of the metadata for a metadata message.|
292		-|DataSetAction|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).|
293		-|DataSetID|IDType|DataSetID provides an identifier for a contained data set.|
294		-|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data.|
295		-|Source|TextType|Source provides human-readable information about the source of the data.|
	295	+(% style="width:1027.29px" %)
	296	+|**Name**|**Type**|(% style="width:678px" %)**Documentation**
	297	+|ID|IDType|(% style="width:678px" %)ID identifies an identification for the message, assigned by the sender.
	298	+|Test|xs:boolean|(% style="width:678px" %)Test indicates whether the message is for test purposes or not.
	299	+|Prepared|HeaderTimeType|(% style="width:678px" %)Prepared is the date the message was prepared.
	300	+|Sender|SenderType|(% style="width:678px" %)Sender is information about the party that is transmitting the message.
	301	+|Receiver|PartyType|(% style="width:678px" %)Receiver is information about the party that is the intended recipient of the message.
	302	+|Name|TextType|(% style="width:678px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
	303	+|Structure|GenericMetadataStructureType|(% style="width:678px" %)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.
	304	+|MetadataProvider|MetadataProviderReferenceType|(% style="width:678px" %)MetadataProvider identifies the provider of the metadata for a metadata message.
	305	+|DataSetAction|ActionType|(% style="width:678px" %)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).
	306	+|DataSetID|IDType|(% style="width:678px" %)DataSetID provides an identifier for a contained [[data set>>doc:sdmx:Glossary.Data set.WebHome]].
	307	+|Extracted|xs:dateTime|(% style="width:678px" %)Extracted is a time-stamp from the system rendering the data.
	308	+|Source|TextType|(% style="width:678px" %)Source provides human-readable information about the source of the data.
296	296
297	297	**BasicHeaderType:** BasicHeaderType defines the most basic header information used in simple message exchanges.
298	298
...	...	@@ -299,7 +299,7 @@
299	299	Derivation:
300	300
301	301	BaseHeaderType (restriction)
302		-   BasicHeaderType
	315	+ BasicHeaderType
303	303
304	304	Content:
305	305	ID, Test, Prepared, Sender, Receiver
...	...	@@ -306,12 +306,13 @@
306	306
307	307	Element Documentation:
308	308
309		-|**Name**|**Type**|**Documentation**|
310		-|ID|IDType|ID identifies an identification for the message, assigned by the sender.|
311		-|Test|xs:boolean|Test indicates whether the message is for test purposes or not.|
312		-|Prepared|HeaderTimeType|Prepared is the date the message was prepared.|
313		-|Sender|SenderType|Sender is information about the party that is transmitting the message.|
314		-|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.|
	322	+(% style="width:1002.29px" %)
	323	+|**Name**|**Type**|**Documentation**
	324	+|ID|IDType|ID identifies an identification for the message, assigned by the sender.
	325	+|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
	326	+|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
	327	+|Sender|SenderType|Sender is information about the party that is transmitting the message.
	328	+|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
315	315
316	316	**PartyType:** PartyType defines the information which is sent about various parties such as senders and receivers of messages.
317	317
...	...	@@ -319,18 +319,20 @@
319	319	id
320	320
321	321	Content:
322		-Name*, Contact
	336	+Name*, (% style="color:#e74c3c" %)Contact
323	323
324		-Attribute Documentation:
	338	+[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
325	325
326		-|**Name**|**Type**|**Documentation**|
327		-|id|IDType|The id attribute holds the identification of the party.|
	340	+(% style="width:973.294px" %)
	341	+|**Name**|**Type**|**Documentation**
	342	+|id|IDType|The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
328	328
329	329	Element Documentation:
330	330
331		-|**Name**|**Type**|**Documentation**|
332		-|Name|TextType|Name is a human-readable name of the party.|
333		-|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.|
	346	+(% style="width:975.294px" %)
	347	+|(% style="width:114px" %)**Name**|(% style="width:132px" %)**Type**|(% style="width:727px" %)**Documentation**
	348	+|(% style="width:114px" %)Name|(% style="width:132px" %)TextType|(% style="width:727px" %)Name is a human-readable name of the party.
	349	+|(% style="width:114px" %)(% style="color:#e74c3c" %)Contact|(% style="width:132px" %)ContactType|(% style="width:727px" %)(% style="color:#e74c3c" %)Contact(%%) provides (% style="color:#e74c3c" %)contact(%%) information for the party in regard to the transmission of the message.
334	334
335	335	**SenderType:** SenderType extends the basic party structure to add an optional time zone declaration.
336	336
...	...	@@ -337,27 +337,29 @@
337	337	Derivation:
338	338
339	339	PartyType (extension)
340		-   SenderType
	356	+ SenderType
341	341
342	342	Attributes:
343	343	id
344	344
345	345	Content:
346		-Name*, Contact*, Timezone?
	362	+Name*, (% style="color:#e74c3c" %)Contact(%%)*, Timezone?
347	347
348		-Attribute Documentation:
	364	+[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
349	349
350		-|**Name**|**Type**|**Documentation**|
351		-|id|IDType|The id attribute holds the identification of the party.|
	366	+(% style="width:1000.29px" %)
	367	+|**Name**|**Type**|**Documentation**
	368	+|id|IDType|The id [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] holds the identification of the party.
352	352
353	353	Element Documentation:
354	354
355		-|**Name**|**Type**|**Documentation**|
356		-|Name|TextType|Name is a human-readable name of the party.|
357		-|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.|
358		-|Timezone|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".|
	372	+(% style="width:1003.29px" %)
	373	+|**Name**|**Type**|**Documentation**
	374	+|Name|TextType|Name is a human-readable name of the party.
	375	+|(%%)(% 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.
	376	+|Timezone|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".
359	359
360		-**ContactType:** ContactType provides defines the contact information about a party.
	378	+**ContactType:** ContactType provides defines the (% style="color:#e74c3c" %)contact(%%) information about a party.
361	361
362	362	Content:
363	363	Name*, Department*, Role*, (Telephone|Fax|X400|URI|Email)
...	...	@@ -364,15 +364,16 @@
364	364
365	365	Element Documentation:
366	366
367		-|**Name**|**Type**|**Documentation**|
368		-|Name|TextType|Name contains a human-readable name for the contact.|
369		-|Department|TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.|
370		-|Role|TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.|
371		-|Telephone|xs:string|Telephone holds the telephone number for the contact person.|
372		-|Fax|xs:string|Fax holds the fax number for the contact person.|
373		-|X400|xs:string|X400 holds the X.400 address for the contact person.|
374		-|URI|xs:anyURI|URI holds an information URL for the contact person.|
375		-|Email|xs:string|Email holds the email address for the contact person.|
	385	+(% style="width:1002.29px" %)
	386	+|**Name**|**Type**|**Documentation**
	387	+|Name|TextType|Name contains a human-readable name for the (% style="color:#e74c3c" %)contact(%%).
	388	+|Department|TextType|Department is designation of the organisational structure by a linguistic expression, within which the (% style="color:#e74c3c" %)contact(%%) person works.
	389	+|Role|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(%%).
	390	+|Telephone|xs:string|Telephone holds the [[telephone number>>doc:sdmx:Glossary.Contact phone number.WebHome]] for the (% style="color:#e74c3c" %)contact(%%) person.
	391	+|Fax|xs:string|Fax holds the fax number for the (% style="color:#e74c3c" %)contact(%%) person.
	392	+|X400|xs:string|X400 holds the X.400 address for the (% style="color:#e74c3c" %)contact(%%) person.
	393	+|URI|xs:anyURI|URI holds an information URL for the (% style="color:#e74c3c" %)contact(%%) person.
	394	+|Email|xs:string|Email holds the email address for the (% style="color:#e74c3c" %)contact(%%) person.
376	376
377	377	=== 2.1.4 Simple Types ===
378	378
...	...	@@ -389,13 +389,14 @@
389	389
390	390	Referenced Namespaces:
391	391
392		-|**Namespace**|**Prefix**|
393		-|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
394		-|http://www.w3.org/2001/XMLSchema|xs|
	411	+(% style="width:970.294px" %)
	412	+|(% style="width:495px" %)**Namespace**|(% style="width:472px" %)**Prefix**
	413	+|(% style="width:495px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|(% style="width:472px" %)common
	414	+|(% style="width:495px" %)http://www.w3.org/2001/XMLSchema|(% style="width:472px" %)xs
395	395
396	396	Contents:
397		-1 Global Element
398		-2 Complex Types
	417	+1 Global Element
	418	+2 Complex Types
399	399	1 Simple Type
400	400
401	401	=== 2.2.2 Global Elements ===
...	...	@@ -411,33 +411,36 @@
411	411
412	412	Element Documentation:
413	413
414		-|**Name**|**Type**|**Documentation**|
415		-|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.|
	434	+(% style="width:1005.29px" %)
	435	+|**Name**|**Type**|**Documentation**
	436	+|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.
416	416
417		-**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.
	438	+**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.
418	418
419	419	Derivation:
420	420
421	421	StatusMessageType (restriction)
422		-   CodedStatusMessageType (extension)
423		-         FooterMessageType
	443	+ CodedStatusMessageType (extension)
	444	+ FooterMessageType
424	424
425	425	Attributes:
426		-code, severity?
	447	+[[code>>doc:sdmx:Glossary.Code.WebHome]], severity?
427	427
428	428	Content:
429	429	Text+
430	430
431		-Attribute Documentation:
	452	+[[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]] Documentation:
432	432
433		-|**Name**|**Type**|**Documentation**|
434		-|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.|
435		-|severity|SeverityCodeType||
	454	+(% style="width:1008.29px" %)
	455	+|**Name**|**Type**|(% style="width:785px" %)**Documentation**
	456	+|[[code>>doc:sdmx:Glossary.Code.WebHome]]|xs:string|(% style="width:785px" %)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.
	457	+|severity|SeverityCodeType|(% style="width:785px" %)
436	436
437	437	Element Documentation:
438	438
439		-|**Name**|**Type**|**Documentation**|
440		-|Text|TextType|Text contains the text of the message, in parallel language values.|
	461	+(% style="width:1015.29px" %)
	462	+|**Name**|**Type**|(% style="width:542px" %)**Documentation**
	463	+|Text|TextType|(% style="width:542px" %)Text contains the text of the message, in parallel language values.
441	441
442	442	=== 2.2.4 Simple Types ===
443	443
...	...	@@ -447,7 +447,8 @@
447	447
448	448	Enumerations:
449	449
450		-|**Value**|**Documentation**|
451		-|Error|Error indicates the status message coresponds to an error.|
452		-|Warning|Warning indicates that the status message corresponds to a warning.|
453		-|Information|Information indicates that the status message corresponds to an informational message.|
	473	+(% style="width:1026.29px" %)
	474	+|**Value**|**Documentation**
	475	+|Error|Error indicates the status message coresponds to an error.
	476	+|Warning|Warning indicates that the status message corresponds to a warning.
	477	+|Information|Information indicates that the status message corresponds to an informational message.

SUZ.Methodology.Code.MethodologyClass[0]

index

...	...	@@ -1,1 +1,1 @@
1		-1
	1	+2