All Downloads are FREE. Search and download functionalities are using the official Maven repository.

xsd.2_0.SDMXMessage.xsd Maven / Gradle / Ivy





	
	
	
	
	
	
	
	
	
	
	
		
			The Structure is a message that contains all the structural metadata about a data set. This can be key families, concepts, or codelists.
		
	
	
		
			The GenericDataType is used to convey data in a cross-key-family form.
		
	
	
		
			The UtilityData contains data in an XML form which is specific to each key family, according to standard mappings, and which is optimized to support guided editing tools and other applications which expect a "typical" XML schema. This format can be used to validate data in a key-family-specific fashion as is typically expected of XML schemas, and requires the entire data set. It cannot be used for incremental updates.
		
	
	
		
			CompactData contains data in an XML format which is optimized for incremental updating, and the transfer of large data sets bilaterally. It is specific to each key family, according to standard mappings. It allows for key values to be expressed at a Group level.
		
	
	
		
			CrossSectionalData contains data in an XML format which is optimized for describing many observations at a single point in time, and for the transfer of large data sets bilaterally. It is specific to each key family, according to standard mappings. It allows for key values to be expressed from the Group level down to the Observation level, and permits multiple observation values with different "measures".
		
	
	
		
			GenericMetadata contains reported metadata in an XML format which supports any metadata structure definition.
		
	
	
		
			MetadataReport contains a metadata report which is specific to a particular metadata structure definition. This format allows for the validation of the constraints described in the metadata structure definition with a generic XML parser.
		
	
	
		
			The RegistryInterfaceMessage is used to conduct all interactions with the SDMX Registry Services.
		
	
	
		
			The QueryMessageType is used to query databases published on the web, and to invoke web services. It allows for queries to be made regarding both data and structural metadata.
		
	
	
		
			The MessageGroupType is used to allow for more than one data or metadata message of a single type to be included in a single transmission. This element arises from the requirement for some services to be able to exchange data or metadata which may come from more than one source, and be structured according to more than one key family or metadata structure definition.
		
	
	
		
			The Message is an abstract type which is used by all of the messages, to allow inheritance of common features. It also provides uniqueness constraints for the header fields.
		
		
			
				
					
					
				
				
					
					
				
				
					
					
				
				
					
					
				
			
		
	
	
		
			StructureType defines the contents of a structure message.
		
		
			
				
					
					
					
					
					
					
					
					
					
					
					
					
				
			
		
	
	
		
			GenericDataType defines the contents of a GenericData message.
		
		
			
				
					
				
			
		
	
	
		
			UtilityDataType defines the contents of a UtilityData message.
		
		
			
				
					
				
			
		
	
	
		
			CompactDataType defines the contents of a CompactData message.
		
		
			
				
					
				
			
		
	
	
		
			CrossSectionalDataType defines the contents of a CrossSectionalData message.
		
		
			
				
					
				
			
		
	
	
		
			GenericMetadataType defines the contents of a Generic Metadata message.
		
		
			
				
					
				
			
		
	
	
		
			MetadataReportType defines the contents of a metadata structure definition-specific Metadata Report message.
		
		
			
				
					
				
			
		
	
	
		
			QueryMessageType defines the contents of a QueryMessage.
		
		
			
				
					
				
			
		
	
	
		
			This is a type which describes a structure for holding all of the various dedicated registry interface message types.
		
		
			
				
					
					
					
					
					
					
					
					
					
					
					
					
					
					
					
				
			
		
	
	
		
			MessageGroupType defines the contents of a MessageGroup message.
		
		
			
				
					
					
					
					
					
					
				
				
			
		
	
	
		
			Header type is declared globally so that it can function as the head of a substitution group for schemas which are used internally. While this is an exception to the overall design of SDMX-ML, many users feel this construct is useful. Note that when SDMX-ML messages are exchanged outside an organization, the standard header should be used - no assumptions about additional fields in substituted types should be made unless explicitly agreed-to by counterparties.
		
	
	
		
			HeaderType defines the header fields used for all messages. ID identifies a data flow definition, which, when combined with time, uniquely identifies the data set. Test indicates whather the message is for test purposes or not. Truncated is used in data messages which are responding to Query messages, and is set to true only if the response has been truncated to meet size limits suggested by the defaultLimit attribute in the Query mesage.  Name provides a name for the transmission. Prepared is the date prepared. Sender is information about the sender, and Receiver is information about the receiver. Agency provides the code identifier/abbreviation for the maintenance agency of a data set. Data set id provides an identifier for a contained data set. Action code provides a code for determining whether the enclosed message is an Update or Delete message (not to be used with the UtilityData message). KeyFamilyRef is used to reference a key family for a contained data set, using its id. (This information is required at the DataSet level for some messages, but is provided here as a convenience for those messages which do not require it.) KeyFamilyAgency specifies the agency of the key family using its coded id.  Fields which refer to a contained data set need not be used if the message contains a query or structural information - these messages provide specific fields for holding this information. The ones here are not to be used as defaults. Extracted is a time-stamp from the system rendering the data; ReportingBegin and ReportingEnd provide the time period covered by the message (in the case of data). Source provides human-readable information about the source of the data.
		
		
			
			
			
			
			
			
				
					
					
				
			
			
				
					
					
				
			
			
			
			
			
			
			
			
			
			
		
	
	
		
			PartyType defines the information which is sent about various parties such as senders and receivers of messages. The Name is the ID of the party, and Contact provides contact details.
		
		
			
			
			
		
		
		
	
	
		
			ContactType provides defines the contact information about a party. The Name provides a human-readable name.
		
		
			
			
			
			
				
				
				
				
				
			
		
	
	
		
			Provides a union type of xs:date and xs:dateTime for the header fields in the message.
		
		
	





© 2015 - 2024 Weber Informatics LLC | Privacy Policy