[
Lists Home |
Date Index |
Thread Index
]
- From: uche.ogbuji@fourthought.com
- To: Francis Norton <francis@redrice.com>
- Date: Tue, 28 Dec 1999 19:54:39 -0700
> I get the impression that my desire to have xpath included in the DOM
> may be naive, but I haven't yet formed a clear picture of the
> alternatives. Is there an architectural solution which would allow one
> to plug any arbitrary (but compatible) xpath processor in to a DOM
> processor? And then use it to select nodes from a document that has been
> opened in the DOM, and then update those nodes using the DOM?
I don't know whether it's what you term an "architectural solution", but
4XPath and 4DOM allow such manipulation right now:
http://FourThought.com/4Suite
--
Uche Ogbuji
FourThought LLC, IT Consultants
uche.ogbuji@fourthought.com (970)481-0805
Software engineering, project management, Intranets and Extranets
http://FourThought.com http://OpenTechnology.org
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
