[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: We need an XPath API

From: Sean McGrath <sean@digitome.com>
To: "Simon St.Laurent" <simonstl@simonstl.com>,Charles Reitzel <creitzel@mediaone.net>, xml-dev@lists.xml.org
Date: Sun, 04 Mar 2001 10:49:31 +0000

At 04:53 PM 3/3/01 -0500, Simon St.Laurent wrote:
>At 04:29 PM 3/3/01 -0500, Charles Reitzel wrote:
> >Proposal: let's give XPath the SAX treatment.
> >
> >What should such an API do?  How should it behave?
>
>Just for prior art, there's a Simple API for CSS.  Don't know if there'd be
>any overlap at all, but you never know:
>http://www.xmlhack.com/read.php?item=685
>http://www.w3.org/TR/SAC/
>

Its me, Mr. Layers back again. Why not XPath -> WF XML
and then a SAX API for it just drops out?

regards,
Sean

Follow-Ups:
- Re: We need an XPath API
  - From: Robin Berjon <robin@knowscape.com>
- Re: We need an XPath API
  - From: Eric van der Vlist <vdv@dyomedea.com>

References:
- We need an XPath API
  - From: Charles Reitzel <creitzel@mediaone.net>
- Re: We need an XPath API
  - From: "Simon St.Laurent" <simonstl@simonstl.com>

Prev by Date: Re: Best way to parse XML data and display in on a browser
Next by Date: Re: Blowout
Previous by thread: Re: We need an XPath API
Next by thread: Re: We need an XPath API
Index(es):
- Date
- Thread