Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML.
XML has been designed for ease of implementation and for interoperability with both SGML and HTML.
It would be my job to take the supplied XML, extract out the data I needed and proceed accordingly. In order to write something reliable I needed to be able to validate that the supplied XML was as I expected. If you're familiar with XML then you're probably equally familar with XSD which, to quote Wikipedia . Indeed why is this more interesting than the newer, and hence obviously cooler, LINQ to XML? It's fine but I think that generally I prefer my XSDs to be as vanilla as possible.
Data; namespace XMLParser This entry was posted on March 10, 2011 at am and is filed under c#
But the glory of this situation is, I never have to think about it. All I have to deal with are nice strongly typed objects which makes writing robust code a doddle. As much as I like LINQ to XML I turned to use instead.
But now now I've investigated it a bit I've found that it, combined with the XSD/XML Schema Generator can make for a nice tool to add to the utility belt. But if you need it, as I did recently, then this is for you.
Truth be told, I've been aware of it for years but up until now I've not had need of it.
You can leave a response, or trackback from your own site.
You can follow any responses to this entry through the RSS 2.0 feed.
So I was delighted to discover an online tool to simplify the task. What this marvellous tool does is allow you to enter an example of your XML which it then uses to reverse engineer an XSD. This is great because it does the hard work for you, allowing you to step back, mop your brow and then heartily approve the results. Thanks to Ajay for bringing it to my attention though.
XML plays an important role in many different IT systems.
The j Query Certificate documents your knowledge of j Query.