Re: [Json] Possible next work for the WG

Barry Leiba <barryleiba@computer.org> Wed, 16 October 2013 17:21 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 7521521F849C for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level:
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 DKi4pmlXfgZk for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:21:32 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9163311E8182 for <json@ietf.org>; Wed, 16 Oct 2013 10:21:28 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id u14so911619lbd.16 for <json@ietf.org>; Wed, 16 Oct 2013 10:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xoh6Wg1ZzlpCx1eb5NqbKF9BQmywkWGWg2ENmOceDbc=; b=MxAMOlNoxA8ZnXjvJA6hl0L0F1nHrxhjNGysPxCZ/2FDOxESbj+NYdGms9GaUg33+c V4IPBNOA81833FfpxliXoOBABgW2KAKMztc/6DpqL5SN/zaM6LpEM8OhfOH2w+vcUZGO 7vX99HlpLtEnhfxh0z6vItaoJw+S4JCLgLCfcwxuv/HpXrB973GAmEcpBhdnzfLQ325Y CsYmImIvndRFeWzTHBOk1JfHtAbcQaEq1qrpgZtErv25jigxDX8i7qw/BF+pR+Ry7Xwm SeMIRsfq00C8DeC3aQlhapYrwpFYzxemO5wAvLukTGpIJnS+3jY5R/FMfY5cZh92Q3Ku NFiA==
MIME-Version: 1.0
X-Received: by 10.152.202.167 with SMTP id kj7mr2234498lac.43.1381944087270; Wed, 16 Oct 2013 10:21:27 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Wed, 16 Oct 2013 10:21:27 -0700 (PDT)
In-Reply-To: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org>
References: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org>
Date: Wed, 16 Oct 2013 13:21:27 -0400
X-Google-Sender-Auth: -TrJg_LA4F0rGSoVPQQMsxsZH38
Message-ID: <CAC4RtVB5ePdG5EF6bCTvJKdDn4nd9q35gfDsZOu0YnPU72ArKQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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:21:32 -0000

> 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