IETF Logo Mail Archive

Re: [Json] JSON Schema Language

Nico Williams <nico@cryptonector.com> Mon, 06 May 2019 21:46 UTC

Return-Path: <nico@cryptonector.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 0988312002F for <json@ietfa.amsl.com>; Mon, 6 May 2019 14:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 dBoTiACzQF2q for <json@ietfa.amsl.com>; Mon, 6 May 2019 14:46:17 -0700 (PDT)
Received: from bonobo.maple.relay.mailchannels.net (bonobo.maple.relay.mailchannels.net [23.83.214.22]) (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 5E322120021 for <json@ietf.org>; Mon, 6 May 2019 14:46:17 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id A42F45E1EBD; Mon, 6 May 2019 21:46:16 +0000 (UTC)
Received: from pdx1-sub0-mail-a100.g.dreamhost.com (100-96-79-6.trex.outbound.svc.cluster.local [100.96.79.6]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id EDDF05E2347; Mon, 6 May 2019 21:46:15 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a100.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.2); Mon, 06 May 2019 21:46:16 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Daffy-Print: 48a6105f6800110f_1557179176379_798604708
X-MC-Loop-Signature: 1557179176379:4189520318
X-MC-Ingress-Time: 1557179176378
Received: from pdx1-sub0-mail-a100.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a100.g.dreamhost.com (Postfix) with ESMTP id DFBE47FEC2; Mon, 6 May 2019 14:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=iksIL1mEJi1yiKUlaKvUkPJ/O9c=; b=GAQr2+2agB5 qmayxoy5xvF9rwnsCF8UdsP6lPBQNIF2RrgMosnayo1jZXm8TYBoGI48KIjgw7Dd bcbgpICZo+jcVVAjFDxMAiPh6W+6W64mn6p3AQbjMEr2KWTs95w/bi+COfpehyEb 6y7/2CS94AznB+zY/9WvSqNmaMC0dlQg=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a100.g.dreamhost.com (Postfix) with ESMTPSA id E35317FEBE; Mon, 6 May 2019 14:46:10 -0700 (PDT)
Date: Mon, 06 May 2019 16:46:08 -0500
X-DH-BACKEND: pdx1-sub0-mail-a100
From: Nico Williams <nico@cryptonector.com>
To: Austin Wright <aaa@bzfx.net>
Cc: Carsten Bormann <cabo@tzi.org>, json@ietf.org
Message-ID: <20190506214607.GN21049@localhost>
References: <35E2623E-753D-4918-8AF4-BF0BC5DE4868@bzfx.net> <6260354b-aca2-e001-7145-148b32658416@gmail.com> <9D90C1F1-6747-4373-93B0-8D51C5B25F1C@bzfx.net> <751DAC92-D70C-4C5E-9C61-954D6E300A1F@tzi.org> <20190506192453.GK21049@localhost> <753A412B-299F-400F-9D19-A9688068D842@bzfx.net> <20190506211509.GL21049@localhost> <32F23E7E-F3AA-4244-AAEC-4582AE7919B9@bzfx.net> <20190506213224.GM21049@localhost> <957CDE65-2987-41A9-B5EB-D54D978B433A@bzfx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <957CDE65-2987-41A9-B5EB-D54D978B433A@bzfx.net>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduuddrjeelgddtfecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggugfgjfgesthekredttderjeenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucfkphepvdegrddvkedruddtkedrudekfeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhenucevlhhushhtvghrufhiiigvpedt
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/lvH6DW5YDYLNzXeFEujiKuUN0Oo>
Subject: Re: [Json] JSON Schema Language
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, 06 May 2019 21:46:19 -0000

On Mon, May 06, 2019 at 02:40:08PM -0700, Austin Wright wrote:
> >> I never suggested this. While JSON doesn’t specify what an “integer”
> >> is (i.e. we could define it to be any subset of number that we want),
> >> JSON Schema tries to be liberal and specifies that excessive precision
> >> still qualifies as an integer. (I’m the one who added that language.)
> > 
> > Then accept 10.0 as an integer.
> 
> The only JSON parsers/JSON Schema validators I maintain are in
> ECMAScript, and both validate `10.0` as an integer. [1] [2]
> 
> If you’re talking about the Newtonsoft JSON parser, or anything else,
> you should ask them directly. By all means, feel free to copy me on
> that email or GitHub issue.

Oy, I think I confused who wanted 10.0 not to parse as an integer.
Sorry about that.

v2.23.0 | Report a Bug | By Email