Re: [Json] Proposed change to the title of the spec - LAST CHANCE ON PROPOSALS
Tatu Saloranta <tsaloranta@gmail.com> Mon, 10 June 2013 21:25 UTC
Return-Path: <tsaloranta@gmail.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 72FC421F9A3A for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 14:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.421
X-Spam-Level:
X-Spam-Status: No, score=-2.421 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 9uJCHK4siNv2 for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 14:25:11 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 213CF21F9A38 for <json@ietf.org>; Mon, 10 Jun 2013 14:25:10 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id m46so5359221wev.30 for <json@ietf.org>; Mon, 10 Jun 2013 14:25:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fewToqIDzAsvvJu2L5NdhmUAS/k7F30CpF4USQj3wAU=; b=tq2KnJKme0ON52whGlyMeJ0QhcqY3feieeB3ErlwQNumwPbZNq0TJEiqNk+cdRZk5Z G0XYz8+xm/1VboUaIOMWH9LgLLbo7ZXL3Cxl4DKRDg7tzq2hk1GYSQ1xG/OSE3PYnCoH EgY0I03vQpOw+TL6DOpzmxfpRLZPkOKKNVJxbp74PxN7UNwNaxv3gSgKB6spMOf0Ds3w fW6ABoRdImElecX18AIxhT+OuiuuYRhXiHlw8iJD7tM1hUCxq/N7ZPcqvV/azoLXxlpg sojr4ag29fmQ5BepXUvmDQAZHxt+cEQbaPiI9mUHindLGFD/H9wWGuw+lMYyUzf90vrj 5g7w==
MIME-Version: 1.0
X-Received: by 10.180.185.44 with SMTP id ez12mr5730926wic.7.1370899509899; Mon, 10 Jun 2013 14:25:09 -0700 (PDT)
Received: by 10.227.72.74 with HTTP; Mon, 10 Jun 2013 14:25:09 -0700 (PDT)
In-Reply-To: <CAK3OfOiPgmMBZ4hkXUd8HQRk2z=DpQisAAAB_R6tK7umXCNKjA@mail.gmail.com>
References: <FED4D467-E578-4BD2-AF4F-A7F956F41B4F@vpnc.org> <BF7E36B9C495A6468E8EC573603ED94115282053@xmb-aln-x11.cisco.com> <51B63979.40601@drees.name> <CAK3OfOiPgmMBZ4hkXUd8HQRk2z=DpQisAAAB_R6tK7umXCNKjA@mail.gmail.com>
Date: Mon, 10 Jun 2013 14:25:09 -0700
Message-ID: <CAGrxA263KJLxrEULWZSvh6pR8qKsetyyeCd2ixkNLO5d7G9aPQ@mail.gmail.com>
From: Tatu Saloranta <tsaloranta@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Content-Type: multipart/alternative; boundary="001a11c225744f793904ded36ad1"
Cc: "Matt Miller (mamille2)" <mamille2@cisco.com>, stefan@drees.name, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposed change to the title of the spec - LAST CHANCE ON PROPOSALS
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: Mon, 10 Jun 2013 21:25:13 -0000
On Mon, Jun 10, 2013 at 2:03 PM, Nico Williams <nico@cryptonector.com>wrote: > On Mon, Jun 10, 2013 at 3:39 PM, Stefan Drees <stefan@drees.name> wrote: > > I thus hereby propose as new title: > > > > NEW: > > """ > > > > The JSON Text Format > > > > """ > > I would object. It is conceivable to have a binary encoding (like the > recently proposed CBOR) that could (or a subset of which could) > represent the same data as JSON. And it might even be possible to > update the UTF detection logic to support the such an encoding. The > new thing could be equivalent to JSON and a reasonable transformation > of it, but it wouldn't be text. Not just could but there already exist multiple, like Smile ( http://wiki.fasterxml.com/SmileFormatSpec) and ubjson (http://ubjson.org/). Smile supports auto-detection just as you suggested, to allow seamless detection. And indeed, the idea of logical JSON model and one or more matching physical serializations is simple, powerful and useful thing (similar to binary infosets for xml). Then again, _this_ specification does define details of textual serialization of logical model, so existence of binary serialization does not in itself invalidate use of "text" in title. -+ Tatu +-
- [Json] Proposed change to the title of the spec Paul Hoffman
- Re: [Json] Proposed change to the title of the sp… Nico Williams
- Re: [Json] Proposed change to the title of the sp… Tim Bray
- Re: [Json] Proposed change to the title of the sp… Vinny A
- Re: [Json] Proposed change to the title of the sp… Stefan Drees
- Re: [Json] Proposed change to the title of the sp… Peter Brooks
- Re: [Json] Proposed change to the title of the sp… Paul Hoffman
- Re: [Json] Proposed change to the title of the sp… Carsten Bormann
- Re: [Json] Proposed change to the title of the sp… Markus Lanthaler
- Re: [Json] Proposed change to the title of the sp… Douglas Crockford
- Re: [Json] Proposed change to the title of the sp… Matt Miller (mamille2)
- Re: [Json] Proposed change to the title of the sp… Tim Bray
- Re: [Json] Proposed change to the title of the sp… Vinny A
- Re: [Json] Proposed change to the title of the sp… Matthew Morley
- Re: [Json] Proposed change to the title of the sp… Matt Miller (mamille2)
- Re: [Json] Proposed change to the title of the sp… Tim Bray
- Re: [Json] Proposed change to the title of the sp… Stefan Drees
- Re: [Json] Proposed change to the title of the sp… R S
- Re: [Json] Proposed change to the title of the sp… Rick Waldron
- Re: [Json] Proposed change to the title of the sp… Paul Hoffman
- Re: [Json] Proposed change to the title of the sp… Nico Williams
- Re: [Json] Proposed change to the title of the sp… Tatu Saloranta