Re: [Json] Comments on the proposed charter
Paul Hoffman <paul.hoffman@vpnc.org> Wed, 20 February 2013 02:22 UTC
Return-Path: <paul.hoffman@vpnc.org>
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 E865221F8814 for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 18:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level:
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 369kuxO+wC3z for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 18:22:42 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 887B921F8802 for <json@ietf.org>; Tue, 19 Feb 2013 18:22:42 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r1K2Me2C058890 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 19 Feb 2013 19:22:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <95501AA5-EA26-4D74-8C6B-187F0E52C524@mnot.net>
Date: Tue, 19 Feb 2013 18:22:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBD5A35E-4541-49AA-B486-0C41D1643E8D@vpnc.org>
References: <E0597F3D-773C-4CDD-8087-09B99ADCF156@mnot.net> <CALcybBD-ksPe71YY9BY-NZ9VP0tNqToySn8zp+9swtM=P9MiCw@mail.gmail.com> <95501AA5-EA26-4D74-8C6B-187F0E52C524@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.1499)
Cc: Francis Galiegue <fgaliegue@gmail.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Comments on the proposed charter
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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, 20 Feb 2013 02:22:43 -0000
> There are ways to be aware of how JSON will be used without taking responsibility for defining those uses. <repeatedly mashing the Like button> --Paul Hoffman
- [Json] Comments on the proposed charter Mark Nottingham
- Re: [Json] Comments on the proposed charter Peter Saint-Andre
- Re: [Json] Comments on the proposed charter Francis Galiegue
- Re: [Json] Comments on the proposed charter Mark Nottingham
- Re: [Json] Comments on the proposed charter Paul Hoffman
- Re: [Json] Comments on the proposed charter Matt Miller (mamille2)
- Re: [Json] Comments on the proposed charter Francis Galiegue
- Re: [Json] Comments on the proposed charter Peter Saint-Andre
- Re: [Json] Comments on the proposed charter Francis Galiegue
- Re: [Json] Comments on the proposed charter Peter Saint-Andre
- Re: [Json] Comments on the proposed charter Francis Galiegue
- Re: [Json] Comments on the proposed charter Peter Saint-Andre
- Re: [Json] Comments on the proposed charter SM