IETF Logo Mail Archive

Re: [Json] JSON Schema

"Paul Hoffman" <paul.hoffman@vpnc.org> Sat, 20 January 2018 22:59 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 712EC126DC2 for <json@ietfa.amsl.com>; Sat, 20 Jan 2018 14:59:22 -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 Qx9IhdzHjaZM for <json@ietfa.amsl.com>; Sat, 20 Jan 2018 14:59:21 -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 35A7F1201F2 for <json@ietf.org>; Sat, 20 Jan 2018 14:59:21 -0800 (PST)
Received: from [10.32.60.60] (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 w0KMx49v032239 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 20 Jan 2018 15:59:05 -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 [10.32.60.60]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Henry Andrews <henry@cloudflare.com>
Cc: json@ietf.org
Date: Sat, 20 Jan 2018 14:59:16 -0800
X-Mailer: MailMate (1.10r5443)
Message-ID: <1ECAA6AB-6A96-4E45-AB5C-22F53673FBE1@vpnc.org>
In-Reply-To: <CANp5f1OzPukQ9T69kDaVVTXs0DYdXzY+n=AN6iVRgKKHR4S9CA@mail.gmail.com>
References: <CANp5f1OzPukQ9T69kDaVVTXs0DYdXzY+n=AN6iVRgKKHR4S9CA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Q_7denXo6sU73RHLdk-Xv2gCLwE>
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: Sat, 20 Jan 2018 22:59:22 -0000

On 20 Jan 2018, at 13:25, Henry Andrews wrote:

> Hi folks,
>   I'm one of the JSON Schema draft editors, and it's been brought to 
> our
> attention that the JSON Schema project may fit within this working 
> group
> (or a successor?  I'm a little confused as to the current status and 
> scope
> of this group).

The WG is closed and thus has no charter. If you want an IETF WG for 
JSON Schema, it would need to be a new WG. The new WG could be chartered 
just to work on JSON Schema, and not every other JSON-y idea that comes 
by.

>   The current draft is draft-07 (although the actual IETF numbering is
> complicated).  So draft-02 was a very long time ago :-)

Could you point to the actual documents you are talking about? I see 
draft-handrews-json-schema-00, which is not at -07,

--Paul Hoffman

v2.23.0 | Report a Bug | By Email