In the context of developing programs exchanging data on heterogeneous systems for operative systems and programming language, the SOAP protocol is the more used standard to overcome these infrastructural barriers.
In a nutshell, SOAP defines the data structures to be conveyed and the destination of the communication, the so-called endpoint.
The physical support on which these definitions are based is a particular XML file, known as WSDL from the extension that distinguishes it, and which response to the specifications of the World Wide Web Consortium (W3C), https://www.w3.org/.
The definition of the data structures contained in a WSDL responds to another standard, defined by Microsoft in 2006 and also sanctioned by the W3C, the XML Schema.
The XML Schema, known as XSD after the extension of its files, is also based on XML structures.
The composition of a WSDL file, therefore, includes one or more XSDs, depending on how many data structures it includes, and the definition of the destination endpoints.
The so-called WebServices, the real interface programs that convey the data to be transferred from one system to another, are based on the SOAP protocol.
What does XMas do in this context to support the developer? Starting from an XSD file, XMas can generate an example of the corresponding XML data file, xsd2xml, a service also available on numerous websites. Still, above all, it can encapsulate it within a WSDL, xsd2wsdl, thus generating the file by W3C specifications.
While it is easy to find xsd2xml services, it is not so easy to find the xsd2wsdl service and XMas fills this gap.