Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Sat, 20 Jul 2002, Dare Obasanjo wrote: > -----Original Message----- > From: Uche Ogbuji [mailto:uche.ogbuji@f...] > Sent: Sat 7/20/2002 1:04 PM > To: Garland foster > Cc: Dare Obasanjo; xml-dev@l... > Subject: Re: Question for the XPath and DOM folks > > >Than there can only be one answer to Dare's question, which is what I gave. > > Let's explore your answer then. So if I have a W3C XML Document Object Model (DOM) implementation containing the XML > > <foo> bar <![CDATA[ baz ]]> quux </foo> > > and query it with the following XPath > > //text() > > I should get back a single text node containing "bar baz quux". So a few > questions from an application programmer Before you even get into those questions, consider Thomas Passin's post, which said: >Results: > >===> msxml3: > >bar > >===> Saxon and Xalan (and Sablotron and XT): > >bar > >baz > >quux > >Putting the "//text()" up in the select attribute of the template works >the same in all three (it returns all three strings). > >This is a bit unnerving - what else does msxml3 disagree with the others >on that could lead to a really big difference? As I see it, that's a much more important question to answer rather than whether it's a DOM node or who its parents and children are. [snip] -- J. David Eisenberg http://catcode.com/
|
