Changes for page Part I. Message Namespace

Last modified by Helena K. on 2026/06/09 12:28

From 3.4 to 3.5 From 15.2 to 15.3

From version 3.5

edited by Helena K.
on 2025/07/02 11:00

Change comment: There is no comment for this version

To version 15.2

edited by Helena K.
on 2026/06/09 12:22

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (0 modified, 1 added, 1 removed)
- SUZ.Methodology.Code.MethodologyClass[0]
- SKMS.Methodology.Code.MethodologyClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Part I. Message
++Part I. Message Namespace

Content

@@ -4,11 +4,11 @@
  = 1 Introduction =
--At the core of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]].
++At the core of the [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] XML messages are the message namespaces. These namespaces define the general structure of all messages and define the specific messages that are available for exchange in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]].
--There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] is http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message. Associated with this is another sub-namespace, http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer. This namespace defines footer (% style="color:#e74c3c" %)level(%%) information that is available in messages which might require non-standard payload information to be transmitted.
++There are two namespaces associated with the messages. The main namespace schema which defines every message in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] is http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message. Associated with this is another sub-namespace, http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message/footer. This namespace defines footer level information that is available in messages which might require non-standard payload information to be transmitted.
--In general, every message in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] follows common format of:
++In general, every message in [[SDMX>>doc:sdmx:Glossary 2\.1.Statistical data and metadata exchange.WebHome]] follows common format of:
  * Header
  * Payload (0..n)
@@ -37,21 +37,21 @@
  |(% style="width:610px" %)http://www.w3.org/2001/XMLSchema|(% style="width:360px" %)xs
  Contents:
--7 Global Elements
--16 Complex Types
++7 Global Elements
++16 Complex Types
 Simple Type
  === 2.1.2 Global Elements ===
--**Structure (StructureType):** Structure is a message that contains [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]]. It may contain any of the following; categorisations, [[category schemes>>doc:sdmx:Glossary.Category scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], (% style="color:#e74c3c" %)concepts(%%) ([[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]]), data and metadata (% style="color:#e74c3c" %)constraints(%%), [[data flows>>doc:sdmx:Glossary.Dataflow.WebHome]], [[hierarchical code lists>>doc:sdmx:Glossary.Hierarchical code list.WebHome]], [[metadata flows>>doc:sdmx:Glossary.Metadataflow.WebHome]], [[metadata structure definitions>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], organisation schemes, processes, [[reporting taxonomies>>doc:sdmx:Glossary.Reporting taxonomy.WebHome]], structure (% style="color:#e74c3c" %)maps(%%), [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)maps(%%), .
++**Structure (StructureType):** Structure is a message that contains structural metadata. It may contain any of the following; categorisations, category schemes, code lists, concepts (concept schemes), data and metadata constraints, data flows, hierarchical code lists, metadata flows, metadata structure definitions, organisation schemes, processes, reporting taxonomies, structure maps, representation maps.
--**StructureSpecificData (StructureSpecificDataType):** StructureSpecificData is used to convey data structure specific according to [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]]. The payload of this message (i.e. the [[data sets>>doc:sdmx:Glossary.Data set.WebHome]]) will be based on XML schemas which are specific to the [[data structure definition>>doc:sdmx:Glossary.Data structure definition.WebHome]] and the orientation (i.e. the observation [[dimension>>doc:sdmx:Glossary.Dimension.WebHome]]) of the data.
++**StructureSpecificData (StructureSpecificDataType):** StructureSpecificData is used to convey data structure specific according to data structure definition. The payload of this message (i.e. the data sets) will be based on XML schemas which are specific to the data structure definition and the orientation (i.e. the observation dimension) of the data.
  **GenericMetadata (GenericMetadataType):** GenericMetadata contains reported metadata in a format which supports any metadata structure definition.
--**RegistryInterface (RegistryInterfaceType):** RegistryInterface is used to conduct all interactions with the [[SDMX Registry>>doc:sdmx:Glossary.SDMX Registry.WebHome]] Services.
++**RegistryInterface (RegistryInterfaceType):** RegistryInterface is used to conduct all interactions with the SDMX Registry Services.
--**SubmitStructureRequest (SubmitStructureRequestType):** SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, (% style="color:#e74c3c" %)concepts(%%) and [[concept schemes>>doc:sdmx:Glossary.Concept scheme.WebHome]], [[code lists>>doc:sdmx:Glossary.Code list.WebHome]], etc.) to be submitted may be communicated in-line or be supplied in a referenced [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] Structure messages external to the registry. A response will indicate status and contain any relevant error information.
++**SubmitStructureRequest (SubmitStructureRequestType):** SubmitStructureRequest is used to submit structure definitions to the repository. The structure resources (key families, agencies, concepts and concept schemes, code lists, etc.) to be submitted may be communicated in-line or be supplied in a referenced SDMX-ML Structure messages external to the registry. A response will indicate status and contain any relevant error information.
  **SubmitStructureResponse (SubmitStructureResponseType):** SubmitStructureResponse is returned by the registry when a structure submission request is received. It indicates the status of the submission, and carries any error messages which are generated, if relevant.
@@ -59,17 +59,17 @@
  === 2.1.3 Complex Types ===
--***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.
++//**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.
  Content:
--Header, {any element with namespace of http://www.sdmx.org/resources/sdmxml/schemas/v3_1/message}*, Footer?
++Header, {any element with namespace of http:~/~/www.sdmx.org/resources/sdmxml/schemas/v3_1/message}, Footer?
  Element Documentation:
  (% style="width:1007.29px" %)
  |**Name**|(% style="width:192px" %)**Type**|(% style="width:662px" %)**Documentation**
--|Header|(% style="width:192px" %)*BaseHeaderType*|(% style="width:662px" %)
++|Header|(% style="width:192px" %)//BaseHeaderType//|(% style="width:662px" %)
  |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.
  **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,7 +76,7 @@
  Derivation:
--MessageType (restriction)
++MessageType (restriction)
     StructureType
  Content:
@@ -105,7 +105,7 @@
  (% style="width:1005.29px" %)
  |**Name**|(% style="width:269px" %)**Type**|(% style="width:585px" %)**Documentation**
  |Header|(% style="width:269px" %)StructureSpecificDat aHeaderType|(% style="width:585px" %)
--|DataSet|(% style="width:269px" %)*DataSetType*|(% style="width:585px" %)
++|DataSet|(% style="width:269px" %)//DataSetType//|(% style="width:585px" %)
  |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.
  **GenericMetadataType:** GenericMetadataType defines the contents of a generic metadata message.
@@ -112,7 +112,7 @@
  Derivation:
--MessageType (restriction)
++MessageType (restriction)
     GenericMetadataType
  Content:
@@ -130,11 +130,11 @@
  Derivation:
--MessageType (restriction)
++MessageType (restriction)
     RegistryInterfaceType
  Content:
--Header, (SubmitRegistrationsRequest|SubmitRegistrationsResponse|QueryRegistrationRequest|QueryRegistrationResponse|SubmitStructureRequest|SubmitStructureResponse|SubmitSubscriptionsRequest|SubmitSubscriptionsResponse|QuerySubscriptionRequest|QuerySubscriptionResponse|NotifyRegistryEvent)?, Footer?
++Header, (SubmitRegistrationsRequest | SubmitRegistrationsResponse | QueryRegistrationRequest | QueryRegistrationResponse | SubmitStructureRequest | SubmitStructureResponse | SubmitSubscriptionsRequest | SubmitSubscriptionsResponse | QuerySubscriptionRequest | QuerySubscriptionResponse | NotifyRegistryEvent)?, Footer?
  Element Documentation:
@@ -158,8 +158,8 @@
  Derivation:
--MessageType (restriction)
--   RegistryInterfaceType (restriction)
++MessageType (restriction)
++   RegistryInterfaceType (restriction)
           SubmitStructureRequestType
  Content:
@@ -176,8 +176,8 @@
  Derivation:
--MessageType (restriction)
--   RegistryInterfaceType (restriction)
++MessageType (restriction)
++   RegistryInterfaceType (restriction)
           SubmitStructureResponseType
  Content:
@@ -202,7 +202,7 @@
  |**Name**|**Type**|**Documentation**
  |ErrorMessage|CodedStatusMessageType|ErrorMessage contains the error message. It can occur multiple times to communicate message for multiple errors, or to communicate the error message in parallel languages. If both messages for multiple errors and parallel language messages are used, then each error message should be given a code in order to distinguish message for unique errors.
--***BaseHeaderType*:** BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
++//**BaseHeaderType:**// BaseHeaderType in an abstract base type that defines the basis for all message headers. Specific message formats will refine this
  Content:
  ID, Test, Prepared, Sender, Receiver*, Name*, Structure*, DataProvider?, MetadataProvider?, DataSetAction?, DataSetID*, Extracted?, ReportingBegin?, ReportingEnd?, EmbargoDate?, Source
@@ -217,7 +217,7 @@
  |Sender|SenderType|(% style="width:612px" %)Sender is information about the party that is transmitting the message.
  |Receiver|PartyType|(% style="width:612px" %)Receiver is information about the party that is the intended recipient of the message.
  |Name|TextType|(% style="width:612px" %)Name provides a name for the transmission. Multiple instances allow for parallel language values.
--|Structure|*PayloadStructureType*|(% style="width:612px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
++|Structure|//PayloadStructureType//|(% style="width:612px" %)Structure provides a reference to the structure (either explicitly or through a structure usage reference) that describes the format of data or reference metadata. 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.
  |DataProvider|DataProviderReferenceType|(% style="width:612px" %)DataProvider identifies the provider of the data for a data message.
  |MetadataProvider|MetadataProviderReferenceType|(% style="width:612px" %)MetadataProvider identifies the provider of the metadata for a metadata message.
  |DataSetAction|ActionType|(% style="width:612px" %)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).
@@ -319,12 +319,13 @@
  Element Documentation:
--|**Name**|**Type**|**Documentation**|
--|ID|IDType|ID identifies an identification for the message, assigned by the sender.|
--|Test|xs:boolean|Test indicates whether the message is for test purposes or not.|
--|Prepared|HeaderTimeType|Prepared is the date the message was prepared.|
--|Sender|SenderType|Sender is information about the party that is transmitting the message.|
--|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.|
++(% style="width:1002.29px" %)
++|**Name**|**Type**|**Documentation**
++|ID|IDType|ID identifies an identification for the message, assigned by the sender.
++|Test|xs:boolean|Test indicates whether the message is for test purposes or not.
++|Prepared|HeaderTimeType|Prepared is the date the message was prepared.
++|Sender|SenderType|Sender is information about the party that is transmitting the message.
++|Receiver|PartyType|Receiver is information about the party that is the intended recipient of the message.
  **PartyType:** PartyType defines the information which is sent about various parties such as senders and receivers of messages.
@@ -336,14 +336,16 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**|
--|id|IDType|The id attribute holds the identification of the party.|
++(% style="width:973.294px" %)
++|**Name**|**Type**|**Documentation**
++|id|IDType|The id attribute holds the identification of the party.
  Element Documentation:
--|**Name**|**Type**|**Documentation**|
--|Name|TextType|Name is a human-readable name of the party.|
--|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.|
++(% style="width:975.294px" %)
++|(% style="width:114px" %)**Name**|(% style="width:132px" %)**Type**|(% style="width:727px" %)**Documentation**
++|(% style="width:114px" %)Name|(% style="width:132px" %)TextType|(% style="width:727px" %)Name is a human-readable name of the party.
++|(% style="width:114px" %)Contact|(% style="width:132px" %)ContactType|(% style="width:727px" %)Contact provides contact information for the party in regard to the transmission of the message.
  **SenderType:** SenderType extends the basic party structure to add an optional time zone declaration.
@@ -360,15 +360,17 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**|
--|id|IDType|The id attribute holds the identification of the party.|
++(% style="width:1000.29px" %)
++|**Name**|**Type**|**Documentation**
++|id|IDType|The id attribute holds the identification of the party.
  Element Documentation:
--|**Name**|**Type**|**Documentation**|
--|Name|TextType|Name is a human-readable name of the party.|
--|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.|
--|Timezone|TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".|
++(% style="width:1003.29px" %)
++|**Name**|**Type**|**Documentation**
++|Name|TextType|Name is a human-readable name of the party.
++|Contact|ContactType|Contact provides contact information for the party in regard to the transmission of the message.
++|Timezone|TimezoneType|Timezone specifies the time zone of the sender, and if specified can be applied to all un-time zoned time values in the message. In the absence of this, any dates without time zone are implied to be in an indeterminate "local time".
  **ContactType:** ContactType provides defines the contact information about a party.
@@ -377,15 +377,16 @@
  Element Documentation:
--|**Name**|**Type**|**Documentation**|
--|Name|TextType|Name contains a human-readable name for the contact.|
--|Department|TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.|
--|Role|TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.|
--|Telephone|xs:string|Telephone holds the telephone number for the contact person.|
--|Fax|xs:string|Fax holds the fax number for the contact person.|
--|X400|xs:string|X400 holds the X.400 address for the contact person.|
--|URI|xs:anyURI|URI holds an information URL for the contact person.|
--|Email|xs:string|Email holds the email address for the contact person.|
++(% style="width:1002.29px" %)
++|**Name**|**Type**|**Documentation**
++|Name|TextType|Name contains a human-readable name for the contact.
++|Department|TextType|Department is designation of the organisational structure by a linguistic expression, within which the contact person works.
++|Role|TextType|Role is the responsibility of the contact person with respect to the object for which this person is the contact.
++|Telephone|xs:string|Telephone holds the telephone number for the contact person.
++|Fax|xs:string|Fax holds the fax number for the contact person.
++|X400|xs:string|X400 holds the X.400 address for the contact person.
++|URI|xs:anyURI|URI holds an information URL for the contact person.
++|Email|xs:string|Email holds the email address for the contact person.
  === 2.1.4 Simple Types ===
@@ -402,13 +402,14 @@
  Referenced Namespaces:
--|**Namespace**|**Prefix**|
--|http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|common|
--|http://www.w3.org/2001/XMLSchema|xs|
++(% style="width:970.294px" %)
++|(% style="width:495px" %)**Namespace**|(% style="width:472px" %)**Prefix**
++|(% style="width:495px" %)http://www.sdmx.org/resources/sdmxml/schemas/v3_1/common|(% style="width:472px" %)common
++|(% style="width:495px" %)http://www.w3.org/2001/XMLSchema|(% style="width:472px" %)xs
  Contents:
--1 Global Element
--2 Complex Types
++1 Global Element
++2 Complex Types
 Simple Type
  === 2.2.2 Global Elements ===
@@ -424,8 +424,9 @@
  Element Documentation:
--|**Name**|**Type**|**Documentation**|
--|Message|FooterMessageType|Message contains a single error, information, or warning message. A code is provided along with an optional severity. The text of the message can be expressed in multiple languages.|
++(% style="width:1005.29px" %)
++|**Name**|**Type**|**Documentation**
++|Message|FooterMessageType|Message contains a single error, information, or warning message. A code is provided along with an optional severity. The text of the message can be expressed in multiple languages.
  **FooterMessageType:** FooterMessageType defines the structure of a message that is contained in the footer of a message. It is a status message that have a severity code of Error, Information, or Warning added to it.
@@ -443,14 +443,16 @@
  Attribute Documentation:
--|**Name**|**Type**|**Documentation**|
--|code|xs:string|The code attribute holds an optional code identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.|
--|severity|SeverityCodeType| |
++(% style="width:1008.29px" %)
++|**Name**|**Type**|(% style="width:785px" %)**Documentation**
++|code|xs:string|(% style="width:785px" %)The code attribute holds an optional code identifying the underlying error that generated the message. This should be used if parallel language descriptions of the error are supplied, to distinguish which of the multiple error messages are for the same underlying error.
++|severity|SeverityCodeType|(% style="width:785px" %)
  Element Documentation:
--|**Name**|**Type**|**Documentation**|
--|Text|TextType|Text contains the text of the message, in parallel language values.|
++(% style="width:1015.29px" %)
++|**Name**|**Type**|(% style="width:542px" %)**Documentation**
++|Text|TextType|(% style="width:542px" %)Text contains the text of the message, in parallel language values.
  === 2.2.4 Simple Types ===
@@ -460,7 +460,8 @@
  Enumerations:
--|**Value**|**Documentation**|
--|Error|Error indicates the status message coresponds to an error.|
--|Warning|Warning indicates that the status message corresponds to a warning.|
--|Information|Information indicates that the status message corresponds to an informational message.|
++(% style="width:1026.29px" %)
++|**Value**|**Documentation**
++|Error|Error indicates the status message coresponds to an error.
++|Warning|Warning indicates that the status message corresponds to a warning.
++|Information|Information indicates that the status message corresponds to an informational message.

SUZ.Methodology.Code.MethodologyClass[0]

index

...	...	@@ -1,1 +1,0 @@
1		-1

SKMS.Methodology.Code.MethodologyClass[0]

Index

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