Re: [Json] What are we trying to do?

Tim Bray <tbray@textuality.com> Wed, 03 July 2013 19:35 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 90A6211E821B for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 12:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 MkWm+v0goPSD for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 12:35:33 -0700 (PDT)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by ietfa.amsl.com (Postfix) with ESMTP id 9308D21F9D89 for <json@ietf.org>; Wed, 3 Jul 2013 12:35:28 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id r11so547387lbv.13 for <json@ietf.org>; Wed, 03 Jul 2013 12:35:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=arcwPPUIqrCHxpDp3QbHZsIKTHxOGLj9uqtwxNEJnJg=; b=MM+xqJq4fjMyis6no4+kcgPS62WmBcJblQkgo4bTw4BH4kB4OBlPBAMcqgCoiEPRW2 eV/3BCHduqyEGhCcgxlyPemxoEezx0zGE324/7dbvpqAunjdgo5rpY5BItLokDz+9rSJ 3TcuqOUdzTj3QYzcbREp7VHnenOXil7cOXfZSQHxIlsL7XKTSsKK7RRxwLTLTZJmgHRP CvSF60MZVH53t8Yvrbsdv4VIukMc/W/nfS69CobGYNXRK4xHd526+0v+XujbFVDITTHZ qvv0I2eTuicRBXgbgG6HcRiD0W7ixwuVtWXf+2FHU5K//8N0U/ZmfhUgPlG/jdntbiJG b81Q==
MIME-Version: 1.0
X-Received: by 10.152.25.135 with SMTP id c7mr1172150lag.39.1372880127427; Wed, 03 Jul 2013 12:35:27 -0700 (PDT)
Received: by 10.114.71.51 with HTTP; Wed, 3 Jul 2013 12:35:27 -0700 (PDT)
X-Originating-IP: [209.121.225.216]
In-Reply-To: <CAK3OfOjvtU6=3EowmU0ccWAfQPSoGaUhPMLe+uK6pVR_sQDGFg@mail.gmail.com>
References: <CAHBU6iv0wXYvAyasSE8Wga0K_sD_pKL6o-a-ca9yemhy3m6zzw@mail.gmail.com> <FB90FFED-5128-4B5C-85DE-78DFE2674310@vpnc.org> <CAK3OfOjvtU6=3EowmU0ccWAfQPSoGaUhPMLe+uK6pVR_sQDGFg@mail.gmail.com>
Date: Wed, 03 Jul 2013 12:35:27 -0700
Message-ID: <CAHBU6iv_ARMKb655pQucrPg=_u63EQPmLZ3gcwqds_tqbTFEMQ@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Nico Williams <nico@cryptonector.com>
Content-Type: multipart/alternative; boundary="089e0160c4065096ce04e0a09021"
X-Gm-Message-State: ALoCoQnUAG19b6MshiqgELC7dOSPuSBlqrMz2CGxYLz2V13XRUYLVF1NlXKYeq1djnvEQ4/qIEtn
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] What are we trying to do?
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, 03 Jul 2013 19:35:39 -0000

+1 to Nico’s suggestion.  -T


On Wed, Jul 3, 2013 at 9:29 AM, Nico Williams <nico@cryptonector.com> wrote:

> On Wed, Jul 3, 2013 at 10:37 AM, Paul Hoffman <paul.hoffman@vpnc.org>
> wrote:
> > <no hats>
> >
> > +1 to everything Tim said, particularly "charter is self-contradictory".
> We didn't realize this when we put together the charter (a process in which
> dozens of people participated), but we do now.
>
> Re-reading the charter I'm not sure that there's a contradiction.  We
> can do something:
>
>  - remove the safe-for-eval regexp silliness
>
>  - add a section describing divergent interpretations
>
>  - leave the rest mostly as-is with only those changes for which we
> can get consensus
>
>    E.g., we can probably get consensus for "generators SHOULD NOT
> output duplicate names" and "parsers SHOULD use the last of any
> duplicate names" with appropriate text describing when and why one
> might deviate from this guidance.
>
>    E.g., we can probably get consensus for describing a subset of JSON
> strings that is guaranteed to interoperate, even though we can't ban
> unpaired surrogates.
>
> Then re-charter and publish a BCP.
>
> Alternatively, we could re-charter now.  I can propose text as soon as
> we decide to start that discussion.
>
> Nico
> --
>