Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)

John Cowan <cowan@mercury.ccil.org> Thu, 28 November 2013 03:49 UTC

Return-Path: <cowan@ccil.org>
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 46E9A1AE0EF; Wed, 27 Nov 2013 19:49:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 TV1DuoJQwYL5; Wed, 27 Nov 2013 19:49:43 -0800 (PST)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 87DF11AE0AD; Wed, 27 Nov 2013 19:49:43 -0800 (PST)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Vlsbl-0001pp-BF; Wed, 27 Nov 2013 22:49:41 -0500
Date: Wed, 27 Nov 2013 22:49:41 -0500
From: John Cowan <cowan@mercury.ccil.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20131128034941.GK29489@mercury.ccil.org>
References: <CADnb78h8AjPcQLOCwNm0Pt3pObh6uFV5+zy0c_YU6B-u4MtY1Q@mail.gmail.com> <AA45B3C6-1DC5-4B1E-8045-C9FE76022584@vpnc.org> <C93F89AD-81D2-4489-ADC4-AB05A5B10883@cisco.com> <CAHBU6itgE9=WP+c0oXt1W647b1zz+N6+4ZqRa63Ve91TUsGzTA@mail.gmail.com> <CANr5HFVhG5SNhW4yJxDicvFman94FaNi8UZHhcpQbH6AG6pfQg@mail.gmail.com> <92E7AA8E-F77C-4552-B463-D65703576AB9@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <92E7AA8E-F77C-4552-B463-D65703576AB9@vpnc.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: es-discuss <es-discuss@mozilla.org>, Alex Russell <slightlyoff@google.com>, IETF Discussion <ietf@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
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: <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: Thu, 28 Nov 2013 03:49:45 -0000

Paul Hoffman scripsit:

> If you believe that ECMA-404 will change in the future, that
> would indicate that ECMA might break interoperability with current
> implementations, even for what they perceive as "good reasons". In
> general, the IETF tries not to have its long-lived standards normatively
> latch on to moving targets for this very reason. Even when other SDOs
> have assured us that they will not make backwards-incompatible changes,
> they have done so anyway (cue the Klensin-esqe theme music...), and
> that has caused serious interoperability problems for the IETF specs.

Binding specifically to the first edition of ECMA-404 would resolve
that problem.  Binding to a specific edition doesn't work so well with
Unicode, but that is because Unicode is a special case: it expands its
coverage in successive editions to ever-larger portions of the world
of writing systems.  It would have been impossible to do the whole
thing at once, unlike even the largest ordinary technical standard.
ECMA-404 is not in that league.

-- 
Not to perambulate                 John Cowan <cowan@ccil.org>
    the corridors                  http://www.ccil.org/~cowan
during the hours of repose
    in the boots of ascension.       --Sign in Austrian ski-resort hotel