What is a valid XML?  |     
     If XML is confirming to DTD rules then it is a valid     XML.   |     
     What is CDATA section in XML?  |     
     All data is normally parsed in XML but if you want to     exclude some elements, you will need to put those elements in CDATA.   |     
     What is XSL?  |     
     XSL (the extensible Style sheet Language) is used to     transform XML document to some other document. Therefore, its     transformation document which can convert XML to some other document. For     instance, you can apply XSL to XML and convert it to HTML document or     probably CSV files.   |     
     Which are the namespaces in .NET used for XML?  |     
     “System.xml.dll” is the actual physical file, which has     all XML implementation. Below are the commonly used namespaces:-  
 
System.Xml 
System.Xml.Schema 
System.Xml.XPath 
System.Xml.Xsl  |     
     What are the standard ways of parsing XML document?  |     
     
       XML parser sits in between the XML document and the       application who want to use the XML document. Parser exposes set of       well-defined interfaces, which can be used by the application for adding,       modifying, and deleting the XML document contents. Now whatever       interfaces XML parser exposes should be standard or else that would lead       to different vendors preparing there own custom way of interacting with       XML document.  
 
There are two standard specifications, which are very common and should       be followed by a XML parser:-  
 
DOM: - Document Object Model. 
DOM is a W3C recommended way for treating XML documents. In DOM, we load       entire XML document into memory and allows us to manipulate the structure       and data of XML document.  
 
SAX: - Simple API for XML. 
SAX is event driven way for processing XML documents. In DOM, we load the       whole XML document in to memory and then application manipulates the XML       document. However, this is not always the best way to process large XML       documents, which have huge data elements. For instance, you only want one       element from the whole XML document or you only want to see if the XML is       proper which means loading the whole XML in memory will be quiet resource       intensive. SAX parsers parse the XML document sequentially and emit       events like start and end of the document, elements, text content etc.       Therefore, applications who are interested in processing these events can       register implementations of callback interfaces. SAX parser then only       sends those event messages, which the application has demanded.   |         
  |        
 
  |     
     In What scenarios will you use a DOM parser and SAX     parser?  |     
     If you do not need all the data from the XML file then     SAX approach is much preferred than DOM as DOM can be quiet memory     intensive. In short, if you need large portion of the XML document its     better to have DOM.  
 
With SAX parser, you have to write more code than DOM.  
 
If you want to write the XML in to a file, DOM is the efficient way to do     it.  
 
Some time you only need to validate the XML structure and do not want to     retrieve any Data for those instances SAX is the right approach.   |     
     How was XML handled during COM times?  |     
     During COM, it was done by using MSXML 4.0. So old     languages like VB6, VC++ used MSXML 4.0, which was shipped with SP1     (Service Pack 1).   |     
     What is the main difference between MSML and .NET     Framework XML classes?  |     
     MSXML supports XMLDOM and SAX parsers while .NET     framework XML classes support XML DOM and XML readers and writers.  
 
MSXML supports asynchronous loading and validation while parsing. For     instance, you can send synchronous and asynchronous calls to a remote URL.     However, as such there is not direct support of synchronous and     asynchronous calls in .NET framework XML. However, it can be achieved by     using “System.Net” namespaces.   |     
     What are the core functionalities in XML .NET framework?     Can you explain in detail those functionalities?  |     
     
        
  |        The XML API for the .NET Framework comprises the       following set of functionalities:  
 
XML readers 
With XML readers, the client application gets reference to instance of       reader class. Reader class allows you to scroll forward through the       contents like moving from node to node or element to element. You can       compare it with the “SqlDataReader” object in ADO.NET, which is forward       only. In short, XML reader allows you to browse through the XML document.        
 
XML writers 
Using XML writers, you can store the XML contents to any other storage       media. For instance,you want to store the whole in memory XML to a       physical file or any other media.  
 
XML document classes 
XML documents provides a in memory representation for the data in an       XMLDOM structure as defined by W3C. It also supports browsing and editing       of the document. Therefore, it gives you a complete memory tree structure       representation of your XML document.   |        
 
  |     
     What is XSLT?  |     
     XSLT is a rule-based language used to transform XML     documents in to other file formats. XSLT are nothing but generic     transformation rules, which can be applied to transform XML document to     HTML, CS, Rich text etc.   |     
      
  |     
     
  |