Re: [Json] Consensus call: document title
Vinny A <jsontest@yahoo.com> Sat, 22 June 2013 01:23 UTC
Return-Path: <jsontest@yahoo.com>
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 676491F0D3D for <json@ietfa.amsl.com>; Fri, 21 Jun 2013 18:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.382
X-Spam-Level:
X-Spam-Status: No, score=-0.382 tagged_above=-999 required=5 tests=[AWL=0.821, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pfsp9eTUYPiv for <json@ietfa.amsl.com>; Fri, 21 Jun 2013 18:23:34 -0700 (PDT)
Received: from nm16.bullet.mail.bf1.yahoo.com (nm16.bullet.mail.bf1.yahoo.com [98.139.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id C6E481F0D3B for <json@ietf.org>; Fri, 21 Jun 2013 18:23:31 -0700 (PDT)
Received: from [66.196.81.172] by nm16.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2013 01:23:30 -0000
Received: from [98.139.211.160] by tm18.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2013 01:23:30 -0000
Received: from [127.0.0.1] by smtp217.mail.bf1.yahoo.com with NNFMP; 22 Jun 2013 01:23:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1371864210; bh=wLwh1AMXQjD9z+gH9C3rho33rqfwkQUwPUBhWxhJTpE=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:References:From:Content-Type:X-Mailer:In-Reply-To:Message-Id:Date:To:Content-Transfer-Encoding:Mime-Version; b=TG7lrMgVMTPcTonfTL8tf5Td23YV6HFuOg0FRaHs+rY2aX4LrbZA3LL8xUuRPFvYpM24LYZHEH7dV8maLc06r1Qa0JfQ3wtcMWyqaSrr6LqL4p6kAIoECJAi14QNbZ3rsTNNu/uhZnKSXt6EFn1Mm4mn5GPtgAl1IMmh+OuvUoQ=
X-Yahoo-Newman-Id: 397778.11751.bm@smtp217.mail.bf1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: yQT856MVM1ka_VrndG7P0wAbpzJpm6j_8FUEgqQ0A7PLcMN 0ZEKohsgzpOO0EiQ6mVOqYGvEDrpB3iX.Dn5q0sPxnsSTe.bjNtM.WtvR.zX kNSEG2UUzCkQsZbFVBRGFfl4UKj06V8x57DKnVLrYBdMjFkNf4Mj3BcS6Rz0 RfXWzy812qnss9KY4N8qiRpWfkO2XoR8LMWcJDBPNrZMV4VH3VyzUqGXXoW1 dj7phoys1HNFyU1rPvX3pdb3tLx81S8m.JvBNYPwAd7tmQx6nG6jO.tE_LIZ 5h1te.e9HzbVo9eskURC4vGcerfiDoQIo4fZh5EiS1IMODkSXXl59Swm3thp ClS59hlOWuGWgwrF1WSu95EE02ASdCd.horW.WCnFJ9fH1zFa_Py05xOCvW4 _JyrphgSLDUQ19y8dcPhDoDEYJ2ZALg_bnT2tCZi7zY3cUKR7CZv67kI.yO2 Fff.B_PwfhDud.sJanJdwz_X8W.XwBuhaLy6L81cDN2vdGmfE3cKMlLVc8aE Q5hMNV8goUBZezH3B0RWvJwMC
X-Yahoo-SMTP: indQcmSswBC8IKsm6t4aCAPskK3T
X-Rocket-Received: from [192.168.0.102] (jsontest@76.29.100.42 with ) by smtp217.mail.bf1.yahoo.com with SMTP; 21 Jun 2013 18:23:30 -0700 PDT
References: <90B659B8-D4AC-41AF-8C06-67FC65C8BD74@vpnc.org>
From: Vinny A <jsontest@yahoo.com>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: iPod Mail (9B206)
In-Reply-To: <90B659B8-D4AC-41AF-8C06-67FC65C8BD74@vpnc.org>
Message-Id: <ECA8C2C2-38AF-4DE9-8E4D-D08F14D3FC6F@yahoo.com>
Date: Fri, 21 Jun 2013 20:23:29 -0500
To: JSON WG <json@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [Json] Consensus call: document title
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Jun 2013 01:23:46 -0000
On Jun 21, 2013, at 11:38 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote: > There are three proposals for dealing with the document title: > 0) Leave the title in the current draft as-is: > The application/json Media Type for JavaScript Object Notation (JSON) > 1) Change the title to > The JSON Data Interchange Format > 2) Change the title to > The JSON Format for Encoding Data > > Please respond to this message with a list of proposals you could accept, ordered from highest to lowest. Do not list proposals you cannot live with. If you cannot accept any of the proposals, please respond and say why. 1 >>> 2 > 0 1 is by far the best. 2 is still acceptable, while 0 is completely unacceptable ( we're trying to move away from JSON's JS origins, aren't we?) ----------------- Vinny www.jsontest.com
- Re: [Json] Consensus call: document title douglas@crockford.com
- [Json] Consensus call: document title Paul Hoffman
- Re: [Json] Consensus call: document title John Cowan
- Re: [Json] Consensus call: document title Tim Bray
- Re: [Json] Consensus call: document title Stephan Beal
- Re: [Json] Consensus call: document title Carsten Bormann
- Re: [Json] Consensus call: document title Barry Leiba
- Re: [Json] Consensus call: document title Jim Schaad
- Re: [Json] Consensus call: document title Norbert Lindenberg
- Re: [Json] Consensus call: document title Vinny A
- Re: [Json] Consensus call: document title R S
- Re: [Json] Consensus call: document title Martin J. Dürst
- Re: [Json] Consensus call: document title Stefan Drees
- Re: [Json] Consensus call: document title Matthew Morley