IETF Logo Mail Archive

Re: [Json] Two Documents

John Cowan <cowan@mercury.ccil.org> Wed, 19 June 2013 15: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 B5B5021F9BF3 for <json@ietfa.amsl.com>; Wed, 19 Jun 2013 08:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.463
X-Spam-Level:
X-Spam-Status: No, score=-3.463 tagged_above=-999 required=5 tests=[AWL=0.136, 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 PnLQyHCi3tNR for <json@ietfa.amsl.com>; Wed, 19 Jun 2013 08:03:34 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 8B00021F9CA8 for <json@ietf.org>; Wed, 19 Jun 2013 08:03:34 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UpJv2-0005yN-MB; Wed, 19 Jun 2013 11:03:32 -0400
Date: Wed, 19 Jun 2013 11:03:32 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tim Bray <tbray@textuality.com>
Message-ID: <20130619150332.GB24889@mercury.ccil.org>
References: <51B9EA49.2050604@crockford.com> <BF7E36B9C495A6468E8EC573603ED9411528A0E2@xmb-aln-x11.cisco.com> <51C1121E.8050004@crockford.com> <CAHBU6isgo-pLBUHM-6ix3eChD4khMgFBEyf6pDYzU3-oteAD=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAHBU6isgo-pLBUHM-6ix3eChD4khMgFBEyf6pDYzU3-oteAD=g@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: "Matt Miller (mamille2)" <mamille2@cisco.com>, Douglas Crockford <douglas@crockford.com>, "json@ietf.org" <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: Wed, 19 Jun 2013 15:03:39 -0000

Tim Bray scripsit:

> So I think it would be abusive to our customers to make them read two
> documents to get their jobs done.  I’m scratching my head to think of
> anyone who would read one of these documents but not the other, and I’m
> coming up empty.

People who are reading or writing JSON text with general editors are the
obvious targets for a syntax-only document.  One group would be
programmers dealing with JSON literals; another would be people writing
books or papers or standards that involve JSON examples.  This group
doesn't care about encoding or security, but I agree that they would
not be injured by an RFC that contains this information, provided it is
not intertwingled with the syntax.

-- 
The first thing you learn in a lawin' family    John Cowan
is that there ain't no definite answers         cowan@ccil.org
to anything.  --Calpurnia in To Kill A Mockingbird

v2.23.0 | Report a Bug | By Email