Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
Tony Hansen <tony@att.com> Mon, 17 March 2014 02:38 UTC
Return-Path: <tony@att.com>
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 1A5461A0365 for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 19:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.126
X-Spam-Level:
X-Spam-Status: No, score=-2.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] 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 4li9Y2xjRyLg for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 19:38:39 -0700 (PDT)
Received: from egssmtp03.att.com (egssmtp03.att.com [144.160.128.152]) by ietfa.amsl.com (Postfix) with ESMTP id 676AF1A0250 for <json@ietf.org>; Sun, 16 Mar 2014 19:38:39 -0700 (PDT)
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp03.att.com ( egs 8.14.5/8.14.5) with ESMTP id s2H2cUdf026295 for <json@ietf.org>; Sun, 16 Mar 2014 19:38:31 -0700
Received: from vpn-135-70-97-222.vpn.swst.att.com ([135.70.97.222]) by maillennium.att.com (mailgw1) with ESMTP id <20140317023829gw100j0c82e>; Mon, 17 Mar 2014 02:38:30 +0000
X-Originating-IP: [135.70.97.222]
Message-ID: <5326601E.3040501@att.com>
Date: Sun, 16 Mar 2014 22:38:22 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
CC: IETF JSON WG <json@ietf.org>
References: <53238F21.2030508@cisco.com> <nll8i999lis5u0f719iv6bgte71d8uus52@hive.bjoern.hoehrmann.de>
In-Reply-To: <nll8i999lis5u0f719iv6bgte71d8uus52@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/json/gJCN2M5N93FmIoBkyhVCaCp9Qok
Subject: Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
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: Mon, 17 Mar 2014 02:38:41 -0000
On 3/15/14, 9:46 AM, Bjoern Hoehrmann wrote: > * Matt Miller wrote: >> The chairs are seeking comment on whether we should adopt I-JSON >> (http://tools.ietf.org/html/draft-bray-i-json-01) as a WG item in our >> charter. Remember that adopting this draft does not mean it is done; >> changes can happen based on the consensus of the WG. > No, not without changing the nature of the document considerably. These > are just best practises and not a separate format with its own name. Based on the conversation that we had at the WG session in London, I came away convinced that: *) it does need to be a WG item *) we need neither a new media type nor a mandatory internal-tag indicating compliance with i-json, so that stuff needs to be removed from the document *) an optional internal-tag might need some more discussion *) the document should really just reflect a set of restrictions on the json format that can be (optionally?) validated against - Tony Hansen
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nico Williams
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tony Hansen
- [Json] Call for WG Consensus to Adopt I-JSON as a… Matt Miller
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tim Bray
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nat Sakimura
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Dave Cottlehuber
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Levine
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Martin J. Dürst
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Stefan Drees
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tim Bray
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Larry Masinter
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nico Williams
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker