IETF Logo Mail Archive

Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter

Bjoern Hoehrmann <derhoermi@gmx.net> Sat, 15 March 2014 17:01 UTC

Return-Path: <derhoermi@gmx.net>
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 7B9401A00F9 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 10:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, 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 ex3vHjzpI3UV for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 10:01:30 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0CE1A0156 for <json@ietf.org>; Sat, 15 Mar 2014 10:01:28 -0700 (PDT)
Received: from netb ([89.204.139.147]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Mdrph-1WmKcY0BLR-00PccU; Sat, 15 Mar 2014 18:01:17 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John Cowan <cowan@mercury.ccil.org>
Date: Sat, 15 Mar 2014 18:01:16 +0100
Message-ID: <2j19i95f0hkm2aef74l3vaqp3qo6epbua8@hive.bjoern.hoehrmann.de>
References: <53238F21.2030508@cisco.com> <nll8i999lis5u0f719iv6bgte71d8uus52@hive.bjoern.hoehrmann.de> <20140315143553.GC30147@mercury.ccil.org> <72u8i9dj6ih7o95cibq44o8kuq8k2dm40l@hive.bjoern.hoehrmann.de> <CAHBU6it+GfM7RR5q3Rr+Oj5PU4UnK7yW1LPsrXf6FxxoWDNfFQ@mail.gmail.com> <20140315163758.GC24343@mercury.ccil.org>
In-Reply-To: <20140315163758.GC24343@mercury.ccil.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:9K2iwevM5fI25Pa/xhEl7uYUEeZJvg/FYcUunXPtXmgd9BnQnCi gaq9hWWS23ITB72hV+Ddc6EW9fifYmwczhlawgb5fmAG988cdDcx7+XVKvG7DTHkoqkTg41 Gm8R/Y3trJLM4ue28UhdujORmSOHNbpGa9FlmbvvAfqqH+Q1FQG2uhgs3xkZLewknHlw2ku k9D9axiyQ1/yWamKCSHQg==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/CpVmKsAm1qr28-OFXJHeFKBg2nc
Cc: Matt Miller <mamille2@cisco.com>, Tim Bray <tbray@textuality.com>, json@ietf.org
Subject: Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item 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: Sat, 15 Mar 2014 17:01:32 -0000

* John Cowan wrote:
>Tim Bray scripsit:
>
>> > For human-readable documentation purposes it is entirely sufficient to
>> > say "follows RFC XXXX conventions" and
>> 
>> What is XXXX?
>
>The as yet unassigned number for the I-JSON RFC.  Bjoern is IIUC arguing
>against a new MIME type specific to I-JSON.

Yes, and also against inline identifiers and the name "I-JSON" (or any
other name) and anything else that makes avoiding the things the JSON
RFC says are an interoperability problem appear a format on its own.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

v2.29.0 | Report a Bug | By Email | System Status