caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: tab@snarc.org (Vincent Hanquez)
To: "Bünzli Daniel" <daniel.buenzli@erratique.ch>
Cc: caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] [OSR] Suggested topic - XML processing API
Date: Wed, 30 Jan 2008 16:55:18 +0100	[thread overview]
Message-ID: <20080130155518.GA9526@snarc.org> (raw)
In-Reply-To: <52FAAA41-5B70-4F87-9F83-B8A96EA48D34@erratique.ch>

On Wed, Jan 30, 2008 at 03:37:59AM +0100, Bünzli Daniel wrote:
>
> Le 30 janv. 08 à 01:54, Jim Miller a écrit :
>
>> Inspired by the existing recommendation on the cocan wiki for I/O, I'd 
>> like to recommend the development of a standard interface for XML 
>> processing.  Currently there are many different implementations of XML 
>> parsers but their interfaces are very different and don't allow for easy 
>> swapping of implementations.
>
> There are many approaches to xml parsing (partial implementations, 
> leniency, well-formedness, validity, etc.), to parsing results (tree, 
> custom data structure, stream, namespace support etc.) and to processing 
> (mainly dependent on the parsing result). Xml processing cannot be seen as 
> an abstract datatype with different implementations, there are different 
> ways.
>
> As such I'm not sure such an interface is really feasible. Now if you see a 
> common pattern or concrete type signatures that could be changed to make 
> parsers more compatible do not hesitate to communicate them. If it benefits 
> the users of my parser and remains in its philosophy I'll happily implement 
> them. But _you_ have to make concrete proposal, I'm not going to research 
> this. Please do not just initiate a discussion because you like the 
> abstract idea of being able to swap xml parser implementations, make 
> proposals.

a do-everything interface is absolutely impossible, but providing a "simple"
library that parse DOM and SAX style to fill _common_ needs, is
relatively "easy".

For people that got specifics needs, there's nothing preventing them to
implement/use a side library without using the common distributed library.

-- 
Vincent Hanquez


      parent reply	other threads:[~2008-01-30 15:55 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
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 [this message]

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=20080130155518.GA9526@snarc.org \
    --to=tab@snarc.org \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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;
as well as URLs for NNTP newsgroup(s).