From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alain@frisch.fr>
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled 
	version=3.1.3
X-Original-To: caml-list@yquem.inria.fr
Delivered-To: caml-list@yquem.inria.fr
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by yquem.inria.fr (Postfix) with ESMTP id E40F4BC6C
	for <caml-list@yquem.inria.fr>; Thu,  7 Feb 2008 23:08:34 +0100 (CET)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAEsQq0dQoE1yiGdsb2JhbACQJA0BAQEIBAYICRibQg
X-IronPort-AV: E=Sophos;i="4.25,318,1199660400"; 
   d="scan'208";a="22376538"
Received: from pasmtpa.tele.dk ([80.160.77.114])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 07 Feb 2008 23:08:34 +0100
Received: from [192.168.9.171] (unknown [62.243.120.69])
	by pasmtpA.tele.dk (Postfix) with ESMTP id B186480173C;
	Thu,  7 Feb 2008 23:08:33 +0100 (CET)
Message-ID: <47AB802B.1000201@frisch.fr>
Date: Thu, 07 Feb 2008 23:03:23 +0100
From: Alain Frisch <alain@frisch.fr>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?B=FCnzli_Daniel?= <daniel.buenzli@erratique.ch>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] xmlm and names(paces)
References: <998006DB-6778-42F1-B2F4-31CB5E9AA6A2@erratique.ch> <47AA2C33.70902@frisch.fr> <B227B75D-06FC-4F8F-9880-38FE4D32FF1F@erratique.ch>
In-Reply-To: <B227B75D-06FC-4F8F-9880-38FE4D32FF1F@erratique.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam: no; 0.00; frisch:01 frisch:01 bunzli:01 namespaces:01 well-formed:01 namespaces:01 event-based:01 unbound:01 parsed:01 wrote:01 caml-list:01 alain:01 alain:01 prefixes:01 parse:02 

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