Re: [Json] Kicking Off JSONbis

Tim Bray <tbray@textuality.com> Sun, 18 October 2015 18:35 UTC

Return-Path: <tbray@textuality.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 04E7E1ACD55 for <json@ietfa.amsl.com>; Sun, 18 Oct 2015 11:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 Xq72UI6ql4Bf for <json@ietfa.amsl.com>; Sun, 18 Oct 2015 11:35:15 -0700 (PDT)
Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com [209.85.213.177]) (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 E0F121ACD53 for <json@ietf.org>; Sun, 18 Oct 2015 11:35:14 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so43241865igb.0 for <json@ietf.org>; Sun, 18 Oct 2015 11:35:14 -0700 (PDT)
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:content-type; bh=EskZv9P/1rPff895qDF5Z2nltVyp3hL6voGlAbtT8J0=; b=MStr5OdHaix26LkiHaznKv7baJpd72+EIUDnGwNJ3KjddDsP5uETxAvdIXQ3wYcVs+ ipOIbb9SlYG/+UdpHD8HAfGNImEHCPZF9TNFJjFVnHJ8SHTrAh6aP6yPFoJBhKNKHEq3 TvlOqgjzAXHLdMnXTSKnYJurZKilvo+S6tlOaA7YxFISPrNW4Xklfc7XSJfu4kQ6HjH0 YOiMlqQLBTs26iGheIAEzQLq5RxhFWyPAZek84g/3iPjv4b5fRfZvKnhwbzHij0+3E2B IZX3zf4FTUM01TEDLTdVbchakkfjefqdxkd8f+HG/osdpfd31ofa1bFZf+k8K7Jzi3Ji pjfw==
X-Gm-Message-State: ALoCoQlYV1ncJ8lih9d4vveuPTTeG+wFQKSQ4fHyg3Ey1zzLdCXhKoZrNLUOS32O41iFJi3dCFLf
X-Received: by 10.50.39.109 with SMTP id o13mr16221045igk.43.1445193314195; Sun, 18 Oct 2015 11:35:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.30.4 with HTTP; Sun, 18 Oct 2015 11:34:54 -0700 (PDT)
X-Originating-IP: [209.52.88.169]
In-Reply-To: <CALaySJJ01gEoHqZ4ehVHzv8mqD1CXKV3Ave3yQPrgrAGe4yckg@mail.gmail.com>
References: <DB74C466-D542-42D6-95B0-690A564435A9@cisco.com> <CAC4RtVD3cKThDTr_eS-QCUhKqZkMS0y+nPS5HxCk3f1RQ7VyJQ@mail.gmail.com> <CAHBU6iv_w_O95Nq-bU1z2GOKgouuGrMbZP4Uwio25pPtFCc3UQ@mail.gmail.com> <CALaySJ+==5_mstrgHEd7bUGzSo85Er9VR_zEaJ+gh-O+zSpK=w@mail.gmail.com> <88A80A45-E673-4D0A-995B-3872874C23AE@cisco.com> <CALaySJJ01gEoHqZ4ehVHzv8mqD1CXKV3Ave3yQPrgrAGe4yckg@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Sun, 18 Oct 2015 11:34:54 -0700
Message-ID: <CAHBU6iuxBvn3ug9LwcK9gvrQDLr1uz=3NCrcrZaejF2iUwiLVA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=047d7bd76d041ff77c0522654a9f
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/3N0xuCJOQVoiRazh3kF83Rg26h8>
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: Sun, 18 Oct 2015 18:35:17 -0000

[I'll post a 7159bis with errata by end-of-day whether I get an answer on
the errata-wonkery or not.  Now, returning to the meat of the discussion.]

I have really major heartburn with introducing a Normative Reference to
ECMA404 in 7159bis.  Because language in standards documents should be used
carefully, and “Normative Reference” has a very specific meaning, and that
meaning clearly does not apply in this case.  However, since there is
apparently a feeling that there is some benefit to the community in
achieving “standards harmony”, let me propose three ways forward:

1. Include a normative reference to ECMA404, but accompany it with text
explaining that this reference is marked normative because it is considered
authoritative in the community of JavaScript language specifiers, not in
the normal sense of “normative”; there is no necessity to read it in order
too understand or implement RFC7159bis, nor does it specify any technology
which must be present in an implementation that is not also described in
7159bis.”

2. Do not include a normative reference, but expand the note about ECMA404
in Section 1.2 to emphasize that ECMA404 may be considered authoritative in
the community of JavaScript implementers.

3. Conclude that this effort has no observable benefit to the community
implementing JSON on the Internet and abandon the RFC7159bis project.

On Wed, Oct 14, 2015 at 9:10 AM, Barry Leiba <barryleiba@computer.org>
wrote:

> >>> Sure, but isn’t a consensus call on the substantive change to the spec
> in
> >>> order?
> >>
> >> That could be done by posting an I-D to make the proposal, and have
> >> the working group review it and comment on it.  Right now, there's
> >> just a "here's what we plan to do", and there've been a few comments
> >> about that.  Specific text to review might help, no?
> >
> > RFC 7159 has the following verified errata:
> >
> > * https://www.rfc-editor.org/errata_search.php?rfc=7159&eid=3915
> > * https://www.rfc-editor.org/errata_search.php?rfc=7159&eid=4264
> > * https://www.rfc-editor.org/errata_search.php?rfc=7159&eid=4336
> >
> > I suggest at the least an I-D be published that applies these.
>
> That works for me.
>
> As to the other, specific text proposed on the list will give people
> something to discuss.
>
> Barry
>



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