Re: [mmox] XML serialization

Jon Watte <jwatte@gmail.com> Mon, 23 February 2009 20:56 UTC

Return-Path: <jwatte@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF7BF3A68A6 for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 12:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level:
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8n6YjWedQPt for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 12:56:13 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by core3.amsl.com (Postfix) with ESMTP id D25273A6897 for <mmox@ietf.org>; Mon, 23 Feb 2009 12:56:12 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so1976983yxm.49 for <mmox@ietf.org>; Mon, 23 Feb 2009 12:56:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=K4NYY9YVaw7NrJV1HZvkISvFf4YG5DHjM+6ZUIxj+Do=; b=mCw5AX6HnxMwOeNV0HU0z0TytMye1DSCoTMC2U4Fah8zgPjcwh58obl8WKQJbR5sCG 6sNisUic0yMJeKKVAasLacfDL99Hg70H1hmDgfwWd16v7x0AZNCDP0bnyk7gXPZTLQB2 Ez3Xjd+2Z7SdGK3g7/mgv7hXy3DBV0C4FBVY8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=mUfZnL5juW7j3fRadTAVd9VNC2vHqRCFAOC1M9cdT1eWL3VCDpv0nQHpDxcCT8GqS+ x8cB/fRI8C5lr8vgKSn8IVsQ/WozlTP4DwQvcwyCYZ+gztshNz95GpoTcxF/qYmC9dxj gubnIG0gY+jqqqHH26zvBWpJpMp2XFtEJuNJ0=
Received: by 10.100.225.19 with SMTP id x19mr2371784ang.24.1235422590911; Mon, 23 Feb 2009 12:56:30 -0800 (PST)
Received: from ?192.168.168.111? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id d21sm6210451and.6.2009.02.23.12.56.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 12:56:28 -0800 (PST)
Message-ID: <49A30D7A.3040003@gmail.com>
Date: Mon, 23 Feb 2009 12:56:26 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Catherine Pfeffer <cathypfeffer@gmail.com>
References: <ebe4d1860902230239q207d4c0ar5b0582ad7ca855bf@mail.gmail.com>
In-Reply-To: <ebe4d1860902230239q207d4c0ar5b0582ad7ca855bf@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] XML serialization
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2009 20:56:13 -0000

Catherine Pfeffer wrote:
> <llsd>
>    <map>
>       <entry>
>         <key>success</key>
>         <boolean>true</boolean>
>       </entry>
>       <entry>
>         <key>something_i_like_to_eat_on_sundays</key>
>         <string>bananas</string>
>        </entry>
>    </map>
> </llsd>

A better way is

<map>
  <value type="boolean" key="success>true</value>
  <value type="string" 
key="something_i_like_to_eat_on_sundays">bananas</value>
</map>

natural way to express it.This has less of the angle bracket tax, and it 
has a VERY straight-forward parsing style. In fact, in my opinion it's 
the most In XPath, it's now trivial: "value[@key=success]"


I'm working on a list of the things I think are wrong with the current 
proposal, of which this is one thing (there are about six). If we're 
open to change on those things (including this), then I could get behind 
the LLSD. Stay tuned :-)

Sincerely,

jw