[Json] Re: A fork in the road [was: Re: Please comment on draft-ietf-jsonschema-json-schema-01]

Carsten Bormann <cabo@tzi.org> Sat, 27 June 2026 16:56 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@mail2.ietf.org
Delivered-To: json@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 9EBAE108CDB01 for <json@mail2.ietf.org>; Sat, 27 Jun 2026 09:56:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782579410; bh=gWwrfJn6/QLgXcTaevhnnwQzispZDWv0COOBOKP1YMU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=PhTtcwXBX8WFCnFVVDUKvlFNh95jQvi9L6z2X+q0bihaX6nVFRCBJLpxEyr+nBVCb 8C6Ax47nnQ0tXDhbqQblKJ2nb/RmVDafiB5kCkOTisaRKCN+MX4A5sm2fM0Gi+tAKl ZdwaGCfYJm8aHMULT/XBTCMOT+oqgMpwa0AFsj1Q=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.389
X-Spam-Level:
X-Spam-Status: No, score=-4.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tzi.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YbjV5uKRUn0Z for <json@mail2.ietf.org>; Sat, 27 Jun 2026 09:56:49 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8E613108CDAA7 for <json@ietf.org>; Sat, 27 Jun 2026 09:56:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1782579400; bh=gWwrfJn6/QLgXcTaevhnnwQzispZDWv0COOBOKP1YMU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=aRhJXBDDdLEQSx2b474aNFuiXMCtOo1NneHS/s6OkS0RrnbzxX31pm0h0ZjpwKPRV Eaqhp+59a+zuPUaHud3U2p1ygjcX9xa7EOQTXO8b96rL4r6R6FVRvfDjJiV9KiVMx6 yGOcUqq/tFq0Ptitz0hzVmV3JAoFapxtMn7AHwFMHAtl93jkGsK3ll/xkWg4azmlxY NZt2RxseNlKQtCSoknOvS/2+/WuBikL/3rsLZ7sM8KBWtUp+oF05g4Bhhbx1dm+Rgw k7OkxDhZbPaoywctvIr2aB8bOE4gXx9t5018YdLINCL1z3yYTjy8UpZ+egXljq+xaG 0G+jl7JrAzGHA==
Received: from [192.168.217.132] (p5089ab3c.dip0.t-ipconnect.de [80.137.171.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: cabo) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4gndx43LxQzDCbL; Sat, 27 Jun 2026 18:56:40 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAGC3UE=3oDtbZtcbUx+zsy53sLkmRse2-mjXXrF_0Y010wbGJA@mail.gmail.com>
Date: Sat, 27 Jun 2026 18:56:39 +0200
X-Mao-Original-Outgoing-Id: 804272199.798615-11fdb71b3f92ec4e12fc305e883eab54
Content-Transfer-Encoding: quoted-printable
Message-Id: <03E24523-81C2-462A-AC47-8AD1AEA779F7@tzi.org>
References: <CAE5tNmrOfv73=NSvk4ss-WYf7ZNPts7qFvt3irEb0f1x2tnsNw@mail.gmail.com> <FF7D01A5-7258-45CF-8B8C-07C946A67618@tzi.org> <CAE5tNmrnq4HcO2gYOPZRNJDjGSAOckbmYH-DHgEZM5Vta_+zMw@mail.gmail.com> <CAE5tNmqTnvWgPHVfq5PoNAY0_taU+dSZEX_NKU+x3_KALc9-VQ@mail.gmail.com> <CAGC3UE==08xtwVrbAi6Bk=-_6X8+FmoAifg3kCsGuf-rg6YE=Q@mail.gmail.com> <CAGC3UE=3oDtbZtcbUx+zsy53sLkmRse2-mjXXrF_0Y010wbGJA@mail.gmail.com>
To: John Carlson <yottzumm@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
X-FromAuthMilter: ok
Message-ID-Hash: WLNUW7ZHKLTJHA3FTNALBMROY6IDEKNR
X-Message-ID-Hash: WLNUW7ZHKLTJHA3FTNALBMROY6IDEKNR
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-json.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: David Kemp <dk190a@gmail.com>, "json@ietf.org" <json@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Json] Re: A fork in the road [was: Re: Please comment on draft-ietf-jsonschema-json-schema-01]
List-Id: "JavaScript Object Notation (JSON) WG mailing list" <json.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/e82hpF4230nHtlB4aZYPg774IlI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Owner: <mailto:json-owner@ietf.org>
List-Post: <mailto:json@ietf.org>
List-Subscribe: <mailto:json-join@ietf.org>
List-Unsubscribe: <mailto:json-leave@ietf.org>

On 2026-06-27, at 18:22, John Carlson <yottzumm@gmail.com> wrote:
> 
> As I stated before, are we discussing how to validate many types of schema? JSON schema, XML Schema, YAML schema, RDF schema, etc.  Or are we just validating JSON schema?  That should guide us.  If we just validate JSON schema, then just validating JSON values (minus syntax) should be OK.  

Non sequitur (i.e., that is not the reason, but may be I’m parsing the above wrong), but still true:

> Just validating JSON values (minus syntax) should be OK


(A better reason is that the WG has been chartered that way [1].
"JSON Schema is a JSON language for describing the data structures of other JSON documents.”
Keep in mind:
"The working group may recharter to broaden the group's scope of work only after completing the working group's initial milestone.”
Other groups [e.g., one's local YAML fanclub] can of course do work outside that scope.)

So we agree on this and can stop discussing it?
(Don’t answer if the answer is yes.)

Grüße, Carsten


[1]: https://datatracker.ietf.org/group/jsonschema/about/

You have to assume semantic equivalence of “just validating JSON values (minus syntax)” (in the cited mail) and "describing the data structures of other JSON documents” (in the charter) to agree with the way I personally arrived at this conclusion, but that is not necessary to simply agree with the conclusion.