Skip to Content

Changes for page Part I. Message Namespace

Last modified by Elena on 2025/09/10 11:19
From version 3.4
edited by Helena
on 2025/07/02 10:55
Change comment: There is no comment for this version
To version 3.2
edited by Helena
on 2025/07/02 10:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,15 +26,14 @@
26 26  
27 27  Referenced Namespaces:
28 28  
29 -(% style="width:973.294px" %)
30 -|(% style="width:610px" %)**Namespace**|(% style="width:360px" %)**Prefix**
31 -|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|(% style="width:360px" %)common
32 -|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|(% style="width:360px" %)dsd
33 -|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer|(% style="width:360px" %)footer
34 -|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic|(% style="width:360px" %)metadata
35 -|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/registry|(% style="width:360px" %)registry
36 -|(% style="width:610px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/structure|(% style="width:360px" %)structure
37 -|(% style="width:610px" %)http://www.w3.org/2001/XMLSchema|(% style="width:360px" %)xs
29 +|**Namespace**|**Prefix**|
30 +|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
31 +|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/data/structurespecific|dsd|
32 +|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer|footer|
33 +|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/metadata/generic|metadata|
34 +|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/registry|registry|
35 +|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/structure|structure|
36 +|http://www.w3.org/2001/XMLSchema|xs|
38 38  
39 39  Contents:
40 40  7 Global Elements
... ... @@ -67,10 +67,9 @@
67 67  
68 68  Element Documentation:
69 69  
70 -(% style="width:1007.29px" %)
71 -|**Name**|(% style="width:192px" %)**Type**|(% style="width:662px" %)**Documentation**
72 -|Header|(% style="width:192px" %)*BaseHeaderType*|(% style="width:662px" %)
73 -|Footer|(% style="width:192px" %)FooterType|(% style="width:662px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
69 +|**Name**|**Type**|**Documentation**|
70 +|Header|*BaseHeaderType*| |
71 +|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
74 74  
75 75  **StructureType:** StructureType defines the contents of a structure message. The payload is optional since this message may be returned from a web service with only information in the footer.
76 76  
... ... @@ -84,11 +84,10 @@
84 84  
85 85  Element Documentation:
86 86  
87 -(% style="width:1007.29px" %)
88 -|**Name**|(% style="width:228px" %)**Type**|(% style="width:589px" %)**Documentation**
89 -|Header|(% style="width:228px" %)StructureHeaderType|(% style="width:589px" %)
90 -|Structures|(% style="width:228px" %)StructuresType|(% style="width:589px" %)
91 -|Footer|(% style="width:228px" %)FooterType|(% style="width:589px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
85 +|**Name**|**Type**|**Documentation**|
86 +|Header|StructureHeaderType| |
87 +|Structures|StructuresType| |
88 +|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
92 92  
93 93  **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.
94 94  
... ... @@ -102,11 +102,10 @@
102 102  
103 103  Element Documentation:
104 104  
105 -(% style="width:1005.29px" %)
106 -|**Name**|(% style="width:269px" %)**Type**|(% style="width:585px" %)**Documentation**
107 -|Header|(% style="width:269px" %)StructureSpecificDat aHeaderType|(% style="width:585px" %)
108 -|DataSet|(% style="width:269px" %)*DataSetType*|(% style="width:585px" %)
109 -|Footer|(% style="width:269px" %)FooterType|(% style="width:585px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
102 +|**Name**|**Type**|**Documentation**|
103 +|Header|StructureSpecificDat aHeaderType| |
104 +|DataSet|*DataSetType*| |
105 +|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
110 110  
111 111  **GenericMetadataType:** GenericMetadataType defines the contents of a generic metadata message.
112 112  
... ... @@ -120,11 +120,10 @@
120 120  
121 121  Element Documentation:
122 122  
123 -(% style="width:1012.29px" %)
124 -|**Name**|(% style="width:309px" %)**Type**|(% style="width:593px" %)**Documentation**
125 -|Header|(% style="width:309px" %)GenericMetadataHeaderType|(% style="width:593px" %)
126 -|MetadataSet|(% style="width:309px" %)MetadataSetType|(% style="width:593px" %)
127 -|Footer|(% style="width:309px" %)FooterType|(% style="width:593px" %)Footer is used to communicate information such as error and warnings after the payload of a message.
119 +|**Name**|**Type**|**Documentation**|
120 +|Header|GenericMetadataHeade rType| |
121 +|MetadataSet|MetadataSetType| |
122 +|Footer|FooterType|Footer is used to communicate information such as error and warnings after the payload of a message.|
128 128  
129 129  **RegistryInterfaceType:** This is a type which describes a structure for holding all of the various dedicated registry interface message types.
130 130  
... ... @@ -140,10 +140,10 @@
140 140  
141 141  |**Name**|**Type**|**Documentation**|
142 142  |Header|BasicHeaderType| |
143 -|SubmitRegistrationsRequest|SubmitRegistrationsRequestType|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.|
144 -|SubmitRegistrationsResponse|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.|
145 -|QueryRegistrationRequest|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.|
146 -|QueryRegistrationResponse|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.|
138 +|SubmitRegistrationsR equest|SubmitRegistrationsR equestType|SubmitRegistrationsRequest is sent to the registry by an agency or data/metadata provider to request one or more registrations for a data set or metadata set. The data source to be registered must be accessible to the registry services at an indicated URL, so that it can be processed by those services.|
139 +|SubmitRegistrationsR esponse|SubmitRegistrationsR esponseType|SubmitRegistrationsResponse is sent to the agency or data/metadata provider in response to a submit registrations request. It indicates the success or failure of each registration request, and contains any error messages generated by the registration service.|
140 +|QueryRegistrationReq uest|QueryRegistrationReq uestType|QueryRegistrationRequest is used to query the contents of a registry for data sets and metadata sets. It specifies whether the result set should include metadata sets, data sets, or both. The search can be characterized by providing constraints including reference periods, data regions, and data keys.|
141 +|QueryRegistrationRes ponse|QueryRegistrationRes ponseType|QueryRegistrationResponse is sent as a response to any query of the contents of a registry. The result set contains a set of links to data and/or metadata If the result set is null, or there is some other problem with the query, then appropriate error messages and statuses will be returned.|
147 147  |SubmitStructureReque st|SubmitStructureReque stType|SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.|
148 148  |SubmitStructureRespo nse|SubmitStructureRespo nseType|SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.|
149 149  |SubmitSubscriptionsR equest|SubmitSubscriptionsR equestType|SubmitSubscriptionsRequest contains one or more requests submitted to the registry to subscribe to registration and change events for specific registry resources.|