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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id 15F18BC6C for ; Wed, 6 Feb 2008 22:26:03 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAHu0qUfAXQImh2dsb2JhbACQLgEBAQgKKZY0hhs X-IronPort-AV: E=Sophos;i="4.25,314,1199660400"; d="scan'208";a="8874776" Received: from discorde.inria.fr ([192.93.2.38]) by mail3-smtp-sop.national.inria.fr with ESMTP; 06 Feb 2008 22:26:02 +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 m16LPxTl022808 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 6 Feb 2008 22:26:02 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAHu0qUfRVZKwk2dsb2JhbACQLgEBAQEHBAQLCBaWNoYb X-IronPort-AV: E=Sophos;i="4.25,314,1199660400"; d="scan'208";a="8874775" Received: from wa-out-1112.google.com ([209.85.146.176]) by mail3-smtp-sop.national.inria.fr with ESMTP; 06 Feb 2008 22:26:01 +0100 Received: by wa-out-1112.google.com with SMTP id m34so761634wag.9 for ; Wed, 06 Feb 2008 13:26:00 -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=3eWws8KVWRv0Y2v+bHx55NRfKULvUHaVjPILp29mBsI=; b=OKP/RvyHoj3QO71n0++v9tSZZenPhatSB4yVEbjP592kZGKQcPDJlYh+1Rg5Ms5RplH16BeiGpNnFh8zNtNYbYA1ksKjMC7QdKxbnmjSSsK0op4CB+kTMxrPQvGaev++TU92u1wM5r1VuNedjuWzM+JBqsJ+5s2KpRqtsxY4j6c= 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=FJqSbb9aU6h6rCb5GWTqVmvseTWJYAtOS/dqI7U+FEe1qPKDsfHP5LAa+LgXI9KQIxVcb3dO1sq4GHoxYxFxH/aU6cqXqJhpyl7sHg+bTL8cVZyAH5VkWbVxLTsi0LrFQo0eMFrd5Bv0Y31E6KbsxBYWROpXZsGFrDSELg5+LJk= Received: by 10.114.183.1 with SMTP id g1mr10619240waf.3.1202333160168; Wed, 06 Feb 2008 13:26:00 -0800 (PST) Received: from ?192.168.1.58? ( [85.2.96.197]) by mx.google.com with ESMTPS id h1sm27161860nfh.20.2008.02.06.13.25.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Feb 2008 13:25:59 -0800 (PST) Message-Id: <4F065FC5-974F-4F21-86CD-393AC977B582@erratique.ch> From: =?ISO-8859-1?Q?B=FCnzli_Daniel?= To: caml-list List In-Reply-To: <1202331557.6452.12.camel@Blefuscu> 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: Wed, 6 Feb 2008 22:26:04 +0100 References: <998006DB-6778-42F1-B2F4-31CB5E9AA6A2@erratique.ch> <1202331557.6452.12.camel@Blefuscu> X-Mailer: Apple Mail (2.915) Sender: =?ISO-8859-1?Q?Daniel=20B=FCnzli?= X-Miltered: at discorde with ID 47AA25E7.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; bunzli:01 buenzli:01 ad-hoc:01 namespaces:01 bindings:01 readable:01 caml-list:01 prefixes:01 prefixes:01 conventions:02 output:02 output:02 daniel:04 daniel:04 ecrit:06 Le 6 f=E9vr. 08 =E0 21:59, David Teller a =E9crit : > As far as I know, the only difference is when you try and produce > human-readable XML documents. In this case, there are often ad-hoc > conventions regarding which prefix maps to what namespace (e.g. for =20= > the > same namespace, xhtml: is more readable than, say, ns1:) -- which =20 > might > be useful for people writing, say, editors. As a side note I'll also add that xmlm's handling of namespaces is =20 going to keep attributes of the xmlns namespace instead of removing =20 them. This allows to know which prefix bindings were done in the =20 document. Given how output is going to work chaining xmlm's input with =20= output you'll get the same prefixes that were present on input =20 (provided the same ns is not bound to two different prefixes in a =20 given context in which case there may be differences). Best, Daniel