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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Mon, 18 February 2013 23:52 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 357AF21E8087; Mon, 18 Feb 2013 15:52:29 -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 2dHQjGgR4UVs; Mon, 18 Feb 2013 15:52:28 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5E9A521F8D39; Mon, 18 Feb 2013 15:52:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=666; q=dns/txt; s=iport; t=1361231545; x=1362441145; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=NFjddzjdNZf/54qUItK/GMPZ2PxAJg7Eu1G/juh59E8=; b=b4IWH4m0yPMAsdH/kB2mOJOeDfFfqQUSt7XcMrM5zt66wpL6mxU2bCzp hroiy5G7Eo9EqAKlgVXvGQA03bQhBp26oIGojm6PR/T4nAfHxme8GCtqD a9fdR/Eo31+rptmS9ELYHpZKHMUmv+tEhffMj6KjdffwtgtcR3W/w8U7S 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYFAJu9IlGtJXG+/2dsb2JhbABEhgK6IoEFFnOCIQEEOjQLEgEIDhQUMRElAgQOBQiHeAMPDLdJDYlajFCCLTEHY4F8YQOUUYJ4iiaFFYJ6DYIn
X-IronPort-AV: E=Sophos;i="4.84,691,1355097600"; d="scan'208";a="178521988"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-3.cisco.com with ESMTP; 18 Feb 2013 23:52:25 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r1INqOTV018930 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Feb 2013 23:52:24 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Mon, 18 Feb 2013 17:52:24 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Francis Galiegue <fgaliegue@gmail.com>
Thread-Topic: [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODhKwsPxTte9Ry0KhDmvQvHsA3piAfuyA//+6JQA=
Date: Mon, 18 Feb 2013 23:52:24 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F8950F8@xmb-rcd-x10.cisco.com>
In-Reply-To: <CALcybBDTd7fDnQ-zAiaG5srEJppfJHgQdBQzyoaU7DaHA=wPPw@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: <DFFA9F094CB8C8449FAE618902432ACE@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 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: Mon, 18 Feb 2013 23:52:29 -0000

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

>>http://trac.tools.ietf.org/wg/appsawg/trac/wiki/JSON
>
>JSON Schema is missing from this page (it has been updated recently
>and is now three specifications).

As an individual.

I'd say that a way to unambiguously specify further standards that use
JSON seems reasonable.  Whether it's json-schema or json-content-rules, or
something else seems like a fertile ground for discussion.

I like Cyrus's argument that all we need is the ABNF of the JSON world,
and that any attempt to get more complicated than that will likely lead us
down the XSD rathole.

-- 
Joe Hildebrand