IETF Logo Mail Archive

Re: [Json] JSON Schema Language: extensibility and unspecified properties

Ulysse Carion <ulysse@segment.com> Mon, 19 August 2019 20:46 UTC

Return-Path: <ulysse@segment.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 0B1C612016E for <json@ietfa.amsl.com>; Mon, 19 Aug 2019 13:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=segment.com
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 5OomRLS2b9u3 for <json@ietfa.amsl.com>; Mon, 19 Aug 2019 13:46:52 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ACA1120048 for <json@ietf.org>; Mon, 19 Aug 2019 13:46:52 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id s21so7370824ioa.1 for <json@ietf.org>; Mon, 19 Aug 2019 13:46:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=segment.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xJy4xSL/Si8Z8cXKLlR+Aiyy8air1cX8eZJKRbY6dqw=; b=NDfPoImihshKCBb3g1+v0CbG/mKf3t4Om6zgs9ZjFM+QavJUMumUw7LoCSJBXsFGBl GnvT7rdKtLHhljSf62wWpniqY+lV+2mBkfIEKogqE5SlD+DPc91fp464QqYz0xBTzCsW Sn8KKvUFHiLlFCmIsiTty1GHaW/G+WFDLs7F0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=xJy4xSL/Si8Z8cXKLlR+Aiyy8air1cX8eZJKRbY6dqw=; b=QUhvAZjzV/fNRu85yDc21Zg5LcmZEUYxIYNKBv86Ba0fcKdahuNZRuq4P5FccDYRLA CCuKQOEEOdfw5l8b6SfmZyDqJq8xusMs1qcs453nTvTJWbGJRnHZcPAU0vBzkjbnuBFY F8X8DeTzazo93DQpVaHdO+ooKa78zbm46xFohw9ODJCT1U0TvrWr3AoK6yNVVVWO13cf Ki4XNW1tPipAFy7aWNHbMGwoNpXc1CahDpbItq4j2ETlEAdc7NJ9T2J4Ihu9bTI0Fo2/ cXxCwsCb1RmyYjwAN57OUrOv3lLNs3WeULNmEm9stLTupPL9JYLKX28o7S7YpKdhxZ5d CZfQ==
X-Gm-Message-State: APjAAAVOx6LYgvKIZmbFc0PTeb0iRONIOv0F3UyJ7NynV1NOUX1dL/vp HAEtfbJqevN2hrLW6UAyaIE5io9o4gtoJ/ft97UhGQ==
X-Google-Smtp-Source: APXvYqxgaGAY4Nv2CT+cm54eF3u6jlPZg7e5V4avgfZH9waiiOzQTwWYe2DrnRUWEWHPQejcv7r16jigkMce/cQsDPE=
X-Received: by 2002:a02:a518:: with SMTP id e24mr20573137jam.44.1566247611240; Mon, 19 Aug 2019 13:46:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAJK=1RhXp85cz-pOAQPw2JM=CYHgGSygj4Hw0spht56jbzQE2g@mail.gmail.com> <53094378-B559-49E1-B42B-54FBA8BC35AA@tzi.org> <CAJK=1Rj6Q3CvpF9aYML=47SF_XP49=O2hLhcBo8gZCb73C0RAw@mail.gmail.com> <FDB93E41-9D7D-4BF2-8D01-F4D075774848@tzi.org> <CAJK=1RiE_+nHkeB77DericN498w1v9mf2hsBgnQtgsZTVM9N9A@mail.gmail.com> <118F844A-453D-497D-8107-CF2BD05AC313@tzi.org> <CAJK=1Rgqek+rh+dj2xNWD7WKS48oQoHiqhj5dDT2D3dD7OZs1Q@mail.gmail.com> <CALH+fvpwM1hRByXv1y0UwUYPwKcb2JZT4v5qqZVeySFvEo-Z7A@mail.gmail.com>
In-Reply-To: <CALH+fvpwM1hRByXv1y0UwUYPwKcb2JZT4v5qqZVeySFvEo-Z7A@mail.gmail.com>
From: Ulysse Carion <ulysse@segment.com>
Date: Mon, 19 Aug 2019 13:46:40 -0700
Message-ID: <CAJK=1RjJUzrpL+=t+5sXAnkYBDKpNazZCViY=PZt7qFFcN2t3g@mail.gmail.com>
To: Richard Gibson <richard.gibson@gmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, JSON WG <json@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/neTDW9cq-Hnxd30jgoay1Vm1PWQ>
Subject: Re: [Json] JSON Schema Language: extensibility and unspecified properties
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 19 Aug 2019 20:46:56 -0000

> But is the portability argument not sufficient for including such a constraint, as it was for I-JSON?

What constraint are you referring to here?
On Sun, Aug 18, 2019 at 6:32 PM Richard Gibson <richard.gibson@gmail.com> wrote:
>
> On Sat, Aug 17, 2019 at 9:35 PM Ulysse Carion <ulysse@segment.com> wrote:
>>
>> no mainstream language I know of has support for integers strictly up to 2^53
>
>
> From a certain point of view, nearly all mainstream languages do so, because that is the maximum value in the range of contiguous IEEE 754 binary64 integers and thus the upper bound on portable integers (which is why RFC 7493 section 2.2 limits I-JSON numbers to being strictly less than it). But you're right that languages have no int53-specific type, because those with specific integer types have at least the larger range of int64 and those without them have the larger reduced-precision range of binary64. But is the portability argument not sufficient for including such a constraint, as it was for I-JSON?

v2.23.0 | Report a Bug | By Email