Check out the following link: http://www.w3schools.com/xsl/cdcatalog_with_xsl.xml
The page comes up as a nicely formatted HTML page, but if you do "View Source", you'll see that it's just XML data. At the top, it references an XSLT file that handles the transformation - that's what I was referring to when I said "no programming". You can also transform an XML file with XSLT using .NET code (or just about any other language), but for quick and simple transformation, all you need is just that one line at the top of your XML. Actually, the whole tutorial on w3schools is pretty nice - worth checking out: http://www.w3schools.com/xsl/default.asp The complete list if their tutorials is at: http://www.w3schools.com/sitemap/sitemap_tutorials.asp There's stuff in there on XSD, DTD, and a bunch of other XML technologies, great for getting a quick understanding of them. Regarding using DOM parsers or the .NET framework classes, I really don't know. I've used XSD and XSLT outside of .NET only - inside .NET, I've only worked with simple XmlReader/XmlWriter objects and basic serialization. But I do know that XML support inside of .NET is extensive - anything you want to do can be done probably two or three different ways using the .NET framework, so I'd probably suggest looking in the framework before trying any third-party stuff. On Jun 12, 9:33 am, Learner <pra...@gmail.com> wrote: > Hi Joe, > > Thanks a bunch. Your explantion helps me understand where we use > XSLT. I am going through a small XML, XSLT exmple at > > http://www.csharpfriends.com/Articles/getArticle.aspx?articleID=63 > > there are files named sampledoc.xml and sample.xsl files in text area > as samples to test and see the result.html. The 'Transform' method is > the one that converts the xml into an html out put using XSLT. > > In your last paragrph you said that you didn't need to use any > programming at all to convert into HTML in your scenario. Could you > please take couple of minutes to explain how it was in your scnario? > In the given example could it be done with out using the 'Transofrm' > method? > > And the other question I would have is in the example link I provided > here the guy was not using any parsers like DOM or SAX (off course > this is an event based and used for huge xml files) but atleast he > didn't use DOM parser in this scenario to manipulate the sampledoc.xml > XML document but just used the default .NET name spaces instead. Then > my question is when we need to use pasers like DOM (for XML files) > instead of the default .NET namespaces? Or in what scenarios we use > one over the other? > > You really are making a person to quickly understand and dive into XML > world. Thanks for the help again. > > Thanks, > > -L > > On Jun 12, 11:32 am, Joe Enos <j...@jtenos.com> wrote: > > > XPath is for querying XML data, not converting it or navigating it. > > Think of it like SQL for XML data. > > > You can use XSLT to transform XML from one format to another - suppose > > your job function is to receive XML data from your clients, and upload > > it into a central repository - each client gives you the same basic > > data, but in a different format. You can use XSLT to turn that into a > > standard format, which your system knows how to handle - that way, you > > don't have to program a bunch of different input formats into your > > system - it only needs to know how to handle one file type. All you'd > > need is to build an XSLT file for each client. > > > For example, you can convert: > > <Person FirstName="John" LastName="Doe" /> > > into > > <Person><FirstName>John</FirstName><LastName>Doe</LastName></Person> > > > I've used it once to convert XML into HTML - we had an application > > that stored business rules in XML, and wanted a visual representation > > of that, so we could easily see what the XML was "saying". We > > converted it into HTML, adding things like style tags so that certain > > sections stood out by color, boldness, etc. Once the XSLT was done, > > all we needed to do was transform it, and it spit out the HTML - no > > programming required. > > > On Jun 12, 8:23 am, Learner <pra...@gmail.com> wrote: > > > > Hi, > > > > I have a high level understanding of why the above technologies > > > are used. > > > > XML - mainly used for data transformation from desperate systems > > > XSLT - is used to transform the XML documents into other XML, or HTML > > > or WML or any other browser recognizable formats > > > XPATH - is used to navigate throught the XML file (please correct me > > > if I am worng) > > > XSD - The most I know about the XSD is strongly typed datasets which I > > > used in my recent assignment. I created .XSD files to store the data > > > that I get from the database and used those (strongly typed) datasets > > > to populate/bind to the .NET controls in the front. Is there any thing > > > that I need to know about XSD files other than what I know in my > > > scenario or if when some one talks about XML Schema Defintion (XSD?) > > > then the knowledge I have on XSD (files) is no where related to this? > > > > The another thing is I am trying to find a besiness scenarion (need) > > > of transformaing XML documents into per say a HTML out put using the > > > XSLT. > > > > In one of the projects I had to deal with the XML files which were > > > comming from the JAVA world where I used a DOM parser to manipulate > > > the XML data files in VB.NET and sotred the data in a SQL Server > > > database. And later populate that in various modules of the systems as > > > needed. > > > > But I am trying to understand a business scenario where I would need > > > to transform the XML files directly into any of the above said formats > > > using XSLT. Could some one please help me a scenario where I could > > > have used or should use XSLT and XPATH? > > > > Thanks, > > > > -L- Hide quoted text - > > > - Show quoted text -
