[
Lists Home |
Date Index |
Thread Index
]
- To: <veillard@redhat.com>
- Subject: RE: [xml-dev] Question for the XPath and DOM folks
- From: "Dare Obasanjo" <dareo@microsoft.com>
- Date: Sat, 20 Jul 2002 12:53:51 -0700
- Cc: <xml-dev@lists.xml.org>
- Thread-index: AcIwJfLfT2rTEFGlSIaE6402qu0G1wAALb0a
- Thread-topic: [xml-dev] Question for the XPath and DOM folks
Ahhh. But many vendors (including Microsoft) have shipped DOM implementations that enable XPath queries. Also the W3C DOM working group is in the process of standardizing XPath over the DOM as we speak[0] so you can't just punt and say it shouldn't happen and is thus undefined since it already does.
[0] http://www.w3.org/TR/2002/WD-DOM-Level-3-XPath-20020328/
-----Original Message-----
From: Daniel Veillard [mailto:veillard@redhat.com]
Sent: Sat 7/20/2002 12:45 PM
To: Dare Obasanjo
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Question for the XPath and DOM folks
On Sat, Jul 20, 2002 at 11:19:25AM -0700, Dare Obasanjo wrote:
> Given the following XML in a DOM document
>
> <foo>
> bar
> <![CDATA[
> baz
> ]]>
> quux
> </foo>
>
> and the following XPath
>
> //text()
>
> what should be the resulting DOM nodes and why? I can think of two answers but they both have problems.
Well the theorical answer is that XPath operates on an XPath
data model, not a DOM view. Your question has no answer, XPath is not
designed to work on a standard DOM tree, CDATA are transparently
turned in (the container) text node.
it returns the text node of the XPath data model which is the unique
children of the foo element node.
Daniel
--
Daniel Veillard | Red Hat Network https://rhn.redhat.com/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
|