Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries [Thread Prev] >Thread Next - Re: DOM Vs XPath + ancestor : whats the point? DOM Vs XPath + ancestor : whats the point?To: NULL Date: 8/2/2004 1:11:00 PM Having spent a day or so trying to understand XPath + ancestor nodesets, to create a subset of an existing document, I am not overwhelmed by its usefullness. I know I can use the XML DOM for this purpose but I thought XPath was intended to make it simpler! In the following newgroup newsgroup message it appears the XPATH is unable to perform what I would have thought are relatively basic filtering operations on an XML input file. http://sqljunkies.com/Newsgroups/microsoft.public.dotnet.xml/2004/3/31/13945 1.aspx While I understand that XSLT exists for transforming documents from one format to another, surely XPATH should be able to perform what is effectively a filtering operation ie only retaining the nodes you do want . In other words the format of the file does not change - as its just a subset *********************************************************** Is this a fault of the XPath spec or the MS node set created? | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
