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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 19 February 2013 01:07 UTC

Return-Path: <jhildebr@cisco.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 B663A21E8063; Mon, 18 Feb 2013 17:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 y8pb5SJy13hb; Mon, 18 Feb 2013 17:07:38 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 27BC321E8044; Mon, 18 Feb 2013 17:07:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1160; q=dns/txt; s=iport; t=1361236058; x=1362445658; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=0Ydq1sRzavbAoylHxitDzc666BHZbUMPpfAW+bX6b+k=; b=R8stN0XRA3kTzytfWM2BnMvTezEF2BlIG0WDR2zXRHwHTEKFrHsSh/eF 1M229qR4sVSijbIRdTBhVWToeoW5WcLcxL4+JT0cTEmZ0Cm4LORG4TQkN 7HvflvylNUYEslM/oTEY1ARwdHX3tBHDHPoEe0NqpzNMHZjw4L35QTqSN s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFANTPIlGtJXG+/2dsb2JhbABEwCmBBRZzgh8BAQEDATo0CwUNAQgOFBQxESUCBA4FCId4AwkGsUCGDw2JWoxQgi0xB4JfYQOSbYFkjR6FFYMHgWskGA
X-IronPort-AV: E=Sophos;i="4.84,692,1355097600"; d="scan'208";a="178504137"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 19 Feb 2013 01:07:37 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1J17bI8031648 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 01:07:37 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Mon, 18 Feb 2013 19:07:37 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Francis Galiegue <fgaliegue@gmail.com>
Thread-Topic: [Json] [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODhKwsPxTte9Ry0KhDmvQvHsA3piAfuyA//+6JQCAAHtEgP//mcEA
Date: Tue, 19 Feb 2013 01:07:36 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F89529D@xmb-rcd-x10.cisco.com>
In-Reply-To: <CALcybBASCnye2JB98-vQnknkb2Pwu9wfOrXY_ygQqNipac5qwg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.129.24.68]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B703AE9FFCFA9A4EA871C902F0420B61@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:07:38 -0000

On 2/18/13 5:13 PM, "Francis Galiegue" <fgaliegue@gmail.com> wrote:

>I have really struggled to make this specification useful, and
>witnessing the users of my library alone, it looks like the pure
>validation part of JSON Schema already has quite a few users...
>
>I also make the best efforts not to repeat XSD's mistakes, and right
>now JSON Schema is young enough that it cannot have made such mistakes
>(I _think_). But in order not to repeat such mistakes, advice from
>external people is of course needed.

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.

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.


-- 
Joe Hildebrand