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

Ulysse Carion <ulysse@segment.com> Mon, 12 August 2019 07:43 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 24A11120E38 for <json@ietfa.amsl.com>; Mon, 12 Aug 2019 00:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 w1NJc9kZpZwa for <json@ietfa.amsl.com>; Mon, 12 Aug 2019 00:42:51 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 4CBB812008D for <json@ietf.org>; Sun, 11 Aug 2019 10:34:02 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id z17so32664955otk.13 for <json@ietf.org>; Sun, 11 Aug 2019 10:34:02 -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=YY7KeW+rla3p4BATYpbDyKYtWVRckIjg81ALj6799RY=; b=mYAjviaqxoBuuwY2H1AZNBKKAGyRE7owAFSvk7ZZ7dlMY3DJeeVVUKdHNH6dkCE0W/ aW0rYURU7NeWibSGUtDB7WjCNfdmFNUMwXEe7NIjXOAxc2+bDmp1XWF9N9fO6Vry393H kFOYy9sEhIf9bl6y4dXsGs+W/gejh1wwdDYVc=
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=YY7KeW+rla3p4BATYpbDyKYtWVRckIjg81ALj6799RY=; b=QqocU/DSFTCTl9osgKUwSVnjlqiYjjQPAIT1YXU5PduPqzrHL2/42DlgRF6CUZG9gj 58j81dhPpzJ3V9RF5/xdntE08mwjgvc9B5lQGP3QPGZe1KhD+X0EiH5gnBPRN5yxRfNl zhCyAtNG65Iy4/I+XWe1nrZZyR8rMct0llEbYZMZv5LxHkf8Y131o9fP07W3xvOsQ4bC aUtAWnoOyuBpRZ2b2/XOKZeeA3wRFU/rydVKOhZxlaL+4H7fMaQ/oE/JpcNil6ftoapU Da3aNnVi1fyIUdidRNHRLHJ+KiOGMWaZS+LbNqZ2ZXtX2RE5zF7a13s9e+vkVNC+2T6l oUDw==
X-Gm-Message-State: APjAAAUHzXKqoEosv4hAHYvk3GkSQMEMk3HYeP5lLczNOq3VFy036CC5 p+m4oTFFR2gVdQLMoELxYwjMWFyTY1GyTl6CPGf9lkA8ALk=
X-Google-Smtp-Source: APXvYqxiQSYs73FiYn//TqfGI1YXajAUdQswf7hj2b2i5WeBHizHpY6T6nSUSN768jWL/IUuum9slAWTl7ZEF+0zZCI=
X-Received: by 2002:a6b:ce19:: with SMTP id p25mr16624668iob.201.1565544841440; Sun, 11 Aug 2019 10:34:01 -0700 (PDT)
MIME-Version: 1.0
References: <CAJK=1RhXp85cz-pOAQPw2JM=CYHgGSygj4Hw0spht56jbzQE2g@mail.gmail.com> <53094378-B559-49E1-B42B-54FBA8BC35AA@tzi.org>
In-Reply-To: <53094378-B559-49E1-B42B-54FBA8BC35AA@tzi.org>
From: Ulysse Carion <ulysse@segment.com>
Date: Sun, 11 Aug 2019 10:33:50 -0700
Message-ID: <CAJK=1Rj6Q3CvpF9aYML=47SF_XP49=O2hLhcBo8gZCb73C0RAw@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: 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/-FC-RsXQhii20_u_764ZSaJQ8Ow>
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, 12 Aug 2019 07:43:52 -0000

> This is a nice demonstration that it was a mistake to remove uint53.

Perhaps. But perhaps instead I should just use {"type": "number"}, and
accept that JSL isn't going to be able to express certain things about
numbers?

Re-reading https://tools.ietf.org/html/rfc7071, it seems it constrains
the timestamps to not have a fractional part at the JSON syntax level.
That's another thing JSL can't deal with. But I'm not sure if in
practice that's such a big deal.

On Fri, Aug 9, 2019 at 11:23 PM Carsten Bormann <cabo@tzi.org> wrote:
>
> Examples are good:
>
>    This schema […] limits “generated” and
>    "expires" to timestamps less than 2^32 seconds after January 1, 1970
>    00:00 UTC.
>
> This is a nice demonstration that it was a mistake to remove uint53.
>
> (Note that on 32-bit systems time_t is an int32.  But you definitely don’t want that restriction; 2038 is coming too close now.  Uint32 is completely arbitrary and wrong in many ways.)
>
> Grüße, Carsten
>