IETF Logo Mail Archive

Re: [Json] Schemas & so on

Peter Cordell <petejson@codalogic.com> Tue, 03 May 2016 15:33 UTC

Return-Path: <petejson@codalogic.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 CA7FA12D529 for <json@ietfa.amsl.com>; Tue, 3 May 2016 08:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 ctPeKR64yzzG for <json@ietfa.amsl.com>; Tue, 3 May 2016 08:33:02 -0700 (PDT)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37D5712D0EC for <json@ietf.org>; Tue, 3 May 2016 08:33:02 -0700 (PDT)
Received: (qmail 28159 invoked from network); 3 May 2016 16:28:22 +0100
Received: from host31-54-178-133.range31-54.btcentralplus.com (HELO ?192.168.1.72?) (31.54.178.133) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 3 May 2016 16:28:22 +0100
To: John Cowan <cowan@mercury.ccil.org>
References: <CAHBU6itCV9MXmALdKtE9-vjUPG6-6ZqdqzrmZkcEzSUysi3S-w@mail.gmail.com> <AC93811D-A16A-4527-B2EB-C6A9FC6D4F17@mnot.net> <4bb21809-bb40-7a3e-b7c7-f37da0976ea2@dret.net> <20160503131248.GA22066@mercury.ccil.org> <60c96d28-70a5-f3a3-30b3-b6f7232b60ab@codalogic.com> <20160503150844.GI29513@mercury.ccil.org>
From: Peter Cordell <petejson@codalogic.com>
Message-ID: <4273095f-0590-07df-bb22-fe09f9c4157d@codalogic.com>
Date: Tue, 03 May 2016 16:32:57 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <20160503150844.GI29513@mercury.ccil.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/9M5rX38rRJ_dkiRSXmbjKgzr0rs>
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Schemas & so on
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 03 May 2016 15:33:04 -0000

On 03/05/2016 16:08, John Cowan wrote:
> Peter Cordell scripsit:
>
> I have a lot of specific comments on JCR.  What's the best forum for them?
>

I'd be very interested to get your feedback.  Now would be a good time 
as we've been quite fluid up until now, but are starting to feel things 
are firming up.

For the time being discuss@json-content-rules.org is the best option. 
It's not a mailing as such but will fan out to Andy and I.

Longer term, I believe that the IETF can set up (or used to be able to 
setup) a mailing list for topics even if they are not associated with a 
working group.  If that's still an option, and there's enough interest, 
that might be something worth pursuing.

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com
---------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email