Changes for page Part I. Message Namespace

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -6,7 +6,7 @@
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	11	Various parts of the the documentation refer to stand-alone concepts, which were part of earlier draft releases but ultimately excluded from the final release of the standard.
12	12
...	...	@@ -14,7 +14,7 @@
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	19	At the core of the SDMX XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in SDMX.
20	20
...	...	@@ -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		-= 2. Schema Documentation =
	31	+1. Schema Documentation
	32	+11. Message Namespace
32	32
33		-== 2.1 Message Namespace ==
34		-
35	35	**http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message**
36	36
37		-=== 2.1.1 Summary ===
	36	+1.
	37	+11.
	38	+111. Summary
38	38
39	39	Referenced Namespaces:
40	40
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
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
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
	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
53	53
54	54	Contents:
55	55
...	...	@@ -57,7 +57,9 @@
57	57	62 Complex Types
58	58	1 Simple Type
59	59
60		-=== 2.1.2 Global Elements ===
	60	+1.
	61	+11.
	62	+111. Global Elements
61	61
62	62	**Structure (StructureType): **Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), constraints (attachment and content) data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, and structure sets.
63	63
...	...	@@ -159,7 +159,9 @@
159	159
160	160	**Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages.
161	161
162		-=== 2.1.3 Complex Types ===
	164	+1.
	165	+11.
	166	+111. Complex Types
163	163
164	164	**//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.
165	165
...	...	@@ -178,7 +178,7 @@
178	178	Derivation:
179	179
180	180	//MessageType// (restriction)
181		- StructureType
	185	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureType
182	182
183	183	Content:
184	184
...	...	@@ -186,11 +186,10 @@
186	186
187	187	Element Documentation:
188	188
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.
	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.
194	194
195	195	**GenericDataType: **GenericDataType defines the contents of a generic data message.
196	196
...	...	@@ -197,7 +197,7 @@
197	197	Derivation:
198	198
199	199	//MessageType// (restriction)
200		- GenericDataType
	203	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataType
201	201
202	202	Content:
203	203
...	...	@@ -205,19 +205,18 @@
205	205
206	206	Element Documentation:
207	207
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|(% 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.
	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.
213	213
214	214	**GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message.
215	215
216	216	Derivation:
217	217
218		-* //MessageType// (restriction)
219		-** GenericDataType (restriction)
220		-*** GenericTimeSeriesDataType
	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="-"]] GenericTimeSeriesDataType
221	221
222	222	Content:
223	223
...	...	@@ -225,18 +225,17 @@
225	225
226	226	Element Documentation:
227	227
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|(% 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.
	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.
233	233
234	234	**StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
235	235
236	236	Derivation:
237	237
238		-* //MessageType// (restriction)
239		-** StructureSpecificDataType
	239	+//MessageType// (restriction)
	240	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificDataType
240	240
241	241	Content:
242	242
...	...	@@ -244,19 +244,18 @@
244	244
245	245	Element Documentation:
246	246
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|(% style="width:247px" %)//dsd: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.
	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.
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		-** StructureSpecificDataType (restriction)
259		-*** StructureSpecificTimeSeriesDataType
	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="-"]] StructureSpecificTimeSeriesDataType
260	260
261	261	Content:
262	262
...	...	@@ -264,18 +264,17 @@
264	264
265	265	Element Documentation:
266	266
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|(% style="width:256px" %)//dsd: 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.
	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.
272	272
273	273	**GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message.
274	274
275	275	Derivation:
276	276
277		-* //MessageType// (restriction)
278		-** GenericMetadataType
	276	+//MessageType// (restriction)
	277	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericMetadataType
279	279
280	280	Content:
281	281
...	...	@@ -283,18 +283,17 @@
283	283
284	284	Element Documentation:
285	285
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.
	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.
291	291
292	292	**StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known.
293	293
294	294	Derivation:
295	295
296		-* //MessageType// (restriction)
297		-** StructureSpecificMetadataType
	294	+//MessageType// (restriction)
	295	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataType
298	298
299	299	Content:
300	300
...	...	@@ -302,18 +302,17 @@
302	302
303	303	Element Documentation:
304	304
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: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.
	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.
310	310
311	311	**RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types.
312	312
313	313	Derivation:
314	314
315		-* //MessageType// (restriction)
316		-** RegistryInterfaceType
	312	+//MessageType// (restriction)
	313	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType
317	317
318	318	Content:
319	319
...	...	@@ -321,29 +321,28 @@
321	321
322	322	Element Documentation:
323	323
324		-(% style="width:903.294px" %)
325		-|**Name**|**Type**|(% style="width:441px" %)**Documentation**
326		-|Header|BasicHeaderType|(% style="width:441px" %)
327		-|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.
328		-|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|(% style="width:441px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.
329		-|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:441px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.
330		-|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|(% style="width:441px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.
331		-|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:441px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
332		-|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|(% style="width:441px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
333		-|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|(% style="width:441px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.
334		-|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:441px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID.
335		-|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|(% style="width:441px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation.
336		-|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|(% style="width:441px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent.
337		-|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:441px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided.
338		-|ftr:Footer|ftr:FooterType|(% style="width:441px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
	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.
339	339
340	340	**SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document.
341	341
342	342	Derivation:
343	343
344		-* //MessageType// (restriction)
345		-** RegistryInterfaceType (restriction)
346		-*** SubmitRegistrationsRequestType
	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="-"]] SubmitRegistrationsRequestType
347	347
348	348	Content:
349	349
...	...	@@ -360,8 +360,8 @@
360	360	Derivation:
361	361
362	362	//MessageType// (restriction)
363		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
364		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitRegistrationsResponseType
	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="-"]] SubmitRegistrationsResponseType
365	365
366	366	Content:
367	367
...	...	@@ -379,8 +379,8 @@
379	379	Derivation:
380	380
381	381	//MessageType// (restriction)
382		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
383		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationRequestType
	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="-"]] QueryRegistrationRequestType
384	384
385	385	Content:
386	386
...	...	@@ -397,8 +397,8 @@
397	397	Derivation:
398	398
399	399	//MessageType// (restriction)
400		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
401		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QueryRegistrationResponseType
	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="-"]] QueryRegistrationResponseType
402	402
403	403	Content:
404	404
...	...	@@ -416,8 +416,8 @@
416	416	Derivation:
417	417
418	418	//MessageType// (restriction)
419		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
420		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureRequestType
	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="-"]] SubmitStructureRequestType
421	421
422	422	Content:
423	423
...	...	@@ -434,8 +434,8 @@
434	434	Derivation:
435	435
436	436	//MessageType// (restriction)
437		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
438		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType
	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="-"]] SubmitStructureResponseType
439	439
440	440	Content:
441	441
...	...	@@ -453,8 +453,8 @@
453	453	Derivation:
454	454
455	455	//MessageType// (restriction)
456		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
457		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType
	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="-"]] SubmitSubscriptionsRequestType
458	458
459	459	Content:
460	460
...	...	@@ -471,8 +471,8 @@
471	471	Derivation:
472	472
473	473	//MessageType// (restriction)
474		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
475		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType
	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="-"]] SubmitSubscriptionsResponseType
476	476
477	477	Content:
478	478
...	...	@@ -490,8 +490,8 @@
490	490	Derivation:
491	491
492	492	//MessageType// (restriction)
493		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
494		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType
	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="-"]] QuerySubscriptionRequestType
495	495
496	496	Content:
497	497
...	...	@@ -508,8 +508,8 @@
508	508	Derivation:
509	509
510	510	//MessageType// (restriction)
511		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction)
512		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType
	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="-"]] QuerySubscriptionResponseType
513	513
514	514	Content:
515	515
...	...	@@ -1025,7 +1025,7 @@
1025	1025	Derivation:
1026	1026
1027	1027	//MessageType// (restriction)
1028		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
	1024	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType
1029	1029
1030	1030	Content:
1031	1031
...	...	@@ -1100,7 +1100,7 @@
1100	1100	Derivation:
1101	1101
1102	1102	//BaseHeaderType// (restriction)
1103		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
	1099	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType
1104	1104
1105	1105	Content:
1106	1106
...	...	@@ -1249,7 +1249,7 @@
1249	1249	Derivation:
1250	1250
1251	1251	//BaseHeaderType// (restriction)
1252		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
	1248	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType
1253	1253
1254	1254	Content:
1255	1255
...	...	@@ -1276,7 +1276,7 @@
1276	1276	Derivation:
1277	1277
1278	1278	//BaseHeaderType// (restriction)
1279		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
	1275	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType
1280	1280
1281	1281	Content:
1282	1282
...	...	@@ -1317,7 +1317,7 @@
1317	1317	Derivation:
1318	1318
1319	1319	PartyType (extension)
1320		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
	1316	+ [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType
1321	1321
1322	1322	Attributes:
1323	1323
...	...	@@ -1414,8 +1414,8 @@
1414	1414	Derivation:
1415	1415
1416	1416	com:StatusMessageType (restriction)
1417		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension)
1418		- [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType
	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="-"]] FooterMessageType
1419	1419
1420	1420	Attributes:
1421	1421