Re: [Json] Possible next work for the WG

Tim Bray <tbray@textuality.com> Wed, 16 October 2013 17:26 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 8638411E81E8 for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.017
X-Spam-Level:
X-Spam-Status: No, score=-3.017 tagged_above=-999 required=5 tests=[AWL=-0.041, 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 XsMxNjSoocKX for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:26:18 -0700 (PDT)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8603411E82EA for <json@ietf.org>; Wed, 16 Oct 2013 10:25:33 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id q14so532155vbe.13 for <json@ietf.org>; Wed, 16 Oct 2013 10:25:19 -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:date :message-id:subject:from:to:cc:content-type; bh=G0O6yeo+ljJ0divRf0/FZUHgFtfgGlykS1KbdNiM0YU=; b=myBY8w6Njt29//nXGlv9Ba/tM1F3o0unS4DDJIiNPfBSImzBkh+Rpgzl9SLNp5EY61 g+MsDau43ejLMPa8CLLSK+3HuGJ5moTXybiegnoWWby1EWmXe6JRwbf3ySTZQ4eXfx1H pH30rgy0GYL17bSKPq2YZELcid84hMiCvoZUE+I9mlZqcCAXdH5Wp+5gKSE/Hw0aXLc9 6Fo+L9g3uNg3kwTME23+jDfn694M9ywYnok5TxgQkvNyEFB0xe3yVyMEfq2nCzg+h7bw us+aLmLoLBeOYjMita7BpXkHJFVPI0d2N9uXqBb6tA3daUDzf00/cafQdZc2yvfRYVsY YkHQ==
X-Gm-Message-State: ALoCoQnTs7eClo/nf1pbfM4UDKtNJFUIJEBPb3l21YnNkaJl7L2PfjzM8jW8ZmoIy7dHQEGcPgHV
MIME-Version: 1.0
X-Received: by 10.220.1.203 with SMTP id 11mr3179486vcg.15.1381944319397; Wed, 16 Oct 2013 10:25:19 -0700 (PDT)
Received: by 10.220.174.197 with HTTP; Wed, 16 Oct 2013 10:25:19 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <CAC4RtVB5ePdG5EF6bCTvJKdDn4nd9q35gfDsZOu0YnPU72ArKQ@mail.gmail.com>
References: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org> <CAC4RtVB5ePdG5EF6bCTvJKdDn4nd9q35gfDsZOu0YnPU72ArKQ@mail.gmail.com>
Date: Wed, 16 Oct 2013 10:25:19 -0700
Message-ID: <CAHBU6itbo6Pd-utOTcKUffd3_3YTxJZb8Lt44Vgx5201gOV8Bg@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a11c3d3f441e4bc04e8defcc4
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Possible next work for the WG
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, 16 Oct 2013 17:26:27 -0000

+1 to Barry. This would be super-useful, independent of whether we do
I-JSON or not.


On Wed, Oct 16, 2013 at 10:21 AM, Barry Leiba <barryleiba@computer.org>wrote;wrote:

> > Greetings again. While our AD ponders the 4627bis document
> > (probably on its way to IETF Last Call), the Working Group can
> > start to think about what it wants to do next, if anything. The
> > chairs have heard of at least four topics that the WG might or
> > might not want to add to its charter:
> ...
> > - Best practices document for JSON implementers and folks who
> > use JSON in protocols
>
> As I've mentioned, I'd like to do a document about guidelines for
> defining JSON objects in other documents/protocols, to make sure that
> we use JSON primitives for those definitions, and don't try to
> duplicate JSON grammar in ABNF.  See Section 6.2 of
> draft-ietf-repute-media-type-13 (currently in the RFC Editor queue)
> for an example, and look at Section 6.1.1 of version -12 of that
> document for the ABNF version of how I think it should NOT be done.
>
> Such a document could be on its own, or it could be part of the best
> practices document Paul mentioned.
>
> Barry
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>