Re: [Json] Kicking Off JSONbis

"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Thu, 01 October 2015 20:47 UTC

Return-Path: <pfpschneider@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2FF61A88E3 for <json@ietfa.amsl.com>; Thu, 1 Oct 2015 13:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8BuhvBXQpyIz for <json@ietfa.amsl.com>; Thu, 1 Oct 2015 13:47:52 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D0A51A88EF for <json@ietf.org>; Thu, 1 Oct 2015 13:47:48 -0700 (PDT)
Received: by ioii196 with SMTP id i196so99446322ioi.3 for <json@ietf.org>; Thu, 01 Oct 2015 13:47:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=ELkyJpRkfNIV1kSiRnTWsCOaR2xmiY835xdFEcCJUS0=; b=R/54aCMY7JQ5iS0tb8E4cOeKVdL3mrIW/Sg/8YDFUPxeAMf/fd+1RcpuAxSbBYGHCu UIUMvVl510gcuSMSawBz9ay26dLadLDij4l5i/oa6EcO9BteWYQH5PWhsA7Ny0r4YzP1 9D/49KjWn55P2BgCEd8MFAEHeVg2ZiEkQkOPnjekIvpXdEf84LBy13jz3Yi7VUN/UHd3 gw95lM2f31Z0V+hJ9i6D69DGkn6ym6scliLqqlh+3t5gikm0dOija85vi0ORNH0SQS1n Lj5mJ3+vpFqTlGRb0WQh/0X8beMyGLuSRlYNcSBdz95aJ1qqJyR3U8+JgOCBjt8rNxPG KL1w==
X-Received: by 10.107.138.213 with SMTP id c82mr13088200ioj.179.1443732467547; Thu, 01 Oct 2015 13:47:47 -0700 (PDT)
Received: from idefix.nuance.com ([184.151.36.114]) by smtp.gmail.com with ESMTPSA id l2sm2101325igv.11.2015.10.01.13.47.45 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 13:47:46 -0700 (PDT)
To: Barry Leiba <barryleiba@computer.org>
References: <DB74C466-D542-42D6-95B0-690A564435A9@cisco.com> <560C8C12.2010805@gmail.com> <CAC4RtVB=L2Pu+omABvXqmH-EMGia8o65zbbi6g0H0e94vfFUGg@mail.gmail.com>
From: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <560D9BF0.9050504@gmail.com>
Date: Thu, 01 Oct 2015 13:47:44 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CAC4RtVB=L2Pu+omABvXqmH-EMGia8o65zbbi6g0H0e94vfFUGg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/xqw2TqCBKMi8FRP66nYVNfFRiuk>
Cc: "json@ietf.org" <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] Kicking Off JSONbis
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 01 Oct 2015 20:47:53 -0000

On 10/01/2015 11:54 AM, Barry Leiba wrote:
>> I must admit that I am puzzled as to how ECMA-404 can be a normative
>> reference for any document that is a minor change from rfc7159.  What in
>> ECMA-404 is needed to understand or implement what is in rfc7159?
> 
> Rob has it nailed in his message:
> "To me, it seems like a political or diplomatic gesture that helps the
> Internet to move forward.
> 
> "Framing it in technical or standards-wonk terms seems counterproductive.
> I don't think there are substantive issues in those areas that would be
> resolved by objecting to the plan in the charter."
> 
> That really is the point: tying the two documents together more tight,
> to make people more comfortable that they are not likely (certainly
> not intended) to 

further (?)

> diverge later.
> 
>> As has been stated, rfc7159 already references ECMA-404.  A conservative way
>> to make a closer connection from rfc7159 to ECMA-404 would be to state that
>> ECMA-404 has an alternative description of JSON that is extremely close to
>> the definition in rfc7159.
> 
> Such a statement would, indeed, be an excellent one to put into 7159bis.
> 
> Barry, responsible AD
> 

peter