From: Alain Frisch <alain@frisch.fr>
To: Jim Miller <gordon.j.miller@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [OSR] Suggested topic - XML processing API
Date: Tue, 05 Feb 2008 06:02:54 +0100 [thread overview]
Message-ID: <47A7EDFE.1050805@frisch.fr> (raw)
In-Reply-To: <beed19130802041923o951d2cfq6907a3826e0cddad@mail.gmail.com>
Jim Miller wrote:
> I await suggestions/flames.
As suggested before, you really need to say something, at least, about:
- namespaces (including for attributes): the most acceptable solution is
probably to do nothing about them and remove the first argument to the
XmlElement constructor;
- encoding of strings in the internal representation: probably always utf-8;
- whether the parser may create XmlMany nodes: probably no.
Other remarks:
- a 'pull' API (where the client asks the parser for more parsing
events/tokens) is more convenient than the SAX-like 'push' API. You
might want to add such an API to you spec;
- having a common spec for several libs makes more sense if they can
share common types; maybe you should use polymorphic variants instead of
regular ones?
-- Alain
next prev parent reply other threads:[~2008-02-05 5:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 0:54 Jim Miller
2008-01-30 2:37 ` [Caml-list] " Bünzli Daniel
2008-01-30 3:26 ` Jim Miller
2008-01-30 7:35 ` Alain Frisch
2008-01-30 10:32 ` Bünzli Daniel
2008-01-30 10:35 ` Jon Harrop
2008-01-30 17:25 ` Jim Miller
2008-02-05 3:23 ` Jim Miller
2008-02-05 5:02 ` Alain Frisch [this message]
2008-02-05 8:36 ` Bünzli Daniel
2008-02-05 9:51 ` Vincent Hanquez
2008-02-05 10:13 ` Jacques Garrigue
2008-02-05 11:14 ` Vincent Hanquez
2008-02-05 10:31 ` Bünzli Daniel
2008-02-05 10:43 ` Nicolas Pouillard
2008-02-05 13:29 ` Jon Harrop
2008-02-05 14:53 ` micha
2008-02-05 14:53 ` Jon Harrop
2008-02-05 14:57 ` David Teller
2008-02-05 11:21 ` Vincent Hanquez
2008-02-05 8:15 ` Vincent Hanquez
2008-02-05 11:16 ` Stefano Zacchiroli
2008-01-30 15:55 ` Vincent Hanquez
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=47A7EDFE.1050805@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@yquem.inria.fr \
--cc=gordon.j.miller@gmail.com \
/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