Return-Path: <paul@luminas.co.uk>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 2780 invoked from network); 9 Feb 2001 13:23:42 -0000
Received: from cmailg1.svr.pol.co.uk (195.92.195.171)
  by h31.sny.collab.net with SMTP; 9 Feb 2001 13:23:42 -0000
Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk)
	by cmailg1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 14RDWY-0006ml-00
	for cocoon-dev@xml.apache.org; Fri, 09 Feb 2001 13:23:42 +0000
Received: from modem-64.ohio.dialup.pol.co.uk ([62.137.86.64] helo=hydrogen)
	by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 14RDWX-0006QD-00
	for cocoon-dev@xml.apache.org; Fri, 09 Feb 2001 13:23:42 +0000
Received: from paulr by hydrogen with local (Exim 3.20 #1 (Debian))
	id 14RDWR-0000m5-00
	for <cocoon-dev@xml.apache.org>; Fri, 09 Feb 2001 13:23:35 +0000
Date: Fri, 9 Feb 2001 13:23:35 +0000
From: Paul Russell <paul@luminas.co.uk>
To: cocoon-dev@xml.apache.org
Subject: Re: generate and additional xpath
Message-ID: <20010209132335.E630@hydrogen.internal.luminas.co.uk>
Reply-To: Paul Russell <prussell@apache.org>
References: <20010209115507.D630@hydrogen.internal.luminas.co.uk>
 <CHEGLKNOIJHFNDNBCIAJAEIACAAA.tcurdt@dff.st>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
In-Reply-To: <CHEGLKNOIJHFNDNBCIAJAEIACAAA.tcurdt@dff.st>;
 from tcurdt@dff.st on Fri, Feb 09, 2001 at 01:18:14PM +0100
Sender: Paul Russell <paulr@hydrogen.internal.luminas.co.uk>
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

* Torsten Curdt (tcurdt@dff.st) wrote :
> Yepp... another victim got hit by the syndrome ;)

Hehe.

> But do really think the creation of a DOM is needed? I'm not that into
> SAX but couldn't we just create the events for the xpath prefix?
> So we would get a tree structured like this (for example):
> <page>
>   <title>
> <page>
> <page>
>    <content>
>       ...
>    </content>
> </page>
> <page>
>    <content>
>       ....
>    </content>
> </page>

Sadly, that's not a valid XML document, so wouldn't cut the mustard.
SAX literally streams the document; there is no facility for inserting
nodes after the event. There *may* be a way of doing it under SAX, but
that would require an event driven XPath engine, and I'm not sure one is
available, yet.

> Don't know if it is really useful...
> ...just some idle thought ;)

Heh. It's certainly worth considering, yes. I think it's time I sent out
a summing up of all of these ideas and got on with getting votes and
then implementing. I've been really busy again recently, which has got
in the way (grr).


P.

-- 
Paul Russell                                 Email:   paul@luminas.co.uk
Technical Director                             Tel:  +44 (0)20 8553 6622
Luminas Internet Applications                  Fax:  +44 (0)870 28 47489
This is not an official statement or order.    Web:    www.luminas.co.uk