Re: [Json] Proposed rechartering for the JSON WG
Cyrus Daboo <cyrus@daboo.name> Sun, 09 February 2014 16:09 UTC
Return-Path: <cyrus@daboo.name>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2E7D1A03B3 for <json@ietfa.amsl.com>; Sun, 9 Feb 2014 08:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4joc9kme8OgW for <json@ietfa.amsl.com>; Sun, 9 Feb 2014 08:09:52 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 258341A017E for <json@ietf.org>; Sun, 9 Feb 2014 08:09:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 7F3A75C16240; Sun, 9 Feb 2014 11:09:50 -0500 (EST)
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 tzM7XKzoN9Re; Sun, 9 Feb 2014 11:09:49 -0500 (EST)
Received: from [10.251.51.14] (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id 5DC295C16236; Sun, 9 Feb 2014 11:09:49 -0500 (EST)
Date: Sun, 09 Feb 2014 11:09:47 -0800
From: Cyrus Daboo <cyrus@daboo.name>
To: Paul Hoffman <paul.hoffman@vpnc.org>, JSON WG <json@ietf.org>
Message-ID: <8AA70C014EEED3158A177F1C@cyrus.local>
In-Reply-To: <7E1F7FE6-E7A9-4B7D-902C-A60D39B7B994@vpnc.org>
References: <52D9B39C.5020102@cisco.com> <1C1347D2-0D99-4D49-B4C1-199246167D23@vpnc.org> <CAMm+Lwj0phrmP563tBbZJKHeYw=Azh1as6GZOA6rANPpC6PJgA@mail.gmail.com> <CAHBU6iv+-9xQYAjZdfZk7+GeA6J+sjaV5era3L+PiJ9RoauBYg@mail.gmail.com> <CAMm+Lwh0O4+iuaJMUhYgj+0GS8e9b_nZtNNX91hOmjUypsgkTQ@mail.gmail.com> <CAK3OfOhu0GZY9CVQrqD4SyjHLVEoEg1DtYj_6imZbbHtzX2eEw@mail.gmail.com> <CAHBU6iuR0MPm9q483jBMqTRkGV1f2giGNhp+UciQ7rRnrvcEBA@mail.gmail.com> <C271F837-40FD-4E87-A56B-0F0357553923@mnot.net> <7E1F7FE6-E7A9-4B7D-902C-A60D39B7B994@vpnc.org>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size="1175"
Subject: Re: [Json] Proposed rechartering for the JSON WG
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 09 Feb 2014 16:09:54 -0000
Hi Paul, --On February 8, 2014 at 7:13:16 PM -0800 Paul Hoffman <paul.hoffman@vpnc.org> wrote: >> I’d be more comfortable if the charter were more explicit about this; >> e.g., “A set of natural-language terms and/or phrases for use in >> future specifications that use JSON. This explicitly excludes schema >> languages and similar formalisms.” > > Do the folks who earlier +1'd the proposed text like Mark's reformulation? > Would that rule out something like: <http://tools.ietf.org/html/draft-newton-json-content-rules-01>? I have found that extremely useful in a couple of specs I have used. It focusses the spec developer on enumerating the structure and set of members etc in a JSON document. It helps developers by making clear all the possible options (something examples are not good at). I am not sure a "natural-language" formalism is sufficient because that is not as expressive as a "structured" formalism for describing things like hierarchy, e.g.: A contains B contains C vs A : { B : { C } } Even with "natural language" I suspect people will introduce lists, indents etc leading to something more structured. -- Cyrus Daboo
- Re: [Json] Proposed rechartering for the JSON WG Phillip Hallam-Baker
- Re: [Json] Proposed rechartering for the JSON WG Paul Hoffman
- [Json] Proposed rechartering for the JSON WG Matt Miller
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Martin J. Dürst
- Re: [Json] Proposed rechartering for the JSON WG Erik Wilde
- Re: [Json] Proposed rechartering for the JSON WG Martin J. Dürst
- Re: [Json] Proposed rechartering for the JSON WG Barry Leiba
- Re: [Json] Proposed rechartering for the JSON WG Carsten Bormann
- Re: [Json] Proposed rechartering for the JSON WG Paul Hoffman
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Paul Hoffman
- Re: [Json] Proposed rechartering for the JSON WG Joe Hildebrand (jhildebr)
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Stefan Drees
- Re: [Json] Proposed rechartering for the JSON WG Joe Hildebrand (jhildebr)
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Larry Masinter
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Martin J. Dürst
- Re: [Json] Proposed rechartering for the JSON WG Paul Hoffman
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Phillip Hallam-Baker
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Stefan Drees
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Mark Nottingham
- Re: [Json] Proposed rechartering for the JSON WG Phillip Hallam-Baker
- Re: [Json] Proposed rechartering for the JSON WG Paul Hoffman
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Cyrus Daboo
- Re: [Json] Proposed rechartering for the JSON WG Carsten Bormann
- Re: [Json] Proposed rechartering for the JSON WG Stefan Drees
- Re: [Json] Proposed rechartering for the JSON WG Phillip Hallam-Baker
- Re: [Json] Proposed rechartering for the JSON WG Tim Bray
- Re: [Json] Proposed rechartering for the JSON WG Andrew Newton
- Re: [Json] Proposed rechartering for the JSON WG Mark Nottingham
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Phillip Hallam-Baker
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams
- Re: [Json] Proposed rechartering for the JSON WG Phillip Hallam-Baker
- Re: [Json] Proposed rechartering for the JSON WG John Cowan
- Re: [Json] Proposed rechartering for the JSON WG Nico Williams