caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: "Bünzli Daniel" <daniel.buenzli@erratique.ch>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] xmlm and names(paces)
Date: Thu, 07 Feb 2008 23:03:23 +0100	[thread overview]
Message-ID: <47AB802B.1000201@frisch.fr> (raw)
In-Reply-To: <B227B75D-06FC-4F8F-9880-38FE4D32FF1F@erratique.ch>

Bünzli Daniel wrote:
> Le 6 févr. 08 à 22:52, Alain Frisch a écrit :
>> It is also a good idea to be able to parse XML documents that conform
>> to the XML spec but not the XML Namespaces spec.
> 
> But don't you automatically get that ?
> 
> A document that has no xmlns namespace declarations and no prefixes if 
> parsed according to the xmlns spec will result in names with empty 
> namespace names.

The following documents are well-formed w.r.t. the XML spec:

<a::::x/>   (syntactically invalid QName w.r.t. XML Namespaces)

<a:x/>   (unbound prefix)

>> type name = string * [`N of string * string|`U of string * string|`X]
> [...]
> 
> Too heavy weight for my taste.

Actually, I agree. What about doing nothing about namespaces?  For the 
event-based API at least, and maybe for the tree-based one as well, it 
doesn't seem too bad to let the client manage it (maybe you can simply 
provide a small module to help manage namespace dictionnaries and 
resolution).

-- Alain


  parent reply	other threads:[~2008-02-07 22:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 20:44 Bünzli Daniel
2008-02-06 20:59 ` [Caml-list] " David Teller
2008-02-06 21:26   ` Bünzli Daniel
2008-02-06 21:52 ` Alain Frisch
2008-02-06 22:56   ` Bünzli Daniel
2008-02-06 23:51     ` Bünzli Daniel
2008-02-07 22:03     ` Alain Frisch [this message]
2008-02-07  8:13 oleg
2008-02-07  8:59 ` [Caml-list] " Bünzli Daniel

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=47AB802B.1000201@frisch.fr \
    --to=alain@frisch.fr \
    --cc=caml-list@yquem.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).