IETF Logo Mail Archive

Re: [ogpx] type-system : binary elements in JSON serializations

"Hurliman, John" <john.hurliman@intel.com> Tue, 30 March 2010 18:42 UTC

Return-Path: <john.hurliman@intel.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D04DB3A6978 for <ogpx@core3.amsl.com>; Tue, 30 Mar 2010 11:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level:
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4]
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 2eFp6sF6EDXt for <ogpx@core3.amsl.com>; Tue, 30 Mar 2010 11:42:34 -0700 (PDT)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by core3.amsl.com (Postfix) with ESMTP id DAFEA3A6823 for <ogpx@ietf.org>; Tue, 30 Mar 2010 11:42:33 -0700 (PDT)
Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 30 Mar 2010 11:43:02 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.51,335,1267430400"; d="scan'208";a="504964064"
Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by orsmga002.jf.intel.com with ESMTP; 30 Mar 2010 11:43:02 -0700
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx604.amr.corp.intel.com ([10.31.0.170]) with mapi; Tue, 30 Mar 2010 12:43:02 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: ogpx <ogpx@ietf.org>
Date: Tue, 30 Mar 2010 12:42:55 -0600
Thread-Topic: [ogpx] type-system : binary elements in JSON serializations
Thread-Index: AcrQLb+2rabej+H3QPyfPop8tEsVGQACj4kg
Message-ID: <62BFE5680C037E4DA0B0A08946C0933DCB5FBCB3@rrsmsx506.amr.corp.intel.com>
References: <b325928b1003281033p28c92367x2be877cc348268da@mail.gmail.com> <62BFE5680C037E4DA0B0A08946C0933DCB5FB69D@rrsmsx506.amr.corp.intel.com> <OF525A1644.1F7FE877-ON852576F5.00641451-852576F5.00641932@us.ibm.com> <b325928b1003291124i47c4ca3bpa55724f57d4ad7d8@mail.gmail.com> <62BFE5680C037E4DA0B0A08946C0933DCB5FB75C@rrsmsx506.amr.corp.intel.com> <b325928b1003291313h6204c04bs5bf55a03447e9844@mail.gmail.com> <f72742de1003301022u971914fl75d8c0a56c7b1b3f@mail.gmail.com>
In-Reply-To: <f72742de1003301022u971914fl75d8c0a56c7b1b3f@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [ogpx] type-system : binary elements in JSON serializations
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Mar 2010 18:42:34 -0000

> -----Original Message-----
> From: ogpx-bounces@ietf.org [mailto:ogpx-bounces@ietf.org] On Behalf Of
> Joshua Bell
> Sent: Tuesday, March 30, 2010 10:23 AM
> To: ogpx
> Subject: Re: [ogpx] type-system : binary elements in JSON
> serializations
> 
> in 4.2. (JSON Serialization) draft-hamrick-vwrap-type-system-00 calls
> out:
> 
> Binary  LLSD 'Binary' values are represented as a JSON 'JSONArray'.
>        That is, they follow the ECMA-262 [ECMA262r5] 'JSONArray' non-
>        terminal whose members are integer numbers representing each
>        octet of the binary array.
> 
> This thread seems predicated on conversion between Binary and String as
> a convenience for both JSON and XML serialization. However, the current
> JSON serialization of Binary is an array of octets, and there are no
> conversions defined for arrays.
> 
> I believe an unstated implication of this thread (and F2F discussion)
> is that we should change the JSON serialization of Binary from octet
> array to base64 string. Otherwise, after a memory->JSON->memory round-
> trip, the base64->string conversion isn't very useful.
> 
> (My apologies if it was stated but I missed it.)
> 

Yes, I think that was stated earlier in the thread but thank you for clarifying that point. It can get confusing when the conversations move between face to face meetings and e-mail threads.

To summarize, this change would alter sections "2.1.5 String", "2.1.9 Binary", and "4.2 JSON Serialization".

John

v2.23.0 | Report a Bug | By Email