caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Sébastien Hinderer" <Sebastien.Hinderer@ens-lyon.org>
To: caml-list@inria.fr
Subject: Which types for representing HTML documents ?
Date: Mon, 8 Jun 2009 06:59:57 +0200	[thread overview]
Message-ID: <20090608045957.GA7611@pema> (raw)

Dear all,

According to you, how could an HTML document best be represented in
OCaml ?
In particular: would you rather use classes or records, polymorphic
variants or normal constructors ?

There are attributes which can occur in several elements, such as id,
class... How shold these be represented ?
Should the types reflect the differences between inline elements and
other types of elements ?

Many thanks in advance for your suggestions,
Sébastien.


             reply	other threads:[~2009-06-08  4:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  4:59 Sébastien Hinderer [this message]
2009-06-08  6:03 ` [Caml-list] " Gabriel Kerneis
2009-06-08 10:05 ` Richard Jones
2009-06-08 11:35 ` Martin Jambon

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=20090608045957.GA7611@pema \
    --to=sebastien.hinderer@ens-lyon.org \
    --cc=caml-list@inria.fr \
    /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).