Re: [apps-discuss] [Json] JSON mailing list and BoF

Francis Galiegue <fgaliegue@gmail.com> Tue, 19 February 2013 01:15 UTC

Return-Path: <fgaliegue@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5A121E8053; Mon, 18 Feb 2013 17:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmFcGqIZ-YXG; Mon, 18 Feb 2013 17:15:16 -0800 (PST)
Received: from mail-ea0-f171.google.com (mail-ea0-f171.google.com [209.85.215.171]) by ietfa.amsl.com (Postfix) with ESMTP id C646021E8044; Mon, 18 Feb 2013 17:15:15 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id c13so2547101eaa.30 for <multiple recipients>; Mon, 18 Feb 2013 17:15:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=R7I2vmOLFVliJAyFE4XM5zSP8/0Tqha4+mVIivB2+UQ=; b=gHYJeMoO1A0utRhUTleOUrEvywikxfjgE03/nFRbQX3hvDPSux/XyiIU+Pd59ovo2U NTIlSKqqyIOgwFv5fVcYnSwc0gMt4vQcAUr3Z4P9D1LvggMueGZUR+bfASjaYeanXIsg BfoyIG9zuO6anm0SJt8cmpygXNEpI77ZP5bixp+mUD4wYdeZqLExutfOsek1N9qurWrl 4R0vZjWYCNmWTgq+I7ZJ7TcyLTljvOkNsHRfPD7HTJZ7a/EKallJobem2Lua+FScePBx 1EnyHgCctEAWrCiH9nKhb/9xlgPDLfTy9bZFme8qkSIO6TiRbc/Ja15JYvtzduVa2sg1 RDPQ==
MIME-Version: 1.0
X-Received: by 10.14.183.67 with SMTP id p43mr50721333eem.10.1361236514813; Mon, 18 Feb 2013 17:15:14 -0800 (PST)
Received: by 10.14.1.7 with HTTP; Mon, 18 Feb 2013 17:15:14 -0800 (PST)
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F89529D@xmb-rcd-x10.cisco.com>
References: <CALcybBASCnye2JB98-vQnknkb2Pwu9wfOrXY_ygQqNipac5qwg@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A70F89529D@xmb-rcd-x10.cisco.com>
Date: Tue, 19 Feb 2013 02:15:14 +0100
Message-ID: <CALcybBAK++79uX8WqH6Y0n6f_5LcdcWNMeXkB58iwc-T8ayT9A@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [apps-discuss] [Json] JSON mailing list and BoF
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 01:15:17 -0000

On Tue, Feb 19, 2013 at 2:07 AM, Joe Hildebrand (jhildebr)
<jhildebr@cisco.com> wrote:
[...]
>
> Oh! Sorry, I didn't mean to imply that I didn't like json-schema, just
> that there are several different approaches that have been proposed, and
> it makes sense to have a conversation about what our requirements are and
> if we think we're meeting them with one of those proposals.
>

I'd certainly like to have a digest of this discussion! I have my own
needs, and even my own implementation, so I cannot be partial here --
just be a witness on my use case.

> Charter-wise, setting the requirement to be "as simple as possible, but no
> simpler" is probably something we can all agree on; agreeing on what
> constitutes "simple" is likely to be more complex. :)
>
>> Which is why reviews are always welcome!
>
> I certainly need to review the latest versions before having an opinion.
>

Looking forward to this!

Have fun,
-- 
Francis Galiegue, fgaliegue@gmail.com
Try out your JSON Schemas: http://json-schema-validator.herokuapp.com