[mmox] More LLIDL questions

"Hurliman, John" <john.hurliman@intel.com> Wed, 18 February 2009 20:40 UTC

From: "Hurliman, John" <john.hurliman@intel.com>
To: "mmox@ietf.org" <mmox@ietf.org>
Date: Wed, 18 Feb 2009 13:39:43 -0700
Thread-Topic: More LLIDL questions
Thread-Index: AcmSCQdElIdDvWmrRs66TZORxodjTQ==
Message-ID: <62BFE5680C037E4DA0B0A08946C0933D501FE18E@rrsmsx506.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mmox] More LLIDL questions
Precedence: list

; An LLSD value containing { member1 : true, member2 : true } comes in. Is member3 a string or an int?
&a = { member1 : true, member2 : false, member3 : string }
&a = { member1 : false, member2 : true, member3 : int }

; How is a parser supposed to handle this?
&b = { $ : &b }
; Or this?
&c = { $ : &d }
&d = { $ : &c }

; The first variant has the type uri. The second variant has the type string?
&e = uri
&e = "http://www.google.com/"

; Forward-slash seems like an odd addition to 0-9+A-Z. Why this character?
&f/ = "hello slash"


John

[mmox] More LLIDL questions Hurliman, John
Re: [mmox] More LLIDL questions Mark Lentczner
Re: [mmox] More LLIDL questions Hurliman, John
[mmox] LLSD Charles Krinke
Re: [mmox] LLSD Meadhbh Hamrick (Infinity)
Re: [mmox] More LLIDL questions Meadhbh Hamrick (Infinity)
Re: [mmox] LLSD Charles Krinke
Re: [mmox] LLSD Meadhbh Hamrick (Infinity)
Re: [mmox] More LLIDL questions Hurliman, John
Re: [mmox] LLSD Charles Krinke
Re: [mmox] LLSD Jesrad
Re: [mmox] LLSD Charles Krinke
Re: [mmox] More LLIDL questions Mark Lentczner
Re: [mmox] LLSD Meadhbh Hamrick (Infinity)
[mmox] LLSD and content schema Jon Watte
Re: [mmox] LLSD and content schema Morgaine
Re: [mmox] LLSD and content schema Meadhbh Hamrick (Infinity)
Re: [mmox] LLSD and content schema Jon Watte
Re: [mmox] LLSD and content schema Lisa Dusseault
Re: [mmox] LLSD and content schema Jon Watte