IETF Logo Mail Archive

Re: [Json] Complete section 3 proposal

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 18 June 2013 22:16 UTC

Return-Path: <paul.hoffman@vpnc.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 78FB611E8106 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 15:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level:
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, 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 80NvIbdAglBE for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 15:16:40 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0089521F8F6E for <json@ietf.org>; Tue, 18 Jun 2013 15:16:39 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5IMGb0u099548 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 15:16:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70FC58C0B@xmb-rcd-x10.cisco.com>
Date: Tue, 18 Jun 2013 15:16:36 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9A3CF00-3B30-4DE4-95C4-9F3E6CA2DA86@vpnc.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC58C0B@xmb-rcd-x10.cisco.com>
To: Joe Hildebrand <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Complete section 3 proposal
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 22:16:40 -0000

On Jun 18, 2013, at 1:40 PM, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:

>    Since the first code point of JSON text will always be an ASCII
> character [RFC0020],

You were so good with using "encoding schemes", then you fell into this. :-) While the reference to RFC 20 is cute, it actually doesn't help here. A more direct statement would be:

=====
Because the first code point of a JSON text will always be a character in the range U+0022 to U+007B,
=====

On Jun 18, 2013, at 1:49 PM, Carsten Bormann <cabo@tzi.org> wrote:

> Looks great, except that the phrase
> 
>> in a MIME context
> 
> may be not quite what is meant here.
> 
> (This paragraph is specifically about application/json; if I want to go ahead and register an application/json-in-zos-ebcdic tomorrow, there should be no problem with me using that once I've been released from the asylum.)

=====
so when used in the application/json MIME context, 
=====

v2.23.0 | Report a Bug | By Email