From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=1.0 required=5.0 tests=AWL,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id D17F4BC6C for ; Thu, 7 Feb 2008 09:59:58 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAHRXqkfAXQImh2dsb2JhbACQMgEBAQgKKYEVlEiFaQ X-IronPort-AV: E=Sophos;i="4.25,315,1199660400"; d="scan'208";a="7037836" Received: from discorde.inria.fr ([192.93.2.38]) by mail2-smtp-roc.national.inria.fr with ESMTP; 07 Feb 2008 09:59:53 +0100 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m178xqh9008450 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Thu, 7 Feb 2008 09:59:52 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAHRXqkdA6ba/kmdsb2JhbACQMgEBAQEHBAQJChaBF5RIhWk X-IronPort-AV: E=Sophos;i="4.25,315,1199660400"; d="scan'208";a="8897956" Received: from nf-out-0910.google.com ([64.233.182.191]) by mail3-smtp-sop.national.inria.fr with ESMTP; 07 Feb 2008 09:59:51 +0100 Received: by nf-out-0910.google.com with SMTP id g13so967561nfb.7 for ; Thu, 07 Feb 2008 00:59:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; bh=wi+iwGiUh2sjElv4CSitUs7WWe9E6JzHF136/yk4IaE=; b=fUKvVAvmsY3pCT7HUJKG3LesfjZkGgp3wANkO9TWShWNM1JyDR6kuFmAVCiykfcymexscJgbQQkYUcPn+CALlvIQblOgpIsk9fSz9q/ewuHTNehguZ+EjlEK0YpOWbL3/m0rYfZRzf6sYBGJQxaBwin99bE/rQ+xirCmLGvP2CQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; b=WoDIUDUEljjG9vbx3XEksZbHli9hZ6//dYVBn3pZ64cbWETgq+xj8XHpRkDbBB43he4YUFhysknfd3dyU9j8q8j4ZthQGMH1fW+Acwx4FrG4zojDhLJAX/f/d2dPGL54775qMI00pyLDdpx4LwTVZC4exvZd2+sssmfLuIq2gQc= Received: by 10.78.107.8 with SMTP id f8mr19626548huc.40.1202374791217; Thu, 07 Feb 2008 00:59:51 -0800 (PST) Received: from ?192.168.1.58? ( [85.2.3.160]) by mx.google.com with ESMTPS id 6sm4301177nfv.14.2008.02.07.00.59.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Feb 2008 00:59:50 -0800 (PST) Message-Id: <03F3E69B-A0EB-47E9-99C4-47F55CC580B6@erratique.ch> From: =?ISO-8859-1?Q?B=FCnzli_Daniel?= To: caml-list List In-Reply-To: <20080207081337.DD110A99B@Adric.metnet.fnmoc.navy.mil> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v915) Subject: Re: [Caml-list] xmlm and names(paces) Date: Thu, 7 Feb 2008 09:59:54 +0100 References: <20080207081337.DD110A99B@Adric.metnet.fnmoc.navy.mil> X-Mailer: Apple Mail (2.915) Sender: =?ISO-8859-1?Q?Daniel=20B=FCnzli?= X-Miltered: at discorde with ID 47AAC888.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; bunzli:01 buenzli:01 oleg:01 alain's:01 invokes:01 parser:01 iirc:01 wrote:01 ideally:01 parsing:01 parsing:01 caml-list:01 prefixes:01 data:02 functional:02 Le 7 f=E9vr. 08 =E0 09:13, oleg@okmij.org a =E9crit : > It should be mentioned that the prefixes of qualified names cannot > just be alpha-converted. It is quite common to see the following, > quoted from http://www.w3.org/TR/xmlschema-0/ > > > ... > Argh ! I now understand Alain's comment about the need to keep that =20 information. This is a complete misuse of the namespace recommandation =20= which says nothing about binding pefixes in attribute and character =20 data. The w3c is really hopeless. > One may really wonder what kind of people wrote all those voluminous > XML recommendations. You tell me. > So, ideally one may wish to keep the original prefix (in addition to > its corresponding URL). It is also reasonable for a user to specify a > `shortcut'. Unlike the prefix, which is chosen by the author of the > document, a shortcut is chosen by the person who invokes a parser. As mentionned in my previous email with xmlm you can do that by =20 yourself since all the info is there and you have full control on the =20= parsing result. However for the aformentionned case this may mean a =20 lot of work. On the other hand xml schema seems to be seen as a broken =20= technology (even the xml spec editor says so iirc). So the question =20 is, is it worth complexifiying the interface to facilitate the parsing =20= of this obviously broken and marginal (is it ?) case. > Incidentally, some of the design decisions of SSAX (despite being > produced by an enemy) might be pertinent to this discussion. Thanks for the link, I will have a look at it (functional programming =20= languages are no enemies). Best, Daniel