Re: [Json] The parts of JSON (a possible aid to discussion)

John Cowan <cowan@mercury.ccil.org> Fri, 07 June 2013 17:03 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 1D3B621F95EF for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 10:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.044
X-Spam-Level:
X-Spam-Status: No, score=-4.044 tagged_above=-999 required=5 tests=[AWL=1.255, BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, 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 cNnz9kOTk3wp for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 10:03:17 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB1421F93D2 for <json@ietf.org>; Fri, 7 Jun 2013 10:03:17 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Ul04H-0006HD-0i; Fri, 07 Jun 2013 13:03:13 -0400
Date: Fri, 07 Jun 2013 13:03:12 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Message-ID: <20130607170312.GB13569@mercury.ccil.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC31717@xmb-rcd-x10.cisco.com> <51B1A1E2.7020202@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <51B1A1E2.7020202@it.aoyama.ac.jp>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Jacob Davies <jacob@well.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] The parts of JSON (a possible aid to discussion)
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: Fri, 07 Jun 2013 17:03:22 -0000

"Martin J. Dürst" scripsit:

> You don't need to use an Unicode encoding for concrete
> representation. You may not need an Unicode encoding for byte
> serialization. But you need a concrete representation, and a byte
> encoding, than will handle all strings of Unicode code points and no
> other strings.

Not really.  The whole point of the escapes is so that you can encode
JSON in pure ASCII or any other encoding.  As long as the letters a,
b, c, d, e, f, l, n, r, s, t, and u, the digits 0-9, and the symbols
and punctuation marks left and right square bracket, left and right
brace, comma, period, minus sign, colon, double quote, and backslash
are representable, JSON is representable.  (You could design a 5-bit
encoding to do so.)

-- 
John Cowan    http://ccil.org/~cowan    cowan@ccil.org
The work of Henry James has always seemed divisible by a simple dynastic
arrangement into three reigns: James I, James II, and the Old Pretender.
                --Philip Guedalla