Re: [Json] Call for WG Consensus on Whether or Not to Adopt Nomenclature Document(s) in the Charter

Stefan Drees <stefan@drees.name> Sat, 15 March 2014 10:57 UTC

Return-Path: <stefan@drees.name>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789B81A00F4 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 03:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 VmHkgCc77DSY for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 03:57:55 -0700 (PDT)
Received: from mout.web.de (mout.web.de [212.227.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5251A00EF for <json@ietf.org>; Sat, 15 Mar 2014 03:57:55 -0700 (PDT)
Received: from newyork.local.box ([80.187.100.89]) by smtp.web.de (mrweb102) with ESMTPSA (Nemesis) id 0M09dQ-1XGtVP2976-00uJro for <json@ietf.org>; Sat, 15 Mar 2014 11:57:47 +0100
Message-ID: <5324322B.1030001@drees.name>
Date: Sat, 15 Mar 2014 11:57:47 +0100
From: Stefan Drees <stefan@drees.name>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: json@ietf.org
References: <53238F2E.5010105@cisco.com>
In-Reply-To: <53238F2E.5010105@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:9zafMcFNRw1saIQp2l4Gsf8gqbjM45gLkL9NwRQIfm+EsagQFCK sVeAwF3E65/7X58nKPbO4JdNYzvgxUh2KN0+1y2mL9v+x6N4MN017Dt4L2ww+HQoHbVbaNH P59PN0AJZZ2kUc3tZZuPp+oj+s1rjGF4GXkJLUYvyCZ3FFTlGXhqW/6w4GRKhzqf3qsqXlg svqXuB1IO3/93MaLTwJFw==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/P9SHXk0QD_iG0XRb1S_ozCO9W_0
Subject: Re: [Json] Call for WG Consensus on Whether or Not to Adopt Nomenclature Document(s) in the Charter
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stefan@drees.name
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: <http://www.ietf.org/mail-archive/web/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, 15 Mar 2014 10:57:56 -0000

On 2014-03-15 00:22 +01:00, Matt Miller wrote:
> The chairs are seeking comment on whether or not the WG wants to adopt
> one or more nomenclature / schema / description documents in the WG
> charter. A few such documents have been brought to the WG, but our
> initial take is that the WG doesn't want to make any of them WG
> documents. They could proceed towards becoming RFCs without any
> interaction from the WG, depending on the wishes of the ADs and/or the
> Independent Stream Editor. Once a nomenclature document is an RFC, other
> RFCs could use it to describe the JSON in those later RFCs.
>
> Please speak up whether or not you believe our charter should be amended
> to include a work item that would adopt one or more nomenclature /
> schema / description documents.

+0 on opening up for inclusion. I think discussion / inspection of 
additional examples (besides RFC 6962) would help guide us to a 
well-informed consensus in that regard.

>
> --Paul Hoffman and Matt Miller

"All the best,
Stefan"