Re: [Json] Status of 7159bis

Stefan Hagen <stefan@dilettant.eu> Mon, 09 January 2017 11:03 UTC

Return-Path: <stefan@dilettant.eu>
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 F3089129BDE for <json@ietfa.amsl.com>; Mon, 9 Jan 2017 03:03:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dilettant.eu
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 oVI72hg92_N3 for <json@ietfa.amsl.com>; Mon, 9 Jan 2017 03:03:13 -0800 (PST)
Received: from mailrelay4.public.one.com (mailrelay4.public.one.com [195.47.247.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AD49128874 for <json@ietf.org>; Mon, 9 Jan 2017 03:03:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dilettant.eu; s=20140924; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=MW8cYcXec2Gr2q+FRgSdqzAGCSUyjLptf8/W/Pv+R/E=; b=qkQ2gJJnlIsGaWqerg3HfrGC3Ir5GjZzqcYSSnLsa7WGc6mVy3W96EoLeD5wxoqgNIK20za18CuEl 5QJfuQhCTIRI8ik8qv33HoNC2lG1Sb+7PI/JPBQj1BaV5UR9YqoOHLoNrNgI0YlHxXEdZ2nZubzpMJ vcfigmpc6pnctBCc=
X-HalOne-Cookie: 185293392e30393c10e28ef7f816d2c6c9580195
X-HalOne-ID: 33c12fab-d65b-11e6-9cd7-b8ca3afa9d73
Received: from [10.228.218.29] (unknown [173.38.220.40]) by smtpfilter1.public.one.com (Halon) with ESMTPSA id 33c12fab-d65b-11e6-9cd7-b8ca3afa9d73; Mon, 09 Jan 2017 11:03:08 +0000 (UTC)
To: Anders Rundgren <anders.rundgren.net@gmail.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
References: <7f687476-a694-0f7d-2e2f-84d23a9ea430@gmx.de> <78D16356-4962-445D-A513-44E432F6C87F@fastmail.fm> <c25e8737-a6fb-031d-75b1-3112e12c0d8e@gmail.com> <6BC16581-9781-4704-B763-401EF9C2142C@fastmail.fm> <ba0f9df3-028b-9d98-2a72-f9dd289e0056@gmail.com>
From: Stefan Hagen <stefan@dilettant.eu>
Message-ID: <b25691fb-e5a2-cf45-747e-b406d72a6dac@dilettant.eu>
Date: Mon, 09 Jan 2017 12:03:07 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <ba0f9df3-028b-9d98-2a72-f9dd289e0056@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/7OLFAI5FCK4Yn_F7-a15Mxg6quU>
Cc: Julian Reschke <julian.reschke@gmx.de>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Status of 7159bis
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: Mon, 09 Jan 2017 11:03:15 -0000

On 09/01/17 11:06, Anders Rundgren wrote:
> On 2017-01-09 10:59, Alexey Melnikov wrote:
>>
>>> On 8 Jan 2017, at 19:48, Peter F. Patel-Schneider
>>> <pfpschneider@gmail.com> wrote:
>>>
>>>> On 01/08/2017 12:44 AM, Alexey Melnikov wrote:
>>>> Hi Julian,
>>>>
>>>>> On 7 Jan 2017, at 15:35, Julian Reschke <julian.reschke@gmx.de> wrote:
>>>>>
>>>>> Hi there,
>>>>>
>>>>> I just noticed that the document went to state "Publication
>>>>> Requested" early December, with no notification of the working
>>>>> group, and (IMHO) some of the few feedback that the document
>>>>> received during WG LC being ignored (such as
>>>>> <https://www.ietf.org/mail-archive/web/json/current/msg03945.html>
>>>>> and
>>>>> <https://www.ietf.org/mail-archive/web/json/current/msg03978.html>).
>>>>>
>>>>> What's going on here?
>>>>
>>>> I moved it to the Publication Requested state in datatracker in
>>>> order to get the document done and get the WG closed. Negotiations
>>>> with the WG chair and document editor are ongoing. WGLC comments
>>>> will be handled (or at least replied to).
>>>>
>>>> Best Regards,
>>>> Alexey
>>>
>>> Progress on this document was waiting for progress on ECMA 404.  I
>>> don't see
>>> that anything has happened with ECMA 404, so this document can't
>>> progress.
>>
>> It is quite the opposite: If the document doesn't progress, ECMA is
>> not going to do anything.
>
> Which highlights the impossibility having two normative standards for
> the same thing.
> Dropping the references to ECMA is the only sensible way forward.

respecting substantial back and forth to create the best possible 
specification is one thing, accepting merely formal shall I stay, or 
shall I go, I really don't know kind of discussions is another.
So I am +0 with Anders here to avoid further erosion of human forces in 
the field - if I may bluntly put it that way in a language foreign to me.

"Stefan"