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

John Cowan <cowan@mercury.ccil.org> Sat, 15 June 2013 22:39 UTC

Return-Path: <cowan@ccil.org>
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 315D921F9E31 for <json@ietfa.amsl.com>; Sat, 15 Jun 2013 15:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.443
X-Spam-Level:
X-Spam-Status: No, score=-3.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 0E91R9bDiSJY for <json@ietfa.amsl.com>; Sat, 15 Jun 2013 15:39:15 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id D589C21F9E30 for <json@ietf.org>; Sat, 15 Jun 2013 15:39:15 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Unz7o-0000y3-Bk; Sat, 15 Jun 2013 18:39:12 -0400
Date: Sat, 15 Jun 2013 18:39:12 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Message-ID: <20130615223912.GI30796@mercury.ccil.org>
References: <20130615160648.GC30796@mercury.ccil.org> <A723FC6ECC552A4D8C8249D9E07425A70FC4E706@xmb-rcd-x10.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70FC4E706@xmb-rcd-x10.cisco.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Norbert Lindenberg <ietf@lindenbergsoftware.com>, Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <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: Sat, 15 Jun 2013 22:39:20 -0000

Joe Hildebrand (jhildebr) scripsit:

> Is that only because of the multiple encodings?  For example, if JSON was
> UTF8-only, could we define a purely concrete syntax of octet sequences?

In principle, but that would make it difficult to embed JSON in HTML
or XML or JavaScript or another format defined by characters.

-- 
Business before pleasure, if not too bloomering long before.
        --Nicholas van Rijn
                John Cowan <cowan@ccil.org>
                    http://www.ccil.org/~cowan