IETF Logo Mail Archive

Re: [Json] Two Documents

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 18 June 2013 14:04 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 F3D9C21F949F for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 07:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level:
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 kOxtxcsuyvBK for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 07:04:31 -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 7AF7721F93E0 for <json@ietf.org>; Tue, 18 Jun 2013 07:04:31 -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 r5IE4RoL083325 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 07:04:28 -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: <5FBB0E3C-E538-48F9-AD32-45AD00151C12@yahoo.com>
Date: Tue, 18 Jun 2013 07:04:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <44704970-2F3A-43B6-B9B8-5D6052B51361@vpnc.org>
References: <51B9EA49.2050604@crockford.com> <BF7E36B9C495A6468E8EC573603ED9411528A0E2@xmb-aln-x11.cisco.com> <5FBB0E3C-E538-48F9-AD32-45AD00151C12@yahoo.com>
To: Vinny A <jsontest@yahoo.com>
X-Mailer: Apple Mail (2.1508)
Cc: Douglas Crockford <douglas@crockford.com>, json@ietf.org
Subject: Re: [Json] Two Documents
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 14:04:32 -0000

On Jun 17, 2013, at 8:19 PM, Vinny A <jsontest@yahoo.com> wrote:

> On Jun 17, 2013, at 7:14 PM, "Matt Miller (mamille2)" <mamille2@cisco.com> wrote:
> 
>> In order for the WG to fully understand your proposal, we need a more definitive list of what to expect in each document.
>> 
>> As a starting point, can you describe which sections of the current RFC4627 would be in "JSON Data Interchange Format" and which would be in the JSON best practices document?  Clearly the latter will have many additions from the recent discussions, but it is less clear which portions of the current text goes into which document.
> 
> 
> Obviously I'm not Douglas, but I'd like to make a proposal in this department.

<grumpy hat>

Not only are you not Douglas (who made the original proposal, and thus the question was directed at him), you did not even answer Matt's request. Douglas proposed two documents but did not clearly state what might be removed from the current WG draft; knowing that will help the WG decide whether or not to adopt Douglas' proposal. Your list of ideas for the new document is fine, but is out of scope for the current charter *unless* you are proposing to remove sections from the current WG draft.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email