IETF Logo Mail Archive

Re: [apps-discuss] Concise Binary Object Representation (CBOR)

Carsten Bormann <cabo@tzi.org> Thu, 23 May 2013 20:35 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE22F21F9638 for <apps-discuss@ietfa.amsl.com>; Thu, 23 May 2013 13:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.214
X-Spam-Level:
X-Spam-Status: No, score=-106.214 tagged_above=-999 required=5 tests=[AWL=0.035, 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 lhsDUy+UtbW2 for <apps-discuss@ietfa.amsl.com>; Thu, 23 May 2013 13:35:25 -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 D4F1E21F949A for <apps-discuss@ietf.org>; Thu, 23 May 2013 12:56:26 -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 r4NJtvhr019917; Thu, 23 May 2013 21:55:57 +0200 (CEST)
Received: from [192.168.217.105] (p54891C3A.dip0.t-ipconnect.de [84.137.28.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 1D3F23161; Thu, 23 May 2013 21:55:57 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAMm+LwibNh4mYU2+o6h8Vk1763PXMXx66t7utftAqy_J8TAQzA@mail.gmail.com>
Date: Thu, 23 May 2013 21:55:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A6FC529-F95D-4F2D-9BCF-F0C7ED24CD54@tzi.org>
References: <61CB1D18-BABC-4C77-93E6-A9E8CDA8326B@vpnc.org> <CAK3OfOhVRqUp+xn8mBj8_x8pgubc7bhWebzsFLvoj+ieWmr5gg@mail.gmail.com> <142483A4-2E80-43F1-B3BE-B5B01650BB8F@tzi.org> <CAK3OfOim44hRaRoFh8vKfK5SPVAnvTGiBV4cizvw30K=ZQPJHQ@mail.gmail.com> <84317001-DB56-4DBE-9D1E-A4E605BC07A0@tzi.org> <alpine.LSU.2.00.1305231811430.30305@hermes-2.csi.cam.ac.uk> <CAMm+LwibNh4mYU2+o6h8Vk1763PXMXx66t7utftAqy_J8TAQzA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, General discussion of application-layer protocols <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Concise Binary Object Representation (CBOR)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 20:35:41 -0000

On May 23, 2013, at 21:31, Phillip Hallam-Baker <hallam@gmail.com> wrote:

> Completely off topic here but raised by the discussion. JSON needs to address NaN encoding.
> 
> NaN is essential for exchange of numeric data in scientific applications. JSON is going to be used in those applications. It would be better to have one way to use JSON in scientific applications rather than have different work arounds emerge.

The applications I have seen trying to address the problem have simply used null to encode NaN.
There is rarely a case when you need to be able to express both null and NaN in one place (use CBOR, then :-).

A bigger problem is -Infinity/Infinity, but similar hacks can be used there, too (say, use false/true, or stringify).

> There is an ongoing effort to document JSON, this should be included in those efforts.

JSON MUST NOT change, so I don't think I agree with that (neither does the proposed charter of the WG).

Grüße, Carsten

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