IETF Logo Mail Archive

Re: [Json] Two Documents

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 19 June 2013 03:14 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 28CCE21F9B20 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 20:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level:
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 Fm9aNLUwc3VR for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 20:14:23 -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 A11B221F9B4D for <json@ietf.org>; Tue, 18 Jun 2013 20:14:04 -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 r5J3E3Sf007325 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Tue, 18 Jun 2013 20:14:04 -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: <51C1121E.8050004@crockford.com>
Date: Tue, 18 Jun 2013 20:14:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3CE009B-CF14-4B2F-86C4-E2E06165316E@vpnc.org>
References: <51B9EA49.2050604@crockford.com> <BF7E36B9C495A6468E8EC573603ED9411528A0E2@xmb-aln-x11.cisco.com> <51C1121E.8050004@crockford.com>
To: "json@ietf.org" <json@ietf.org>
X-Mailer: Apple Mail (2.1508)
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: Wed, 19 Jun 2013 03:14:24 -0000

<no hat>

On Jun 18, 2013, at 7:06 PM, Douglas Crockford <douglas@crockford.com> wrote:

> It includes an abstract, an introduction, the detailing of the elements (object, array, string, etc), and security considerations. No parsers or generators, no octets, no MIME types.

The parser and generator sections define interoperability specifications. Removing them is a huge change to the technical specification, one that feels well outside of the "minimal changes" in our charter.

I still want the WG to later work on an implementation guidance document after we have finished work on refining the current technical specification; in fact, it is probably negligent if we don't make a run at that. But calling requirements on parsers and generators "implementation guidance" at this late date seems like a very bad move.

--Paul Hoffman

v2.29.0 | Report a Bug | By Email | System Status