Re: [Json] Normative reference reasoning and logistics

Tim Bray <tbray@textuality.com> Fri, 13 May 2016 05:12 UTC

Return-Path: <tbray@textuality.com>
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 B723412B017 for <json@ietfa.amsl.com>; Thu, 12 May 2016 22:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20150623.gappssmtp.com
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 doMHRq2yizBL for <json@ietfa.amsl.com>; Thu, 12 May 2016 22:12:15 -0700 (PDT)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (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 2217812D09A for <json@ietf.org>; Thu, 12 May 2016 22:12:15 -0700 (PDT)
Received: by mail-qg0-x236.google.com with SMTP id f92so52553506qgf.0 for <json@ietf.org>; Thu, 12 May 2016 22:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2V6uq0b9kit6L35zNKeK0wZ8d0rIrF0XKel1K1OTpZs=; b=OA6tyJX1zbe37wret1AqaC4SytLtkL0sj/uwDHqioXBT/rHSxjoh1/Zr2LrZxjri0z sDFIoVodYZvYWOkW5i64qX3Sc/ccnG9IVZPUZxGKRU6no3Hua/sZ9IyjxuG4q4qSw/9o DaI5OOXqUn4z9VkJwbzzUI8NQS3DagpoPJYKpSGd/3Tn1yxXKcXRGQZqFLT6Bdop1OJR TvMOcIO7LefYZKA6IgdIEEQMsfzZutu47tmEtvx+9gmNfKuZEKnIYNaN9X9Fzscmy1H0 a/tTMOWPdjrvotHKvI1SvjnYuTqUSiUDOQP232bC7XFUE/sJan+LuUvTrv2NZGE9qW7E Kvgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2V6uq0b9kit6L35zNKeK0wZ8d0rIrF0XKel1K1OTpZs=; b=Rzx2LVM5RpXq20QDxYmmy3zCzlfqyFC2HLE6kJ/5RwMELjyOCHsYOO/fARKdG3tVdc 28WfAciaPBZEgFqdSzSNSmAQDwsOeuI7HqO7KMU5SVJgLdgZAaN7rbcB1h4A4axe8FT2 oY0t0tSuSyr9Ef5eBzE0H7mh9YadcEvj8i6sRWY0cOoxlhJbCpKBLJD4+gtQ7tl9a9lK bEg9Slwj8p7UuDwQGsTewYl+WiXX/70dwOwoEC0vIQpBfQHHe2oUMd0vEwco5nhMZqTu 3+VXKRxGfwUWxHLdaV/LUZym6jRbJ6/pPywhyMBv+Xqs7tR+r0sPx4OC3cv9SzCnLSjH bvrg==
X-Gm-Message-State: AOPr4FU19MnLAkBw37HmufRGDsIvFrn/aBvnPbQl+lzTGxq+f7ExwgQ5PKuQvQGDpBmQB6VJmhCByEe+4B0AZw==
X-Received: by 10.140.194.138 with SMTP id p132mr14089111qha.78.1463116334260; Thu, 12 May 2016 22:12:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.94.201 with HTTP; Thu, 12 May 2016 22:11:54 -0700 (PDT)
X-Originating-IP: [24.84.248.61]
In-Reply-To: <4BA8C03B-C38F-4322-96F4-DD39C6ED6E68@cisco.com>
References: <CAHBU6iu0j492Mzbo2HriFtjm_o5516yCsQCX9PGHvqAxhU0Zjg@mail.gmail.com> <CAHBU6isb+A4crvdEMkMqhreXLcox3Q5O-TJeOYvb4vvUqYupmg@mail.gmail.com> <978CE59C-19EA-44E0-8AA9-620B854ACB6F@cisco.com> <CAHBU6ivnZ5x1vno61jTH8ou4PhNesVf9eb5TA_wb_3GEqEsQxA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E13BD0AFB47F@WSMSG3153V.srv.dir.telstra.com> <896CAFF7-A29E-48F1-B2DA-F4A09CD9B313@cisco.com> <D1499328-45D8-4E75-A25E-1F37823B706A@mnot.net> <4BA8C03B-C38F-4322-96F4-DD39C6ED6E68@cisco.com>
From: Tim Bray <tbray@textuality.com>
Date: Thu, 12 May 2016 22:11:54 -0700
Message-ID: <CAHBU6it_B0vdYbA7WhqQAtLS_KD=EwY=jTnKan0ojRV_ZZxvuw@mail.gmail.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary=001a114338b25e7cd10532b25144
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/jp9BStHbhGTZrovBjpwoD7bf2zY>
Cc: "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Normative reference reasoning and logistics
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 13 May 2016 05:12:18 -0000

Will do.

On Mon, May 9, 2016 at 8:55 AM, Matt Miller (mamille2) <mamille2@cisco.com>
wrote:

> Hello all,
>
> It appears we have rough consensus to include a combination of the
> following text suggested by Tim Bray:
>
>     The reference to ECMA-404 in the previous sentence is normative,
>     not with the usual meaning that implementors need to consult it
>     in order to understand this document, but to emphasize that there
>     are no inconsistencies in the definition of the term “JSON text”
>     in any of its specifications. Note, however, that ECMA-404 allows
>     several practices which this specification recommends avoiding in
>     the interests of maximal interoperability.
>
> With these additional points suggested by Joe Hildebrand:
>
>     - The intent is that the grammar is the same between the two
>       documents, although different descriptions are used.  If there a
>       difference is found between them, ECMA and the IETF will work
>       together to update both documents.
>
>     - If an error is found with either document, the other should be
>       examined to see if it has a similar error, and fixed if possible.
>
>     - If either document is changed in the future, ECMA and the IETF will
>       work together to ensure that the two documents stay aligned through
>       the change.
>
> If there are no objections, then Tim and Joe can finalize the text and
> include it with the next revision to draft-ietf-jsonbis-rfc7159bis.
>
>
> Thank you,
>
> - JSON Chair
>



-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)