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
-
... ... @@ -38,17 +38,18 @@ 38 38 39 39 Referenced Namespaces: 40 40 41 -|**Namespace**|**Prefix** 42 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com 43 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/generic|dat 44 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/data/structurespecific|dsd 45 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer|ftr 46 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic|rep 47 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/structurespecific|msd 48 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/query|qry 49 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/registry|ref 50 -|http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/structure|str 51 -|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 52 52 53 53 Contents: 54 54 ... ... @@ -56,9 +56,7 @@ 56 56 62 Complex Types 57 57 1 Simple Type 58 58 59 -1. 60 -11. 61 -111. Global Elements 60 +=== 2.1.2 Global Elements === 62 62 63 63 **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. 64 64 ... ... @@ -160,9 +160,7 @@ 160 160 161 161 **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. 162 162 163 -1. 164 -11. 165 -111. Complex Types 162 +=== 2.1.3 Complex Types === 166 166 167 167 **//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. 168 168 ... ... @@ -181,7 +181,7 @@ 181 181 Derivation: 182 182 183 183 //MessageType// (restriction) 184 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureType181 + StructureType 185 185 186 186 Content: 187 187 ... ... @@ -189,10 +189,11 @@ 189 189 190 190 Element Documentation: 191 191 192 -|**Name**|**Type**|**Documentation** 193 -|Header|StructureHeaderType| 194 -|Structures|str:StructuresType| 195 -|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. 196 196 197 197 **GenericDataType: **GenericDataType defines the contents of a generic data message. 198 198 ... ... @@ -199,7 +199,7 @@ 199 199 Derivation: 200 200 201 201 //MessageType// (restriction) 202 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType200 + GenericDataType 203 203 204 204 Content: 205 205 ... ... @@ -207,18 +207,19 @@ 207 207 208 208 Element Documentation: 209 209 210 -|**Name**|**Type**|**Documentation** 211 -|Header|GenericDataHeaderTyp e| 212 -|DataSet|dat:DataSetType| 213 -|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. 214 214 215 215 **GenericTimeSeriesDataType: **GenericTimeSeriesDataType defines the structure of the generic time series data message. 216 216 217 217 Derivation: 218 218 219 -//MessageType// (restriction) 220 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataType (restriction)221 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericTimeSeriesDataType218 +* //MessageType// (restriction) 219 +** GenericDataType (restriction) 220 +*** GenericTimeSeriesDataType 222 222 223 223 Content: 224 224 ... ... @@ -226,17 +226,18 @@ 226 226 227 227 Element Documentation: 228 228 229 -|**Name**|**Type**|**Documentation** 230 -|Header|GenericTimeSeriesDat aHeaderType| 231 -|DataSet|dat: TimeSeriesDataSetTyp e| 232 -|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. 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 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType238 +* //MessageType// (restriction) 239 +** StructureSpecificDataType 240 240 241 241 Content: 242 242 ... ... @@ -244,18 +244,19 @@ 244 244 245 245 Element Documentation: 246 246 247 -|**Name**|**Type**|**Documentation** 248 -|Header|StructureSpecificDat aHeaderType| 249 -|DataSet|//dsd:DataSetType//| 250 -|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. 251 251 252 252 **StructureSpecificTimeSeriesDataType: **StructureSpecificTimeSeriesDataType defines the structure of the structure specific time series data message. 253 253 254 254 Derivation: 255 255 256 -//MessageType// (restriction) 257 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificDataType (restriction)258 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificTimeSeriesDataType257 +* //MessageType// (restriction) 258 +** StructureSpecificDataType (restriction) 259 +*** StructureSpecificTimeSeriesDataType 259 259 260 260 Content: 261 261 ... ... @@ -263,17 +263,18 @@ 263 263 264 264 Element Documentation: 265 265 266 -|**Name**|**Type**|**Documentation** 267 -|Header|StructureSpecificTim eSeriesDataHeaderTyp e| 268 -|DataSet|//dsd: TimeSeriesDataSetTyp e//| 269 -|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. 270 270 271 271 **GenericMetadataType: **GenericMetadataType defines the contents of a generic metadata message. 272 272 273 273 Derivation: 274 274 275 -//MessageType// (restriction) 276 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericMetadataType277 +* //MessageType// (restriction) 278 +** GenericMetadataType 277 277 278 278 Content: 279 279 ... ... @@ -281,17 +281,18 @@ 281 281 282 282 Element Documentation: 283 283 284 -|**Name**|**Type**|**Documentation** 285 -|Header|GenericMetadataHeade rType| 286 -|MetadataSet|rep:MetadataSetType| 287 -|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. 288 288 289 289 **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. 290 290 291 291 Derivation: 292 292 293 -//MessageType// (restriction) 294 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]StructureSpecificMetadataType296 +* //MessageType// (restriction) 297 +** StructureSpecificMetadataType 295 295 296 296 Content: 297 297 ... ... @@ -299,17 +299,18 @@ 299 299 300 300 Element Documentation: 301 301 302 -|**Name**|**Type**|**Documentation** 303 -|Header|StructureSpecificMet adataHeaderType| 304 -|MetadataSet|//msd:MetadataSetType//| 305 -|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. 306 306 307 307 **RegistryInterfaceType: **This is a type which describes a structure for holding all of the various dedicated registry interface message types. 308 308 309 309 Derivation: 310 310 311 -//MessageType// (restriction) 312 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType315 +* //MessageType// (restriction) 316 +** RegistryInterfaceType 313 313 314 314 Content: 315 315 ... ... @@ -317,83 +317,84 @@ 317 317 318 318 Element Documentation: 319 319 320 -|**Name**|**Type**|**Documentation** 321 -|Header|BasicHeaderType| 322 -|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. 323 -|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. 324 -|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. 325 -|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. 326 -|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. 327 -|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. 328 -|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. 329 -|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. 330 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 331 -|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. 332 -|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. 333 -|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. 334 334 335 335 **SubmitRegistrationsRequestType: **SubmitRegistrationsRequestType defines the structure of a registry submit registration requests document. 336 336 337 337 Derivation: 338 338 339 -//MessageType// (restriction) 340 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)341 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsRequestType344 +* //MessageType// (restriction) 345 +** RegistryInterfaceType (restriction) 346 +*** SubmitRegistrationsRequestType 342 342 343 343 Content: 344 344 345 -Header, SubmitRegistrationsRequest 350 +* Header, SubmitRegistrationsRequest 351 +* Element Documentation: 346 346 347 -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. 348 348 349 -|**Name**|**Type**|**Documentation** 350 -|Header|BasicHeaderType| 351 -|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. 352 - 353 353 **SubmitRegistrationsResponseType: **SubmitRegistrationsResponseType defines the structure of a registry submit registration response document. 354 354 355 355 Derivation: 356 356 357 -//MessageType// (restriction) 358 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)359 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitRegistrationsResponseType362 +* //MessageType// (restriction) 363 +** RegistryInterfaceType (restriction) 364 +*** SubmitRegistrationsResponseType 360 360 361 361 Content: 362 362 363 -Header, SubmitRegistrationsResponse, ftr:Footer? 368 +* Header, SubmitRegistrationsResponse, ftr:Footer? 369 +* Element Documentation: 364 364 365 -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. 366 366 367 -|**Name**|**Type**|**Documentation** 368 -|Header|BasicHeaderType| 369 -|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. 370 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 371 - 372 372 **QueryRegistrationRequestType: **QueryRegistrationRequestType defines the structure of a registry query registration request document. 373 373 374 374 Derivation: 375 375 376 -//MessageType// (restriction) 377 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)378 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationRequestType381 +* //MessageType// (restriction) 382 +** RegistryInterfaceType (restriction) 383 +*** QueryRegistrationRequestType 379 379 380 380 Content: 381 381 382 -Header, QueryRegistrationRequest 387 +* Header, QueryRegistrationRequest 388 +* Element Documentation: 383 383 384 -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. 385 385 386 -|**Name**|**Type**|**Documentation** 387 -|Header|BasicHeaderType| 388 -|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. 389 - 390 390 **QueryRegistrationResponseType: **SubmitRegistrationRequestType defines the structure of a registry submit registration response document. 391 391 392 392 Derivation: 393 393 394 -//MessageType// (restriction) 395 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)396 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QueryRegistrationResponseType399 +* //MessageType// (restriction) 400 +** RegistryInterfaceType (restriction) 401 +*** QueryRegistrationResponseType 397 397 398 398 Content: 399 399 ... ... @@ -401,18 +401,19 @@ 401 401 402 402 Element Documentation: 403 403 404 -|**Name**|**Type**|**Documentation** 405 -|Header|BasicHeaderType| 406 -|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. 407 -|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. 408 408 409 409 **SubmitStructureRequestType: **SubmitStructureRequestType defines the structure of a registry submit structure request document. 410 410 411 411 Derivation: 412 412 413 -//MessageType// (restriction) 414 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)415 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureRequestType419 +* //MessageType// (restriction) 420 +** RegistryInterfaceType (restriction) 421 +*** SubmitStructureRequestType 416 416 417 417 Content: 418 418 ... ... @@ -420,629 +420,630 @@ 420 420 421 421 Element Documentation: 422 422 423 -|**Name**|**Type**|**Documentation** 424 -|Header|BasicHeaderType| 425 -|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. 429 +(% style="width:870.294px" %) 430 +|**Name**|**Type**|(% style="width:453px" %)**Documentation** 431 +|Header|BasicHeaderType|(% style="width:453px" %) 432 +|SubmitStructureReque st|ref: SubmitStructureReque stType|(% style="width:453px" %)SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information. 426 426 427 427 **SubmitStructureResponseType: **SubmitStructureResponseType defines the structure of a registry submit registration response document. 428 428 429 429 Derivation: 430 430 431 -//MessageType// (restriction) 432 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)433 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitStructureResponseType438 +* //MessageType// (restriction) 439 +** RegistryInterfaceType (restriction) 440 +*** SubmitStructureResponseType 434 434 435 435 Content: 436 436 437 -Header, SubmitStructureResponse, ftr:Footer? 444 +* Header, SubmitStructureResponse, ftr:Footer? 445 +* Element Documentation: 438 438 439 -Element Documentation: 447 +(% style="width:835.294px" %) 448 +|**Name**|(% style="width:246px" %)**Type**|(% style="width:366px" %)**Documentation** 449 +|Header|(% style="width:246px" %)BasicHeaderType|(% style="width:366px" %) 450 +|SubmitStructureRespo nse|(% style="width:246px" %)ref: SubmitStructureRespo nseType|(% style="width:366px" %)SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant. 451 +|ftr:Footer|(% style="width:246px" %)ftr:FooterType|(% style="width:366px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 440 440 441 -|**Name**|**Type**|**Documentation** 442 -|Header|BasicHeaderType| 443 -|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. 444 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 445 - 446 446 **SubmitSubscriptionsRequestType: **SubmitSubscriptionsRequestType defines the structure of a registry submit subscription request document. 447 447 448 448 Derivation: 449 449 450 -//MessageType// (restriction) 451 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)452 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsRequestType457 +* //MessageType// (restriction) 458 +** RegistryInterfaceType (restriction) 459 +*** SubmitSubscriptionsRequestType 453 453 454 454 Content: 455 455 456 -Header, SubmitSubscriptionsRequest 463 +* Header, SubmitSubscriptionsRequest 464 +* Element Documentation: 457 457 458 -Element Documentation: 466 +(% style="width:832.294px" %) 467 +|**Name**|(% style="width:227px" %)**Type**|(% style="width:319px" %)**Documentation** 468 +|Header|(% style="width:227px" %)BasicHeaderType|(% style="width:319px" %) 469 +|SubmitSubscriptionsR equest|(% style="width:227px" %)ref: SubmitSubscriptionsR equestType|(% style="width:319px" %)SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources. 459 459 460 -|**Name**|**Type**|**Documentation** 461 -|Header|BasicHeaderType| 462 -|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. 463 - 464 464 **SubmitSubscriptionsResponseType: **SubmitSubscriptionsResponseType defines the structure of a registry submit subscription response document. 465 465 466 466 Derivation: 467 467 468 -//MessageType// (restriction) 469 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)470 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]SubmitSubscriptionsResponseType475 +* //MessageType// (restriction) 476 +** RegistryInterfaceType (restriction) 477 +*** SubmitSubscriptionsResponseType 471 471 472 472 Content: 473 473 474 -Header, SubmitSubscriptionsResponse, ftr:Footer? 481 +* Header, SubmitSubscriptionsResponse, ftr:Footer? 482 +* Element Documentation: 475 475 476 -Element Documentation: 484 +(% style="width:843.294px" %) 485 +|**Name**|**Type**|(% style="width:362px" %)**Documentation** 486 +|Header|BasicHeaderType|(% style="width:362px" %) 487 +|SubmitSubscriptionsR esponse|ref: SubmitSubscriptionsR esponseType|(% style="width:362px" %)SubmitSubscriptionsResponse is the response to a submit subscriptions request. It contains information which describes the success or failure of each subscription request, providing any error messages in the event of failure. If successful, it returns the registry URN of the subscription, and the subscriber-assigned ID. 488 +|ftr:Footer|ftr:FooterType|(% style="width:362px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 477 477 478 -|**Name**|**Type**|**Documentation** 479 -|Header|BasicHeaderType| 480 -|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. 481 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 482 - 483 483 **QuerySubscriptionRequestType: **QuerySubscriptionRequestType defines the structure of a registry query subscription request document. 484 484 485 485 Derivation: 486 486 487 -//MessageType// (restriction) 488 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)489 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionRequestType494 +* //MessageType// (restriction) 495 +** RegistryInterfaceType (restriction) 496 +*** QuerySubscriptionRequestType 490 490 491 491 Content: 492 492 493 -Header, QuerySubscriptionRequest 500 +* Header, QuerySubscriptionRequest 501 +* Element Documentation: 494 494 495 -Element Documentation: 503 +(% style="width:839.294px" %) 504 +|(% style="width:230px" %)**Name**|(% style="width:254px" %)**Type**|(% style="width:352px" %)**Documentation** 505 +|(% style="width:230px" %)Header|(% style="width:254px" %)BasicHeaderType|(% style="width:352px" %) 506 +|(% style="width:230px" %)QuerySubscriptionReq uest|(% style="width:254px" %)ref: QuerySubscriptionReq uestType|(% style="width:352px" %)QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 496 496 497 -|**Name**|**Type**|**Documentation** 498 -|Header|BasicHeaderType| 499 -|QuerySubscriptionReq uest|ref: QuerySubscriptionReq uestType|QuerySubscriptionRequest is used to query the registry for the subscriptions of a given organisation. 500 - 501 501 **QuerySubscriptionResponseType: **QuerySubscriptionResponseType defines the structure of a registry query subscription response document. 502 502 503 503 Derivation: 504 504 505 -//MessageType// (restriction) 506 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]RegistryInterfaceType (restriction)507 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]QuerySubscriptionResponseType512 +* //MessageType// (restriction) 513 +** RegistryInterfaceType (restriction) 514 +*** QuerySubscriptionResponseType 508 508 509 509 Content: 510 510 511 -Header, QuerySubscriptionResponse, ftr:Footer? 518 +* Header, QuerySubscriptionResponse, ftr:Footer? 519 +* Element Documentation: 512 512 513 -Element Documentation: 521 +(% style="width:912.294px" %) 522 +|**Name**|(% style="width:304px" %)**Type**|(% style="width:336px" %)**Documentation** 523 +|Header|(% style="width:304px" %)BasicHeaderType|(% style="width:336px" %) 524 +|QuerySubscriptionRes ponse|(% style="width:304px" %)ref: QuerySubscriptionRes ponseType|(% style="width:336px" %)QuerySubscriptionResponse is sent as a response to a subscription query. If the query is successful, the details of all subscriptions for the requested organisation are sent. 525 +|ftr:Footer|(% style="width:304px" %)ftr:FooterType|(% style="width:336px" %)Footer is used to communicate information such as error and warnings after the payload of a message. 514 514 515 -|**Name**|**Type**|**Documentation** 516 -|Header|BasicHeaderType| 517 -|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. 518 -|ftr:Footer|ftr:FooterType|Footer is used to communicate information such as error and warnings after the payload of a message. 519 - 520 520 **NotifyRegistryEventType: **NotifyRegistryEventType defines the structure of a registry notification document. 521 521 522 522 Derivation: 523 523 524 -//MessageType// (restriction) 525 - 526 - 531 +* //MessageType// (restriction) 532 +** RegistryInterfaceType (restriction) 533 +*** NotifyRegistryEventType 527 527 528 528 Content: 529 529 530 -Header, NotifyRegistryEvent 537 +* Header, NotifyRegistryEvent 538 +* Element Documentation: 531 531 532 -Element Documentation: 540 +(% style="width:836.294px" %) 541 +|**Name**|**Type**|(% style="width:473px" %)**Documentation** 542 +|Header|BasicHeaderType|(% style="width:473px" %) 543 +|NotifyRegistryEvent|ref: NotifyRegistryEventT ype|(% style="width:473px" %)NotifyRegistryEvent is sent by the registry services to subscribers, to notify them of specific registration and change events. Basic information about the event, such as the object that triggered it, the time of the event, the action that took place, and the subscription that triggered the notification are always sent. Optionally, the details of the changed object may also be provided. 533 533 534 -|**Name**|**Type**|**Documentation** 535 -|Header|BasicHeaderType| 536 -|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. 537 - 538 538 **DataQueryType: **DataQueryType defines the structure of a data query message. 539 539 540 540 Derivation: 541 541 542 -//MessageType// (restriction) 543 - 549 +* //MessageType// (restriction) 550 +** DataQueryType 544 544 545 545 Content: 546 546 547 -Header, Query 554 +* Header, Query 555 +* Element Documentation: 548 548 549 -Element Documentation: 557 +(% style="width:839.294px" %) 558 +|(% style="width:244px" %)**Name**|(% style="width:262px" %)**Type**|(% style="width:330px" %)**Documentation** 559 +|(% style="width:244px" %)Header|(% style="width:262px" %)BasicHeaderType|(% style="width:330px" %) 560 +|(% style="width:244px" %)Query|(% style="width:262px" %)qry:DataQueryType|(% style="width:330px" %) 550 550 551 -|**Name**|**Type**|**Documentation** 552 -|Header|BasicHeaderType| 553 -|Query|qry:DataQueryType| 554 - 555 555 **GenericDataQueryType: **DataQueryType defines the structure of a generic data query message. 556 556 557 557 Derivation: 558 558 559 -//MessageType// (restriction) 560 - 561 - 566 +* //MessageType// (restriction) 567 +** DataQueryType (restriction) 568 +*** GenericDataQueryType 562 562 563 563 Content: 564 564 565 -Header, Query 572 +* Header, Query 573 +* Element Documentation: 566 566 567 -Element Documentation: 575 +(% style="width:833.294px" %) 576 +|(% style="width:213px" %)**Name**|(% style="width:243px" %)**Type**|(% style="width:374px" %)**Documentation** 577 +|(% style="width:213px" %)Header|(% style="width:243px" %)BasicHeaderType|(% style="width:374px" %) 578 +|(% style="width:213px" %)Query|(% style="width:243px" %)qry: GenericDataQueryType|(% style="width:374px" %) 568 568 569 -|**Name**|**Type**|**Documentation** 570 -|Header|BasicHeaderType| 571 -|Query|qry: GenericDataQueryType| 572 - 573 573 **GenericTimeSeriesDataQueryType: **GenericTimeSeriesDataQueryType defines the structure of a time series generic data query message. 574 574 575 575 Derivation: 576 576 577 -//MessageType// (restriction) 578 - 579 - 580 - 584 +* //MessageType// (restriction) 585 +** DataQueryType (restriction) 586 +*** GenericDataQueryType (restriction) 587 +**** GenericTimeSeriesDataQueryType 581 581 582 582 Content: 583 583 584 -Header, Query 591 +* Header, Query 592 +* Element Documentation: 585 585 586 -Element Documentation: 594 +(% style="width:909.294px" %) 595 +|(% style="width:221px" %)**Name**|(% style="width:305px" %)**Type**|(% style="width:380px" %)**Documentation** 596 +|(% style="width:221px" %)Header|(% style="width:305px" %)BasicHeaderType|(% style="width:380px" %) 597 +|(% style="width:221px" %)Query|(% style="width:305px" %)qry: GenericTimeSeriesDat aQueryType|(% style="width:380px" %) 587 587 588 -|**Name**|**Type**|**Documentation** 589 -|Header|BasicHeaderType| 590 -|Query|qry: GenericTimeSeriesDat aQueryType| 591 - 592 592 **StructureSpecificTimeSeriesDataQueryType: **StructureSpecificTimeSeriesDataQueryType defines the structure of a time series generic data query message. 593 593 594 594 Derivation: 595 595 596 -//MessageType// (restriction) 597 - 598 - 603 +* //MessageType// (restriction) 604 +** DataQueryType (restriction) 605 +*** StructureSpecificTimeSeriesDataQueryType 599 599 600 600 Content: 601 601 602 -Header, Query 609 +* Header, Query 610 +* Element Documentation: 603 603 604 -Element Documentation: 612 +(% style="width:903.294px" %) 613 +|(% style="width:189px" %)**Name**|(% style="width:259px" %)**Type**|(% style="width:452px" %)**Documentation** 614 +|(% style="width:189px" %)Header|(% style="width:259px" %)BasicHeaderType|(% style="width:452px" %) 615 +|(% style="width:189px" %)Query|(% style="width:259px" %)qry: TimeSeriesDataQueryType|(% style="width:452px" %) 605 605 606 -|**Name**|**Type**|**Documentation** 607 -|Header|BasicHeaderType| 608 -|Query|qry: TimeSeriesDataQueryT ype| 609 - 610 610 **MetadataQueryType: **MetadataQueryType defines the structure of a reference metadata query message. 611 611 612 612 Derivation: 613 613 614 -//MessageType// (restriction) 615 - 621 +* //MessageType// (restriction) 622 +** MetadataQueryType 616 616 617 617 Content: 618 618 619 -Header, Query 626 +* Header, Query 627 +* Element Documentation: 620 620 621 -Element Documentation: 629 +(% style="width:858.294px" %) 630 +|(% style="width:138px" %)**Name**|(% style="width:246px" %)**Type**|(% style="width:471px" %)**Documentation** 631 +|(% style="width:138px" %)Header|(% style="width:246px" %)BasicHeaderType|(% style="width:471px" %) 632 +|(% style="width:138px" %)Query|(% style="width:246px" %)qry: MetadataQueryType|(% style="width:471px" %) 622 622 623 -|**Name**|**Type**|**Documentation** 624 -|Header|BasicHeaderType| 625 -|Query|qry: MetadataQueryType| 626 - 627 627 **DataSchemaQueryType: **DataSchemaQueryType defines the structure of a data schema query message. 628 628 629 629 Derivation: 630 630 631 -//MessageType// (restriction) 632 - 638 +* //MessageType// (restriction) 639 +** DataSchemaQueryType 633 633 634 634 Content: 635 635 636 -Header, Query 643 +* Header, Query 644 +* Element Documentation: 637 637 638 -Element Documentation: 646 +(% style="width:895.294px" %) 647 +|(% style="width:185px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:413px" %)**Documentation** 648 +|(% style="width:185px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:413px" %) 649 +|(% style="width:185px" %)Query|(% style="width:294px" %)qry: DataSchemaQueryType|(% style="width:413px" %) 639 639 640 -|**Name**|**Type**|**Documentation** 641 -|Header|BasicHeaderType| 642 -|Query|qry: DataSchemaQueryType| 643 - 644 644 **MetadataSchemaQueryType: **MetadataSchemaQueryType defines the structure of a metadata schema query message. 645 645 646 646 Derivation: 647 647 648 -//MessageType// (restriction) 649 - 655 +* //MessageType// (restriction) 656 +** MetadataSchemaQueryType 650 650 651 651 Content: 652 652 653 -Header, Query 660 +* Header, Query 661 +* Element Documentation: 654 654 655 -Element Documentation: 663 +(% style="width:897.294px" %) 664 +|(% style="width:166px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:447px" %)**Documentation** 665 +|(% style="width:166px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:447px" %) 666 +|(% style="width:166px" %)Query|(% style="width:281px" %)qry: MetadataSchemaQueryType|(% style="width:447px" %) 656 656 657 -|**Name**|**Type**|**Documentation** 658 -|Header|BasicHeaderType| 659 -|Query|qry: MetadataSchemaQueryT ype| 660 - 661 661 **StructuresQueryType: **StructuresQueryType defines the structure of a structures query message. 662 662 663 663 Derivation: 664 664 665 -//MessageType// (restriction) 666 - 672 +* //MessageType// (restriction) 673 +** StructuresQueryType 667 667 668 668 Content: 669 669 670 -Header, Query 677 +* Header, Query 678 +* Element Documentation: 671 671 672 -Element Documentation: 680 +(% style="width:886.294px" %) 681 +|(% style="width:223px" %)**Name**|(% style="width:255px" %)**Type**|(% style="width:405px" %)**Documentation** 682 +|(% style="width:223px" %)Header|(% style="width:255px" %)BasicHeaderType|(% style="width:405px" %) 683 +|(% style="width:223px" %)Query|(% style="width:255px" %)qry: StructuresQueryType|(% style="width:405px" %) 673 673 674 -|**Name**|**Type**|**Documentation** 675 -|Header|BasicHeaderType| 676 -|Query|qry: StructuresQueryType| 677 - 678 678 **DataflowQueryType: **DataflowQueryType defines the structure of a dataflow query message. 679 679 680 680 Derivation: 681 681 682 -//MessageType// (restriction) 683 - 689 +* //MessageType// (restriction) 690 +** DataflowQueryType 684 684 685 685 Content: 686 686 687 -Header, Query 694 +* Header, Query 695 +* Element Documentation: 688 688 689 -Element Documentation: 697 +(% style="width:888.294px" %) 698 +|(% style="width:176px" %)**Name**|(% style="width:260px" %)**Type**|(% style="width:449px" %)**Documentation** 699 +|(% style="width:176px" %)Header|(% style="width:260px" %)BasicHeaderType|(% style="width:449px" %) 700 +|(% style="width:176px" %)Query|(% style="width:260px" %)qry: DataflowQueryType|(% style="width:449px" %) 690 690 691 -|**Name**|**Type**|**Documentation** 692 -|Header|BasicHeaderType| 693 -|Query|qry: DataflowQueryType| 694 - 695 695 **MetadataflowQueryType: **MetadataflowQueryType defines the structure of a metadata flow query message. 696 696 697 697 Derivation: 698 698 699 -//MessageType// (restriction) 700 - 706 +* //MessageType// (restriction) 707 +** MetadataflowQueryType 701 701 702 702 Content: 703 703 704 -Header, Query 711 +* Header, Query 712 +* Element Documentation: 705 705 706 -Element Documentation: 714 +(% style="width:886.294px" %) 715 +|(% style="width:199px" %)**Name**|(% style="width:296px" %)**Type**|(% style="width:388px" %)**Documentation** 716 +|(% style="width:199px" %)Header|(% style="width:296px" %)BasicHeaderType|(% style="width:388px" %) 717 +|(% style="width:199px" %)Query|(% style="width:296px" %)qry: MetadataflowQueryType|(% style="width:388px" %) 707 707 708 -|**Name**|**Type**|**Documentation** 709 -|Header|BasicHeaderType| 710 -|Query|qry: MetadataflowQueryTyp e| 711 - 712 712 **DataStructureQueryType: **KeyFamilyQueryType defines the structure of a data structure query message. 713 713 714 714 Derivation: 715 715 716 -//MessageType// (restriction) 717 - 723 +* //MessageType// (restriction) 724 +** DataStructureQueryType 718 718 719 719 Content: 720 720 721 -Header, Query 728 +* Header, Query 729 +* Element Documentation: 722 722 723 -Element Documentation: 731 +(% style="width:901.294px" %) 732 +|(% style="width:202px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:393px" %)**Documentation** 733 +|(% style="width:202px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:393px" %) 734 +|(% style="width:202px" %)Query|(% style="width:303px" %)qry: DataStructureQueryType|(% style="width:393px" %) 724 724 725 -|**Name**|**Type**|**Documentation** 726 -|Header|BasicHeaderType| 727 -|Query|qry: DataStructureQueryTy pe| 728 - 729 729 **MetadataStructureQueryType: **MetadataStructureQueryType defines the structure of a metadata structure query message. 730 730 731 731 Derivation: 732 732 733 -//MessageType// (restriction) 734 - 740 +* //MessageType// (restriction) 741 +** MetadataStructureQueryType 735 735 736 736 Content: 737 737 738 -Header, Query 745 +* Header, Query 746 +* Element Documentation: 739 739 740 -Element Documentation: 748 +(% style="width:904.294px" %) 749 +|(% style="width:226px" %)**Name**|(% style="width:275px" %)**Type**|(% style="width:400px" %)**Documentation** 750 +|(% style="width:226px" %)Header|(% style="width:275px" %)BasicHeaderType|(% style="width:400px" %) 751 +|(% style="width:226px" %)Query|(% style="width:275px" %)qry: MetadataStructureQueryType|(% style="width:400px" %) 741 741 742 -|**Name**|**Type**|**Documentation** 743 -|Header|BasicHeaderType| 744 -|Query|qry: MetadataStructureQue ryType| 745 - 746 746 **CategorySchemeQueryType: **CategorySchemeQueryType defines the structure of a category scheme query message. 747 747 748 748 Derivation: 749 749 750 -//MessageType// (restriction) 751 - 757 +* //MessageType// (restriction) 758 +** CategorySchemeQueryType 752 752 753 753 Content: 754 754 755 -Header, Query 762 +* Header, Query 763 +* Element Documentation: 756 756 757 -Element Documentation: 765 +(% style="width:915.294px" %) 766 +|(% style="width:196px" %)**Name**|(% style="width:347px" %)**Type**|(% style="width:369px" %)**Documentation** 767 +|(% style="width:196px" %)Header|(% style="width:347px" %)BasicHeaderType|(% style="width:369px" %) 768 +|(% style="width:196px" %)Query|(% style="width:347px" %)qry: CategorySchemeQueryType|(% style="width:369px" %) 758 758 759 -|**Name**|**Type**|**Documentation** 760 -|Header|BasicHeaderType| 761 -|Query|qry: CategorySchemeQueryT ype| 762 - 763 763 **ConceptSchemeQueryType: **ConceptSchemeQueryType defines the structure of a concept scheme query message. 764 764 765 765 Derivation: 766 766 767 -//MessageType// (restriction) 768 - 774 +* //MessageType// (restriction) 775 +** ConceptSchemeQueryType 769 769 770 770 Content: 771 771 772 -Header, Query 779 +* Header, Query 780 +* Element Documentation: 773 773 774 -Element Documentation: 782 +(% style="width:895.294px" %) 783 +|(% style="width:222px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:331px" %)**Documentation** 784 +|(% style="width:222px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:331px" %) 785 +|(% style="width:222px" %)Query|(% style="width:339px" %)qry: ConceptSchemeQueryType|(% style="width:331px" %) 775 775 776 -|**Name**|**Type**|**Documentation** 777 -|Header|BasicHeaderType| 778 -|Query|qry: ConceptSchemeQueryTy pe| 779 - 780 780 **CodelistQueryType: **CodelistQueryType defines the structure of a codelist query message. 781 781 782 782 Derivation: 783 783 784 -//MessageType// (restriction) 785 - 791 +* //MessageType// (restriction) 792 +** CodelistQueryType 786 786 787 787 Content: 788 788 789 -Header, Query 796 +* Header, Query 797 +* Element Documentation: 790 790 791 -Element Documentation: 799 +(% style="width:911.294px" %) 800 +|(% style="width:204px" %)**Name**|(% style="width:295px" %)**Type**|(% style="width:409px" %)**Documentation** 801 +|(% style="width:204px" %)Header|(% style="width:295px" %)BasicHeaderType|(% style="width:409px" %) 802 +|(% style="width:204px" %)Query|(% style="width:295px" %)qry:CodelistQueryType|(% style="width:409px" %) 792 792 793 -|**Name**|**Type**|**Documentation** 794 -|Header|BasicHeaderType| 795 -|Query|qry: CodelistQueryType| 796 - 797 797 **HierarchicalCodelistQueryType: **HierarchicalCodelistQueryType defines the structure of a hierarchical codelist query message. 798 798 799 799 Derivation: 800 800 801 -//MessageType// (restriction) 802 - 808 +* //MessageType// (restriction) 809 +** HierarchicalCodelistQueryType 803 803 804 804 Content: 805 805 806 -Header, Query 813 +* Header, Query 814 +* Element Documentation: 807 807 808 -Element Documentation: 816 +(% style="width:906.294px" %) 817 +|(% style="width:191px" %)**Name**|(% style="width:281px" %)**Type**|(% style="width:430px" %)**Documentation** 818 +|(% style="width:191px" %)Header|(% style="width:281px" %)BasicHeaderType|(% style="width:430px" %) 819 +|(% style="width:191px" %)Query|(% style="width:281px" %)qry: HierarchicalCodelist QueryType|(% style="width:430px" %) 809 809 810 -|**Name**|**Type**|**Documentation** 811 -|Header|BasicHeaderType| 812 -|Query|qry: HierarchicalCodelist QueryType| 813 - 814 814 **OrganisationSchemeQueryType: **OrganisationSchemeQueryType defines the structure of an organisation scheme query message. 815 815 816 816 Derivation: 817 817 818 -//MessageType// (restriction) 819 - 825 +* //MessageType// (restriction) 826 +** OrganisationSchemeQueryType 820 820 821 821 Content: 822 822 823 -Header, Query 830 +* Header, Query 831 +* Element Documentation: 824 824 825 -Element Documentation: 833 +(% style="width:891.294px" %) 834 +|(% style="width:174px" %)**Name**|(% style="width:292px" %)**Type**|(% style="width:422px" %)**Documentation** 835 +|(% style="width:174px" %)Header|(% style="width:292px" %)BasicHeaderType|(% style="width:422px" %) 836 +|(% style="width:174px" %)Query|(% style="width:292px" %)qry: OrganisationSchemeQueryType|(% style="width:422px" %) 826 826 827 -|**Name**|**Type**|**Documentation** 828 -|Header|BasicHeaderType| 829 -|Query|qry: OrganisationSchemeQu eryType| 830 - 831 831 **ReportingTaxonomyQueryType: **ReportingTaxonomyQueryType defines the structure of a reporting taxonomy query message. 832 832 833 833 Derivation: 834 834 835 -//MessageType// (restriction) 836 - 842 +* //MessageType// (restriction) 843 +** ReportingTaxonomyQueryType 837 837 838 838 Content: 839 839 840 -Header, Query 847 +* Header, Query 848 +* Element Documentation: 841 841 842 -Element Documentation: 850 +(% style="width:916.294px" %) 851 +|(% style="width:162px" %)**Name**|(% style="width:318px" %)**Type**|(% style="width:434px" %)**Documentation** 852 +|(% style="width:162px" %)Header|(% style="width:318px" %)BasicHeaderType|(% style="width:434px" %) 853 +|(% style="width:162px" %)Query|(% style="width:318px" %)qry: ReportingTaxonomyQueryType|(% style="width:434px" %) 843 843 844 -|**Name**|**Type**|**Documentation** 845 -|Header|BasicHeaderType| 846 -|Query|qry: ReportingTaxonomyQue ryType| 847 - 848 848 **StructureSetQueryType: **StructureSetQueryType defines the structure of a structure set query message. 849 849 850 850 Derivation: 851 851 852 -//MessageType// (restriction) 853 - 859 +* //MessageType// (restriction) 860 +** StructureSetQueryType 854 854 855 855 Content: 856 856 857 -Header, Query 864 +* Header, Query 865 +* Element Documentation: 858 858 859 -Element Documentation: 867 +(% style="width:896.294px" %) 868 +|(% style="width:182px" %)**Name**|(% style="width:294px" %)**Type**|(% style="width:417px" %)**Documentation** 869 +|(% style="width:182px" %)Header|(% style="width:294px" %)BasicHeaderType|(% style="width:417px" %) 870 +|(% style="width:182px" %)Query|(% style="width:294px" %)qry: StructureSetQueryType|(% style="width:417px" %) 860 860 861 -|**Name**|**Type**|**Documentation** 862 -|Header|BasicHeaderType| 863 -|Query|qry: StructureSetQueryTyp e| 864 - 865 865 **ProcessQueryType: **CategorizationQueryType defines the structure of a categorization query message. 866 866 867 867 Derivation: 868 868 869 -//MessageType// (restriction) 870 - 876 +* //MessageType// (restriction) 877 +** ProcessQueryType 871 871 872 872 Content: 873 873 874 -Header, Query 881 +* Header, Query 882 +* Element Documentation: 875 875 876 -Element Documentation: 884 +(% style="width:907.294px" %) 885 +|(% style="width:189px" %)**Name**|(% style="width:394px" %)**Type**|(% style="width:321px" %)**Documentation** 886 +|(% style="width:189px" %)Header|(% style="width:394px" %)BasicHeaderType|(% style="width:321px" %) 887 +|(% style="width:189px" %)Query|(% style="width:394px" %)qry:ProcessQueryType|(% style="width:321px" %) 877 877 878 -|**Name**|**Type**|**Documentation** 879 -|Header|BasicHeaderType| 880 -|Query|qry:ProcessQueryType| 881 - 882 882 **CategorisationQueryType: **CategorisationQueryType defines the structure of a categorisation query message. 883 883 884 884 Derivation: 885 885 886 -//MessageType// (restriction) 887 - 893 +* //MessageType// (restriction) 894 +** CategorisationQueryType 888 888 889 889 Content: 890 890 891 -Header, Query 898 +* Header, Query 899 +* Element Documentation: 892 892 893 -Element Documentation: 901 +(% style="width:897.294px" %) 902 +|(% style="width:230px" %)**Name**|(% style="width:300px" %)**Type**|(% style="width:363px" %)**Documentation** 903 +|(% style="width:230px" %)Header|(% style="width:300px" %)BasicHeaderType|(% style="width:363px" %) 904 +|(% style="width:230px" %)Query|(% style="width:300px" %)qry: CategorisationQueryType|(% style="width:363px" %) 894 894 895 -|**Name**|**Type**|**Documentation** 896 -|Header|BasicHeaderType| 897 -|Query|qry: CategorisationQueryT ype| 898 - 899 899 **ProvisionAgreementQueryType: **ProvisionAgreementQueryType defines the structure of a provision agreement query message. 900 900 901 901 Derivation: 902 902 903 -//MessageType// (restriction) 904 - 910 +* //MessageType// (restriction) 911 +** ProvisionAgreementQueryType 905 905 906 906 Content: 907 907 908 -Header, Query 915 +* Header, Query 916 +* Element Documentation: 909 909 910 -Element Documentation: 918 +(% style="width:902.294px" %) 919 +|(% style="width:142px" %)**Name**|(% style="width:339px" %)**Type**|(% style="width:418px" %)**Documentation** 920 +|(% style="width:142px" %)Header|(% style="width:339px" %)BasicHeaderType|(% style="width:418px" %) 921 +|(% style="width:142px" %)Query|(% style="width:339px" %)qry: ProvisionAgreementQueryType|(% style="width:418px" %) 911 911 912 -|**Name**|**Type**|**Documentation** 913 -|Header|BasicHeaderType| 914 -|Query|qry: ProvisionAgreementQu eryType| 915 - 916 916 **ConstraintQueryType: **ConstraintQueryType defines the structure of a constraint query message. 917 917 918 918 Derivation: 919 919 920 -//MessageType// (restriction) 921 - 927 +* //MessageType// (restriction) 928 +** ConstraintQueryType 922 922 923 923 Content: 924 924 925 -Header, Query 932 +* Header, Query 933 +* Element Documentation: 926 926 927 -Element Documentation: 935 +(% style="width:902.294px" %) 936 +|(% style="width:167px" %)**Name**|(% style="width:287px" %)**Type**|(% style="width:445px" %)**Documentation** 937 +|(% style="width:167px" %)Header|(% style="width:287px" %)BasicHeaderType|(% style="width:445px" %) 938 +|(% style="width:167px" %)Query|(% style="width:287px" %)qry: ConstraintQueryType|(% style="width:445px" %) 928 928 929 -|**Name**|**Type**|**Documentation** 930 -|Header|BasicHeaderType| 931 -|Query|qry: ConstraintQueryType| 932 - 933 933 **TransformationSchemeQueryType: **TransformationSchemeQueryType defines the structure of a transformation scheme query message. 934 934 935 935 Derivation: 936 936 937 -//MessageType// (restriction) 938 - 944 +* //MessageType// (restriction) 945 +** TransformationSchemeQueryType 939 939 940 940 Content: 941 941 942 -Header, Query 949 +* Header, Query 950 +* Element Documentation: 943 943 944 -Element Documentation: 952 +(% style="width:833.294px" %) 953 +|(% style="width:165px" %)**Name**|(% style="width:325px" %)**Type**|(% style="width:340px" %)**Documentation** 954 +|(% style="width:165px" %)Header|(% style="width:325px" %)BasicHeaderType|(% style="width:340px" %) 955 +|(% style="width:165px" %)Query|(% style="width:325px" %)qry: TransformationSchemeQueryType|(% style="width:340px" %) 945 945 946 -|**Name**|**Type**|**Documentation** 947 -|Header|BasicHeaderType| 948 -|Query|qry: TransformationScheme QueryType| 949 - 950 950 **VtlMappingSchemeQueryType: **VtlMappingSchemeQueryType defines the structure of a VTL mappings scheme query message. 951 951 952 952 Derivation: 953 953 954 -//MessageType// (restriction) 955 - 961 +* //MessageType// (restriction) 962 +** VtlMappingSchemeQueryType 956 956 957 957 Content: 958 958 959 -Header, Query 966 +* Header, Query 967 +* Element Documentation: 960 960 961 -Element Documentation: 969 +(% style="width:843.294px" %) 970 +|(% style="width:164px" %)**Name**|(% style="width:303px" %)**Type**|(% style="width:373px" %)**Documentation** 971 +|(% style="width:164px" %)Header|(% style="width:303px" %)BasicHeaderType|(% style="width:373px" %) 972 +|(% style="width:164px" %)Query|(% style="width:303px" %)qry: VtlMappingSchemeQueryType|(% style="width:373px" %) 962 962 963 -|**Name**|**Type**|**Documentation** 964 -|Header|BasicHeaderType| 965 -|Query|qry: VtlMappingSchemeQuer yType| 966 - 967 967 **NamePersonalisationSchemeQueryType: **NamePersonalisationSchemeQueryType defines the structure of a name personalisation scheme query message. 968 968 969 969 Derivation: 970 970 971 -//MessageType// (restriction) 972 - 978 +* //MessageType// (restriction) 979 +** NamePersonalisationSchemeQueryType 973 973 974 974 Content: 975 975 976 -Header, Query 983 +* Header, Query 984 +* Element Documentation: 977 977 978 -Element Documentation: 986 +(% style="width:895.294px" %) 987 +|(% style="width:186px" %)**Name**|(% style="width:363px" %)**Type**|(% style="width:343px" %)**Documentation** 988 +|(% style="width:186px" %)Header|(% style="width:363px" %)BasicHeaderType|(% style="width:343px" %) 989 +|(% style="width:186px" %)Query|(% style="width:363px" %)qry: NamePersonalisationSchemeQueryType|(% style="width:343px" %) 979 979 980 -|**Name**|**Type**|**Documentation** 981 -|Header|BasicHeaderType| 982 -|Query|qry: NamePersonalisationS chemeQueryType| 983 - 984 984 **RulesetSchemeQueryType: **RulesetSchemeQueryType defines the structure of a ruleset scheme query message. 985 985 986 986 Derivation: 987 987 988 -//MessageType// (restriction) 989 - 995 +* //MessageType// (restriction) 996 +** RulesetSchemeQueryType 990 990 991 991 Content: 992 992 993 -Header, Query 1000 +* Header, Query 1001 +* Element Documentation: 994 994 995 -Element Documentation: 1003 +(% style="width:886.294px" %) 1004 +|(% style="width:152px" %)**Name**|(% style="width:311px" %)**Type**|(% style="width:420px" %)**Documentation** 1005 +|(% style="width:152px" %)Header|(% style="width:311px" %)BasicHeaderType|(% style="width:420px" %) 1006 +|(% style="width:152px" %)Query|(% style="width:311px" %)qry: RulesetSchemeQueryType|(% style="width:420px" %) 996 996 997 -|**Name**|**Type**|**Documentation** 998 -|Header|BasicHeaderType| 999 -|Query|qry: RulesetSchemeQueryTy pe| 1000 - 1001 1001 **UserDefinedOperatorSchemeQueryType: **UserDefinedOperatorSchemeQueryType defines the structure of a user defined operator scheme query message. 1002 1002 1003 1003 Derivation: 1004 1004 1005 -//MessageType// (restriction) 1006 - 1012 +* //MessageType// (restriction) 1013 +** UserDefinedOperatorSchemeQueryType 1007 1007 1008 1008 Content: 1009 1009 1010 -Header, Query 1017 +* Header, Query 1018 +* Element Documentation: 1011 1011 1012 -Element Documentation: 1020 +(% style="width:866.294px" %) 1021 +|(% style="width:174px" %)**Name**|(% style="width:358px" %)**Type**|(% style="width:331px" %)**Documentation** 1022 +|(% style="width:174px" %)Header|(% style="width:358px" %)BasicHeaderType|(% style="width:331px" %) 1023 +|(% style="width:174px" %)Query|(% style="width:358px" %)qry: UserDefinedOperatorSchemeQueryType|(% style="width:331px" %) 1013 1013 1014 -|**Name**|**Type**|**Documentation** 1015 -|Header|BasicHeaderType| 1016 -|Query|qry: UserDefinedOperatorS chemeQueryType| 1017 - 1018 1018 **CustomTypeSchemeQueryType: **CustomTypeSchemeQueryType defines the structure of a custom type scheme query message. 1019 1019 1020 1020 Derivation: 1021 1021 1022 -//MessageType// (restriction) 1023 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]CustomTypeSchemeQueryType1029 +* //MessageType// (restriction) 1030 +** CustomTypeSchemeQueryType 1024 1024 1025 1025 Content: 1026 1026 1027 -Header, Query 1034 +* Header, Query 1035 +* Element Documentation: 1028 1028 1029 -Element Documentation: 1037 +(% style="width:828.294px" %) 1038 +|(% style="width:200px" %)**Name**|(% style="width:308px" %)**Type**|(% style="width:317px" %)**Documentation** 1039 +|(% style="width:200px" %)Header|(% style="width:308px" %)BasicHeaderType|(% style="width:317px" %) 1040 +|(% style="width:200px" %)Query|(% style="width:308px" %)qry: CustomTypeSchemeQueryType|(% style="width:317px" %) 1030 1030 1031 -|**Name**|**Type**|**Documentation** 1032 -|Header|BasicHeaderType| 1033 -|Query|qry: CustomTypeSchemeQuer yType| 1034 - 1035 1035 **ErrorType: **ErrorType describes the structure of an error response. 1036 1036 1037 1037 Content: 1038 1038 1039 -ErrorMessage+ 1046 +* ErrorMessage+ 1047 +* Element Documentation: 1040 1040 1041 -Element Documentation: 1049 +(% style="width:899.294px" %) 1050 +|**Name**|**Type**|(% style="width:546px" %)**Documentation** 1051 +|ErrorMessage|com: CodedStatusMessageTy pe|(% style="width:546px" %)ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors. 1042 1042 1043 -|**Name**|**Type**|**Documentation** 1044 -|ErrorMessage|com: CodedStatusMessageTy pe|ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors. 1045 - 1046 1046 **//BaseHeaderType//: **BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this 1047 1047 1048 1048 Content: ... ... @@ -1051,29 +1051,30 @@ 1051 1051 1052 1052 Element Documentation: 1053 1053 1054 -|**Name**|**Type**|**Documentation** 1055 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1056 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1057 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1058 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1059 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1060 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1061 -|Structure|//com: PayloadStructureType//|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1062 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1063 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1064 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1065 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1066 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1067 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1068 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1069 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1061 +(% style="width:891.294px" %) 1062 +|**Name**|**Type**|(% style="width:552px" %)**Documentation** 1063 +|ID|com:IDType|(% style="width:552px" %)ID identifies an identification for the message, assigned by the sender. 1064 +|Test|xs:boolean|(% style="width:552px" %)Test indicates whether the message is for test purposes or not. 1065 +|Prepared|HeaderTimeType|(% style="width:552px" %)Prepared is the date the message was prepared. 1066 +|Sender|SenderType|(% style="width:552px" %)Sender is information about the party that is transmitting the message. 1067 +|Receiver|PartyType|(% style="width:552px" %)Receiver is information about the party that is the intended recipient of the message. 1068 +|com:Name|com:TextType|(% style="width:552px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1069 +|Structure|//com: PayloadStructureType//|(% style="width:552px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1070 +|DataProvider|com: DataProviderReferenceType|(% style="width:552px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1071 +|DataSetAction|com:ActionType|(% style="width:552px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1072 +|DataSetID|com:IDType|(% style="width:552px" %)DataSetID provides an identifier for a contained data set. 1073 +|Extracted|xs:dateTime|(% style="width:552px" %)Extracted is a time-stamp from the system rendering the data. 1074 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1075 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:552px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1076 +|EmbargoDate|xs:dateTime|(% style="width:552px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1077 +|Source|com:TextType|(% style="width:552px" %)Source provides human-readable information about the source of the data. 1070 1070 1071 1071 **StructureHeaderType: **StructureHeaderType defines the structure for structural metadata messages. 1072 1072 1073 1073 Derivation: 1074 1074 1075 -//BaseHeaderType// (restriction) 1076 - 1083 +* //BaseHeaderType// (restriction) 1084 +** StructureHeaderType 1077 1077 1078 1078 Content: 1079 1079 ... ... @@ -1081,21 +1081,22 @@ 1081 1081 1082 1082 Element Documentation: 1083 1083 1084 -|**Name**|**Type**|**Documentation** 1085 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1086 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1087 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1088 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1089 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1090 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1091 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1092 +(% style="width:1099.29px" %) 1093 +|**Name**|(% style="width:224px" %)**Type**|(% style="width:663px" %)**Documentation** 1094 +|ID|(% style="width:224px" %)com:IDType|(% style="width:663px" %)ID identifies an identification for the message, assigned by the sender. 1095 +|Test|(% style="width:224px" %)xs:boolean|(% style="width:663px" %)Test indicates whether the message is for test purposes or not. 1096 +|Prepared|(% style="width:224px" %)HeaderTimeType|(% style="width:663px" %)Prepared is the date the message was prepared. 1097 +|Sender|(% style="width:224px" %)SenderType|(% style="width:663px" %)Sender is information about the party that is transmitting the message. 1098 +|Receiver|(% style="width:224px" %)PartyType|(% style="width:663px" %)Receiver is information about the party that is the intended recipient of the message. 1099 +|com:Name|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1100 +|Source|(% style="width:224px" %)com:TextType|(% style="width:663px" %)Source provides human-readable information about the source of the data. 1092 1092 1093 1093 **GenericDataHeaderType: **GenericDataHeaderType defines the header structure for a generic data message. 1094 1094 1095 1095 Derivation: 1096 1096 1097 -//BaseHeaderType// (restriction) 1098 - [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]]GenericDataHeaderType1106 +* //BaseHeaderType// (restriction) 1107 +** GenericDataHeaderType 1099 1099 1100 1100 Content: 1101 1101 ... ... @@ -1103,30 +1103,31 @@ 1103 1103 1104 1104 Element Documentation: 1105 1105 1106 -|**Name**|**Type**|**Documentation** 1107 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1108 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1109 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1110 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1111 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1112 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1113 -|Structure|com: GenericDataStructure Type|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1114 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1115 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1116 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1117 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1118 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1119 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1120 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1121 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1115 +(% style="width:895.294px" %) 1116 +|**Name**|**Type**|(% style="width:556px" %)**Documentation** 1117 +|ID|com:IDType|(% style="width:556px" %)ID identifies an identification for the message, assigned by the sender. 1118 +|Test|xs:boolean|(% style="width:556px" %)Test indicates whether the message is for test purposes or not. 1119 +|Prepared|HeaderTimeType|(% style="width:556px" %)Prepared is the date the message was prepared. 1120 +|Sender|SenderType|(% style="width:556px" %)Sender is information about the party that is transmitting the message. 1121 +|Receiver|PartyType|(% style="width:556px" %)Receiver is information about the party that is the intended recipient of the message. 1122 +|com:Name|com:TextType|(% style="width:556px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1123 +|Structure|com: GenericDataStructureType|(% style="width:556px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1124 +|DataProvider|com: DataProviderReferenceType|(% style="width:556px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1125 +|DataSetAction|com:ActionType|(% style="width:556px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1126 +|DataSetID|com:IDType|(% style="width:556px" %)DataSetID provides an identifier for a contained data set. 1127 +|Extracted|xs:dateTime|(% style="width:556px" %)Extracted is a time-stamp from the system rendering the data. 1128 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1129 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:556px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1130 +|EmbargoDate|xs:dateTime|(% style="width:556px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1131 +|Source|com:TextType|(% style="width:556px" %)Source provides human-readable information about the source of the data. 1122 1122 1123 1123 **GenericTimeSeriesDataHeaderType: **GenericTimeSeriesDataHeaderType defines the header structure for a time series only generic data message. 1124 1124 1125 1125 Derivation: 1126 1126 1127 -//BaseHeaderType// (restriction) 1128 - 1129 - 1137 +* //BaseHeaderType// (restriction) 1138 +** GenericDataHeaderType (restriction) 1139 +*** GenericTimeSeriesDataHeaderType 1130 1130 1131 1131 Content: 1132 1132 ... ... @@ -1134,29 +1134,30 @@ 1134 1134 1135 1135 Element Documentation: 1136 1136 1137 -|**Name**|**Type**|**Documentation** 1138 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1139 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1140 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1141 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1142 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1143 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1144 -|Structure|com: GenericTimeSeriesDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1145 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1146 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1147 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1148 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1149 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1150 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1151 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1152 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1147 +(% style="width:926.294px" %) 1148 +|**Name**|**Type**|(% style="width:497px" %)**Documentation** 1149 +|ID|com:IDType|(% style="width:497px" %)ID identifies an identification for the message, assigned by the sender. 1150 +|Test|xs:boolean|(% style="width:497px" %)Test indicates whether the message is for test purposes or not. 1151 +|Prepared|HeaderTimeType|(% style="width:497px" %)Prepared is the date the message was prepared. 1152 +|Sender|SenderType|(% style="width:497px" %)Sender is information about the party that is transmitting the message. 1153 +|Receiver|PartyType|(% style="width:497px" %)Receiver is information about the party that is the intended recipient of the message. 1154 +|com:Name|com:TextType|(% style="width:497px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1155 +|Structure|com: GenericTimeSeriesDataStructureType|(% style="width:497px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1156 +|DataProvider|com: DataProviderReferenceType|(% style="width:497px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1157 +|DataSetAction|com:ActionType|(% style="width:497px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1158 +|DataSetID|com:IDType|(% style="width:497px" %)DataSetID provides an identifier for a contained data set. 1159 +|Extracted|xs:dateTime|(% style="width:497px" %)Extracted is a time-stamp from the system rendering the data. 1160 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1161 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:497px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1162 +|EmbargoDate|xs:dateTime|(% style="width:497px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1163 +|Source|com:TextType|(% style="width:497px" %)Source provides human-readable information about the source of the data. 1153 1153 1154 1154 **StructureSpecificDataHeaderType: **StructureSpecificDataHeaderType defines the header structure for a structure specific data message. 1155 1155 1156 1156 Derivation: 1157 1157 1158 -//BaseHeaderType// (restriction) 1159 - 1169 +* //BaseHeaderType// (restriction) 1170 +** StructureSpecificDataHeaderType 1160 1160 1161 1161 Content: 1162 1162 ... ... @@ -1164,30 +1164,31 @@ 1164 1164 1165 1165 Element Documentation: 1166 1166 1167 -|**Name**|**Type**|**Documentation** 1168 -|ID|com:IDType|ID identifies an identification for the message, assigned by the sender. 1169 -|Test|xs:boolean|Test indicates whether the message is for test purposes or not. 1170 -|Prepared|HeaderTimeType|Prepared is the date the message was prepared. 1171 -|Sender|SenderType|Sender is information about the party that is transmitting the message. 1172 -|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message. 1173 -|com:Name|com:TextType|Name provides a name for the transmission. Multiple instances allow for parallel language values. 1174 -|Structure|com: StructureSpecificDat aStructureType|Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1175 -|DataProvider|com: DataProviderReferenc eType|DataProvider identifies the provider of the data for a data/reference metadata message. 1176 -|DataSetAction|com:ActionType|DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1177 -|DataSetID|com:IDType|DataSetID provides an identifier for a contained data set. 1178 -|Extracted|xs:dateTime|Extracted is a time-stamp from the system rendering the data. 1179 -|ReportingBegin|com: ObservationalTimePer iodType|ReportingBegin provides the start of the time period covered by the message (in the case of data). 1180 -|ReportingEnd|com: ObservationalTimePer iodType|ReportingEnd provides the end of the time period covered by the message (in the case of data). 1181 -|EmbargoDate|xs:dateTime|EmbargoDate holds a time period before which the data included in this message is not available. 1182 -|Source|com:TextType|Source provides human-readable information about the source of the data. 1178 +(% style="width:930.294px" %) 1179 +|**Name**|**Type**|(% style="width:578px" %)**Documentation** 1180 +|ID|com:IDType|(% style="width:578px" %)ID identifies an identification for the message, assigned by the sender. 1181 +|Test|xs:boolean|(% style="width:578px" %)Test indicates whether the message is for test purposes or not. 1182 +|Prepared|HeaderTimeType|(% style="width:578px" %)Prepared is the date the message was prepared. 1183 +|Sender|SenderType|(% style="width:578px" %)Sender is information about the party that is transmitting the message. 1184 +|Receiver|PartyType|(% style="width:578px" %)Receiver is information about the party that is the intended recipient of the message. 1185 +|com:Name|com:TextType|(% style="width:578px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values. 1186 +|Structure|com: StructureSpecificDataStructureType|(% style="width:578px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. In addition to the structure, it is required to also supply the namespace of the structure specific schema that defines the format of the data/metadata. For cross sectional data, additional information is also required to state which dimension is being used at the observation level. This information will allow the structure specific schema to be generated. For generic format messages, this is used to simply reference the underlying structure. It is not mandatory in these cases and the generic data/metadata sets will require this reference explicitly. 1187 +|DataProvider|com: DataProviderReferenceType|(% style="width:578px" %)DataProvider identifies the provider of the data for a data/reference metadata message. 1188 +|DataSetAction|com:ActionType|(% style="width:578px" %)DataSetAction code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). 1189 +|DataSetID|com:IDType|(% style="width:578px" %)DataSetID provides an identifier for a contained data set. 1190 +|Extracted|xs:dateTime|(% style="width:578px" %)Extracted is a time-stamp from the system rendering the data. 1191 +|ReportingBegin|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingBegin provides the start of the time period covered by the message (in the case of data). 1192 +|ReportingEnd|com: ObservationalTimePeriodType|(% style="width:578px" %)ReportingEnd provides the end of the time period covered by the message (in the case of data). 1193 +|EmbargoDate|xs:dateTime|(% style="width:578px" %)EmbargoDate holds a time period before which the data included in this message is not available. 1194 +|Source|com:TextType|(% style="width:578px" %)Source provides human-readable information about the source of the data. 1183 1183 1184 1184 **StructureSpecificTimeSeriesDataHeaderType: **StructureSpecificTimeSeriesDataHeaderType defines the header structure for a time series only structure specific data message. 1185 1185 1186 1186 Derivation: 1187 1187 1188 -//BaseHeaderType// (restriction) 1189 - 1190 - 1200 +* //BaseHeaderType// (restriction) 1201 +** StructureSpecificDataHeaderType (restriction) 1202 +*** StructureSpecificTimeSeriesDataHeaderType 1191 1191 1192 1192 Content: 1193 1193 ... ... @@ -1244,7 +1244,7 @@ 1244 1244 Derivation: 1245 1245 1246 1246 //BaseHeaderType// (restriction) 1247 - 1259 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] StructureSpecificMetadataHeaderType 1248 1248 1249 1249 Content: 1250 1250 ... ... @@ -1271,7 +1271,7 @@ 1271 1271 Derivation: 1272 1272 1273 1273 //BaseHeaderType// (restriction) 1274 - 1286 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] BasicHeaderType 1275 1275 1276 1276 Content: 1277 1277 ... ... @@ -1312,7 +1312,7 @@ 1312 1312 Derivation: 1313 1313 1314 1314 PartyType (extension) 1315 - 1327 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] SenderType 1316 1316 1317 1317 Attributes: 1318 1318 ... ... @@ -1352,8 +1352,8 @@ 1352 1352 |URI|xs:anyURI|URI holds an information URL for the contact person. 1353 1353 |Email|xs:string|Email holds the email address for the contact person. 1354 1354 1355 -1. 1356 -11. 1367 +1. 1368 +11. 1357 1357 111. Simple Types 1358 1358 1359 1359 **HeaderTimeType: **Provides a union type of xs:date and xs:dateTime for the header fields in the message. ... ... @@ -1362,13 +1362,13 @@ 1362 1362 1363 1363 xs:dateTime, xs:date. 1364 1364 1365 -1. 1377 +1. 1366 1366 11. Message Footer Namespace 1367 1367 1368 1368 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/message/footer** 1369 1369 1370 -1. 1371 -11. 1382 +1. 1383 +11. 1372 1372 111. Summary 1373 1373 1374 1374 Referenced Namespaces: ... ... @@ -1383,14 +1383,14 @@ 1383 1383 2 Complex Types 1384 1384 1 Simple Type 1385 1385 1386 -1. 1387 -11. 1398 +1. 1399 +11. 1388 1388 111. Global Elements 1389 1389 1390 1390 **Footer (FooterType): **Footer is used to communicate information such as error and warnings after the payload of a message. 1391 1391 1392 -1. 1393 -11. 1404 +1. 1405 +11. 1394 1394 111. Complex Types 1395 1395 1396 1396 **FooterType: **FooterType describes the structure of a message footer. The footer is used to convey any error, information, or warning messages. This is to be used when the message has payload, but also needs to communicate additional information. If an error occurs and no payload is generated, an Error message should be returned. ... ... @@ -1409,8 +1409,8 @@ 1409 1409 Derivation: 1410 1410 1411 1411 com:StatusMessageType (restriction) 1412 - 1413 - 1424 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] com:CodedStatusMessageType (extension) 1425 + [[image:Macintosh%20HD:Users:j:Documents:workspace_neon:xsd-docuementation:output:inherit.gif||alt="-"]] FooterMessageType 1414 1414 1415 1415 Attributes: 1416 1416 ... ... @@ -1431,8 +1431,8 @@ 1431 1431 |**Name**|**Type**|**Documentation** 1432 1432 |com:Text|com:TextType|Text contains the text of the message, in parallel language values. 1433 1433 1434 -1. 1435 -11. 1446 +1. 1447 +11. 1436 1436 111. Simple Types 1437 1437 1438 1438 **SeverityCodeType:**