As part of the SOAP specifications it does not include specific definitions for data types, but it includes some built-in rules for encoding data types based on XML Schema specifications. For more details you can access: http://www.w3.org/2001/12/soap-encoding
The XML Schema specification has a list of already supported datatypes that are included in SOAP, you can find more information here: http://www.w3.org/TR/2000/WD-xmlschema-2-20000407/
The following are some of the primitive data types already supported by SOAP:
string: represents character strings in XML.
boolean: used for representing the mathematical concept of binary-valued logic: true or false
float: used for representing the IEEE single-precision 32-bit floating point type
double: used for representing the IEEE double-precision 64-bit floating point type
decimal: used for representing arbitrary precision decimal numbers
binary: used for representing arbitrary precision binary data
The following are some of the derived data types already supported by SOAP:
integer: this data type is derived from decimal
long: this data type is derived from integer.
int: this data type is derived from long.
short: this data type is derived from int.
byte: this data type is derived from short.
time: used for representing an instant of time that recurs every day
date: used for representing a period of time starting at midnight of an specific day and lasts for 24 hours
The XML Schema definition describes that new compound types should be defined by using a complexType element and it usually includes a set of element declarations, perhaps element references and attributes declarations.
The following is a compound definition for a complex type:
<xsd:complexType name = "Address" > <xsd:element name = "street" type = "xsd:string" /> <xsd:element name = "number" type = "xsd:integer" /> </xsd:complexType>