Re: [Json] JSON Schema

"Paul Hoffman" <paul.hoffman@vpnc.org> Mon, 22 January 2018 03:53 UTC

Return-Path: <paul.hoffman@vpnc.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 1B3F5126CC7 for <json@ietfa.amsl.com>; Sun, 21 Jan 2018 19:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 kXnW5q6-EatU for <json@ietfa.amsl.com>; Sun, 21 Jan 2018 19:53:14 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 60C4612025C for <json@ietf.org>; Sun, 21 Jan 2018 19:53:14 -0800 (PST)
Received: from [169.254.236.117] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w0M3qv50093080 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 21 Jan 2018 20:52:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [169.254.236.117]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Henry Andrews <henry@cloudflare.com>
Cc: JSON WG <json@ietf.org>
Date: Sun, 21 Jan 2018 19:53:10 -0800
X-Mailer: MailMate (1.10r5443)
Message-ID: <4E44E944-B830-40EF-8E33-005BF5172CCA@vpnc.org>
In-Reply-To: <CANp5f1PEaax_8CWo9PDfb+kh3XRsutqyyPySEX2OQetdSzUPAw@mail.gmail.com>
References: <CANp5f1OzPukQ9T69kDaVVTXs0DYdXzY+n=AN6iVRgKKHR4S9CA@mail.gmail.com> <1ECAA6AB-6A96-4E45-AB5C-22F53673FBE1@vpnc.org> <CANp5f1MmExKf1JGwTFPZcnVOSRVMYFTwsxPDHXgs9hERXsUu1g@mail.gmail.com> <CAChr6SyeBCh-FEzk+zdRW9NGz-ZvNXogJ+KEKnoco+U_RwELbg@mail.gmail.com> <CAMm+Lwgt4rHvC8wPHvSigV+fNTURbZKBmEN2aBCvd55DiHBE1A@mail.gmail.com> <CANp5f1PEaax_8CWo9PDfb+kh3XRsutqyyPySEX2OQetdSzUPAw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/HSUXh5FAtToI1YiAbziHt1FyuNI>
Subject: Re: [Json] JSON Schema
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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, 22 Jan 2018 03:53:16 -0000

A few procedural notes to correct some misunderstandings. (Wearing no 
hats, just lots of scars from earlier IETF work on JSON and lots of 
other data formats...)

On 21 Jan 2018, at 18:48, Henry Andrews wrote:

> So... the point of me sending this email was to answer a request made 
> to
> the JSON Schema project that I investigate the working group.  The 
> clear
> answer to that is that this working group is closed, and a new one 
> would
> need to be chartered.

If you want an IETF standard, yes.

> It's not clear to me that we would want to charter
> such a group now, although I would be interested in anyone's input on 
> that.

There appears to be interest in something around schema for JSON; it is 
not clear if there is interest in starting from the specific spec at 
https://github.com/json-schema-org/json-schema-spec. I bet there is some 
interest in that, and some interest in something else. This is quite 
typical of requests for the IETF to adopt work that originated outside 
the IETF, with mixed results in any of of "adopt with the intention of 
making only minor changes", "adopt and make major changes", and "start 
from scratch while getting inspiration from the existing work".

The IETF sucks at this, as do most other SDOs. We're just more public 
about our suckage.

> There are several projects
> underway in the same general space, some with quite a bit of momentum 
> of
> their own.  One of them may be a better choice for an IETF working 
> group,
> I'm not in a position to say one way or the other.

None of us are; that's what consensus is for.

> Filing issues or asking questions on our slack channel will probably 
> work
> better than hi-jacking this mailing list, now that I understand it is 
> no
> longer active. :-)

What you have done is *not* hijacking this mailing list: it's a 
completely appropriate use of it. And the list is active, as you have 
just seen. It's just not an IETF WG any more.

> I would be interested in pursuing the IETF process (heavyweight or 
> not)

It will be the former :-(

> , if
> there is interest from the appropriate segment of the IETF community.

This list is a good proxy for that appropriate segment. Everyone who is 
interested in this topic should feel free to use the mailing list for 
it.

--Paul Hoffman