Re: [Json] Proposal: the minimal edit

John Cowan <cowan@mercury.ccil.org> Sat, 22 June 2013 18:52 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 0177021F9EF7 for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 11:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level:
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 i53WAz4u1bON for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 11:52:02 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 9D68921F9EF2 for <json@ietf.org>; Sat, 22 Jun 2013 11:52:02 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UqSun-0007oF-Kl; Sat, 22 Jun 2013 14:52:01 -0400
Date: Sat, 22 Jun 2013 14:52:01 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: R S <sayrer@gmail.com>
Message-ID: <20130622185201.GO31186@mercury.ccil.org>
References: <CAChr6SyN4Z3Hh8OFGHkK+AJN0+S09wMfjeobZ51GjKNL+GhPsw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAChr6SyN4Z3Hh8OFGHkK+AJN0+S09wMfjeobZ51GjKNL+GhPsw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposal: the minimal edit
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, 22 Jun 2013 18:52:07 -0000

R S scripsit:

> It's my opinion that none of the errors or inconsistencies present in
> the document are significant, since JSON works pretty well.

It does at the level of an informational protocol, but not at the level of
standards track.  Would you be willing to sign a contract, arm's-length,
with someone whose only constraint was that their code passed *some*
interpretation of the RFC?  I certainly would not.  As I pointed out
before, the parser conformance clause (first paragraph of Section 4)
is satisfied by any program that accepts arbitrary input and produces
arbitrary output distinct from the input (or indeed no output at all,
given the over-free wording in the second paragraph).

> Note that the IETF does not update all standards track documents with
> obsolete references, which demonstrates that leaving the current
> references in place is tractable.

I don't think that applies to documents entering the standards track in
the first place.

-- 
You are a child of the universe no less         John Cowan
than the trees and all other acyclic            http://www.ccil.org/~cowan
graphs; you have a right to be here.            cowan@ccil.org
  --DeXiderata by Sean McGrath