[rpp] Fwd: [art] JSON Schema work

Pawel Kowalik <kowalik@denic.de> Fri, 27 February 2026 18:31 UTC

Return-Path: <kowalik@denic.de>
X-Original-To: rpp@mail2.ietf.org
Delivered-To: rpp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 29361BFD5FD2 for <rpp@mail2.ietf.org>; Fri, 27 Feb 2026 10:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=denic.de
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 eorMVP88PhHt for <rpp@mail2.ietf.org>; Fri, 27 Feb 2026 10:31:01 -0800 (PST)
Received: from mout-b-206.mailbox.org (mout-b-206.mailbox.org [IPv6:2001:67c:2050:102:465::206]) (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 83958BFD5FC4 for <rpp@ietf.org>; Fri, 27 Feb 2026 10:31:01 -0800 (PST)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-206.mailbox.org (Postfix) with ESMTPS id 4fMxj75pQwz9xQ4 for <rpp@ietf.org>; Fri, 27 Feb 2026 19:30:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1772217051; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rvJoBIpWFa0ucuDs/Z4u4FEdFd5PX6G7kUYs7q5w53o=; b=oy36DQyLKzy8l0A3cf/DtY+B5Mk1cK4TtyRazsrvFzDSY0yCSWQmvOTjRlFYDzQWjx3aiw R/6q+nvH6QeYAhglC1hnegJRDT0GIOBe276SRz4NzmBDZ0/E2rhnKVWTouztiscoPN+JK+ 1EEv5QNC0Km+DifI+XoiykieRXv4lg5pkRu94q5VNOMkBzdbvpCBpWRt/BnOCYe4e+pe4Z McN2KjpJGnFu79ylYVNq86TxHyv5YuPIcj3wdvEX2lCqUx8LxK3ltqFJSdAJVFd4OM8poG s0FtU5TMbgCTpurq1S6caBU5mZpvNM0O4x3kUgM0fujuivOgxdaLDet3ljdNFg==
Message-ID: <97813b66-9cd0-4671-99df-76ccfc2b840e@denic.de>
Date: Fri, 27 Feb 2026 19:30:50 +0100
MIME-Version: 1.0
References: <CAEi+uC6CZqkKmtVNFxc5SyLEACmxzxG-3A+6S-YqFj5r6CECBQ@mail.gmail.com>
Content-Language: en-GB, de-DE
To: "rpp@ietf.org" <rpp@ietf.org>
From: Pawel Kowalik <kowalik@denic.de>
In-Reply-To: <CAEi+uC6CZqkKmtVNFxc5SyLEACmxzxG-3A+6S-YqFj5r6CECBQ@mail.gmail.com>
X-Forwarded-Message-Id: <CAEi+uC6CZqkKmtVNFxc5SyLEACmxzxG-3A+6S-YqFj5r6CECBQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms010106060703060501040003"
X-MBO-RS-META: ta1ztuseox9cayhcqeut4mojabd7x4qm
X-MBO-RS-ID: 45e59dc10b890d590f3
Message-ID-Hash: UHCPD63GRNVHKLFPGCCJP75PIN2HS76N
X-Message-ID-Hash: UHCPD63GRNVHKLFPGCCJP75PIN2HS76N
X-MailFrom: kowalik@denic.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [rpp] Fwd: [art] JSON Schema work
List-Id: "This list discusses a provisioning protocol based on RESTful principles and corresponding data representations using JSON." <rpp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rpp/2fB_mczInQsMNnuB5CzEsaJCFUo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rpp>
List-Help: <mailto:rpp-request@ietf.org?subject=help>
List-Owner: <mailto:rpp-owner@ietf.org>
List-Post: <mailto:rpp@ietf.org>
List-Subscribe: <mailto:rpp-join@ietf.org>
List-Unsubscribe: <mailto:rpp-leave@ietf.org>

This might be relevant to RPP work.


-------- Forwarded Message --------
Subject: 	[art] JSON Schema work
Date: 	Fri, 27 Feb 2026 10:23:04 -0800
From: 	Lisa Dusseault <lisa.dusseault@gmail.com>
To: 	art@ietf.org




Hi ART,

Along with much help from several experts in the JSON Schema community, 
I've prepared a draft that I think would be a good basis for a consensus 
process and open standardization of JSON Schema.

https://datatracker.ietf.org/doc/html/draft-dusseault-json-schema 
<https://datatracker.ietf.org/doc/html/draft-dusseault-json-schema>

I wanted to start from the same functionality the community has been 
using for the last five years (if you've seen the "2020-12" tag in 
schema docs, that's the most recent, common, stable spec).  Moving 
forward from there, anything we add or delete will be visible in 
changelogs and diffs.  But before that, this offers a large-scale 
re-organization of the document (made for some terrible diffs I tell ya) 
, with I feel some progress towards improved readability.
* Terminology section is only terminology, not specification text
* Terms "instance" and "input" have been narrowed and used consistently
* Important sections like the definition of a keyword are never deeper 
than H3 - easier to find in TOC
* Core functionality is described first, then implementation 
requirements especially around loading and following references, then 
extensibility functionality

I welcome feedback on high-level direction: what is included in the spec 
and what is not,  intended status, and WG/charter plans. The highest 
order bit within the spec is probably the knot of related decisions 
around what value goes in "$schema", when that changes, and what that 
means for implementations supporting a given spec version and 
encountering keywords not in that spec version.  The JSON Schema 
community (there's a slack and forums linked off json-schema.org 
<http://json-schema.org>) has a bunch of experience and different plans 
for this so determining consensus will be important.

Lisa