Re: [Json] JSON Schema Language

Anders Rundgren <anders.rundgren.net@gmail.com> Sat, 04 May 2019 04:47 UTC

Return-Path: <anders.rundgren.net@gmail.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 0BF0A1203A4 for <json@ietfa.amsl.com>; Fri, 3 May 2019 21:47:44 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pQxR-07mC5K3 for <json@ietfa.amsl.com>; Fri, 3 May 2019 21:47:41 -0700 (PDT)
Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (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 668A01203A2 for <json@ietf.org>; Fri, 3 May 2019 21:47:41 -0700 (PDT)
Received: by mail-wr1-x442.google.com with SMTP id q10so1525943wrj.10 for <json@ietf.org>; Fri, 03 May 2019 21:47:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=vIqhvWi1znJ9NPg/y2aurhIOZIx0mOZ6JPn8PpONVOE=; b=rUuFJsPZo+WX8/mZi2/OY0wv5ehhMJB7EiT0Y39PIQVYz9D6x4J4sVs2iCLe+a4ABf FnaaqHQi9nLdaOFkS8CcrC1vaSrvWr1s6mnV+duDpbrzcL67v5q9wlKNU0BpvCB64yyK sLPabapcQ2ug/63IpSZci+rsXX3nZQPkA7YycWbdbNPOv/pzQd/5ztNVZhIiavcUtJkc fJitrz/xSjuoppfFDe9UZp4EWIUIMpFnRJ69P1CcebF5jWtuymz1XIVBZk6MOyQWQZdq fD4hEsXUV08L/fo0r+NtYaywYxI9uDstdF4Vq0a3YCPvqs6GU/dIVZuW+ULUNMRVuhJk gXWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vIqhvWi1znJ9NPg/y2aurhIOZIx0mOZ6JPn8PpONVOE=; b=HP6KDnT7UVD47/3vi16YpchlI5DzzxZqo1t4X/E6WTOeoNAFn2Kxu6aNMm9p2pQU7c crhz/VATTjEHTnqJY9P1QUIG0d70P7xNNJ4WK4uvgKIjzkAKQFjvaQWJVUv7CurVqX8q zXTcj+9MttP9nTY1oiXIaP82fF5dfkfoIfKcPQlQkwNCWH/KoasP3W6nPZMeiPy7q0i1 Exi2WXLWRTFoeQvsFXIWm2HlcwnlVXM66+UHxanB9MPhC4zDjgDZoF7nS/mY62BeAbqb F5Tt6shp9Qxy7RJkSSiQeNgg2bV4eoNPgm+5Y4Z2UxZes36Tu4FqV+SPEPfD63NBtOct vFjQ==
X-Gm-Message-State: APjAAAUveg/jKcJmJh57bA7umtYcKc2gJnNDH4u8YWQEEvXYG7+xKJML ij3MInnfOjhE++PKOzXOMTG4K+VcSx4=
X-Google-Smtp-Source: APXvYqwCSObuG7C9Oi3KVStdt0MGyT6U5CkGw8nZOeq44PEVyUn/vMuuXwumEsM2QgxuNwXgYR9fhg==
X-Received: by 2002:a5d:4dc1:: with SMTP id f1mr9819681wru.300.1556945259518; Fri, 03 May 2019 21:47:39 -0700 (PDT)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id l127sm4587045wml.40.2019.05.03.21.47.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 May 2019 21:47:38 -0700 (PDT)
To: Ulysse Carion <ulysse@segment.com>, json@ietf.org
References: <CAJK=1RjV1uv0eOdtFZ8cKn-FfCwCiGP5r2hOz1UamiM6YV4H1A@mail.gmail.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <39682ec8-f993-a44c-d3e2-1638d2c1608f@gmail.com>
Date: Sat, 04 May 2019 06:47:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAJK=1RjV1uv0eOdtFZ8cKn-FfCwCiGP5r2hOz1UamiM6YV4H1A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/m9TePw5Q14JyKLtWkNiSVBrQ2_g>
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: Sat, 04 May 2019 04:47:44 -0000

On 2019-05-04 01:59, Ulysse Carion wrote:
> Hello all,

Hello Ulysse,

I'm a former user of XML Schema.   I was therefore looking for similarities
like data types and facets but didn't find them.

Example: although 10.0 is a valid JSON Number, in system where you expect
an integer, this should be flagged as a syntax error.

thanx,
Anders

> 
> I have recently published an I-D for what I'm calling JSON Schema
> Language, a way to validate JSON data's shape, and generate code
> (i.e., types, classes, docs, etc.) from that shape:
> 
> https://tools.ietf.org/html/draft-json-schema-language-00
> 
> In previous correspondence with this list, Carsten Bormann has noted
> that this WG has hesitated to prematurely adopt any given proposal,
> preferring to let them develop until their distinct applications
> become clear.
> 
> It is my belief that JSON Schema Language does have a clear use-case,
> one which Tim Bray has articulated clearly here:
> 
> https://www.tbray.org/ongoing/When/201x/2018/09/22/JSON-scheming
> 
> I believe JSON Schema Language solves precisely what Tim describes,
> while eschewing his concerns with the json-schema.org project.
> 
> For those inclined toward the concrete, the bottom of this page
> contains a live demo of JSON Schema Language using the TypeScript
> implementation:
> 
> https://json-schema-language.github.io/
> 
> The project's GitHub organization also contains the source for a Rust
> and TypeScript implementation, as well as a full test suite:
> 
> https://github.com/json-schema-language
> 
> With Carsten's note in mind, does there nevertheless exist a path for
> JSON Schema Language, or something like it, to become an RFC? I
> appreciate the desire to avoid premature adoption by this WG. I assume
> this partially stems from caution around throwing the weight of
> json@ietf.org behind any given specification. Perhaps some other path
> to specification exists?
> 
> With kind regards,
> Ulysse Carion
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>