• From: Robin Berjon <robin@k...>
• To: Sean McGrath <sean@d...>
• Date: Sun, 04 Mar 2001 21:18:15 +0100

At 10:49 04/03/2001 +0000, Sean McGrath wrote:
>Its me, Mr. Layers back again. Why not XPath -> WF XML
>and then a SAX API for it just drops out?

It's funny, I was thinking about using XPath -> API and then WF XML just
drops out as layered too :-) Imho, selectors can be complex enough that
it'll be just as hard (if not harder) to get XPath -> WF XML straight as it
will be to have XPath -> API. In addition to that, anyone wishing to
construct a selector object from SAX calls (instead of the more, hopefully
better, specialized SAXPath calls) will have to do more work. I'm pretty
sure that XPath APIs would be at first sight more complex to learn and
implement, but in fine much harder to use in useful ways. I'd be happy to
be proven wrong though.

-- robin b.
Heisenberg may have been here.

• References:
  • Re: We need an XPath API
    • From: "Simon St.Laurent" <simonstl@s...>
  • We need an XPath API
    • From: Charles Reitzel <creitzel@m...>
  • Re: We need an XPath API
    • From: Sean McGrath <sean@d...>

• Prev by Date: Re: About Infosets
• Next by Date: RE: We need an XPath API
• Previous by thread: Re: We need an XPath API
• Next by thread: Re: We need an XPath API
• Index(es):
  • Date
  • Thread