IETF Logo Mail Archive

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

Matt Miller <mamille2@cisco.com> Fri, 14 March 2014 23:22 UTC

Return-Path: <mamille2@cisco.com>
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 7A9421A021C for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 16:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level:
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 3oSTF7_szfgM for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 16:22:30 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 603B21A021B for <json@ietf.org>; Fri, 14 Mar 2014 16:22:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=759; q=dns/txt; s=iport; t=1394839343; x=1396048943; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=c2DQi/9Y3S+B6N7pS9KNRaXvynYaqgxdmMvTQ7a7B18=; b=l1c8xSLMSzkpht9pji1UY2ZoE4YZWuRCphG97CfFNDsQr0M62wBxjicY KM83ranBFRb349kZFuL8uyv//N0xw1LEq44bGXWZcz2JHOkcwubFfPgXp afKN6B6pV26Afq6IacXLvPiodHJzdUV4cjFfQDgmY8c8/KAvjnRyMIUrs U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAKqOI1OtJV2c/2dsb2JhbABZgwaBEsFvgR4WdIJJWz0WGAMCAQIBSw0IAQGHdaI+sX0XkyYBA4kZOI50ki6Bb4Fdggw
X-IronPort-AV: E=Sophos;i="4.97,657,1389744000"; d="scan'208";a="27646708"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-4.cisco.com with ESMTP; 14 Mar 2014 23:22:23 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2ENMNTE003401 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Fri, 14 Mar 2014 23:22:23 GMT
Received: from MAMILLE2-M-T03K.local (64.101.72.33) by xhc-rcd-x05.cisco.com (173.37.183.79) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 14 Mar 2014 18:22:23 -0500
Message-ID: <53238F2E.5010105@cisco.com>
Date: Fri, 14 Mar 2014 17:22:22 -0600
From: Matt Miller <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: IETF JSON WG <json@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [64.101.72.33]
Archived-At: http://mailarchive.ietf.org/arch/msg/json/VuO9xbuj5MqF7ndxbQ3KTqK4fss
Subject: [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
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: Fri, 14 Mar 2014 23:22:37 -0000

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.


--Paul Hoffman and Matt Miller

v2.23.0 | Report a Bug | By Email