W3C home > Mailing lists > Public > www-dom-xpath@w3.org > May 2000

RE: [dom-xpath] XPath or? (was RE: Announcing www-dom-xpath@w3.org)

From: Julian Reschke <reschke@muenster.de>
Date: Fri, 5 May 2000 00:14:22 +0200
To: <dave.pawson@virgin.net>, <www-dom-xpath@w3.org>
Message-ID: <NCBBIPMOPKLLGKJPBINCOEAHEDAA.reschke@muenster.de>
> From: www-dom-xpath-request@w3.org
> [mailto:www-dom-xpath-request@w3.org]On Behalf Of Dave Pawson
> Sent: Thursday, May 04, 2000 7:27 PM
> To: www-dom-xpath@w3.org
> Subject: RE: [dom-xpath] XPath or? (was RE: Announcing
> www-dom-xpath@w3.org)
> ...
>      Maybe this actually is the killer use case for XPath on DOM?
>      That an XSLT
>      engine should be able to use it rather than to have to
>      implement it's own
>      XPath implementation?
> Sorry to sound negative, but I haven't yet heard anything
> convincing that says this is 'real'.
> Some... may.. could.. I guess...
> Can I sound unconvinced that there is a real use case here.
> Regards, DaveP

The point I was trying to make (:-) was: if one aims for a "complete" API,
it certainly needs to implement all XPath functionality an imaginary
XSLT-on-top-of-DOM-implementation would need.

BTW: I am sure that those ones who work on persistent DOMs would love to be
able to use an off-the-shelf XSLT on top of their  own DOM/XPath

Received on Thursday, 4 May 2000 18:14:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:43:07 UTC