IETF Logo Mail Archive

Re: [Json] JSON Schema

Henry Andrews <henry@cloudflare.com> Sun, 21 January 2018 22:11 UTC

Return-Path: <henry@cloudflare.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 4A9721243F3 for <json@ietfa.amsl.com>; Sun, 21 Jan 2018 14:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 D1mI3r194H_0 for <json@ietfa.amsl.com>; Sun, 21 Jan 2018 14:11:33 -0800 (PST)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 132C01200F1 for <json@ietf.org>; Sun, 21 Jan 2018 14:11:33 -0800 (PST)
Received: by mail-wr0-x233.google.com with SMTP id 16so6618947wry.12 for <json@ietf.org>; Sun, 21 Jan 2018 14:11:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v+Zvf6i6Fbne6xv6+F+F6claovgpxEFrRMFzWuNRFeQ=; b=PiT8lSjWHwyMNRVNWuDNxo7Q3XmJ5W+nybC0g0AbxCoTtdAVCh1vTrVEFvRnk9xc9l ss4p9tOcvuxGUMDe5mOFxKtsR0MiNPtudjhv1SyZPUFaqsH8MIyG1eh22expdZbINqOh vbVCfs2YkYYHhZByyfjwgEcHzKS+ZxCQhOSQ8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v+Zvf6i6Fbne6xv6+F+F6claovgpxEFrRMFzWuNRFeQ=; b=sFU1hhf1p3cPs3mwbkeLkpH3z2SbRhKkof7zVjahonxDINm6jP82N9kLi0mp99Mvjd Kqp8o4PL//e0SR9Hqjji384ACu54Yq/1cBxloVTP5JXfTIIhVkAZXC2RCAo8XZCqkBlT RDCpCjI1mz8PJf6PlsQNWWj9jX8LVpYIKkC+qtxrMFNtvQz6+Eg872TdL/XDspKMbfST ta7ffxLtitphsPWrV/IZkGho5PVOL3JlV65VxZd3QYVm9PyIJWj7/YnkAsT93+JSxose j23nxWuEpvAFE+/vlmt/88uyGCD3sWhD2C55nmb/FmwhWTFq4m4Ontym2M8ipRDS/7aK +BOw==
X-Gm-Message-State: AKwxytcztPt2qfwfa1Cg8s6oppwSX3GvyAQbWcjS8n98O0bmjNSczNhg zMS1NjsMV15TY8QtMi7bShN/lZuT96dw3VS0XywmFK1rosI=
X-Google-Smtp-Source: AH8x225Uy72dMV0pN20Ja3ymnEH2WsPVdFURSHyh1GoWdTYr1oUN+Rmc+qr1SXuEGjKL1Jjy56+Pu63TOuxxz9XKhCs=
X-Received: by 10.223.133.150 with SMTP id 22mr2242201wrt.176.1516572691555; Sun, 21 Jan 2018 14:11:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.124.4 with HTTP; Sun, 21 Jan 2018 14:11:11 -0800 (PST)
In-Reply-To: <1ECAA6AB-6A96-4E45-AB5C-22F53673FBE1@vpnc.org>
References: <CANp5f1OzPukQ9T69kDaVVTXs0DYdXzY+n=AN6iVRgKKHR4S9CA@mail.gmail.com> <1ECAA6AB-6A96-4E45-AB5C-22F53673FBE1@vpnc.org>
From: Henry Andrews <henry@cloudflare.com>
Date: Sun, 21 Jan 2018 14:11:11 -0800
Message-ID: <CANp5f1MmExKf1JGwTFPZcnVOSRVMYFTwsxPDHXgs9hERXsUu1g@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: json@ietf.org
Content-Type: multipart/alternative; boundary="001a114918d08e7c39056350988f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/KMIY3LNJzsgIk4GEzpnAt9ASN9A>
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: Sun, 21 Jan 2018 22:11:35 -0000

The full set of current documents is on the web page:

http://json-schema.org/specification.html

The first set of links (in the table) go to locally hosted renderings of
each document.
Beneath that, there are links to the IETF-hosted documents.

If you want to see why the numbering is so incredibly confusing, there's a
"Specification LInks" page linked under "Older Drafts"

-henry


On Sat, Jan 20, 2018 at 2:59 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> 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
>



-- 

   -

   *Henry Andrews*  |  Systems Engineer
   henry@cloudflare.com
   <https://www.cloudflare.com/>

   1 888 99 FLARE  |  www.cloudflare.com
   -

v2.23.0 | Report a Bug | By Email