Changes for page Part I. Message Namespace
Last modified by Artur on 2025/09/10 11:19
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 -1. Schema Documentation 32 -11. Message Namespace 31 += 2. Schema Documentation = 33 33 33 +== 2.1 Message Namespace == 34 + 34 34 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message** 35 35 36 -1. 37 -11. 38 -111. Summary 37 +=== 2.1.1 Summary === 39 39 40 40 Referenced Namespaces: 41 41 42 -|**Namespace**|**Prefix** 43 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com 44 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|dat 45 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|dsd 46 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|ftr 47 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|rep 48 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|msd 49 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|qry 50 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|ref 51 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|str 52 -|http:~/~/www.w3.org/2001/XMLSchema|xs 41 +(% style="width:788.294px" %) 42 +|(% style="width:612px" %)**Namespace**|(% style="width:173px" %)**Prefix** 43 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|(% style="width:173px" %)com 44 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|(% style="width:173px" %)dat 45 +|(% style="width:612px" %)http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|(% style="width:173px" %)dsd 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 53 53 54 54 Contents: 55 55 ... ... @@ -57,9 +57,7 @@ 57 57 62 Complex Types 58 58 1 Simple Type 59 59 60 -1. 61 -11. 62 -111. Global Elements 60 +=== 2.1.2 Global Elements === 63 63 64 64 **Structure (StructureType): **Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), constraints (attachment and content) data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, and structure sets. 65 65 ... ... @@ -161,9 +161,7 @@ 161 161 162 162 **Error (ErrorType): **Error is used to communicate that an error has occurred when responding to a request in an non-registry environment. The content will be a collection of error messages. 163 163 164 -1. 165 -11. 166 -111. Complex Types 162 +=== 2.1.3 Complex Types === 167 167 168 168 **//MessageType//: **MessageType is an abstract type which is used by all of the messages, to allow inheritance of common features. Every message consists of a mandatory header, followed by optional payload (which may occur multiple times), and finally an optional footer section for conveying error, warning, and informational messages. 169 169 ... ... @@ -182,7 +182,7 @@ 182 182 Derivation: 183 183 184 184 //MessageType// (restriction) 185 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureType181 + StructureType 186 186 187 187 Content: 188 188 ... ... @@ -190,10 +190,11 @@ 190 190 191 191 Element Documentation: 192 192 193 -|**Name**|**Type**|**Documentation** 194 -|Header|StructureHeaderType| 195 -|Structures|str:StructuresType| 196 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 189 +(% style="width:856.294px" %) 190 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:455px" %)**Documentation** 191 +|Header|(% style="width:210px" %)StructureHeaderType|(% style="width:455px" %) 192 +|Structures|(% style="width:210px" %)str:StructuresType|(% style="width:455px" %) 193 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:455px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 197 197 198 198 **GenericDataType: **GenericDataType defines the contents of a generic data message. 199 199 ... ... @@ -200,7 +200,7 @@ 200 200 Derivation: 201 201 202 202 //MessageType// (restriction) 203 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType200 + GenericDataType 204 204 205 205 Content: 206 206 ... ... @@ -208,18 +208,19 @@ 208 208 209 209 Element Documentation: 210 210 211 -|**Name**|**Type**|**Documentation** 212 -|Header|GenericDataHeaderTyp e| 213 -|DataSet|dat:DataSetType| 214 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 208 +(% style="width:847.294px" %) 209 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:450px" %)**Documentation** 210 +|Header|(% style="width:227px" %)GenericDataHeaderTyp e|(% style="width:450px" %) 211 +|DataSet|(% style="width:227px" %)dat:DataSetType|(% style="width:450px" %) 212 +|ftr:Footer|(% style="width:227px" %)ftr:FooterType|(% style="width:450px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 215 215 216 216 **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message. 217 217 218 218 Derivation: 219 219 220 -//MessageType// (restriction) 221 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType (restriction)222 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericTimeSeriesDataType218 +* //MessageType// (restriction) 219 +** GenericDataType (restriction) 220 +*** GenericTimeSeriesDataType 223 223 224 224 Content: 225 225 ... ... @@ -227,17 +227,18 @@ 227 227 228 228 Element Documentation: 229 229 230 -|**Name**|**Type**|**Documentation** 231 -|Header|GenericTimeSeriesDat aHeaderType| 232 -|DataSet|dat: TimeSeriesDataSetTyp e| 233 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 228 +(% style="width:856.294px" %) 229 +|**Name**|(% style="width:239px" %)**Type**|(% style="width:458px" %)**Documentation** 230 +|Header|(% style="width:239px" %)GenericTimeSeriesDat aHeaderType|(% style="width:458px" %) 231 +|DataSet|(% style="width:239px" %)dat: TimeSeriesDataSetTyp e|(% style="width:458px" %) 232 +|ftr:Footer|(% style="width:239px" %)ftr:FooterType|(% style="width:458px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 234 234 235 235 **StructureSpecificDataType: **StructureSpecificDataType defines the structure of the structure specific data message. Note that the data set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 236 236 237 237 Derivation: 238 238 239 -//MessageType// (restriction) 240 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType238 +* //MessageType// (restriction) 239 +** StructureSpecificDataType 241 241 242 242 Content: 243 243 ... ... @@ -245,18 +245,19 @@ 245 245 246 246 Element Documentation: 247 247 248 -|**Name**|**Type**|**Documentation** 249 -|Header|StructureSpecificDat aHeaderType| 250 -|DataSet|//dsd:DataSetType//| 251 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 247 +(% style="width:828.294px" %) 248 +|**Name**|(% style="width:247px" %)**Type**|(% style="width:420px" %)**Documentation** 249 +|Header|(% style="width:247px" %)StructureSpecificDat aHeaderType|(% style="width:420px" %) 250 +|DataSet|(% 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. 252 252 253 253 **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message. 254 254 255 255 Derivation: 256 256 257 -//MessageType// (restriction) 258 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType (restriction)259 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificTimeSeriesDataType257 +* //MessageType// (restriction) 258 +** StructureSpecificDataType (restriction) 259 +*** StructureSpecificTimeSeriesDataType 260 260 261 261 Content: 262 262 ... ... @@ -264,17 +264,18 @@ 264 264 265 265 Element Documentation: 266 266 267 -|**Name**|**Type**|**Documentation** 268 -|Header|StructureSpecificTim eSeriesDataHeaderTyp e| 269 -|DataSet|//dsd: TimeSeriesDataSetTyp e//| 270 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 267 +(% style="width:839.294px" %) 268 +|**Name**|(% style="width:256px" %)**Type**|(% style="width:434px" %)**Documentation** 269 +|Header|(% style="width:256px" %)StructureSpecificTim eSeriesDataHeaderTyp e|(% style="width:434px" %) 270 +|DataSet|(% 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. 271 271 272 272 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message. 273 273 274 274 Derivation: 275 275 276 -//MessageType// (restriction) 277 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericMetadataType277 +* //MessageType// (restriction) 278 +** GenericMetadataType 278 278 279 279 Content: 280 280 ... ... @@ -282,17 +282,18 @@ 282 282 283 283 Element Documentation: 284 284 285 -|**Name**|**Type**|**Documentation** 286 -|Header|GenericMetadataHeade rType| 287 -|MetadataSet|rep:MetadataSetType| 288 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 286 +(% style="width:836.294px" %) 287 +|(% style="width:181px" %)**Name**|(% style="width:225px" %)**Type**|(% style="width:427px" %)**Documentation** 288 +|(% style="width:181px" %)Header|(% style="width:225px" %)GenericMetadataHeade rType|(% style="width:427px" %) 289 +|(% style="width:181px" %)MetadataSet|(% style="width:225px" %)rep:MetadataSetType|(% style="width:427px" %) 290 +|(% style="width:181px" %)ftr:Footer|(% style="width:225px" %)ftr:FooterType|(% style="width:427px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 289 289 290 290 **StructureSpecificMetadataType: **StructureSpecificMetadataType defines the structure of a structure specific metadata message. Note that the metadata set payload type is abstract, and therefore it will have to be assigned a type in an instance. This type must be derived from the base type referenced. This base type defines a general structure which can be followed to allow for generic processing of the data even if the exact details of the data structure specific format are not known. 291 291 292 292 Derivation: 293 293 294 -//MessageType// (restriction) 295 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataType296 +* //MessageType// (restriction) 297 +** StructureSpecificMetadataType 296 296 297 297 Content: 298 298 ... ... @@ -300,17 +300,18 @@ 300 300 301 301 Element Documentation: 302 302 303 -|**Name**|**Type**|**Documentation** 304 -|Header|StructureSpecificMet adataHeaderType| 305 -|MetadataSet|//msd:MetadataSetType//| 306 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 305 +(% style="width:841.294px" %) 306 +|(% style="width:160px" %)**Name**|(% style="width:250px" %)**Type**|(% style="width:428px" %)**Documentation** 307 +|(% style="width:160px" %)Header|(% style="width:250px" %)StructureSpecificMet adataHeaderType|(% style="width:428px" %) 308 +|(% style="width:160px" %)MetadataSet|(% style="width:250px" %)//msd:MetadataSetType//|(% style="width:428px" %) 309 +|(% style="width:160px" %)ftr:Footer|(% style="width:250px" %)ftr:FooterType|(% style="width:428px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 307 307 308 308 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. 309 309 310 310 Derivation: 311 311 312 -//MessageType// (restriction) 313 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType315 +* //MessageType// (restriction) 316 +** RegistryInterfaceType 314 314 315 315 Content: 316 316 ... ... @@ -318,83 +318,84 @@ 318 318 319 319 Element Documentation: 320 320 321 -|**Name**|**Type**|**Documentation** 322 -|Header|BasicHeaderType| 323 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 324 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 325 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 326 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 327 -|SubmitStructureReque st|ref: SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 328 -|SubmitStructureRespo nse|ref: SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 329 -|SubmitSubscriptionsR equest|ref: SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 330 -|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 331 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 332 -|QuerySubscriptionRes ponse|ref: QuerySubscriptionRes ponseType|QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 333 -|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 334 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 324 +(% style="width:903.294px" %) 325 +|**Name**|**Type**|(% style="width:441px" %)**Documentation** 326 +|Header|BasicHeaderType|(% style="width:441px" %) 327 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:441px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set 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. 335 335 336 336 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 337 337 338 338 Derivation: 339 339 340 -//MessageType// (restriction) 341 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)342 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsRequestType344 +* //MessageType// (restriction) 345 +** RegistryInterfaceType (restriction) 346 +*** SubmitRegistrationsRequestType 343 343 344 344 Content: 345 345 346 -Header, SubmitRegistrationsRequest 350 +* Header, SubmitRegistrationsRequest 351 +* Element Documentation: 347 347 348 -Element Documentation: 353 +(% style="width:844.294px" %) 354 +|**Name**|**Type**|(% style="width:377px" %)**Documentation** 355 +|Header|BasicHeaderType|(% style="width:377px" %) 356 +|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|(% style="width:377px" %)SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 349 349 350 -|**Name**|**Type**|**Documentation** 351 -|Header|BasicHeaderType| 352 -|SubmitRegistrationsR equest|ref: SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services. 353 - 354 354 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 355 355 356 356 Derivation: 357 357 358 -//MessageType// (restriction) 359 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)360 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsResponseType362 +* //MessageType// (restriction) 363 +** RegistryInterfaceType (restriction) 364 +*** SubmitRegistrationsResponseType 361 361 362 362 Content: 363 363 364 -Header, SubmitRegistrationsResponse, ftr:Footer? 368 +* Header, SubmitRegistrationsResponse, ftr:Footer? 369 +* Element Documentation: 365 365 366 -Element Documentation: 371 +(% style="width:847.294px" %) 372 +|**Name**|(% style="width:210px" %)**Type**|(% style="width:408px" %)**Documentation** 373 +|Header|(% style="width:210px" %)BasicHeaderType|(% style="width:408px" %) 374 +|SubmitRegistrationsR esponse|(% style="width:210px" %)ref: SubmitRegistrationsR esponseType|(% style="width:408px" %)SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 375 +|ftr:Footer|(% style="width:210px" %)ftr:FooterType|(% style="width:408px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 367 367 368 -|**Name**|**Type**|**Documentation** 369 -|Header|BasicHeaderType| 370 -|SubmitRegistrationsR esponse|ref: SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service. 371 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 372 - 373 373 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 374 374 375 375 Derivation: 376 376 377 -//MessageType// (restriction) 378 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)379 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationRequestType381 +* //MessageType// (restriction) 382 +** RegistryInterfaceType (restriction) 383 +*** QueryRegistrationRequestType 380 380 381 381 Content: 382 382 383 -Header, QueryRegistrationRequest 387 +* Header, QueryRegistrationRequest 388 +* Element Documentation: 384 384 385 -Element Documentation: 390 +(% style="width:847.294px" %) 391 +|**Name**|**Type**|(% style="width:397px" %)**Documentation** 392 +|Header|BasicHeaderType|(% style="width:397px" %) 393 +|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|(% style="width:397px" %)QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 386 386 387 -|**Name**|**Type**|**Documentation** 388 -|Header|BasicHeaderType| 389 -|QueryRegistrationReq uest|ref: QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys. 390 - 391 391 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 392 392 393 393 Derivation: 394 394 395 -//MessageType// (restriction) 396 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)397 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationResponseType399 +* //MessageType// (restriction) 400 +** RegistryInterfaceType (restriction) 401 +*** QueryRegistrationResponseType 398 398 399 399 Content: 400 400 ... ... @@ -402,18 +402,19 @@ 402 402 403 403 Element Documentation: 404 404 405 -|**Name**|**Type**|**Documentation** 406 -|Header|BasicHeaderType| 407 -|QueryRegistrationRes ponse|ref: QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 408 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 409 +(% style="width:856.294px" %) 410 +|**Name**|(% style="width:235px" %)**Type**|(% style="width:407px" %)**Documentation** 411 +|Header|(% style="width:235px" %)BasicHeaderType|(% style="width:407px" %) 412 +|QueryRegistrationRes ponse|(% style="width:235px" %)ref: QueryRegistrationRes ponseType|(% style="width:407px" %)QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned. 413 +|ftr:Footer|(% style="width:235px" %)ftr:FooterType|(% style="width:407px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 409 409 410 410 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 411 411 412 412 Derivation: 413 413 414 -//MessageType// (restriction) 415 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)416 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureRequestType419 +* //MessageType// (restriction) 420 +** RegistryInterfaceType (restriction) 421 +*** SubmitStructureRequestType 417 417 418 418 Content: 419 419 ... ... @@ -430,8 +430,8 @@ 430 430 Derivation: 431 431 432 432 //MessageType// (restriction) 433 - 434 - 438 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 439 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitStructureResponseType 435 435 436 436 Content: 437 437 ... ... @@ -449,8 +449,8 @@ 449 449 Derivation: 450 450 451 451 //MessageType// (restriction) 452 - 453 - 457 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 458 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsRequestType 454 454 455 455 Content: 456 456 ... ... @@ -467,8 +467,8 @@ 467 467 Derivation: 468 468 469 469 //MessageType// (restriction) 470 - 471 - 475 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 476 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SubmitSubscriptionsResponseType 472 472 473 473 Content: 474 474 ... ... @@ -486,8 +486,8 @@ 486 486 Derivation: 487 487 488 488 //MessageType// (restriction) 489 - 490 - 494 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 495 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionRequestType 491 491 492 492 Content: 493 493 ... ... @@ -504,8 +504,8 @@ 504 504 Derivation: 505 505 506 506 //MessageType// (restriction) 507 - 508 - 512 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] RegistryInterfaceType (restriction) 513 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] QuerySubscriptionResponseType 509 509 510 510 Content: 511 511 ... ... @@ -1021,7 +1021,7 @@ 1021 1021 Derivation: 1022 1022 1023 1023 //MessageType// (restriction) 1024 - 1029 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] CustomTypeSchemeQueryType 1025 1025 1026 1026 Content: 1027 1027 ... ... @@ -1096,7 +1096,7 @@ 1096 1096 Derivation: 1097 1097 1098 1098 //BaseHeaderType// (restriction) 1099 - 1104 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] GenericDataHeaderType 1100 1100 1101 1101 Content: 1102 1102 ... ... @@ -1245,7 +1245,7 @@ 1245 1245 Derivation: 1246 1246 1247 1247 //BaseHeaderType// (restriction) 1248 - 1253 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType 1249 1249 1250 1250 Content: 1251 1251 ... ... @@ -1272,7 +1272,7 @@ 1272 1272 Derivation: 1273 1273 1274 1274 //BaseHeaderType// (restriction) 1275 - 1280 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType 1276 1276 1277 1277 Content: 1278 1278 ... ... @@ -1313,7 +1313,7 @@ 1313 1313 Derivation: 1314 1314 1315 1315 PartyType (extension) 1316 - 1321 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1317 1317 1318 1318 Attributes: 1319 1319 ... ... @@ -1410,8 +1410,8 @@ 1410 1410 Derivation: 1411 1411 1412 1412 com:StatusMessageType (restriction) 1413 - 1414 - 1418 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1419 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1415 1415 1416 1416 Attributes: 1417 1417