IETF Logo Mail Archive

Re: [Json] "best practices" Vs. Profile for i-json

Phillip Hallam-Baker <ietf@hallambaker.com> Fri, 01 August 2014 23:01 UTC

Return-Path: <hallam@gmail.com>
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 AA61F1A0199 for <json@ietfa.amsl.com>; Fri, 1 Aug 2014 16:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.343
X-Spam-Level: ***
X-Spam-Status: No, score=3.343 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FF_IHOPE_YOU_SINK=2.166, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FRT_ADOBE2=2.455, SPF_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 RSrWNsAAA_CZ for <json@ietfa.amsl.com>; Fri, 1 Aug 2014 16:01:43 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29C0E1A0174 for <json@ietf.org>; Fri, 1 Aug 2014 16:01:42 -0700 (PDT)
Received: by mail-la0-f48.google.com with SMTP id gl10so3751449lab.35 for <json@ietf.org>; Fri, 01 Aug 2014 16:01:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=njxyIULMAgHY5f1ibm1U4R759UDskTuNaBQFWcuwIfI=; b=TPizsLrfXC/Vo4kII6YWpDDXASSA9s26CGGHaQKlikMuSQx0uudtYEWic4IxjDX92k iyow62FGHScaWJCn8okhNU/S6DYLeNyr7/16kktV9w+DabOzZPSOwyILbSppFyYRl+zM 3g8Zv0R/ZC/JgEoyGZ6gikY+Wfltbm8Orgla2qnbe5sXVuVX6oUHUcaAG2uEw3PXyYTW OgXsHxq285bqR5y4mZDJXOlopZcuhS5mDJrdna79zSZdnIJTrIOCOlk3AqDMeqllYEiF DQr5doc9kchp9S80l1qLJNba/NLdQ6Z0LQMGqCijMP0FakKRWL1l4XjiUIKLvJeOmw8O ksPA==
MIME-Version: 1.0
X-Received: by 10.152.29.202 with SMTP id m10mr9530487lah.4.1406934101494; Fri, 01 Aug 2014 16:01:41 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.122.50 with HTTP; Fri, 1 Aug 2014 16:01:41 -0700 (PDT)
In-Reply-To: <2d53157574f749e0b1399b9e39564ecd@BL2PR02MB307.namprd02.prod.outlook.com>
References: <2d53157574f749e0b1399b9e39564ecd@BL2PR02MB307.namprd02.prod.outlook.com>
Date: Fri, 01 Aug 2014 19:01:41 -0400
X-Google-Sender-Auth: FK7Su7MEVvfa-QzOhs3Ey_9vThI
Message-ID: <CAMm+LwhXmtYzs4wO-znptyQvrU9ci3LQvNREgyiSu7mJsOTXsA@mail.gmail.com>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
To: Larry Masinter <masinter@adobe.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/daytiyt85KNDk_hwM3S2YciQrJo
Cc: IETF JSON WG <json@ietf.org>
Subject: Re: [Json] "best practices" Vs. Profile for i-json
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: Fri, 01 Aug 2014 23:01:44 -0000

On Fri, Aug 1, 2014 at 5:55 PM, Larry Masinter <masinter@adobe.com> wrote:
> My conclusion after some discussions at IETF is that i-json needs to separate "best practices" vs "profile".
>
> The SHOULD belongs with best practices: e.g., "numbers in I-JSON SHOULD be representable by IEEE floating point."
>
> If you want a real profile, though, you need clear criteria:
> "All numeric values in I-JSON MUST round-trip to IEEE floating point and back to the same string."
> And then if you want an exception, make it application dependent: "the result must be JSON and SHOULD be I-JSON".

Not happening unless we move to a binary encoding or a binary exponent
encoding. To round trip the floating point between binary and decimal
exponents is ridiculously non-trivial.

v2.23.0 | Report a Bug | By Email