Re: [Json] Scope: Wire format or runtime format?

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 18 June 2013 10:24 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6918221F9B57 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 03:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.99
X-Spam-Level:
X-Spam-Status: No, score=-100.99 tagged_above=-999 required=5 tests=[AWL=-1.800, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_45=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PD5h066r+o5b for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 03:24:16 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id B70D721F9DAC for <json@ietf.org>; Tue, 18 Jun 2013 03:24:15 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r5IAO9lC004161; Tue, 18 Jun 2013 19:24:10 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 2bc9_8000_3650eb16_d801_11e2_8948_001e6722eec2; Tue, 18 Jun 2013 19:24:08 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 7C3CBBF550; Tue, 18 Jun 2013 19:22:49 +0900 (JST)
Message-ID: <51C0353C.3010100@it.aoyama.ac.jp>
Date: Tue, 18 Jun 2013 19:23:56 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John Cowan <cowan@mercury.ccil.org>
References: <6FC6B441-B74D-4B9F-B883-065C05890880@lindenbergsoftware.com> <51BE8DEA.7030307@it.aoyama.ac.jp> <118A7923-5D66-4EF5-8A78-CAE125032010@lindenbergsoftware.com> <20130617115453.GC19150@mercury.ccil.org>
In-Reply-To: <20130617115453.GC19150@mercury.ccil.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Norbert Lindenberg <ietf@lindenbergsoftware.com>, json@ietf.org
Subject: Re: [Json] Scope: Wire format or runtime format?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 10:24:22 -0000

On 2013/06/17 20:54, John Cowan wrote:
> Norbert Lindenberg scripsit:
>
>> Maybe you have a better term for it: What I mean in the ECMAScript
>> context is the format that the functions JSON.parse and JSON.stringify
>> parse and produce [1].
>
> This simply is the description of JSON at the level of characters.

Expressed as UTF-16 because that's what ECMAScript uses.

Regards,   Martin.