IETF Logo Mail Archive

Re: [Json] on serialization of signed zero

Carsten Bormann <cabo@tzi.org> Sun, 05 July 2015 18:57 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 93CEB1A03A3 for <json@ietfa.amsl.com>; Sun, 5 Jul 2015 11:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=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 MRIzELCbreM5 for <json@ietfa.amsl.com>; Sun, 5 Jul 2015 11:57:11 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967FE1A8851 for <json@ietf.org>; Sun, 5 Jul 2015 11:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id t65Iv3KD022338; Sun, 5 Jul 2015 20:57:03 +0200 (CEST)
Received: from alma.local (p5DC7EA60.dip0.t-ipconnect.de [93.199.234.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3mPfQl0Y02z3GFt; Sun, 5 Jul 2015 20:57:02 +0200 (CEST)
Date: Sun, 05 Jul 2015 20:57:01 +0200
From: Carsten Bormann <cabo@tzi.org>
To: Sonny Piers <sonny@fastmail.net>, json@ietf.org
Message-ID: <etPan.55997dfd.73864aa0.109d5@alma.local>
In-Reply-To: <55996D2C.8050907@fastmail.net>
References: <55996D2C.8050907@fastmail.net>
X-Mailer: Airmail (303)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="55997dfd_7e82f69f_109d5"
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/irMXBK-seEDeU5iCVF2Ac-0k4TM>
Subject: Re: [Json] on serialization of signed zero
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Jul 2015 18:57:12 -0000

http://www.ietf.org/mail-archive/web/json/current/msg01661.html

(And the whole thread around that.)

Grüße, Carsten

On 5 Jul 2015 at 19:52:31, Sonny Piers (sonny@fastmail.net) wrote:

Hello,

Signed zeros are included in the IEEE floating point standard.
From my understanding RFC 7159 doesn't forbid them.
But both python and ECMAScript serialize signed zeros (-0) into "0".

I wonder what would be the correct way of serializing them.

Thanks.
_______________________________________________  
json mailing list  
json@ietf.org  
https://www.ietf.org/mailman/listinfo/json

v2.23.0 | Report a Bug | By Email