From: Alain Frisch <Alain.Frisch@inria.fr>
To: Stefano Zacchiroli <zack@bononia.it>
Cc: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Common XML interface
Date: Thu, 21 Apr 2005 08:59:47 +0200 [thread overview]
Message-ID: <42674F63.8030003@inria.fr> (raw)
In-Reply-To: <20050420132332.GA10928@fistandantilus.takhisis.org>
Stefano Zacchiroli wrote:
> On Wed, Apr 20, 2005 at 09:22:23AM +0200, Alain Frisch wrote:
>
>>It would be great to have some common interface. An event-driven
>>interface is probably easier to agree upon. There are many points to
>
>
> Even if certainly easier to agree upon, event-driven interface for XML
> are harder to program than tree based ones.
Some applications really need stream based processing: loading the XML
document into memory is out of question (because it is huge) and/or
processing needs to happen as soon as data is available (e.g. for the
Jabber protocol).
> Basic tree operations should not be that hard to agree upon ...
I'm afraid it will be hard. To start with, do we want mutable trees,
upward pointers ? Do we want to keep locations, namespace declarations,
comments, entity references ... ? Which whitespace to remove ?
Anyway, a tree representation can easily be built on top of an
event-driven interface. The difficult part in parsing XML is really
lexing. We can try to agree upon one or several standard tree
representation, but I believe we should start with an event-driven
interface.
Is someone willing to set-up a mailing list for this discussion ?
-- Alain
next prev parent reply other threads:[~2005-04-21 7:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 6:15 CamlGI question Mike Hamburg
2005-04-18 7:29 ` [Caml-list] " Robert Roessler
2005-04-18 13:49 ` Alex Baretta
2005-04-18 14:31 ` Gerd Stolpmann
2005-04-18 16:04 ` Michael Alexander Hamburg
2005-04-18 16:28 ` Alex Baretta
2005-04-19 3:23 ` Mike Hamburg
2005-04-19 3:26 ` [Caml-list] CamlGI question [doh] Mike Hamburg
2005-04-19 9:18 ` Gerd Stolpmann
2005-04-19 15:28 ` Mike Hamburg
[not found] ` <1113933973.6248.76.camel@localhost.localdomain>
2005-04-19 18:44 ` Eric Stokes
2005-04-19 19:18 ` Christophe TROESTLER
2005-04-19 21:11 ` Eric Stokes
2005-04-19 9:31 ` Alex Baretta
2005-04-19 11:33 ` [Caml-list] CamlGI question Christophe TROESTLER
2005-04-19 12:51 ` Christopher Alexander Stein
2005-04-19 19:03 ` Common CGI interface (was: [Caml-list] CamlGI question) Christophe TROESTLER
2005-04-19 19:54 ` Gerd Stolpmann
2005-04-20 6:55 ` Jean-Christophe Filliatre
2005-04-20 7:22 ` Common XML interface (was: Common CGI interface) Alain Frisch
2005-04-20 11:15 ` [Caml-list] " Gerd Stolpmann
2005-04-20 11:38 ` Nicolas Cannasse
2005-04-20 13:23 ` Stefano Zacchiroli
2005-04-21 6:59 ` Alain Frisch [this message]
2005-04-21 11:34 ` [Caml-list] Common XML interface Gerd Stolpmann
2005-04-20 20:00 ` Common CGI interface Christophe TROESTLER
2005-04-20 21:06 ` [Caml-list] " Gerd Stolpmann
2005-04-21 7:36 ` [Ocamlnet-devel] " Florian Hars
2005-04-21 10:41 ` Gerd Stolpmann
2005-04-25 10:38 ` Christophe TROESTLER
2005-04-26 11:08 ` Gerd Stolpmann
2005-05-06 20:14 ` Christophe TROESTLER
2005-05-10 0:07 ` [Caml-list] " Christophe TROESTLER
2005-05-10 0:10 ` Christophe TROESTLER
2005-04-26 16:24 ` [Caml-list] " Eric Stokes
2005-05-06 20:14 ` Christophe TROESTLER
2005-04-19 20:13 ` [Caml-list] CamlGI question Michael Alexander Hamburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42674F63.8030003@inria.fr \
--to=alain.frisch@inria.fr \
--cc=caml-list@inria.fr \
--cc=zack@bononia.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox