Re: [Json] Last call: JSON charter

Ray Polk <ray.polk@oracle.com> Fri, 29 March 2013 19:41 UTC

Return-Path: <ray.polk@oracle.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 60DA821F8EAB for <json@ietfa.amsl.com>; Fri, 29 Mar 2013 12:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBC7OhTBPD52 for <json@ietfa.amsl.com>; Fri, 29 Mar 2013 12:41:49 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 4036A21F8EA9 for <json@ietf.org>; Fri, 29 Mar 2013 12:41:49 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r2TJflA5000419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 29 Mar 2013 19:41:48 GMT
Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r2TJflEG014957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Mar 2013 19:41:47 GMT
Received: from abhmt103.oracle.com (abhmt103.oracle.com [141.146.116.55]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r2TJfknY028275; Fri, 29 Mar 2013 14:41:47 -0500
MIME-Version: 1.0
Message-ID: <4fcdab52-196d-4ff0-94d3-f6a221e9013f@default>
Date: Fri, 29 Mar 2013 12:41:46 -0700
From: Ray Polk <ray.polk@oracle.com>
To: paul.hoffman@vpnc.org
X-Mailer: Zimbra on Oracle Beehive
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: json@ietf.org
Subject: Re: [Json] Last call: JSON charter
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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, 29 Mar 2013 19:41:50 -0000

Was it suggested (perhaps by Paul?) in Orlando that we consider reorganizing the RFC into three parts?  Then also perhaps replacing one of those parts with a reference to a corresponding section of the ECMAScript spec?  (sorry, I can't find the minutes from the BoF.)

Issues with ECMA dependencies notwithstanding, I liked the idea not repeating ourselves.  Would such an addition be too much of a distraction/detraction from the primary objectives?

-Ray
 
----- Original Message -----
From: paul.hoffman@vpnc.org
To: json@ietf.org
Sent: Friday, March 29, 2013 12:03:58 PM GMT -07:00 US/Canada Mountain
Subject: Re: [Json] Last call: JSON charter

On Mar 29, 2013, at 10:39 AM, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:

> Please review and send your final comments on the proposed charter for a
> potential JSON working group:
> 
> http://trac.tools.ietf.org/wg/appsawg/trac/wiki/JSON
> 
> 
> If you have been participating on the list, please chime in on this thread
> even if you have already said you agree with that text.

The proposed text as it stands today seems fine to me.

(To reiterate what I said to Larry's proposal: I would likely object to adding wording about other SDOs to this charter.)

--Paul Hoffman

_______________________________________________
json mailing list
json@ietf.org
https://www.ietf.org/mailman/listinfo/json