IETF Logo Mail Archive

Re: [Json] JSON Schema Language

Carsten Bormann <cabo@tzi.org> Mon, 06 May 2019 07:22 UTC

Return-Path: <cabo@tzi.org>
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 34C9A1200D5 for <json@ietfa.amsl.com>; Mon, 6 May 2019 00:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 xChEo99v1ToH for <json@ietfa.amsl.com>; Mon, 6 May 2019 00:22:16 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F080120046 for <json@ietf.org>; Mon, 6 May 2019 00:22:16 -0700 (PDT)
Received: from [192.168.217.106] (p54A6CC75.dip0.t-ipconnect.de [84.166.204.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 44yDhQ1P5bz10DD; Mon, 6 May 2019 09:22:14 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0AF01D27-E1A9-4D3B-8256-56859B998946@bzfx.net>
Date: Mon, 06 May 2019 09:22:13 +0200
Cc: json@ietf.org
X-Mao-Original-Outgoing-Id: 578820131.549468-4cbc2bf8f0f4cacedf613f78469c3532
Content-Transfer-Encoding: quoted-printable
Message-Id: <011D66CC-C13C-45BF-A0D4-00F768252911@tzi.org>
References: <CAJK=1RjV1uv0eOdtFZ8cKn-FfCwCiGP5r2hOz1UamiM6YV4H1A@mail.gmail.com> <39682ec8-f993-a44c-d3e2-1638d2c1608f@gmail.com> <29CAE1CE-D6CB-4796-B2F2-2095BE921385@tzi.org> <AD5ABD9C-F5F2-477D-B862-529C890D5472@bzfx.net> <DA1767B8-22D6-4EA9-8112-4B36B79E9039@tzi.org> <D21B379B-23CC-48B3-BE10-D2777308E2E0@bzfx.net> <D8551AB2-48D4-4B64-85F4-058CCAD3432A@tzi.org> <0AF01D27-E1A9-4D3B-8256-56859B998946@bzfx.net>
To: Austin Wright <aaa@bzfx.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/06OI1aovOcd3xZNq1EEStEUqggQ>
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 07:22:18 -0000

On May 6, 2019, at 08:56, Austin Wright <aaa@bzfx.net> wrote:
> 
> You’re right. I should add, it’s not _supposed_ to be normative: it’s not our intention to modify how JSON works or impose restrictions on encoders. 

Good.  So consider my comment a comment on the specific language that is on that website.

> I don’t think we can do that even if we wanted to.

Well, there are several definitions of “can”.

By creating the expectation that 10.0 will be encoded as 10 in the vicinity of your schema data objects, you “are”, even if you “should not be able to”.  If there is an interoperability problem between an encoder that encodes as 10.0 and a decoder that only can handle 10, the implementer of the latter might point to your website and say “works as intended, because you are not supposed to”.  There is your fork.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email