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 mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 2129BBC6C for ; Wed, 6 Feb 2008 21:44:53 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAOCqqUfAXQImh2dsb2JhbACQMgEBAQgKKYEVlS+GGw X-IronPort-AV: E=Sophos;i="4.25,313,1199660400"; d="scan'208";a="22313483" Received: from discorde.inria.fr ([192.93.2.38]) by mail4-smtp-sop.national.inria.fr with ESMTP; 06 Feb 2008 21:44:52 +0100 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m16KiqBT021473 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 6 Feb 2008 21:44:52 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAOCqqUfRVZKwk2dsb2JhbACQMgEBAQEHBAQLCBaBF5Uvhhs X-IronPort-AV: E=Sophos;i="4.25,313,1199660400"; d="scan'208";a="22313481" Received: from wa-out-1112.google.com ([209.85.146.176]) by mail4-smtp-sop.national.inria.fr with ESMTP; 06 Feb 2008 21:44:51 +0100 Received: by wa-out-1112.google.com with SMTP id m34so741215wag.9 for ; Wed, 06 Feb 2008 12:44:50 -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:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer:sender; bh=6DVM0qXSQrKw3GmHKvpJqwLLpKLFWwDgb1IWFt8xzlA=; b=tz7x/IPpQEPvg+twmUO6LabdL8je/veB+Y8P4I5xWJ/N8tTgeBA7GQE7org65NOP0uUvDQGThdlBDFG0niByQ6ml2Klb0N8IX0+vmPXv0Tv/rvBL2JXEzN/Wnqu6siUOA9UZbaFBmdmgds/soHd0/6P3XNb5O4WQUSCc2eGA+IM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer:sender; b=Oy2FlM+Iyl9E96Z3WzQO+a2wyZqc8YB3PzYhNCxBfdoOHbANDX3NUJ+3bL/i7Wc5ZB1VHOmm4LNgAAiqJSPB5n2/VnR+eS08SwP+aJTklkbMvPst3tcQ+XIUKqOiHlGx6c4fvLzU8LlPRB4gSDNrC2GMasOE/V3frR5yWi8a4tw= Received: by 10.114.150.1 with SMTP id x1mr4204316wad.46.1202330689531; Wed, 06 Feb 2008 12:44:49 -0800 (PST) Received: from ?192.168.1.58? ( [85.2.96.197]) by mx.google.com with ESMTPS id 31sm906667nfu.5.2008.02.06.12.44.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Feb 2008 12:44:49 -0800 (PST) Message-Id: <998006DB-6778-42F1-B2F4-31CB5E9AA6A2@erratique.ch> From: =?ISO-8859-1?Q?B=FCnzli_Daniel?= To: caml-list List Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v915) Subject: xmlm and names(paces) Date: Wed, 6 Feb 2008 21:44:52 +0100 X-Mailer: Apple Mail (2.915) Sender: =?ISO-8859-1?Q?Daniel=20B=FCnzli?= X-Miltered: at discorde with ID 47AA1C44.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; bunzli:01 buenzli:01 parsed:01 meaningless:01 prefixes:01 parse:02 daniel:04 daniel:04 converted:04 declarations:04 i'd:06 i'd:06 namespace:07 namespace:07 missing:07 Hello, As I previously said on this list I'm adding better namespace support =20= to xmlm. Up to now xmlm just parsed qualified names into their prefix =20= and local part (prefix, local). Now I'd like to provide the client =20 with expanded names (uri, local). Initially I planned to give the client choice between getting =20 qualified names or expanded names. However the prefix of qualified =20 names is really meaningless (it can be alpha converted) and thus =20 cannot be used to recognize anything in a document. One of the aim of =20= xmlm is simplicity, as such =13I think xmlm should only provide expanded = =20 names. However maybe I'm missing something so I'd like to ask the list if =20 someone think there is any use for clients to get qualified names ? If =20= I you do please tell me. Best, Daniel P.S. There is no distinction betwen qualified and expanded names if =20 you parse documents that have no prefixes and no default namespace =20 declarations. P.P.S. Name expansion has a performance cost but if I support only =20 expanded names I can better reduce it.