Re: [Json] Possible next work for the WG

Cyrus Daboo <cyrus@daboo.name> Wed, 16 October 2013 17:41 UTC

Return-Path: <cyrus@daboo.name>
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 0806B11E82E2 for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, 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 VmZnTZ0mBGeG for <json@ietfa.amsl.com>; Wed, 16 Oct 2013 10:41:14 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 63C7311E8192 for <json@ietf.org>; Wed, 16 Oct 2013 10:41:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 61D4E4E935E5; Wed, 16 Oct 2013 13:41:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kxInOyqCy8cj; Wed, 16 Oct 2013 13:41:10 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 6F47A4E935DA; Wed, 16 Oct 2013 13:41:09 -0400 (EDT)
Date: Wed, 16 Oct 2013 13:41:04 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Barry Leiba <barryleiba@computer.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <4AA3150A764BF415C1DB9786@caldav.corp.apple.com>
In-Reply-To: <CAC4RtVB5ePdG5EF6bCTvJKdDn4nd9q35gfDsZOu0YnPU72ArKQ@mail.gmail.com>
References: <29850F92-23F1-4859-BB5A-BB5F1F20DD38@vpnc.org> <CAC4RtVB5ePdG5EF6bCTvJKdDn4nd9q35gfDsZOu0YnPU72ArKQ@mail.gmail.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=935
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:41:20 -0000

Hi Barry,

--On October 16, 2013 at 1:21:27 PM -0400 Barry Leiba 
<barryleiba@computer.org> wrote:

>> - 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.

Yes! And also please look at 
<http://tools.ietf.org/html/draft-daboo-aggregated-service-discovery-03#section-5> 
which makes use of 
<http://tools.ietf.org/html/draft-newton-json-content-rules-01> as another 
way to describe the "format" of a JSON document.

-- 
Cyrus Daboo