IETF Logo Mail Archive

Re: [Json] What are we trying to do?

Carsten Bormann <cabo@tzi.org> Wed, 03 July 2013 19:42 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 CB3B511E821B for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 12:42:24 -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 O5cI+Za1zpCr for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 12:42:19 -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 AB79811E821A for <json@ietf.org>; Wed, 3 Jul 2013 12:42:18 -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 r63Jg5KC008890; Wed, 3 Jul 2013 21:42:05 +0200 (CEST)
Received: from [192.168.217.105] (p54893DEB.dip0.t-ipconnect.de [84.137.61.235]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 484E637D0; Wed, 3 Jul 2013 21:42:05 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAK3OfOjvtU6=3EowmU0ccWAfQPSoGaUhPMLe+uK6pVR_sQDGFg@mail.gmail.com>
Date: Wed, 03 Jul 2013 21:42:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1AB34263-877A-43FC-899E-4681F90BD7B8@tzi.org>
References: <CAHBU6iv0wXYvAyasSE8Wga0K_sD_pKL6o-a-ca9yemhy3m6zzw@mail.gmail.com> <FB90FFED-5128-4B5C-85DE-78DFE2674310@vpnc.org> <CAK3OfOjvtU6=3EowmU0ccWAfQPSoGaUhPMLe+uK6pVR_sQDGFg@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1508)
Cc: Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] What are we trying to do?
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, 03 Jul 2013 19:42:24 -0000

On Jul 3, 2013, at 18:29, Nico Williams <nico@cryptonector.com> wrote:

> leave the rest mostly as-is 

That means that every user of JSON has to define their own additional clarifications, as JOSE has started to do.
In effect, each user creates their own little dialect.

A textbook example for how to create soup.

I'd rather have 2 or 3 flavors of JSON than n, where n is the number of users.
(Or, if it has to be, 2 or 3 on/off pizza toppings each of which can be selected or deselected.)

Grüße, Carsten

v2.29.0 | Report a Bug | By Email | System Status