Validating the xml
The editor uses heuristics to open a file using the best interpretation of the tagging that it can.
For example, an element with a missing end tag is simply assumed to end at the end of the document.
For additional information and examples that describe or demonstrate the end-to-end process of working with XML documents in Microsoft Office Word 2003, please see the following articles in the Microsoft Developer Network (MSDN) Library.
The XML editor will process XML files that are invalid or not well-formed.
helps knowing what the inputs and outputs for the web service are.
Then there are the badly-formed web services: they tell you what they expect from you, but then return some nonsense.
I suppose I should have experimented but at that point I just took for granted it had to be valid, end of story! For example if you wish to pick out one or two pieces of data out the XML then move on then it would be best just to extract them and move on.
However if you need the whole XML document, so for example you want to transform it to some other XML format that needs all the fields, then I would get a schema involved.
It's a bit like asking, why do we test our programs. Of course there are scenarios where you know the data isn't wrong, because the program that generates it is well tested and well trusted. I generally find that validating XML is very useful when you're dealing with remote services. If you're just transferring data from a client to server where you control both sides, then it's less useful.I know it makes the XML better and more Semantic but what are the overall benefits of validating XML? Sure, if you only write out some data for your own application to read it may be enough if it just works.If you send a file to somebody else matters may be different.Registration only takes a minute and is of course perfectly free.We are also planning on adding more features to user accounts in the future, such as more advanced comparison options.