Re: [Json] Kicking Off JSONbis

"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Thu, 01 October 2015 01:27 UTC

Return-Path: <pfpschneider@gmail.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 5E7E61ACE25 for <json@ietfa.amsl.com>; Wed, 30 Sep 2015 18:27:52 -0700 (PDT)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 h1xMbjNalLMF for <json@ietfa.amsl.com>; Wed, 30 Sep 2015 18:27:51 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 CB4CE1ACE24 for <json@ietf.org>; Wed, 30 Sep 2015 18:27:50 -0700 (PDT)
Received: by igxx6 with SMTP id x6so4343891igx.1 for <json@ietf.org>; Wed, 30 Sep 2015 18:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=Zjb5ajZJXBEO/XZYLDdslwz7q7Wz8a9IXBtvmwn26L4=; b=qurrzXjoKziLtwBHcxwf+BA+1ymIoKmuDXw2hvVqVHBxKL5rX/sJOXKWZzy611jwBt +BrpO4weQNP0PH5zDD3+o8O5ch1byp1brlkqBa3KQIgQyTdxYN+Vn2TdV+Br3T4pS5Bq TDQi1jJ5YnnbsvUdLFaMcPtAvpiYM4oBI8hArK+tZ6s/4aN7rJEoiHCCukDei5oE6y/y 3UhYFRzGvIW8o/a5wvgy9ujqpJqEX2VN8gnjEU7k7Q6M73vhMcD4ihVIW6e2bYms+H/i Tpr0PMz1gQ+yieqsBcVyr3wNpO/oBqc5zmwTLtoQLV7QXe6G110iB5QobqrU8HyeqWnD I8kA==
X-Received: by 10.50.79.167 with SMTP id k7mr394343igx.67.1443662870163; Wed, 30 Sep 2015 18:27:50 -0700 (PDT)
Received: from idefix.nuance.com ([184.151.36.114]) by smtp.gmail.com with ESMTPSA id e19sm222198igo.14.2015.09.30.18.27.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Sep 2015 18:27:49 -0700 (PDT)
To: "Matt Miller (mamille2)" <mamille2@cisco.com>, "json@ietf.org" <json@ietf.org>
References: <DB74C466-D542-42D6-95B0-690A564435A9@cisco.com>
From: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
X-Enigmail-Draft-Status: N0000
Message-ID: <560C8C12.2010805@gmail.com>
Date: Wed, 30 Sep 2015 18:27:46 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <DB74C466-D542-42D6-95B0-690A564435A9@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/z8p1MrPG7TOps8tqQoOvXSsClW8>
Subject: Re: [Json] Kicking Off JSONbis
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: <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: Thu, 01 Oct 2015 01:27:52 -0000

On 09/29/2015 02:53 PM, Matt Miller (mamille2) wrote:
> Hello all,
> 
> Welcome to the JSONbis working group!
> 
> The WG charter is at < https://datatracker.ietf.org/wg/jsonbis/charter/
> >.
> 
> In a nutshell, the goal of this effort is to produce a bis to 7159 that:
> 
> * promotes JSON to IETF Internet Standard * references ECMA-404 and is a
> reference for ECMA-404
> 
> Tim Bray has agreed to edit 7159bis.
> 
> As a start, I propose we start with rfc7159 and:
> 
> 1) Apply verified errata from <
> https://www.rfc-editor.org/errata_search.php?rfc=7159 > 2) Change the
> reference to ECMA-404 from informative to normative
> 
> 
> -  JSONbis Chair

I must admit that I am puzzled as to how ECMA-404 can be a normative
reference for any document that is a minor change from rfc7159.  What in
ECMA-404 is needed to understand or implement what is in rfc7159?

As has been stated, rfc7159 already references ECMA-404.  A conservative way
to make a closer connection from rfc7159 to ECMA-404 would be to state that
ECMA-404 has an alternative description of JSON that is extremely close to
the definition in rfc7159.

Peter F. Patel-Schneider
Nuance Communications