IETF Logo Mail Archive

Re: [Json] [apps-discuss] JSON mailing list and BoF

Francis Galiegue <fgaliegue@gmail.com> Tue, 19 February 2013 22:05 UTC

Return-Path: <fgaliegue@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 046FD21F89A3; Tue, 19 Feb 2013 14:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.266
X-Spam-Level:
X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTH1PPTN1j-Z; Tue, 19 Feb 2013 14:05:14 -0800 (PST)
Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) by ietfa.amsl.com (Postfix) with ESMTP id 825AB21F8815; Tue, 19 Feb 2013 14:05:09 -0800 (PST)
Received: by mail-ee0-f42.google.com with SMTP id b47so3660830eek.15 for <multiple recipients>; Tue, 19 Feb 2013 14:05:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VmMPrUWxsrfSadz5WAqK0wpjSPpMA1JMlS81TlqR5/A=; b=fDrsKXz9oJ6kgjsOzt6/REW23pppl50TbMhVExO19b3WLqNEFHFWy2fNQuatJnR/yo hlFmwS2+rDWxU2Dg2kC2LQA0dANtn9tDgPynSq/I2/hMQdAlsCv+65Hidhi16nGxE0Hz AHO/VxsI7jUpDsmkZsveeM4AKrE9ZEv0b7D5NxK5Bu3wdc9zaO+jJzwjcXJRbjK8Oxfo h5AhIEzXsYlbeSgFJrdCZfOxOaCMCL+aTOwhWkDipn9gd8sr9iC8OVBA1b+eGyyFKF/i 5SLgcSafZj6epDiw3XZvqWK7TqFvQ/K9pwr7+QdNa5BUtpz7yiQSmcQjDMnVrZR4KRJh x6Hg==
MIME-Version: 1.0
X-Received: by 10.14.183.198 with SMTP id q46mr61937203eem.1.1361311508874; Tue, 19 Feb 2013 14:05:08 -0800 (PST)
Received: by 10.14.1.7 with HTTP; Tue, 19 Feb 2013 14:05:08 -0800 (PST)
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F897C72@xmb-rcd-x10.cisco.com>
References: <CAHBU6iuFU8-BO4k5nneVGg9VCi3rVx=_w4AYz143KmrmEn6zaw@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A70F897C72@xmb-rcd-x10.cisco.com>
Date: Tue, 19 Feb 2013 23:05:08 +0100
Message-ID: <CALcybBCVjH2QPvx9q7qoDDq-Z=NQaOHuXhVzwn9SNzfzaTdKFg@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Mike Jones <Michael.Jones@microsoft.com>, "Matt Miller (mamille2)" <mamille2@cisco.com>, Tim Bray <tbray@textuality.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Tue, 19 Feb 2013 22:05:15 -0000

On Tue, Feb 19, 2013 at 10:55 PM, Joe Hildebrand (jhildebr)
<jhildebr@cisco.com> wrote:
[...]
>
> I can figure out how to generate a -INF, but how do I get a -NaN?
>

The current JSON specification doesn't mandate any limit to the
precision and/or scale of numeric instances, and I was particularly
attentive to this aspect of JSON when writing the JSON Schema specs,
since my first use case for using JSON Schema was the ability to use
keywords such as "minimum", "maximum", "multipleOf" to validate
arbitrary numerical JSON instances. The JSON Schema validation specs
(OK, these are my words) says this:

http://tools.ietf.org/html/draft-fge-json-schema-validation-00#section-3.2

I _do believe that JSON itself should not define NaN. JSON can express
arbitrary data and should not care about the capabilities of language
A or B in a transacation. Only recommendations and/or warnings can be
given at that point.

--
Francis Galiegue, fgaliegue@gmail.com
Try out your JSON Schemas: http://json-schema-validator.herokuapp.com

v2.23.0 | Report a Bug | By Email