Re: [Json] Proposed change to the title of the spec

Carsten Bormann <cabo@tzi.org> Wed, 05 June 2013 17:43 UTC

Return-Path: <cabo@tzi.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 5EEAD21F9BA6 for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 10:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 9GIuo9INchoy for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 10:43:10 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id DECB921F92F5 for <json@ietf.org>; Wed, 5 Jun 2013 10:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r55Hh1Mo015392; Wed, 5 Jun 2013 19:43:01 +0200 (CEST)
Received: from [127.0.0.1] (zoo.informatik.uni-bremen.de [134.102.218.16]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E43783813; Wed, 5 Jun 2013 19:43:00 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6itH4FfTS-0W+tjZ5J+0g1BEH88OxcCcX1bZrVzBLOVDHA@mail.gmail.com>
Date: Wed, 05 Jun 2013 19:42:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CBDD3A1-CEFA-44E6-BA1B-85E8050ECB2C@tzi.org>
References: <FED4D467-E578-4BD2-AF4F-A7F956F41B4F@vpnc.org> <CAK3OfOgD1SdZRA78Ayq-_gAnyT8mmU=tEjtfB94uPmNvZxYtyQ@mail.gmail.com> <CAHBU6itH4FfTS-0W+tjZ5J+0g1BEH88OxcCcX1bZrVzBLOVDHA@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1503)
Cc: json@ietf.org
Subject: Re: [Json] Proposed change to the title of the spec
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: Wed, 05 Jun 2013 17:43:20 -0000

On Jun 5, 2013, at 18:53, Tim Bray <tbray@textuality.com> wrote:

> I’m +0 on this but think it would be just wonderful to take JavaScript out of the name.  

+1

> New title: “The JSON Format for Encoding Data”. Who said JSON had to stand for anything?  -T

Let's not forget to write the RFC editor note explaining why they shouldn't put back an expansion of the abbreviation...

Grüße, Carsten

PS.; s/"Encoding"/"Representing"/, but that is too far in bikeshed territory.