IETF Logo Mail Archive

Re: [Json] Meanwhile, out there...

Carsten Bormann <cabo@tzi.org> Sun, 02 March 2014 12:51 UTC

Return-Path: <cabo@tzi.org>
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 657E31A0D22 for <json@ietfa.amsl.com>; Sun, 2 Mar 2014 04:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
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 cnkETzT0qaZz for <json@ietfa.amsl.com>; Sun, 2 Mar 2014 04:51:05 -0800 (PST)
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 3ED371A0D1A for <json@ietf.org>; Sun, 2 Mar 2014 04:51:05 -0800 (PST)
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.5/8.14.5) with ESMTP id s22CopDk021669; Sun, 2 Mar 2014 13:50:52 +0100 (CET)
Received: from dhcp-9be3.meeting.ietf.org (dhcp-9be3.meeting.ietf.org [31.133.155.227]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 06A37E5F; Sun, 2 Mar 2014 13:50:50 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
X-Priority: 3
In-Reply-To: <211FD4E4CB37411AA3BA79156DEF9160@codalogic>
Date: Sun, 02 Mar 2014 12:50:48 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7D91939-F9D4-4149-85BD-FAAF13638254@tzi.org>
References: <7FE4234C-25BC-4AB9-B0DD-9E1641DB9BE0@mnot.net> <4CA4E293-3252-4082-A40C-DE867D732209@vpnc.org> <CAHBU6is9aq4Ev6zMBRbu+ik0VVbCLmedU9QkKHjxbw9pRjmm2A@mail.gmail.com> <211FD4E4CB37411AA3BA79156DEF9160@codalogic>
To: Pete Cordell <petejson@codalogic.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/xWT7HHm4Dmjhty8y5aiAsfCEyQA
Cc: Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Meanwhile, out there...
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: Sun, 02 Mar 2014 12:51:06 -0000

On 02 Mar 2014, at 12:15, Pete Cordell <petejson@codalogic.com> wrote:

> SHON - Simple Humanized Object Notation

YAML already fills this niche rather nicely.
It is a stable, widely implemented specification.
(It also happens to include JSON as a subset.)

There often is confusion because JSON is “human-readable”.
However, JSON is for app-to-app, not for human-to-app.
Most naive JSON extension proposals are based in not understanding this fine point.

In a pinch, JSON can be used for human-to-app.
But instead of trying to extend JSON to become another YAML, just use YAML for human-to-app.

(Human-readable, more generally speaking text-based, formats have certain advantages over binary formats even for app-to-app.
Insert MEGACO flip-a-coin story here.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email