I can't get any SOAP messages to validate as valid XML.
For example, I took the SOAP message below off of Wikipedia and it failed the Validome validator. For example, W3C says that this xml is well-formed, but it actually is horribly invalid as Validome correctly points out.
In the absence of any schemas, the concept of validity makes no sense.
I've looked through the output from the validator and it's working fine, the SOAP message you're using is as fault. Also there are more errors that the validator isn't reporting I suspect once if finds one problem with the SOAP message it unwinds to the next parent element and carries on.
For instance the next element after If you have to work with this SOAP I suggest you create your own XSD, various tools exist to generate them from an existing Xml message.
Also contacting the site and passing on the problems you've found (using subtlety) would be useful to them.
If you don't have to use this service then so much the better.
When you say that W3C says it's well formed, I'm not sure what you mean.
For instance the inclusion of a space in the element name To make sure a SOAP message looks exactly how it should, you should validate it against all the schemas that are referenced in that message.
In your example, that's SOAP, WS-Addressing, and schema for the custom namespace (my Service).
The schemas for SOAP and WS-Addressing are available from the URL that's also used for the namespace, but that's just convention, not a requirement.
WSDL stands for Web Service Description Language and documents the methods that are available to be consumed in a web service.
A WSDL can be accessed via most browsers simply by typing in the url and adding ?