• To: "Jeff Rafter" <jeffrafter@d...>
• Subject: Re: Does SAX make sense?
• From: Christian Nentwich <christian@s...>
• Date: Mon, 21 Apr 2003 12:09:49 +0100
• Cc: xml-dev@l...
• In-reply-to: <008e01c3078d$64a47af0$22ecd90c@c1980223a>
• Organization: Systemwire
• References: <E196lKL-0001Uj-00@b...><02d301c30646$b3ddc9c0$4bc8a8c0@A...><008e01c3078d$64a47af0$22ecd90c@c1980223a>
• Reply-to: Christian Nentwich <christian@s...>

> XPath comes up here and came up in several of the other responses. Perhaps
> someone could answer what class of XPaths, if known prior to document parse,
> can not be satisfied during the document parsing?

Here's a shot at which ones can, from the STX (Streaming
Transformations for XML) spec.

http://stx.sourceforge.net/documents/spec-stx-20030114.html#stxpath

There's a few more things that STX processors will allow, for example
to access the first text child of a node when the node is encountered
as an event, that's convenient (requires a time delay of one event
when reporting events).

I'm sure the folks on the STX mailing list would happily discuss their
extensive experience with event matching, they've been implementing it
for over a year..

Christian

• References:
  • Re: ANN: White Paper - "Using OWL to Avoid Syntactic Rigor Mortis"
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • Does SAX make sense?
    • From: "Rick Jelliffe" <ricko@a...>
  • Re: Does SAX make sense?
    • From: "Jeff Rafter" <jeffrafter@d...>

• Prev by Date: Re: Does SAX make sense?
• Next by Date: Re: Software Management Vocabularies
• Previous by thread: Re: Does SAX make sense?
• Next by thread: Re: ANN: White Paper - "Using OWL to Avoid Syntactic Rigor Mortis"
• Index(es):
  • Date
  • Thread